enigma-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Enigma-devel] BUG: tolua verirrt


From: Tacvek
Subject: Re: [Enigma-devel] BUG: tolua verirrt
Date: Wed, 29 Nov 2006 15:25:41 -0500


----- Original Message ----- From: "Ronald Lamprecht" <address@hidden> To: "martin capitanio" <address@hidden>; "Raoul Bourquin" <address@hidden>; "Erich Schubert" <address@hidden>
Cc: <address@hidden>
Sent: Wednesday, November 29, 2006 2:58 PM
Subject: Re: [Enigma-devel] BUG: tolua verirrt


Hi,

martin capitanio wrote:
I just tried compile the svn trunk. The '-x c++' option is
misapplied here.

Martin Capitanio

svn up
Revision 484

...
make[1]: Leaving directory `/rep/svn/public/enigma-game-trunk/lib-src'
Making all in tools
make[1]: Entering directory `/rep/svn/public/enigma-game-trunk/tools'
gcc -I../lib-src/lua -x c++ -DENABLE_ASSERT -g -DCXXLUA -g -O2 -o tolua tolua-tolua.o tolua-toluabind.o -L../lib-src/lua -
llua -lstdc++ -lxerces-c -lpng -ldl

Just guessing - you use Debian with autoconf 2.60a-4, a test version of autoconf?

Raoul had exactly the same problem. My recommendation was to downgrade to the stable 2.59a-3 autoconf version what seemed to help.

@Raoul did you downgrade automake, too?

The gcc command above is nonsense. The error should be anywhere in autoconf/automake.

Please report the error to the maintainers of the autoconf/automake package.

Ronald, are you sure about that? It looks to me like either automake or autoconf decided to use gcc as the linker. IIRC that is perfectly valid, as gcc is happy to pretend to be a linker, and simply pass the relevant arguments on to the linker. The problem is that it used both $CFLAGS and $LDFLAGS when calling gcc as a linker. The "-x c++" causes gcc to ignore the file extentions, and attempt to compile the .o files as though they were C++ files, before trying to link them.

If there is a bug in atuoconf/automake I would say it is passing $CFLAGS to gcc when invoking gcc as a linker. That said, upsteam may feel that is the correct thing to do. I doubt upstream autoconf and automake maintainers support use of "-x c++" in $CLAGS, for many reasons, not the least of which is that that option is not very portable.




reply via email to

[Prev in Thread] Current Thread [Next in Thread]