>>>>> "Albert" == Albert Chin <[EMAIL PROTECTED]> writes:

Albert> On Thu, May 30, 2002 at 05:29:03PM +0200, Jean-Marc Lasgouttes
Albert> wrote:
>> I am currently trying to build with gcc 2.95.2, but I am stuck with
>> the following:
>> 
>> make[3]: Entering directory
>> `/afs/inria.fr/rocq/home/meval/lasgoutt/src/lyx/oldb/src/mathed'
>> /bin/ksh ../../libtool --mode=compile g++ -DHAVE_CONFIG_H -I.
>> -I../../../1.2.x/src/mathed -I../../src
>> -I../../../1.2.x/src/mathed/../ -I../.. -I../../../1.2.x
>> -I../../../1.2.x/boost -I/afs/rocq/home/meval/common/include
>> -I/usr/local/include -O -fno-rtti -fno-exceptions -W -Wall -c
>> ../../../1.2.x/src/mathed/textpainter.C Waiting for
>> textpainter.o.lock to be removed Waiting for textpainter.o.lock to
>> be removed Waiting for textpainter.o.lock to be removed Waiting for
>> textpainter.o.lock to be removed [...]
>> 
>> Has anybody seen that? What is the culprit?

Albert> The culprit is libtool. Look at the ./configure output. It
Albert> should have attempted to build with -c and -o and failed. We
Albert> should try to fnid out why.

I see 

configure:5648: checking if gcc supports -c -o file.o
configure:5667: g++ -c -O -fno-rtti -fno-exceptions -W -Wall  -I/afs/rocq/home/m
eval/common/include  -I/usr/local/include  conftest.C 1>&5

and no error. However, I see in the libtool script
# Does compiler simultaneously support -c and -o options?
compiler_c_o="no"

Later, I see 
# Must we lock files when doing compilation ?
need_locks="yes"

Changing the later to "no" fixed my problem. I still do not know
however what happens...

JMarc

Reply via email to