From: Matthew Locke <mlocke@mvista.com>
To: "Justin (Gus) Hurwitz" <ghurwitz@dyndns.com>
Cc: Michael Habermann <MHabermann@gmx.de>,
linuxppc-embedded@lists.linuxppc.org
Subject: Re: Segmentation fault while dynamic linking
Date: Thu, 28 Jun 2001 09:20:03 -0700 [thread overview]
Message-ID: <3B3B5933.4050509@mvista.com> (raw)
In-Reply-To: Pine.LNX.3.95.1010628024351.5112B-100000@november.bhjjh.erols.com
Justin (Gus) Hurwitz wrote:
> On Thu, 28 Jun 2001, Michael Habermann wrote:
>
>
>>At 10:08 AM 6/27/2001 -0700, Matthew Locke wrote:
>>
>>
>>>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.
>>>
>>Yeah, deleting memset.S solved my problem.
>>
>>Thanks to you and the guys who answered by private mail.
>>
>
> Could you post a quick summary of what yo had to do to get this to work
> (ie, which source you downloaded, which patches you downloaded and
> applied, and which flags you used to compile)?
>
> I've been trying to get uClibc to work, but am having IO errors with it,
> so I'm thinking of giving glibc another try.
>
that is probably best:-) Just grab our toolchain it works and it has
the patches in its src rpm.
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
prev parent reply other threads:[~2001-06-28 16:20 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
2001-06-28 2:57 ` Michael Habermann
2001-06-28 6:46 ` Justin (Gus) Hurwitz
2001-06-28 16:20 ` 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=3B3B5933.4050509@mvista.com \
--to=mlocke@mvista.com \
--cc=MHabermann@gmx.de \
--cc=ghurwitz@dyndns.com \
--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).