can't find crt1.o. egcs powerpc-linux cross-compile problem.

can't find crt1.o. egcs powerpc-linux cross-compile problem.

[Brendan Simon]

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.

Thanks,
Brendan Simon.

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 ?



[[ 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.   ]]

Re: can't find crt1.o. egcs powerpc-linux cross-compile problem.

[David Edelsohn]

	Did you build cross-binutils at the same time as cross-gcc?

David

[[ 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.   ]]

Re: can't find crt1.o. egcs powerpc-linux cross-compile problem.

[Brendan Simon]

David Edelsohn wrote:

>         Did you build cross-binutils at the same time as cross-gcc?
>
> David

Nope.  I built binutils seperately and installed them.  I then added the
install path to my PATH environment variable and then started to build
egcs.  I was following the LinuxPPC cross-compiler instructions and have
done this for a powerpc-eabi cross-compiler.  The only difference was
that I left out the --with-newlib option to configure.  Having read
other replies, this option MIGHT solve my problem.  The LinuxPPC
instructions for building a cross-compiler say that the --with-newlib
option is there to avoid linking in __eprintf.  I know that Linux now
uses glibc and was a bit worried about using the --with-newlib switch in
case it stuffed things up later.  I couldn't find any references to
linux in the newlib source (which is sort of what I expected) so I
thought that I did not need use the --with-newlib option.

Can anyone advise me on the best approach ?

Thanks,
Brendan Simon.


[[ 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.   ]]

Re: can't find crt1.o. egcs powerpc-linux cross-compile problem.

[jpgarcia]

> Can anyone advise me on the best approach ?

http://www.in-berlin.de/User/kraxel/cross-compiler.html

Here is a mini-howto that shows how to make a cross compiler for a sparc.  I applied it to make a cross compiler for an alpha from a ppc running r4.  It worked pretty good.  just exchange the platform types and it should work.

--

Joseph Garcia
Madison, WI
jpgarcia@execpc.com



[[ 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.   ]]

Re: can't find crt1.o. egcs powerpc-linux cross-compile problem.

[Jeffrey A Law]

  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.   ]]