On 30 Mai, Akos Maroy wrote:
Can you please test the CVS version of LAME with the attached patch
(I've no gcc 3.1 at the moment)?
Some more details.
There is a bug in your GCC_version sed script. Instead of:
GCC_version=`${CC} --version | sed -n '1s/^[^ ]* (.*) //;s/ .*$//;1p`
a
I don't have problems with removing the generated files from CVS (I know
how to use auto*). But as long as there's no majority of the people with
write access to the LAME CVS repository which wants to have them removed
they will stay there.
As a cygwin user, for wich packages are often
Alexander Leidinger wrote:
Now I have another problem: the configure script uses
--no-verify for libtool. Therefore I _have_ to use
configure mycpu-blafasel-mysystem to configure it. As a workaround
I've committed a configure script with --no-verify removed. I haven't
found a way to do it
Am Sonntag, 2. Juni 2002 16:34 schrieb Gabriel Bouvigne:
I don't have problems with removing the generated files from CVS (I know
how to use auto*). But as long as there's no majority of the people with
write access to the LAME CVS repository which wants to have them removed
they will
just joined the list. thought I had a problem...when I ran ./configure,
I was worried about the fact that the gtk test failed. I didn't know
what to do, since I had installed gtk, and thus, there couldn't have
really been a problem. In fact, I continued with the installation, and
