From: Alexandre Oliva <oliva@lsd.ic.unicamp.br>
To: Markus Werle <markus@lufmech.rwth-aachen.de>
Cc: gcc-help@gcc.gnu.org
Subject: Re: ld problem on hpux 10.20 with egcs-20000124
Date: Sat, 29 Jan 2000 13:57:00 -0000 [thread overview]
Message-ID: <orbt64k0cq.fsf@garnize.lsd.ic.unicamp.br> (raw)
In-Reply-To: <38919357.B7FD0620@lufmech.rwth-aachen.de>
On Jan 28, 2000, Markus Werle <markus@lufmech.rwth-aachen.de> wrote:
> IMHO the error is not in hp ld.
It is crashing. This is always an error.
> Please believe, I do not want to blame the developers of gcc,
That's not the point. I didn't think you were, I just pointed you at
an evident problem that you should attempt to get fixed before
assuming other problems would remain.
> The problem is their interaction and all those nasty side effects.
> HP will tell me the same answer only with inverse sign.
I recall having read about a patch for HP/UX's ld before. Did you
ever install such a beast?
> Any idea where the linker should find the symbols?
Some of those you mention would be in libgcc, some in libstdc++.
--
Alexandre Oliva http://www.ic.unicamp.br/~oliva IC-Unicamp, Bra[sz]il
oliva@{lsd.ic.unicamp.br,guarana.{org,com}} aoliva@{acm,computer}.org
oliva@{gnu.org,kaffe.org,{egcs,sourceware}.cygnus.com,samba.org}
** I may forward mail about projects to mailing lists; please use them
WARNING: multiple messages have this Message-ID
From: Alexandre Oliva <oliva@lsd.ic.unicamp.br>
To: Markus Werle <markus@lufmech.rwth-aachen.de>
Cc: gcc-help@gcc.gnu.org
Subject: Re: ld problem on hpux 10.20 with egcs-20000124
Date: Sat, 01 Apr 2000 00:00:00 -0000 [thread overview]
Message-ID: <orbt64k0cq.fsf@garnize.lsd.ic.unicamp.br> (raw)
Message-ID: <20000401000000.GkpJR-aKOQ_0qR20Vv1Ujv962HIvzmGPRssJxvp46OE@z> (raw)
In-Reply-To: <38919357.B7FD0620@lufmech.rwth-aachen.de>
On Jan 28, 2000, Markus Werle <markus@lufmech.rwth-aachen.de> wrote:
> IMHO the error is not in hp ld.
It is crashing. This is always an error.
> Please believe, I do not want to blame the developers of gcc,
That's not the point. I didn't think you were, I just pointed you at
an evident problem that you should attempt to get fixed before
assuming other problems would remain.
> The problem is their interaction and all those nasty side effects.
> HP will tell me the same answer only with inverse sign.
I recall having read about a patch for HP/UX's ld before. Did you
ever install such a beast?
> Any idea where the linker should find the symbols?
Some of those you mention would be in libgcc, some in libstdc++.
--
Alexandre Oliva http://www.ic.unicamp.br/~oliva IC-Unicamp, Bra[sz]il
oliva@{lsd.ic.unicamp.br,guarana.{org,com}} aoliva@{acm,computer}.org
oliva@{gnu.org,kaffe.org,{egcs,sourceware}.cygnus.com,samba.org}
** I may forward mail about projects to mailing lists; please use them
next prev parent reply other threads:[~2000-01-29 13:57 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-01-28 3:26 Markus Werle
2000-01-28 4:07 ` Alexandre Oliva
2000-01-28 5:01 ` Markus Werle
2000-01-29 13:57 ` Alexandre Oliva [this message]
2000-04-01 0:00 ` Alexandre Oliva
2000-04-01 0:00 ` Markus Werle
2000-04-01 0:00 ` Alexandre Oliva
2000-04-01 0:00 ` Markus Werle
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=orbt64k0cq.fsf@garnize.lsd.ic.unicamp.br \
--to=oliva@lsd.ic.unicamp.br \
--cc=gcc-help@gcc.gnu.org \
--cc=markus@lufmech.rwth-aachen.de \
/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).