From: Greicy.Costa-Marques@imag.fr
To: "John (Eljay) Love-Jensen" <eljay@adobe.com>
Cc: "gcc-help@gcc.gnu.org" <gcc-help@gcc.gnu.org>
Subject: RE: How to include a front end to gcc ?
Date: Wed, 18 Nov 2009 14:56:00 -0000 [thread overview]
Message-ID: <20091118155525.320711sm51tc5rkt@webmail.imag.fr> (raw)
In-Reply-To: <204DEA5423F3BF47A6EE88C4E2979EC66BF76562A0@nambx04.corp.adobe.com>
Hey John,
Is necessary install GMP and MPFR? I didn't know that it was necessary
for included the front-end...I use the version 4.2.4 of GCC. And what
versions (GMP and MPFR) I can use with for my version of the GCC and
where?
regards,
greicy
Citando "John (Eljay) Love-Jensen" <eljay@adobe.com>:
>> Thanks for your tip, I tested with your front-end (and the my) with my
>> version and all is well (the first part), but when type make bootstrap or
>> make bootstrap-lean return this:
>>
>> make[3]: Leaving directory `/c/gcc4/gcc-build/gcc'
>> make[2]: *** [ail-stage1-gcc] Error 2
>> make[2]: Leaving directory `/c/gcc4/gcc-build'
>> make[1]: *** [stage1-bubble] Error 2
>> make[1]: Leaving directory `/c/gcc4/gcc-build'
>> make: *** [bootstrap] Error2
>
> In addition to what John G said, also please include your configure
> line, your make line, your platform, the GCC version, GMP and where
> is it, MPFR and where is it, MPC and where is it?
>
> You may have already provided this information from a previous
> inquiry on this forum. But, if so, that information is
> out-of-context.
>
> Sincerely,
> --Eljay
>
next prev parent reply other threads:[~2009-11-18 14:56 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-10 11:00 Greicy.Costa-Marques
2009-11-10 14:56 ` Ian Lance Taylor
2009-11-10 15:56 ` Greicy.Costa-Marques
2009-11-10 15:58 ` Ian Lance Taylor
2009-11-10 19:23 ` Andi Hellmund
2009-11-18 13:34 ` Greicy.Costa-Marques
2009-11-18 14:06 ` John Graham
2009-11-18 14:24 ` John (Eljay) Love-Jensen
2009-11-18 14:56 ` Greicy.Costa-Marques [this message]
2009-11-18 15:53 ` John (Eljay) Love-Jensen
2009-12-03 17:44 ` Greicy.Costa-Marques
2009-12-07 15:53 ` Greicy.Costa-Marques
2009-12-07 15:54 ` John (Eljay) Love-Jensen
2009-12-10 20:55 ` Greicy.Costa-Marques
2009-12-11 0:23 ` Andi Hellmund
2009-12-11 9:51 ` Greicy.Costa-Marques
2009-12-12 2:15 ` Andi Hellmund
2009-12-14 20:11 ` Greicy.Costa-Marques
2009-12-16 16:50 ` Greicy.Costa-Marques
2009-12-16 22:40 ` Cedric Roux
[not found] ` <alpine.DEB.2.00.0912232132210.23563@randazzo>
[not found] ` <20100118171613.37323adazx3nmf65@webmail.imag.fr>
[not found] ` <19bb413aeea8173be0119dc84a99254c-EhVcXl1CTQJeRwgeDAw3AF9BdAJSS1xcXV9EBF41WEVGVFENQV5+BEtdXzBeQ0MGX1taRV1T-webmailer2@server02.webmailer.hosteurope.de>
[not found] ` <20100121110544.618273k2lhw1t054@webmail.imag.fr>
[not found] ` <alpine.DEB.2.00.1001231718010.2115@randazzo>
[not found] ` <20100129160405.10512mrjmwx0n10l@webmail.imag.fr>
[not found] ` <4B65ABE6.8070109@andihellmund.com>
[not found] ` <20100204184027.126147yistgbwjnv@webmail.imag.fr>
[not found] ` <4B6B4CC5.50406@andihellmund.com>
2010-03-05 15:36 ` Greicy.Costa-Marques
2010-03-05 22:43 ` Andi Hellmund
2010-03-08 17:30 ` Greicy.Costa-Marques
2010-03-12 16:41 ` Greicy.Costa-Marques
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=20091118155525.320711sm51tc5rkt@webmail.imag.fr \
--to=greicy.costa-marques@imag.fr \
--cc=eljay@adobe.com \
--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).