From: hjl@lucon.org (H.J. Lu)
To: chip@pobox.com
Cc: egcs@cygnus.com
Subject: Re: 970929: MY patch list
Date: Fri, 10 Oct 1997 15:09:00 -0000 [thread overview]
Message-ID: <m0xJm1e-0004eeC@ocean.lucon.org> (raw)
In-Reply-To: <199710090316.XAA07747@cyprus.atlantic.net>
>
> According to H.J. Lu:
> > I always compile glibc with -fno-exceptions and install egcs in
> > /usr. They may make a difference.
>
> I don't know how my glibc is built, unfortunately, it's the debian
> package.
Please check with debian to see which compiler was used to compile
glibc. If egcs or gcc snapshot was used, -fno-exceptions should
be used. Otherwise, it is looking for trouble since EH is very
buggy. I always use -fno-exceptions to compile glibc.
H.J.
prev parent reply other threads:[~1997-10-10 15:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-10-08 6:04 Chip Salzenberg
1997-10-08 14:41 ` H.J. Lu
1997-10-08 21:19 ` chip
1997-10-09 9:26 ` Michael Alan Dorman
1997-10-10 15:09 ` H.J. Lu [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=m0xJm1e-0004eeC@ocean.lucon.org \
--to=hjl@lucon.org \
--cc=chip@pobox.com \
--cc=egcs@cygnus.com \
/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).