From: Joe Buck <jbuck@synopsys.com>
To: chip@pobox.com
Cc: hjl@lucon.org, egcs@cygnus.com
Subject: Re: 970929 test results: libstdc++ test failures! (sparc-solaris251)
Date: Thu, 02 Oct 1997 13:40:00 -0000 [thread overview]
Message-ID: <199710022039.NAA17585@atrus.synopsys.com> (raw)
In-Reply-To: <199710022027.QAA16116@rio.atlantic.net>
> According to H.J. Lu:
> > > I'm using a Linux system with glibc 2.0.4. Despite Ulrich's patches
> > > that are a part of egcs-970929, a simple program to write to cout
> > > dumps core. I really don't know what to do next.
> >
> > You need glibc 2.0.5c and a patch for linuxthreads enclosed here.
>
> Is 2.0.4 beyond help? Debian doesn't have a 2.0.5 package yet, and
> when I looked at compiling 2.0.5c it seemed likely that I would get
> something wrong.
I want to get out of the mode where I have to continually replace my Linux
C libraries to use a new compiler. I don't have to do that on any other
platform. What's worse, the new libraries often break existing
applications, ones I may not have the source for (e.g. Netscape), and
pointing the finger at the other app developer does no good. Why should
this be acceptable for Linux? It basically says that only wizards may
use new compilers, or else all Linux users must wait for a wizard, such
as HJ Lu, to build binaries for everyone. This makes Linux feel, um,
"proprietary". As Mike Tiemann once said, free software is supposed to
be no-hassle software.
It would be better if the new compiler can adapt to the existing
libraries, possibly by adding more autoconf tests to find problem areas.
When egcs is released, it should be possible for Linux users who have the
then-current Red Hat or Debian distribution to build a working egcs
without upgrading their C library.
next prev parent reply other threads:[~1997-10-02 13:40 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <199710012211.PAA28962.cygnus.egcs@atrus.synopsys.com>
1997-10-01 18:18 ` Jason Merrill
1997-10-02 1:59 ` Torbjorn Lindgren
1997-10-02 6:31 ` 970929 test results: libstdc++ test failures! Torbjorn Lindgren
1997-10-02 10:46 ` 970929 test results: libstdc++ test failures! (sparc-solaris251) Joe Buck
1997-10-02 11:08 ` Jason Merrill
1997-10-02 11:25 ` Joe Buck
1997-10-02 14:40 ` Joe Buck
1997-10-02 15:02 ` Joe Buck
1997-10-02 11:23 ` Chip Salzenberg
1997-10-02 13:23 ` H.J. Lu
1997-10-02 13:28 ` Chip Salzenberg
1997-10-02 13:30 ` H.J. Lu
1997-10-02 13:40 ` Joe Buck [this message]
1997-10-02 13:49 ` H.J. Lu
1997-10-01 15:11 Joe Buck
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=199710022039.NAA17585@atrus.synopsys.com \
--to=jbuck@synopsys.com \
--cc=chip@pobox.com \
--cc=egcs@cygnus.com \
--cc=hjl@lucon.org \
/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).