From: charfi asma <charfiasma@yahoo.fr>
To: mail@andihellmund.com
Cc: "Cc :" <gcc-help@gcc.gnu.org>
Subject: Re : [GCC front end] trying to install sample_fe but fail in make
Date: Mon, 07 Jun 2010 13:34:00 -0000 [thread overview]
Message-ID: <285937.98277.qm@web28506.mail.ukl.yahoo.com> (raw)
In-Reply-To: <7c01c91296c0beecfe4d6761073628bb-EhVcXl1CTQJeRwgeDAw3AF9BdAJSS1xcXV9EBF41WEVGVFENQV5+BEtdXjBeQ0IHWVxaSF9d-webmailer2@server04.webmailer.hosteurope.de>
Hello Andi,
thank you for your answer.
I modified the sfe1.c as you suggested. previous error disappears
but I get 2 other errors generated while calling make bootstrap
DEBUG_ANDI: gsfe - .. ../libcpp/libcpp.a ../libiberty/libiberty.a ..
.. -O2 -g -fomit-frame-pointer -DIN_GCC -W -Wall -Wwrite-strings
-Wstrict-prototypes -Wmissing-prototypes -pedantic -Wno-long-long
-Wno-variadic-macros -Wold-style-definition -Wmissing-format-attribute
-DHAVE_CONFIG_H ..
stage1/xgcc -Bstage1/
-B/usr/local/i686-pc-linux-gnu/bin/ -O2 -g -fomit-frame-pointer
-DIN_GCC -W -Wall -Wwrite-strings -Wstrict-prototypes
-Wmissing-prototypes -pedantic -Wno-long-long -Wno-variadic-macros
-Wold-style-definition -Wmissing-format-attribute -DHAVE_CONFIG_H
-o gsfe sample_fe/gsfe.o \
version.o prefix.o intl.o ../libcpp/libcpp.a ../libiberty/libiberty.a
/usr/lib/crt1.o: In function `_start':
../sysdeps/i386/elf/start.S:115: undefined reference to `main'
collect2: ld returned 1 exit status
make[2]: *** [gsfe] Erreur 1
make[2]: Leaving directory `/home/charfi/Desktop/gccobj/gcc'
make[1]: *** [stage2_build] Erreur 2
make[1]: Leaving directory `/home/charfi/Desktop/gccobj/gcc'
make: *** [bootstrap] Erreur 2
I am calling ./configure after creating an other directory (not related in the source directory) named gcc-obj.
this time, I think the error comes from the driver (gsfe); xhnich line should I modify ;)
thank you very much
Asma
----- Message d'origine ----
De : Andi Hellmund <mail@andihellmund.com>
À : charfi asma <charfiasma@yahoo.fr>
Cc : gcc-help@gcc.gnu.org
Envoyé le : Ven 4 juin 2010, 17h 04min 38s
Objet : Re: [GCC front end] trying to install sample_fe but fail in make
Hey,
> I try to install "sample_fe" following the steps described in Andi Blog :
> http://blog.lxgcc.net/?p=181
Thanks for trying this :-) And thanks for catching this silly mistake!
> I put the sample_fe in the gcc directory (whith the other fe directory :
> java, cp, ...)
> I configure with ./configure --enable-languages=sample_fe
> when I call make, I get this errors:
Generally, you should follow the install instructions on
http://gcc.gnu.org/install/ and NOT call configure from the source
directory, but from a separated build directory.
> make
> ...build/gengtype.o build/gengtype-lex.o build/gengtype-yacc.o \
> build/errors.o ../build-i686-pc-linux-gnu/libiberty/libiberty.a
> build/gengtype
> /home/charfi/Desktop/gcc-4.1.0/gcc/sample_fe/sfe1.c:24: stray GTY marker
> make[2]: *** [s-gtype] Erreur 1
> make[2]: Leaving directory `/home/charfi/Desktop/gcc-obj/gcc'
> make[1]: *** [all-gcc] Erreur 2
> make[1]: Leaving directory `/home/charfi/Desktop/gcc-obj'
> make: *** [all] Erreur 2
>
> I think it is reltaed with GTY and gengtype but I do not realy understand
> how to correct it.
Yes, I think that as well. You could possibly fix this by changing line 24
of sfe1.c
from
struct GTY(()) lang_identifier
to
struct lang_identifier GTY(())
But, I'm not totally sure if this version of sample_fe will work anyway
with your version, because I just tested it with 4.4.x and you seem to
compile a 4.1.0 version. If you for some reason require to use 4.1.0, then
please continue trying and let me know if you face further problems.
Otherwise, I would recommend using a 4.4.x. I'll upload a 4.5.0-based
version this weekend, so that you could also use gcc-4.5.0 for your
experiments.
I'll update the web page with a modified version ...
Best regards,
Andi
next prev parent reply other threads:[~2010-06-07 11:43 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-04 15:04 charfi asma
2010-06-04 15:46 ` Andi Hellmund
2010-06-07 13:34 ` charfi asma [this message]
2010-06-07 14:28 ` Re : " Andi Hellmund
2010-06-07 16:11 ` Re : " charfi asma
2010-06-07 21:34 ` Philip Herron
[not found] ` <AANLkTimBwfoGdgaz19gkeFoKhbnloKYT0VpVMmjVUgtA@mail.gmail.com>
2010-06-08 18:54 ` Re : " charfi asma
2010-06-08 21:34 ` Andi Hellmund
2010-06-23 16:52 ` Re : " charfi asma
[not found] ` <895794.48229.qm@web28503.mail.ukl.yahoo.com>
2010-06-24 1:53 ` Andi Hellmund
2010-06-24 5:26 ` Philip Herron
2010-06-24 23:41 ` Re : " charfi asma
2010-06-25 4:14 ` Andi Hellmund
2010-06-25 13:28 ` Philip Herron
[not found] ` <4C23C78C.2040903@andihellmund.com>
2010-07-16 14:15 ` Re : " charfi asma
2010-07-17 3:48 ` Philip Herron
2010-07-19 13:56 ` Re : " charfi asma
2010-07-21 15:53 ` Philip Herron
2010-08-16 12:32 ` Re : " charfi asma
2010-08-18 9:22 ` Philip Herron
2010-08-18 16:07 ` Re : " charfi asma
2010-08-18 17:40 ` Philip Herron
2010-08-19 17:39 ` Re : " charfi asma
2010-08-20 4:33 ` Philip Herron
2010-08-21 10:37 ` Re : " charfi asma
2010-08-24 6:34 ` Andi Hellmund
2010-08-24 13:45 ` Re : " charfi asma
2010-08-25 21:46 ` Philip Herron
2010-08-26 13:02 ` Re : " charfi asma
2010-06-25 0:15 ` Re : Re : " Jens Kilian
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=285937.98277.qm@web28506.mail.ukl.yahoo.com \
--to=charfiasma@yahoo.fr \
--cc=gcc-help@gcc.gnu.org \
--cc=mail@andihellmund.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).