Melt-building problem

[Wolfgang]

-------- Original-Nachricht --------
> Datum: Tue, 25 May 2010 16:20:14 +0200
> Von: Basile Starynkevitch <basile@starynkevitch.net>
> An: Wolfgang <wolfgang8081@gmx.de>
> CC: gcc@gcc.gnu.org
> Betreff: Re: Melt-building problem

> On Tue, 2010-05-25 at 12:03 +0200, Wolfgang wrote:
> > Hello,
> > 
> > I tried to compile the gcc-melt branch from svn, 
> 
> A big thanks for testing GCC MELT! What svn revision of the MELT branch
> are you testing? Did you configure gcc-melt with --enable-bootstrap?
> 
> Can you reproduce the bug inside a clean build tree? (I mean, removing
> all your build tree, and start again the configure & the build)
yes, it is reproduceable...i cleaned all and tried to build that new....

> 
> > but i get the following error:
> > 
> > ....
> > make warmelt1
> > make[4]: Entering directory `/home/wolfgang/gcc-melt/objects/gcc'
> > date +"/* empty-file-for-melt.c %c */" > empty-file-for-melt.c-tmp
> > /bin/bash ../../melt-branch/gcc/../move-if-change
> empty-file-for-melt.c-tmp empty-file-for-melt.c
> > make -f ../../melt-branch/gcc/melt-module.mk 
> VPATH=../../melt-branch/gcc:. meltmodule \
> > 	      GCCMELT_CFLAGS="-g -O2 -fomit-frame-pointer -g -g -O2
> -fomit-frame-pointer -gtoggle -DIN_GCC -DHAVE_CONFIG_H -I melt-private-build-include
> -I." \
> > 	     
> GCCMELT_MODULE_SOURCE=../../melt-branch/gcc/melt/generated/warmelt-first.0.c GCCMELT_MODULE_BINARY=warmelt-first.0.so
> > make[5]: Entering directory `/home/wolfgang/gcc-melt/objects/gcc'
> > gcc -g -O2 -fomit-frame-pointer -g -g -O2 -fomit-frame-pointer -gtoggle
> -DIN_GCC -DHAVE_CONFIG_H -I melt-private-build-include -I. -fPIC -c -o
> warmelt-first.0.pic.o ../../melt-branch/gcc/melt/generated//warmelt-first.0.c
> > cc1: error: unrecognised debug output level "toggle"
> 
> Which gcc is this one? (What does gcc -v tells you?).
At the moment, i have the gcc 4.4 installed:
wolfgang@Debian:~/gcc-melt/objects$ gcc -v
Using built-in specs.
Target: i486-linux-gnu
Configured with: ../src/configure -v --with-pkgversion='Debian 4.4.4-1' --with-bugurl=file:///usr/share/doc/gcc-4.4/README.Bugs --enable-languages=c,c++,fortran,objc,obj-c++ --prefix=/usr --enable-shared --enable-multiarch --enable-linker-build-id --with-system-zlib --libexecdir=/usr/lib --without-included-gettext --enable-threads=posix --with-gxx-include-dir=/usr/include/c++/4.4 --program-suffix=-4.4 --enable-nls --enable-clocale=gnu --enable-libstdcxx-debug --enable-objc-gc --enable-targets=all --with-arch-32=i486 --with-tune=generic --enable-checking=release --build=i486-linux-gnu --host=i486-linux-gnu --target=i486-linux-gnu
Thread model: posix
gcc version 4.4.4 (Debian 4.4.4-1)

The Melt-Branch was configuired with:
../melt-branch/configure --enable-languages=c,c++ --enable-shared --enable-threads=posix --enable-nls --enable-objc-gc --enable-mpfr --prefix=/usr/lib/test2 --enable-plugin --enable-lto --with-ppl --enable-bootstrap

I now tried to compile it with the new gcc-4.5

Thanks
Wolfgang

> 
> I hoped to have corrected this bug by adding the MELTHERE_CFLAGS in GCC
> MELT's gcc/Makefile.in near line 5076. I am not a guru in autoconf + GNU
> make tricks. Apparently, something is still wrong.
> 
> A dirty workaround might be to replace every -gtoggle occurrence in the
> build tree gcc/Makefile with -g.
> 
> I will try to reproduce that bug!
> 
> Thanks for reporting it.
> 
> 
> BTW, I am surprised that GCC (even a plain 4.4 or 4.5) issues an error
> for an unrecognised debug output level. I would imagine it would in that
> case issue a warning, and try to do what -g does...
> 
> Cheers.
> 
> 
> -- 
> Basile STARYNKEVITCH         http://starynkevitch.net/Basile/
> email: basile<at>starynkevitch<dot>net mobile: +33 6 8501 2359
> 8, rue de la Faiencerie, 92340 Bourg La Reine, France
> *** opinions {are only mines, sont seulement les miennes} ***
> 

-- 
GRATIS für alle GMX-Mitglieder: Die maxdome Movie-FLAT!
Jetzt freischalten unter http://portal.gmx.net/de/go/maxdome01