From: Brendan Simon <brendan@dgs.monash.edu.au>
To: Cross-GCC <crossgcc@cygnus.com>,
egcs mailing list <egcs@cygnus.com>,
linuxppc-user <linuxppc-user@lists.linuxppc.org>,
linuxppc-dev <linuxppc-dev@lists.linuxppc.org>
Subject: egcs-1.1.2 powerpc cross-compiler question.
Date: Tue, 04 May 1999 03:36:37 +0000 [thread overview]
Message-ID: <372E6B45.92CCD632@dgs.monash.edu.au> (raw)
I've tried building egcs-1.1.2 as a powerpc-eabi cross compiler and a
powerpc-linux cross compiler. I had instructions from the LinuxPPC web
site on building the powerpc-linux cross compiler. The configure
command was "configure --target=powerpc-linux --with-newlib". The only
difference between my setup and the instructions on the web site is that
I am using the FULL egcs-1.1.2 source where as the instructions were for
the CORE egcs-1.1.2 source. I want to use C and C++ so I used the full
distribution. The error message I am getting looks like its related to
the objective C build which I don't need but I am interested in trying
it one day. The errors are:
egcs-1.1.2/gcc/objc/runtime.h:31 stdio.h: No such file or directory
egcs-1.1.2/gcc/objc/runtime.h:31 ctype.h: No such file or directory
I did not have these problems building the native linux build of
egcs-1.1.2. It obviously knows how/where to find the appropriate
headers.
How can I get the objc build to find the appropriate header files ?
Can I just delete the gcc/objc directory to avoid building objc ?
The CONFIGURE file in the INSTALL directory says that if you use
--enable-languages=c++ then the other languages will be omitted. I
tried that but I still get the above error messages indicating that the
objc compiler is trying to be built.
Thanks,
Brendan Simon.
PS. The other difference I had to the LinuxPPC howto, is I included
--program-prefix=powerpc-linux- when building egcs and binutils. Will
egcs have a problem finding the correct binutils with this option ?
Would --exec-prefix help to solve this, if this is a problem ?
Brendan.
[[ This message was sent via the linuxppc-dev mailing list. Replies are ]]
[[ not forced back to the list, so be sure to Cc linuxppc-dev if your ]]
[[ reply is of general interest. Please check http://lists.linuxppc.org/ ]]
[[ and http://www.linuxppc.org/ for useful information before posting. ]]
next reply other threads:[~1999-05-04 3:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-05-04 3:36 Brendan Simon [this message]
1999-05-04 14:36 ` egcs-1.1.2 powerpc cross-compiler question Brian Ford
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=372E6B45.92CCD632@dgs.monash.edu.au \
--to=brendan@dgs.monash.edu.au \
--cc=crossgcc@cygnus.com \
--cc=egcs@cygnus.com \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=linuxppc-user@lists.linuxppc.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.