From: Matthew Locke <mlocke@mvista.com>
To: Magnus Damm <damm@opensource.se>
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: glibc-2.2.2
Date: Mon, 02 Apr 2001 11:29:04 -0700 [thread overview]
Message-ID: <3AC8C4F0.9C009A91@mvista.com> (raw)
In-Reply-To: 3AC8743B.8BC64EA5@opensource.se
Magnus Damm wrote:
>
> Hi all,
>
> Anyone tried glibc-2.2.2?
yep. we found it crashes in the dynamic loader on a cache instruction
during a memset for loading the second dynamic library. since libc is
always the first library loaded any application that only uses libc
works. any app that uses more than libc, seg faults.
> It cross-compiles cleanly, but acts wierd on my mpc8xx target.
>
> I've browsed through my old 2.1.3 patches for the cacheline-
> size and I'm not sure if everything is ok with 2.2.2...
>
we are working it as I type. my guess is the cacheline patches didn't
make it.
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
prev parent reply other threads:[~2001-04-02 18:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-02 12:44 glibc-2.2.2 Magnus Damm
2001-04-02 18:29 ` Matthew Locke [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=3AC8C4F0.9C009A91@mvista.com \
--to=mlocke@mvista.com \
--cc=damm@opensource.se \
--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).