From: "Andi Hellmund" <mail@andihellmund.com>
To: "charfi asma" <charfiasma@yahoo.fr>
Cc: mail@andihellmund.com, gcc-help@gcc.gnu.org
Subject: Re: Re : [GCC front end] trying to install sample_fe but fail in make
Date: Mon, 07 Jun 2010 14:28:00 -0000 [thread overview]
Message-ID: <e72b799b44c5b94d0bdf752b554f2851-EhVcXl1CTQJeRwgeDAw3AF9BdAJSS1xcXV9EBF41WEVdS10OQVl+H1dUWzBeQ0IHVlteRl9S-webmailer2@server08.webmailer.hosteurope.de> (raw)
In-Reply-To: <285937.98277.qm@web28506.mail.ukl.yahoo.com>
Hey,
> I modified the sfe1.c as you suggested. previous error disappears
> but I get 2 other errors generated while calling make bootstrap
okay, that's not good. Usually, when working on a front-end, I disable the
bootstrapping (using --disable-bootstrap) option to accelerate the build
to get the new front-end as fast as possible. Even though the Make-lang.in
of sample_fe isn't complete, it should be able to handle the bootstrap
case
But this error doesn't currenlty look like a problem to the bootstrapping.
Which version of GCC are you using for your tests? Still 4.1.0? If you're
still using 4.1.0, then the sample_fe might not work/build properly
because it was "developped" and tested for 4.4.0. If you face these
problems although you switched to 4.4.0, I need to re-check the
bootstrapping case.
If you however insist on using 4.1.0, I could prepare sample_fe for this
version?
> /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
The linker is missing the 'main' function which isn't - as of 4.4.0 - not
provided by the driver code, but by the GCC infrastructure (IIRC, gcc.c).
So, I assume that just a different object file is missing for the final
linking.
Andi
next prev parent reply other threads:[~2010-06-07 13:34 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 ` Re : " charfi asma
2010-06-07 14:28 ` Andi Hellmund [this message]
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=e72b799b44c5b94d0bdf752b554f2851-EhVcXl1CTQJeRwgeDAw3AF9BdAJSS1xcXV9EBF41WEVdS10OQVl+H1dUWzBeQ0IHVlteRl9S-webmailer2@server08.webmailer.hosteurope.de \
--to=mail@andihellmund.com \
--cc=charfiasma@yahoo.fr \
--cc=gcc-help@gcc.gnu.org \
/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).