All of lore.kernel.org
 help / color / mirror / Atom feed
From: Brendan Simon <brendan@dgs.monash.edu.au>
To: David Edelsohn <dje@watson.ibm.com>
Cc: egcs mailing list <egcs@egcs.cygnus.com>,
	linuxppc-dev <linuxppc-dev@lists.linuxppc.org>,
	Cross-GCC <crossgcc@cygnus.com>
Subject: Re: can't find crt1.o. egcs powerpc-linux cross-compile problem.
Date: Tue, 25 May 1999 23:43:48 +0000	[thread overview]
Message-ID: <374B35B4.F477CA84@dgs.monash.edu.au> (raw)
In-Reply-To: 9905251517.AA44940@marc.watson.ibm.com


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

  reply	other threads:[~1999-05-25 23:43 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 [this message]
1999-05-26  0:06     ` jpgarcia
1999-05-25 16:03 ` Jeffrey A Law

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=374B35B4.F477CA84@dgs.monash.edu.au \
    --to=brendan@dgs.monash.edu.au \
    --cc=crossgcc@cygnus.com \
    --cc=dje@watson.ibm.com \
    --cc=egcs@egcs.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 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.