public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: Markus Werle <markus@lufmech.rwth-aachen.de>
To: Alexandre Oliva <oliva@lsd.ic.unicamp.br>
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: <38919357.B7FD0620@lufmech.rwth-aachen.de> (raw)
Message-ID: <20000401000000.Y0jrKa1EBN6ljgJpvAS4YbxbxFK17lU5WF0OiW8GWZ4@z> (raw)
In-Reply-To: <oriu0epfh2.fsf@garnize.lsd.ic.unicamp.br>

Alexandre Oliva wrote:

> On Jan 28, 2000, Markus Werle <markus@lufmech.rwth-aachen.de> wrote:
>
> > but there seems to be a problem with the linker.
>
> Yup.  So why are you reporting it here? ;-)

The missing symbols are c++ symbols which I expect to get shipped
with gcc. They all belong to "typeinfo".

So maybe there are some symbols missing in libstd++ or libgcc
due to configuration  errors in gcc - or some I did myself
(the latter for sure). IMHO the error is not in hp ld.

As I can read on http://gcc.gnu.org/lists.html:
"gcc-help is a [...] list for people searching for help in building gcc"

I just mentioned I had a little problem and was seeking for an answer.
The whole installation process for gcc on HPUX is a painful story
(far away from linux' configure-make-make_install).
As I can see at dejanews and in the gcc mailing lists
I am not the only one banging his head against the wall.

Please believe, I do not want to blame the developers of gcc,
but rather ask for a discussion that leads back to a really portable
compiler. I am greatful for the work You have done, especially
the template stuff. Let us use it - even on hpux.

> So you should ask for help from HP, not to us.  Maybe you need to
> patch your system?

The problem is *not* gcc and the problem is *not* hpux.
The problem is their interaction and all those nasty side effects.
HP will tell me the same answer only with inverse sign.

Again: I repeat my question:
Any idea where the linker should find the symbols?


Best regards,


Markus

  reply	other threads:[~2000-04-01  0:00 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 [this message]
2000-01-29 13:57     ` Alexandre Oliva
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=38919357.B7FD0620@lufmech.rwth-aachen.de \
    --to=markus@lufmech.rwth-aachen.de \
    --cc=gcc-help@gcc.gnu.org \
    --cc=oliva@lsd.ic.unicamp.br \
    /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).