From: Rohit Arul Raj <rohitarulraj@gmail.com>
To: Khem Raj <raj.khem@gmail.com>
Cc: "Joseph S. Myers" <joseph@codesourcery.com>,
gcc <gcc@gcc.gnu.org>,
patches@eglibc.org, maxim@codesourcery.com
Subject: Re: [patches] Re: Cross compiler build instructions - PowerPC
Date: Mon, 18 Jul 2011 12:44:00 -0000 [thread overview]
Message-ID: <CAPVMLfU-GCTFAFd0sNXTf+mmaoMcaot5+aFwpH-dC76KV8heKQ@mail.gmail.com> (raw)
In-Reply-To: <CAMKF1sq8PQ2Z1G0KqP1dBY4bN9xLUmnKD0O5U4JbUJWF7aAuZA@mail.gmail.com>
On Fri, Jul 8, 2011 at 8:03 PM, Khem Raj <raj.khem@gmail.com> wrote:
> On Fri, Jul 8, 2011 at 1:08 AM, Rohit Arul Raj <rohitarulraj@gmail.com> wrote:
>> On Wed, Mar 23, 2011 at 5:55 PM, Joseph S. Myers
>> <joseph@codesourcery.com> wrote:
>>> On Wed, 23 Mar 2011, Rohit Arul Raj wrote:
>>>
>>>> Hello All,
>>>>
>>>> I have been trying to build a cross compiler (for PowerPC) on x86_64
>>>> linux host. I followed the build procedure given in the link below:
>>>>
>>>> http://www.eglibc.org/archives/patches/msg00078.html
>>>
>>> You should be referring to the current checked-in version of this
>>> documentation, not a four-year-old draft. However, it doesn't appear to
>>> have relevant changes. Maxim, perhaps we should add
>>> --disable-decimal-float --disable-libffi --disable-libquadmath to the
>>> configure options for the first GCC in EGLIBC.cross-building?
>>>
>>> --
>>> Joseph S. Myers
>>> joseph@codesourcery.com
>>>
>>
>> Any updates on this one yet?
>> Adding "--disable-decimal-float --disable-libffi
>> --disable-libquadmath" to configure options gives the same error.
>
> I a script based on these instructions which is uptodate and builds eglibc
> based toolchains
>
> https://github.com/kraj/ct-scripts/blob/master/toolchain-eglibc.sh
>
> You can try that
>
>>
>> Regards,
>> Rohit
>>
>
Thanks Khem, i was able to build the first stage GCC :)
The only difference i can find is:
In the eglibc cross-building instructions, for building the first
stage GCC we give "$make" command only (which works fine with GCC
4.1.1)
And with your script you had given "$make all-gcc"
With the following configure options:
$src/$gccv/configure --target=$target --prefix=$tools
--without-header --with-newlib --disable-shared --disable-threads
--disable-libssp --disable-libgomp --disable-libmudflap
--disable-libquadmath --enable-languages=c
A) The following folders are built with "$make" which leads to the error:
make[1]: Entering directory `/usr/rohit/PA/460test/ppc/obj/gcc1'
make[2]: Entering directory `/usr/rohit/PA/460test/ppc/obj/gcc1/libiberty'
make[3]: Entering directory
`/usr/rohit/PA/460test/ppc/obj/gcc1/libiberty/testsuite'
make[2]: Entering directory
`/usr/rohit/PA/460test/ppc/obj/gcc1/fixincludes'
make[2]: Entering directory `/usr/rohit/PA/460test/ppc/obj/gcc1/lto-plugin'
make[3]: Entering directory `/usr/rohit/PA/460test/ppc/obj/gcc1/lto-plugin'
make[2]: Entering directory `/usr/rohit/PA/460test/ppc/obj/gcc1/intl'
make[2]: Entering directory
`/usr/rohit/PA/460test/ppc/obj/gcc1/build-x86_64-unknown-linux-gnu/libiberty'
make[3]: Entering directory
`/usr/rohit/PA/460test/ppc/obj/gcc1/build-x86_64-unknown-linux-gnu/libiberty/testsuite'
make[2]: Entering directory
`/usr/rohit/PA/460test/ppc/obj/gcc1/build-x86_64-unknown-linux-gnu/fixincludes'
make[2]: Entering directory `/usr/rohit/PA/460test/ppc/obj/gcc1/zlib'
make[2]: Entering directory `/usr/rohit/PA/460test/ppc/obj/gcc1/libcpp'
make[2]: Entering directory
`/usr/rohit/PA/460test/ppc/obj/gcc1/libdecnumber'
make[2]: Entering directory `/usr/rohit/PA/460test/ppc/obj/gcc1/gcc'
make[2]: Entering directory
`/usr/rohit/PA/460test/ppc/obj/gcc1/powerpc-none-linux-gnu/libgcc'
make[3]: Entering directory
`/usr/rohit/PA/460test/ppc/obj/gcc1/powerpc-none-linux-gnu/libgcc'
make[4]: Entering directory
`/usr/rohit/PA/460test/ppc/obj/gcc1/powerpc-none-linux-gnu/nof/libgcc'
B) The following folders are built with "$make all-gcc".
make[1]: Entering directory `/usr/rohit/PA/460test/ppc/obj/gcc1/libiberty'
make[2]: Entering directory
`/usr/rohit/PA/460test/ppc/obj/gcc1/libiberty/testsuite'
make[1]: Entering directory `/usr/rohit/PA/460test/ppc/obj/gcc1/lto-plugin'
make[2]: Entering directory `/usr/rohit/PA/460test/ppc/obj/gcc1/lto-plugin'
make[1]: Entering directory `/usr/rohit/PA/460test/ppc/obj/gcc1/intl'
make[1]: Entering directory
`/usr/rohit/PA/460test/ppc/obj/gcc1/build-x86_64-unknown-linux-gnu/libiberty'
make[2]: Entering directory
`/usr/rohit/PA/460test/ppc/obj/gcc1/build-x86_64-unknown-linux-gnu/libiberty/testsuite'
make[1]: Entering directory
`/usr/rohit/PA/460test/ppc/obj/gcc1/build-x86_64-unknown-linux-gnu/fixincludes'
make[1]: Entering directory `/usr/rohit/PA/460test/ppc/obj/gcc1/zlib'
make[1]: Entering directory `/usr/rohit/PA/460test/ppc/obj/gcc1/libcpp'
make[1]: Entering directory
`/usr/rohit/PA/460test/ppc/obj/gcc1/libdecnumber'
make[1]: Entering directory
`/usr/rohit/PA/460test/ppc/obj/gcc1/fixincludes'
make[1]: Entering directory `/usr/rohit/PA/460test/ppc/obj/gcc1/gcc'
Is this expected behavior?
Regards,
Rohit
next prev parent reply other threads:[~2011-07-18 11:58 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-23 4:58 Rohit Arul Raj
2011-03-23 12:25 ` Joseph S. Myers
2011-07-08 8:08 ` Rohit Arul Raj
2011-07-08 9:12 ` Andreas Schwab
2011-07-08 13:55 ` Joseph S. Myers
2011-07-08 14:34 ` [patches] " Khem Raj
2011-07-18 12:44 ` Rohit Arul Raj [this message]
2011-07-18 15:01 ` Khem Raj
2011-07-19 8:21 ` Rohit Arul Raj
2011-07-19 18:33 ` Anthony Foiani
2011-07-19 22:57 ` Anthony Foiani
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=CAPVMLfU-GCTFAFd0sNXTf+mmaoMcaot5+aFwpH-dC76KV8heKQ@mail.gmail.com \
--to=rohitarulraj@gmail.com \
--cc=gcc@gcc.gnu.org \
--cc=joseph@codesourcery.com \
--cc=maxim@codesourcery.com \
--cc=patches@eglibc.org \
--cc=raj.khem@gmail.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).