Hello,
I used git to get the current gcc-dev directory and I tried to install python,
gcalc and sample_fe at the same time.
I configured with and It worked
when I call make bootstrap, I get an error dealing with the GTY (GTY must be
declared before identifier) in the sfe1.h (sample_fe front end)
I changed the sfe1.h and it works, but I get another error :
checking whether ln -s works... yes
checking for i686-pc-linux-gnu-gcc... /export/home/charfi/objdir/./gcc/xgcc
-B/export/home/charfi/objdir/./gcc/ -B/usr/local/i686-pc-linux-gnu/bin/
-B/usr/local/i686-pc-linux-gnu/lib/ -isystem
/usr/local/i686-pc-linux-gnu/include -isystem
/usr/local/i686-pc-linux-gnu/sys-include
checking for suffix of object files... configure: error: in
`/export/home/charfi/objdir/i686-pc-linux-gnu/libgcc':
configure: error: cannot compute suffix of object files: cannot compile
See `config.log' for more details.
make[2]: *** [configure-stage1-target-libgcc] Erreur 1
make[2]: quittant le répertoire « /export/home/charfi/objdir »
make[1]: *** [stage1-bubble] Erreur 2
make[1]: quittant le répertoire « /export/home/charfi/objdir »
make: *** [all] Erreur 2
any idea ?
thank you very much
ASMA
----- Message d'origine ----
De : Philip Herron <redbrain@xxxxxxxxxxx>
À : charfi asma <charfiasma@xxxxxxxx>
Cc : gcc-help@xxxxxxxxxxx
Envoyé le : Jeu 19 août 2010, 19h 39min 16s
Objet : Re: Re : Re : Re : Re : Re : Re : Re : Re : Re : Re : [GCC front end]
trying to install sample_fe but fail in make
On 19 August 2010 14:03, charfi asma <charfiasma@xxxxxxxx> wrote:
> I tried to add gcalc as a front end to gcc 4.4.4 to understand the purpose of
> this fe.
> but when I call make I get those errors
>
> /export/home/charfi/Bureau/gcc-4.4.4/gcc/gcalc/calc1.c:141:104: erreur: la
>macro
> « build_decl » a reçu 4 arguments, mais elle n'en prend que 3
> /export/home/charfi/Bureau/gcc-4.4.4/gcc/gcalc/calc1.c: In function
> ‘calc_parse_file’:
> /export/home/charfi/Bureau/gcc-4.4.4/gcc/gcalc/calc1.c:141: erreur:
>‘build_decl’
> undeclared (first use in this function)
> /export/home/charfi/Bureau/gcc-4.4.4/gcc/gcalc/calc1.c:141: erreur: (Each
> undeclared identifier is reported only once
> /export/home/charfi/Bureau/gcc-4.4.4/gcc/gcalc/calc1.c:141: erreur: for each
> function it appears in.)
> /export/home/charfi/Bureau/gcc-4.4.4/gcc/gcalc/calc1.c:148:96: erreur: la
macro
> « build_decl » a reçu 4 arguments, mais elle n'en prend que 3
> /export/home/charfi/Bureau/gcc-4.4.4/gcc/gcalc/calc1.c:140: attention : unused
> variable ‘main_fn_type’
> /export/home/charfi/Bureau/gcc-4.4.4/gcc/gcalc/calc1.c: In function
> ‘calc_post_options’:
> /export/home/charfi/Bureau/gcc-4.4.4/gcc/gcalc/calc1.c:274: erreur:
> ‘flag_excess_precision_cmdline’ undeclared (first use in this function)
> /export/home/charfi/Bureau/gcc-4.4.4/gcc/gcalc/calc1.c:274: erreur:
> ‘EXCESS_PRECISION_FAST’ undeclared (first use in this function)
> /export/home/charfi/Bureau/gcc-4.4.4/gcc/gcalc/calc1.c: Hors de toute fonction
>:
> /export/home/charfi/Bureau/gcc-4.4.4/gcc/gcalc/calc1.c:294: erreur:
conflicting
> type qualifiers for ‘lang_hooks’
> /export/home/charfi/Bureau/gcc-4.4.4/gcc/langhooks.h:422: note: previous
> declaration of ‘lang_hooks’ was here
> /export/home/charfi/Bureau/gcc-4.4.4/gcc/gcalc/calc1.c:297:28: erreur:
> gt-gcalc-calc1.h : Aucun fichier ou dossier de ce type
> make[3]: *** [gcalc/calc1.o] Erreur 1
> make[3]: quittant le répertoire « /export/home/charfi/Bureau/gcc_make2/gcc »
> make[2]: *** [all-stage2-gcc] Erreur 2
> make[2]: quittant le répertoire « /export/home/charfi/Bureau/gcc_make2 »
> make[1]: *** [stage2-bubble] Erreur 2
> make[1]: quittant le répertoire « /export/home/charfi/Bureau/gcc_make2 »
> make: *** [all] Erreur 2
>
This looks like langhook's function significant errors. Don't expect
langhooks as is to be stable, since i started my front-end I've
noticed 1 or 2 changes in the last 3 months or so. Its highly doubtful
you could get the gcalc front-end andi build to work on GCC 4.4.4,
without looking into langhooks.{h,def} to get the langhook function
signatures right.
As we have said earlier in this thread, try to work with current gcc
sources (svn/git) its much simpler for us to help you, or if your
heart is set on using a tarball use a snapshot gcc-core tarball or
something.
--Phil
