Re: Re : [GCC front end] trying to install python fe but fail in make

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

 



On 8 September 2010 15:11, charfi asma <charfiasma@xxxxxxxx> wrote:
> Hello,
>
> back to the galley ;)
>
> I tried to install python front end from the gcc-dev following the steps
> explained in http://gcc.gnu.org/wiki/PythonFrontEnd
> $ git clone git://crules.org/git/gcc-dev.git
> $ cd gcc-dev/
> $ git checkout --track -b python origin/python
> $ cd ../
> $ mkdir gcc-python-build
> $ cd gcc-python-build/
> $ ../gcc-dev/configure --enable-languages=c,c++,python --disable-bootstrap
> $ make
>
> but I get this error while calling make
>
>  flex --outfile=lex.py.c ../../gcc-dev/gcc/python/lexer.l
> gcc -std=gnu99 -I../../gcc-dev/gcc/python -g -O2 -fomit-frame-pointer -gtoggle
> -DIN_GCC -W -Wall -Wwrite-strings -Wcast-qual -Wstrict-prototypes
> -Wmissing-prototypes -Wmissing-format-attribute -pedantic -Wno-long-long
> -Wno-variadic-macros -Wno-overlength-strings -Wold-style-definition -Wc++-compat
> -fno-common -DHAVE_CONFIG_H -I. -I. -I../../gcc-dev/gcc -I../../gcc-dev/gcc/.
> -I../../gcc-dev/gcc/../include -I../../gcc-dev/gcc/../libcpp/include
> -I/export/home/charfi/gcc_python_build/./gmp -I/export/home/charfi/gcc-dev/gmp
> -I/export/home/charfi/gcc_python_build/./mpfr -I/export/home/charfi/gcc-dev/mpfr
> -I/export/home/charfi/gcc-dev/mpc/src  -I../../gcc-dev/gcc/../libdecnumber
> -I../../gcc-dev/gcc/../libdecnumber/bid -I../libdecnumber    \
>     -c -o lexer.o lex.py.c
> cc1: erreur: niveau de sortie de mise au point non reconnu "toggle"
> make[2]: *** [lexer.o] Erreur 1
> make[2]: quittant le répertoire « /export/home/charfi/gcc_python_build/gcc »
> make[1]: *** [all-gcc] Erreur 2
> make[1]: quittant le répertoire « /export/home/charfi/gcc_python_build »
> make: *** [all] Erreur 2
>

Forgive me but my french isn't what it used to be, not quite sure what
the error message is, is it "undecalred variable toggle" or something?

I'll look to see if i can recreate this now, since there may be
another compiler error when it hits pypy.c i was in the middle of
adding some more stuff a while back and just commited with syntax
errors so i could catch a train lol.

--Phil



[Index of Archives]     [Linux C Programming]     [Linux Kernel]     [eCos]     [Fedora Development]     [Fedora Announce]     [Autoconf]     [The DWARVES Debugging Tools]     [Yosemite Campsites]     [Yosemite News]     [Linux GCC]

  Powered by Linux