From: David Edelsohn <dje@watson.ibm.com>
To: Doug Semler <doug@seaspace.com>
Cc: egcs@cygnus.com
Subject: Re: EGCS build failure on AIX 4.2
Date: Mon, 06 Apr 1998 11:36:00 -0000 [thread overview]
Message-ID: <9804061833.AA30006@rios1.watson.ibm.com> (raw)
In-Reply-To: <199804061831.LAA09441@seaspace.com>
I also notice that you configure EGCS using
--with-gnu-as and --with-gnu-ld
Are GNU as and GNU ld really primary in your path? Do you really have
those installed? Because of changes in AIX, GNU ld may not work correctly
on AIX 4.2, so I would recommend against using it.
My guess is that if you configured for AIX ld and really used the
AIX linker, the build work succeed.
David
next parent reply other threads:[~1998-04-06 11:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <199804061831.LAA09441@seaspace.com>
1998-04-06 11:36 ` David Edelsohn [this message]
1998-04-06 17:35 ` Doug Semler
1998-04-08 2:13 ` Andrey Slepuhin
1998-04-08 2:13 ` David Edelsohn
1998-04-08 2:13 ` Doug Semler
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=9804061833.AA30006@rios1.watson.ibm.com \
--to=dje@watson.ibm.com \
--cc=doug@seaspace.com \
--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).