linuxppc-dev.lists.ozlabs.org archive mirror
 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: Wed, 27 Jun 2001 10:08:56 -0700	[thread overview]
Message-ID: <3B3A1328.6000602@mvista.com> (raw)
In-Reply-To: 32197.993642129@www29.gmx.net


Michael Habermann wrote:

>>>>>My configuration: Kernel 2.4.4, glibc 2.2.2, bash 2.05, FADS, MPC855T
>>>>>
> ...
>
>>>binutils 2.11.2
>>>gcc 2.95.3
>>>glibc 2.2.2
>>>
>>>Everything unpatched and downloaded from ftp.gnu.org.
>>>
>>

>>From what I read in the mailing list, I would also say it looks like this
> problem.
>
> I've recompiled my toolchain now with plain gnu software and the following
> patches
> from ftp.mvista.com and glibc-src package:
> glibc22-27.patch               glibc22-getaddrinfo.dpatch
> glibc22-disable-static.dpatch  glibc22-nss-upgrade.dpatch
> glibc22-eo_EO.dpatch           glibcbug.dpatch
>
> But the problem is still there.
>
> I couldn't find 'the cacheline patch'. Is it the one mentioned here:
> http://lists.linuxppc.org/listarcs/linuxppc-embedded/200003/msg00073.html
>


There are two places cacheline size affects glibc.  The one above that
you already found and in the glibc ppc optimized memset or memcpy (don't
remember which one).  you can just delete the ppc specific memset and
configure will pull in the generic memset.


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

  reply	other threads:[~2001-06-27 17:08 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
2001-06-27 11:42       ` Michael Habermann
2001-06-27 17:08         ` Matthew Locke [this message]
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=3B3A1328.6000602@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 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).