From: Paolo Carlini <pcarlini@unitus.it>
To: Carlos Ordonez <carloso@us.ibm.com>
Cc: gcc@gcc.gnu.org, aj@suse.de
Subject: Re: missing gcc_eh
Date: Tue, 30 Jul 2002 10:33:00 -0000 [thread overview]
Message-ID: <3D46A11E.6867C91D@unitus.it> (raw)
In-Reply-To: <3D469C54.4DA1A961@us.ibm.com>
Carlos Ordonez wrote:
> I am building glibc 2.2.5 and I am getting an error gcc_eh not found. I
> have tried looking in the internet and found nothing. I am running with
> gcc 3.1 in a 2.4.7 kernel. Did I miss something when I built gcc 3.1?
> Any help would be appreciated. Thanks Carlos :-)
Hi,
irrespective of the specific problem you are reporting it seems to me that
the released glibc2.2.5 cannot be compiled fine with gcc3.1. gcc3.0.4
should be ok OTOH. Alternatively, fetch CVS glibc. Andreas can you
confirm/clarify? Thanks!
http://gcc.gnu.org/ml/gcc-bugs/2002-07/msg00787.html
http://gcc.gnu.org/ml/gcc-bugs/2002-07/msg00788.html
Ciao,
Paolo.
next prev parent reply other threads:[~2002-07-30 14:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-30 9:46 Carlos Ordonez
2002-07-30 10:33 ` Paolo Carlini [this message]
2002-07-30 10:38 ` Andreas Jaeger
2002-07-30 11:18 Carlos Ordonez
2002-07-30 11:36 Carlos Ordonez
2002-07-30 12:07 ` Andreas Jaeger
2002-07-30 16:55 Carlos Ordonez
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=3D46A11E.6867C91D@unitus.it \
--to=pcarlini@unitus.it \
--cc=aj@suse.de \
--cc=carloso@us.ibm.com \
--cc=gcc@gcc.gnu.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).