public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Rohit Arul Raj <rohitarulraj@gmail.com>
To: gcc <gcc@gcc.gnu.org>
Subject: Cross compiler build instructions - PowerPC
Date: Wed, 23 Mar 2011 04:58:00 -0000	[thread overview]
Message-ID: <AANLkTimVFcxch=7rH6OZ+QwH1V6KAEp6H9he1-fCquff@mail.gmail.com> (raw)

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

The build instructions in the link works perfectly fine with the
following revisions:
GCC v4.1.2
Binutils v2.17
linux v2.16.19.1
eglibc v2.5

But while trying to build with the latest revisions, i get some build errors:

GCC v4.5.1
Binutils v2.20.51
linux  2.6.35.2
libc 2.13 (from eglibc)

Error while building 1st stage GCC:
-------------------------------------------------------------

make[4]: Entering directory
`/cross_build/ppc45/obj/gcc1/powerpc-linux-gnu/nof/libgcc'
# If this is the top-level multilib, build all the other
# multilibs.

/cross_build/ppc45/obj/gcc1/./gcc/xgcc -MD -MP -MF decContext.dep -c
/cross_build/ppc45/src/gcc-4.5-2010.09/libgcc/../libdecnumber/decContext.c
/cross_build/ppc45/src/gcc-4.5-2010.09/libgcc/../libdecnumber/decContext.c:33:43:
fatal error: string.h: No such file or directory
compilation terminated.
make[4]: *** [decContext.o] Error 1
make[4]: Leaving directory
`/cross_build/ppc45/obj/gcc1/powerpc-linux-gnu/nof/libgcc'
make[3]: *** [multi-do] Error 1

I was expecting that 'libgcc' will not be built in the first stage? Is
that right?
If i try configuring with '--disable-libgcc', i get errors while
building 'libiberty' & 'zlib'. Disabling all three does help to build
the first stage of GCC but was not sure if this was the right way to
do it.

Do we have different build instructions other than the one mentioned
in the link above to build the latest sources?

Thanks,
Rohit

             reply	other threads:[~2011-03-23  4:58 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-23  4:58 Rohit Arul Raj [this message]
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
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='AANLkTimVFcxch=7rH6OZ+QwH1V6KAEp6H9he1-fCquff@mail.gmail.com' \
    --to=rohitarulraj@gmail.com \
    --cc=gcc@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).