From: Gary Thomas <gthomas@cygnus.co.uk>
To: Andreas Tobler <a.tobler@schweiz.ch>
Cc: "linuxppc-dev@lists.linuxppc.org" <linuxppc-dev@lists.linuxppc.org>
Cc: "linuxppc-dev@lists.linuxppc.org"
<linuxppc-dev@lists.linuxppc.org>,
linux ppc <linuxppc-user@lists.linuxppc.org>
Subject: RE: egcs-1.1.2-RPM
Date: Wed, 17 Mar 1999 14:43:15 -0000 (GMT) [thread overview]
Message-ID: <XFMail.990317144315.gthomas@cygnus.co.uk> (raw)
In-Reply-To: <36EF6F70.61C452E0@schweiz.ch>
On 17-Mar-99 Andreas Tobler wrote:
>
> Hi,
>
> maybe a dump question, is anybody working on a RPM for
> egcs-1.1.2-glibc1.99? And or egcs-1.1.2-glibc-2.1.
> If not can I try it by adapting a RPM from a earlier release? I never
> made a RPM from scratch, I only modified them.
>
> Yesterday, I built egcs-1.1.2 under R4.1. It worked out of the box?! Now
> I have to compare the test results. I can't believe it, before I had so
> many troubles building an egcs directly from egcs.cygnus.com.
>
> A last question, what are the minimal requirements to build egcs under
> pre-R5. Means glibc etc.
>
If you're willing to wait, I was planning on doing this later this week.
[[ 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. Please check http://lists.linuxppc.org/ ]]
[[ and http://www.linuxppc.org/ for useful information before posting. ]]
next prev parent reply other threads:[~1999-03-17 14:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-03-17 9:01 egcs-1.1.2-RPM Andreas Tobler
1999-03-17 14:43 ` Gary Thomas [this message]
1999-03-17 17:29 ` egcs-1.1.2-RPM Anirudh Joshi
-- strict thread matches above, loose matches on Subject: below --
1999-03-17 19:43 egcs-1.1.2-RPM Kaoru Fukui
1999-03-18 14:03 ` egcs-1.1.2-RPM Gary Thomas
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=XFMail.990317144315.gthomas@cygnus.co.uk \
--to=gthomas@cygnus.co.uk \
--cc=a.tobler@schweiz.ch \
--cc=linuxppc-dev@lists.linuxppc.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 NNTP newsgroup(s).