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: Tue, 15 Mar 2011 02:25:00 -0000 [thread overview]
Message-ID: <4D7ECDF9.7000805@googlemail.com> (raw)
In-Reply-To: <mcrd3lt1k5c.fsf@google.com>
>>> You need to first build a vanilla
>>> cross-compiler without building the library.
>>>
>> What does constitute a "vanilla cross-compiler"? Is this a "limited"
>> cross-compiler without the glibc dependencies (because that is the
>> only way I think possible to have glibc and a fully-fledged cross
>> compiler the way I want it)?
>>
>
> Yes, build just the compiler, and none of the libraries.
>
Hmm, that didn't go down well!
The crosstool.sh script is so outdated is unreal! I found it nigh
impossible to use it in its present form, so I have to get what it does
and, hopefully, adapt it. There are many things this script is trying to
do and I am not sure I understand the reason for it. For example, before
starting to build binutils it is trying to execute "make" in the main
linux headers directory with ARCH specified and parameters "include/asm
include/linux/version.h" (line 347) and that obviously fails as there
isn't any target with that name. Why is it doing that it is a mystery to
me! And why the hell do I need to execute "make oldconfig" in the main
linux directory? I am not compiling the kernel (at least not yet).
One other thing is that ARCH named 'ppc' doesn't exist - it is 'powerpc'
and that screws things up even more. The last error I've got after
'patching up' the above "problems" is that during the binutils build
make fails as it is apparently looking for <build_arch>-ar which does
not exist either. Things like that...
So, I'll have a more thorough look tomorrow to see whether I could do
these things 'manually', but I am not at all hopeful.
Has this been done recently? I can't believe there is no methodology for
this and I have to rely on a bloody script which has been last updated 6
years ago!!! Unreal!
MZ
next prev parent reply other threads:[~2011-03-15 2:25 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
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 [this message]
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=4D7ECDF9.7000805@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).