From: Brendan J Simon <Brendan.Simon@ctam.com.au>
To: erammsu@kieraypc01.p.y.ki.era.ericsson.se
Cc: linuxppc-embedded <linuxppc-embedded@lists.linuxppc.org>,
linuxppc-dev <linuxppc-dev@lists.linuxppc.org>,
glibc-linux <glibc-linux@ricardo.ecn.wfu.edu>
Subject: glibc patches for mpc860
Date: Thu, 06 Jan 2000 10:21:14 +1100 [thread overview]
Message-ID: <3873D1E9.916117E0@ctam.com.au> (raw)
> Graham Stoney wrote:
> > Thanks for your great tips on building glibc for the '860. It would
be great if
> > we could get some mods into the next glibc release so that it would
configure
> > out-of-the-box without patching...
> Marcus Sundberg wrote:
> Yes definitely. I intend to submit some patches as soon as I've had
> time to try out glibc 2.1.2pre3 and verified that there are no
> problems with that. Don't know if I will have time before they
> release the final 2.1.2 though. :(
Are the 860 pathces in the latest glibc releases ?
If not, what about in the CVS tree ?
Thanks,
Brendan Simon.
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
reply other threads:[~2000-01-05 23:21 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=3873D1E9.916117E0@ctam.com.au \
--to=brendan.simon@ctam.com.au \
--cc=erammsu@kieraypc01.p.y.ki.era.ericsson.se \
--cc=glibc-linux@ricardo.ecn.wfu.edu \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=linuxppc-embedded@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).