From: Michael Zintakis <michael.zintakis@googlemail.com>
To: Ian Lance Taylor <iant@google.com>
Cc: gcc-help@gcc.gnu.org
Subject: Re: building native cross compiler
Date: Mon, 14 Mar 2011 01:47:00 -0000 [thread overview]
Message-ID: <4D7D738C.2010407@googlemail.com> (raw)
In-Reply-To: <mcrsjuq4h1i.fsf@google.com>
>> Thanks! Downloaded along with mpfr, ppl-0.11.2 (configure said that my
>> existing version is "buggy" :-) ) and cloog-ppl-0.15.9.
>>
>> If I dump mpfr, ppl and cloog-ppl in the main gcc source directory
>> (and name those directories like that - "mpfr", "ppl" and "cloog-ppl")
>> would that be enough for the GCC build or do I have to compile/install
>> them separately?
>>
>
> As far as I know that is fine. I haven't done much with PPL myself.
>
It says on the gcc pre-requisite pages that these packages are good for
doing the optimisations, so I thought there is no harm to include these
in the build as well. I'll try them when I do my 2nd pass.
Currently I took the plunge and dumped the whole binutils directory in
the main gcc source...will see how it goes after I selected
--host=x86_64 and --target=powerpc, fingers crossed!
>> If I copy binutils sources to the main gcc source directory what would
>> be the sign that they are incompatible - the same error as I was
>> getting before (line 83 etc)?
>>
>
> No, the errors are much more subtle. I really can't encourage this
> unless you are prepared to investigate and solve problems yourself.
>
I hope there is no conflict, but if there is and I get an error I will
build binutils separately.
>>> What do you see in the config.log file?
>>>
>>>
>> The same one I was getting with the ppc target - line 83 etc etc.
>>
>
> I'm sorry, I don't recall what that was. If it's a missing 'as' file
> then the simple answer is still going to be to install the binutils. At
> one time gcc would fall back to running 'as' even for a cross-compiler,
> but perhaps that is no longer the case.
>
I am a bloody moron! I forgot to rename the mpfr directory when dumping
the source and this was the reason for the build to stop midway through
- it is OK now, I just compiled GCC with the multilib option on without
any glitches. We're getting there!!!
MZ
next prev parent reply other threads:[~2011-03-14 1:47 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-11 14:56 Michael Zintakis
2011-03-11 16:00 ` Ian Lance Taylor
2011-03-11 16:56 ` Michael Zintakis
2011-03-11 18:57 ` Ian Lance Taylor
2011-03-11 20:47 ` Michael Zintakis
2011-03-11 21:21 ` Ian Lance Taylor
2011-03-11 23:44 ` Michael Zintakis
2011-03-12 0:06 ` Ian Lance Taylor
2011-03-13 14:23 ` Michael Zintakis
2011-03-13 18:45 ` Ian Lance Taylor
2011-03-13 22:10 ` Michael Zintakis
2011-03-14 0:34 ` Ian Lance Taylor
2011-03-14 0:51 ` Michael Zintakis
2011-03-14 1:01 ` Ian Lance Taylor
2011-03-14 1:30 ` Michael Zintakis
2011-03-14 1:39 ` Ian Lance Taylor
2011-03-14 1:47 ` Michael Zintakis [this message]
2011-03-14 1:55 ` Michael Zintakis
2011-03-14 2:01 ` Ian Lance Taylor
2011-03-14 2:08 ` Michael Zintakis
2011-03-14 3:48 ` Michael Zintakis
2011-03-14 15:26 ` Ian Lance Taylor
2011-03-14 15:49 ` Michael Zintakis
2011-03-14 16:00 ` Michael Zintakis
2011-03-14 16:25 ` Ian Lance Taylor
2011-03-14 16:34 ` Michael Zintakis
2011-03-14 16:02 ` Ian Lance Taylor
2011-03-14 16:31 ` Michael Zintakis
2011-03-14 17:23 ` Kai Ruottu
2011-03-14 18:03 ` Michael Zintakis
2011-03-14 19:07 ` Kai Ruottu
2011-03-14 19:25 ` Michael Zintakis
2011-03-14 20:20 ` Ian Lance Taylor
2011-03-14 20:35 ` Michael Zintakis
2011-03-14 21:12 ` Ian Lance Taylor
2011-03-15 2:25 ` Michael Zintakis
2011-03-15 4:23 ` Ian Lance Taylor
2011-03-15 5:01 ` Mick McCreath
2011-03-16 17:26 ` Michael Zintakis
2011-03-20 15:48 ` Michael Zintakis
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=4D7D738C.2010407@googlemail.com \
--to=michael.zintakis@googlemail.com \
--cc=gcc-help@gcc.gnu.org \
--cc=iant@google.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).