LinuxPPC-Dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Torben Mathiasen <torben.mathiasen@hp.com>
To: Joakim Tjernlund <joakim.tjernlund@lumentis.se>
Cc: "'Torben Mathiasen'" <torben.mathiasen@hp.com>,
	linuxppc-embedded@lists.linuxppc.org
Subject: Re: Anyone using uClibc on a 405GP platform?
Date: Tue, 24 Feb 2004 16:01:48 +0100	[thread overview]
Message-ID: <20040224150148.GA15404@tmathiasen> (raw)
In-Reply-To: <002d01c3fad0$c6b220d0$0a01a8c0@LUMENTIS02>


On Tue, Feb 24 2004, Joakim Tjernlund wrote:
> > On Tue, Feb 24 2004, Torben Mathiasen wrote:
> > >
> > > Hi,
> > >
> > > Does anyone successfully use uClibc on a 405GP platform? I
> > tried compiling
> > > uClibc but all my dynamic apps just segfault. Its the
> > shared library loader
> > > that segfaults immediately after execve(). I tried both a
> > recent 2.4 and 2.6
> > > kernel with the same result. Also using latest 0.9.26 uClibc.
> > >
> > > Has anyone gotten this to work?
> > >
> >
> > Funny, I got this to work. I was under the assumption that
> > one should be able
> > to execute the library loader directly, which has never
> > worked for me on
> > powerpc. But a dynamic linked application seems to be working
> > now. Both those
> > I compiled myself and the ones I got from the root_fs_powerpc fs.
>
> hmm, not sure about executing ldso directly, you may have better luck asking
> about that on the uClibc list.
>
> ldso is however somewhat broken. Lots of stuff/fixes has been added
> since the last release.

Thanks for the info. The uClibc I'm using now is the latest from CVS.

Torben
--

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

      reply	other threads:[~2004-02-24 15:01 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-24 11:09 Anyone using uClibc on a 405GP platform? Torben Mathiasen
2004-02-24 11:18 ` Joakim Tjernlund
2004-02-24 11:46 ` Torben Mathiasen
2004-02-24 12:21   ` Joakim Tjernlund
2004-02-24 15:01     ` Torben Mathiasen [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=20040224150148.GA15404@tmathiasen \
    --to=torben.mathiasen@hp.com \
    --cc=joakim.tjernlund@lumentis.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