linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Dave Cogley <dcogley@uslinc.com>
To: PPC Embedded List <linuxppc-embedded@ozlabs.org>
Subject: Updating glibc on SELF image
Date: Wed, 18 Jun 2008 14:35:12 -0700	[thread overview]
Message-ID: <1213824912.4450.20.camel@localhost.localdomain> (raw)

Hi,

I am having some trouble with building my SELF image on a Sequoia board.
I am trying to update some shared library components on the "stock" DENX
provided JFFS file system image.

While running over an NFS root I was able to successfully mount my MTD
device and manually copy libraries my application requires to the SELF
image. This appears to work for most the libraries that are non existent
on the default image (libreadline, libXml etc.). 

The problem is that when developing on the NFS partition (flash_nfs) the
glic version in use is 2.6 and the SELF image only has 2.3.5. I manually
copy over the libc-2.6.so library from the NFS image to the SELF image
and create a new symbolic link "libc.so.6". Now while booting up with
2.6 I get segfaults on start-up daemons and my application segfaults
when starting as well. Changing the link back to the 2.3.5 library
everything works fine (except my application which requires 2.4).

The glibc library I am attempting to use is compiled for the ppc
architecture and works fine on the NFS partition. Am I missing something
else that needs to be updated for the glibc library? Is there anyway I
can update this library on the SELF image without installing make and
gcc?

Thank You,
Dave Cogley

             reply	other threads:[~2008-06-18 21:59 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-18 21:35 Dave Cogley [this message]
2008-06-19 18:45 ` Updating glibc on SELF image Dave Cogley
2008-07-02 18:26   ` Detlev Zundel
2008-07-02 19:18     ` Dave Cogley
2008-07-03 16:24       ` Detlev Zundel

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=1213824912.4450.20.camel@localhost.localdomain \
    --to=dcogley@uslinc.com \
    --cc=linuxppc-embedded@ozlabs.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).