Re: [Enigma-devel] BUG: tolua verirrt

[Ronald Lamprecht]

Hi,

Tacvek wrote:
> > > 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
> 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.

The problem should be reported. Especially as there are no obvious 
alternatives to compile "tolua".

As you figured out the above solution with "-x c++" do you know any 
alternative? What about the approach of renaming the sources that you 
tried in the beginning?

Ronald