From: David Edelsohn <dje@watson.ibm.com>
To: satadru pramanik <satadru@umich.edu>
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: compiler errors
Date: Wed, 13 Jan 1999 14:47:04 -0500 [thread overview]
Message-ID: <9901131947.AA100772@marc.watson.ibm.com> (raw)
In-Reply-To: Message from satadru pramanik <satadru@umich.edu> of "Wed, 13 Jan 1999 13:24:39 EST." <Pine.LNX.4.05.9901131322170.10086-100000@beer.pub.umich.edu>
You do not mention which release of EGCS you are using. This may
have been fixed in egcs-1.1.1, but you need to use Gary Thomas's special
build of egcs-1.1.1 unless your system is running glibc2.1.
David
[[ This message was sent via the linuxppc-dev mailing list. Replies are ]]
[[ not forced back to the list, so be sure to Cc linuxppc-dev if your ]]
[[ reply is of general interest. To unsubscribe from linuxppc-dev, send ]]
[[ the message 'unsubscribe' to linuxppc-dev-request@lists.linuxppc.org ]]
next prev parent reply other threads:[~1999-01-13 19:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-01-13 18:24 compiler errors satadru pramanik
1999-01-13 19:47 ` David Edelsohn [this message]
1999-01-13 19:55 ` satadru pramanik
1999-01-13 20:07 ` David Edelsohn
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=9901131947.AA100772@marc.watson.ibm.com \
--to=dje@watson.ibm.com \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=satadru@umich.edu \
/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 NNTP newsgroup(s).