public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Russ Allbery <rra@stanford.edu>
To: Gerald Pfeifer <pfeifer@dbai.tuwien.ac.at>
Cc: gcc@gcc.gnu.org
Subject: Re: GCC 2.95.x: Major problems on Solaris (was: Lost specific.html  FAQEntry)
Date: Sat, 28 Aug 1999 16:48:00 -0000	[thread overview]
Message-ID: <ylemgn4gbk.fsf@windlord.stanford.edu> (raw)
In-Reply-To: <Pine.GSO.4.10.9908281225440.10135-100000@alphard.dbai.tuwien.ac.at>

Gerald Pfeifer <pfeifer@dbai.tuwien.ac.at> writes:

>  5. Has someone experiencing these problems already submitted bug reports
>     to the binutils developers resp. Sun?

I haven't, under the assumption that the hint file entry in Perl saying
that GNU ld wouldn't work meant that this was a known problem.  If people
think it would help, I can try it again in a few days and put together a
fuller problem report.  Perl makes extensive use of dynamically loaded
modules, and the symptom that I was seeing was that when all of Perl was
linked with GNU ld, it couldn't load the dynamic modules that it had just
built.

-- 
Russ Allbery (rra@stanford.edu)         <URL: http://www.eyrie.org/~eagle/ >

WARNING: multiple messages have this Message-ID
From: Russ Allbery <rra@stanford.edu>
To: Gerald Pfeifer <pfeifer@dbai.tuwien.ac.at>
Cc: gcc@gcc.gnu.org
Subject: Re: GCC 2.95.x: Major problems on Solaris (was: Lost specific.html  FAQEntry)
Date: Tue, 31 Aug 1999 23:20:00 -0000	[thread overview]
Message-ID: <ylemgn4gbk.fsf@windlord.stanford.edu> (raw)
Message-ID: <19990831232000.-8DDu1mI-W315_rEWpXP5BZuBWhRuO_7g36EgXSy1FM@z> (raw)
In-Reply-To: <Pine.GSO.4.10.9908281225440.10135-100000@alphard.dbai.tuwien.ac.at>

Gerald Pfeifer <pfeifer@dbai.tuwien.ac.at> writes:

>  5. Has someone experiencing these problems already submitted bug reports
>     to the binutils developers resp. Sun?

I haven't, under the assumption that the hint file entry in Perl saying
that GNU ld wouldn't work meant that this was a known problem.  If people
think it would help, I can try it again in a few days and put together a
fuller problem report.  Perl makes extensive use of dynamically loaded
modules, and the symptom that I was seeing was that when all of Perl was
linked with GNU ld, it couldn't load the dynamic modules that it had just
built.

-- 
Russ Allbery (rra@stanford.edu)         <URL: http://www.eyrie.org/~eagle/ >

  reply	other threads:[~1999-08-28 16:48 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <Pine.GSO.4.10.9908271827120.19328-100000@markab.dbai.tuwien.ac.at>
1999-08-27 15:28 ` Lost specific.html FAQ Entry Russ Allbery
1999-08-28  3:44   ` GCC 2.95.x: Major problems on Solaris (was: Lost specific.htmlFAQEntry) Gerald Pfeifer
1999-08-28 16:48     ` Russ Allbery [this message]
1999-08-28 17:07       ` GCC 2.95.x: Major problems on Solaris (was: Lost specific.html FAQEntry) H.J. Lu
1999-08-30  3:42         ` Gerald Pfeifer
1999-08-31 23:20           ` Gerald Pfeifer
1999-08-31 23:20         ` H.J. Lu
1999-08-30  2:51       ` Gerald Pfeifer
1999-08-30  3:08         ` Russ Allbery
1999-08-31 23:20           ` Russ Allbery
1999-08-31 23:20         ` Gerald Pfeifer
1999-08-30  9:29       ` Nick Ing-Simmons
1999-08-30 22:31         ` GCC 2.95.x: Major problems on Solaris Russ Allbery
1999-08-31 23:20           ` Russ Allbery
1999-08-31 23:20         ` GCC 2.95.x: Major problems on Solaris (was: Lost specific.html FAQEntry) Nick Ing-Simmons
1999-08-30  9:29       ` Nick Ing-Simmons
1999-08-31 23:20         ` Nick Ing-Simmons
1999-08-31 23:20       ` Russ Allbery
1999-08-29  6:57     ` GCC 2.95.x: Major problems on Solaris (was: Lost specific.html FAQ Entry) Hans-Peter Nilsson
1999-08-31 23:20       ` Hans-Peter Nilsson
1999-08-31 23:20     ` GCC 2.95.x: Major problems on Solaris (was: Lost specific.htmlFAQEntry) Gerald Pfeifer
1999-08-31 23:20   ` Lost specific.html FAQ Entry Russ Allbery
1999-08-28 19:20 GCC 2.95.x: Major problems on Solaris (was: Lost specific.html FAQEntry) Phil Edwards
1999-08-31 23:20 ` Phil Edwards

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=ylemgn4gbk.fsf@windlord.stanford.edu \
    --to=rra@stanford.edu \
    --cc=gcc@gcc.gnu.org \
    --cc=pfeifer@dbai.tuwien.ac.at \
    /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).