From: H.J. Lu <hjl@lucon.org>
To: egcs@cygnus.com
Subject: Re: Problems on PowerPC...
Date: Fri, 22 Aug 1997 19:47:24 -0000 [thread overview]
Message-ID: <m0x21UF-0004ecC@ocean.lucon.org> (raw)
In-Reply-To: Pine.LNX.3.96.970822165528.452B-100000@abduction.greys.org
> It looks like there's a difference in the ld command that's being
> issued...but it also looks like there might be issues of dynamic
> linking involved here when I'm using my normal gcc. Egcs is providing
> an '-m elf32ppc' argument that GCC isn't. GCC is providing an
> extra '-dynamic-linker=/lib/ld.so.1' argument that Egcs isn't.
>
ppc-linux in egcs assumes you are using glibc 2 on ppc.
Also it assumes binutils 2.8.1.0.15 for linux or the
gas snapshot is used.
H.J.
next reply other threads:[~1997-08-22 19:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-08-22 19:47 H.J. Lu [this message]
[not found] <Pine.NEB.3.96.970821084635.26124B-100000@water.waterw.com>
1997-10-20 13:24 ` Jeffrey A Law
-- strict thread matches above, loose matches on Subject: below --
1997-08-28 21:13 Michael Meissner
1997-08-22 19:47 dtm
1997-08-21 21:20 dtm
1997-08-21 16:51 David Edelsohn
1997-08-21 9:21 David McWherter
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=m0x21UF-0004ecC@ocean.lucon.org \
--to=hjl@lucon.org \
--cc=egcs@cygnus.com \
/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).