public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Doug Semler <doug@seaspace.com>
To: David Edelsohn <dje@watson.ibm.com>
Cc: Andrey Slepuhin <pooh@msu.ru>, egcs@cygnus.com
Subject: Re: EGCS build failure on AIX 4.2
Date: Wed, 08 Apr 1998 02:13:00 -0000	[thread overview]
Message-ID: <199804071615.JAA16475@seaspace.com> (raw)
In-Reply-To: <9804071546.AA25180@rios1.watson.ibm.com>

David Edelsohn wrote:
> >>>>> Andrey Slepuhin writes:
> 
> Andrey> As I remember, official gnu ld (2.8.1) doesn't work correctly on AIX4
> .2.
> Andrey> However, problem was fixed in development snapshots. Ian Lance Tailor
> Andrey> sent a patch to 2.8.1 sources to egcs mailing list (letter from 9 Oct
> ).
> Andrey> But I still had problems with complicated C++ code, this cause me
> Andrey> to look more closely at AIX ld+collect2 solution, which now seems
> Andrey> to be stable (except some problems with shared libraries+rtti+excepti
> ons).
> 
> 	I believe that GNU ld was not using strict enough alignment, but
> that was causing failure when a program was invoked, not when it was
> compiled(?).  In another message, Doug seemed to imply that GNU as was
> producing code at which AIX ld balked on AIX 4.2.  I was not aware of that
> type of problem with GNU as on AIX 4.2.  I am not sure the build and
> configuration were restarted cleanly enough to be sure of this assembler
> problem.

But I am: I did an rm -rf of my build directory, and also removed ONLY
the linker from the install of binutils; but I was still using gas.  That
is what prompted the ld error (YES, I am absolutely, positively sure
that there are no other copies of the gnu linker around).  Rebuild
with only the --with-gnu-as flags, and that genattr misalignment happened.
rm -rf'ed the entire binutils directory and build directory, recompiled
egcs without the --with-* flags, and the misalignment goes away.

I am using binutils 2.8.1, and AFAIK a clean install of 4.2.0.  I don't
know if there are any patches to the OS installed on it, we really dropped
the ball on that machine.  (we don't even have the man pages on the damned
thing).  I'm gonna see if I can't talk my boss into re-installing the OS
on the monster :)

---
Doug Semler                       | doug@seaspace.com
SeaSpace Corporation              | Garbage In -- Gospel Out
Least Senior Software Developer;  | Minister of things to do Next Quarter
Low Man on the Totem Pole         | (but will Never Be Done) DNRC  O-
A closed mind is a terrible thing | Bus Error (passengers dumped)

      reply	other threads:[~1998-04-08  2:13 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
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 [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=199804071615.JAA16475@seaspace.com \
    --to=doug@seaspace.com \
    --cc=dje@watson.ibm.com \
    --cc=egcs@cygnus.com \
    --cc=pooh@msu.ru \
    /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).