From: Jeffrey A Law <law@upchuck.cygnus.com>
To: crossgcc@cygnus.com
Cc: egcs mailing list <egcs@cygnus.com>,
linuxppc-dev <linuxppc-dev@lists.linuxppc.org>
Subject: Re: can't find crt1.o. egcs powerpc-linux cross-compile problem.
Date: Tue, 25 May 1999 10:03:18 -0600 [thread overview]
Message-ID: <19448.927648198@upchuck.cygnus.com> (raw)
In-Reply-To: Your message of Tue, 25 May 1999 09:06:21 -0000. <374A680D.8B051E6E@dgs.monash.edu.au>
In message <374A680D.8B051E6E@dgs.monash.edu.au>you write:
>
> I am trying to compile egcs-1.1.2 as a cross-compiler (linux to
> powerpc). I am building on a redhat-5.2 system and have successfully
> compiled and installed a native egcs-1.12. I am using this compiler for
> the cross-compile build and have used the following configure options.
> --target=powerpc-linux
> --program-prefix=powerpc-linux-
> --with-headers=/usr/include
>
> The compilation of xgcc completes. At some later stage, configure tries
> to test the newly built xgcc to see if it can build executables, but it
> fails. When I run the command manually, the error message says that
> "ld" can not find crt1.o. Where is the source for crt1 (egcs or
> glibc) ? I can see crt1 files in the newlib tree so my first assumption
> is that it must be in the glibc tree for linux targets.
>
> Any suggestions to get past my crt1 linking problems.
You have to be able to provide a crt1.o for your target system. I highly
doubt newlib's crt files are going to be appropriate for a linux target.
> PS. With regard to the --with-headers option, should I unpack the glibc
> sources and point --with-headers to the unpacked include directory,
> instead of the original redhat-5.2 ?
What is most important is that you point to header files that are appropriate
for your target. ie, if you're sitting on a rh5.2-ix86 system, then
/usr/include is totally useless for a powerpc target.
jeff
[[ 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. ]]
prev parent reply other threads:[~1999-05-25 16:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-05-25 9:06 can't find crt1.o. egcs powerpc-linux cross-compile problem Brendan Simon
1999-05-25 15:17 ` David Edelsohn
1999-05-25 23:43 ` Brendan Simon
1999-05-26 0:06 ` jpgarcia
1999-05-25 16:03 ` Jeffrey A Law [this message]
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=19448.927648198@upchuck.cygnus.com \
--to=law@upchuck.cygnus.com \
--cc=crossgcc@cygnus.com \
--cc=egcs@cygnus.com \
--cc=law@cygnus.com \
--cc=linuxppc-dev@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 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 NNTP newsgroup(s).