All of lore.kernel.org
 help / color / mirror / Atom feed
From: Matthew Locke <mlocke@mvista.com>
To: Michael Habermann <MHabermann@gmx.de>
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: Segmentation fault while dynamic linking
Date: Tue, 26 Jun 2001 20:26:03 -0700	[thread overview]
Message-ID: <3B39524B.5090108@mvista.com> (raw)
In-Reply-To: 5.0.2.1.0.20010627091411.00a56b90@pop.gmx.de


Michael Habermann wrote:

> At 10:12 AM 6/26/2001 -0700, Matthew Locke wrote:
>
>>> My configuration: Kernel 2.4.4, glibc 2.2.2, bash 2.05, FADS, MPC855T
>>
>>
>> who's toolchain are you using?  glibc 2.2.x has a cacheline size bug
>> for the smaller cacheline ppc processors.  Our toolchain has a fix for
>> it. grab our HHL 2.0 Journeyman edition and give it a try.
>> http://www.mvista.com
>
>
> binutils 2.11.2
> gcc 2.95.3
> glibc 2.2.2
>
> Everything unpatched and downloaded from ftp.gnu.org.


yeah, sounds like the cacheline problem. It is still in glibc 2.2.2 and
2.2.3.

>
> I've read in the mailing list, that the glibc needs to be patched. But
> I've found that the most changes are already made at glibc2.2.2, so I
> assumed it should work.
>
> The kernel is 2.4.4 from ftp.denx.de, patched by a patch posted from
> Dave Ellis.
>
> Ok, I try the mvista glibc.
>
>


** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

  reply	other threads:[~2001-06-27  3:26 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-06-26  9:32 Segmentation fault while dynamic linking Michael Habermann
2001-06-26 17:12 ` Matthew Locke
2001-06-27  1:17   ` Michael Habermann
2001-06-27  3:26     ` Matthew Locke [this message]
2001-06-27 11:42       ` Michael Habermann
2001-06-27 17:08         ` Matthew Locke
2001-06-28  2:57           ` Michael Habermann
2001-06-28  6:46             ` Justin (Gus) Hurwitz
2001-06-28 16:20               ` Matthew Locke

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=3B39524B.5090108@mvista.com \
    --to=mlocke@mvista.com \
    --cc=MHabermann@gmx.de \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.