Updating glibc on SELF image

Updating glibc on SELF image

[Dave Cogley]

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

Re: Updating glibc on SELF image

[Dave Cogley]

Can someone provide a comprehensive guide for building SELF images from
scratch? More specifically how to install dependency libraries?

Thanks,
Dave

On Wed, 2008-06-18 at 14:35 -0700, Dave Cogley wrote:
> 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
> 
> 
> _______________________________________________
> Linuxppc-embedded mailing list
> Linuxppc-embedded@ozlabs.org
> https://ozlabs.org/mailman/listinfo/linuxppc-embedded

Re: Updating glibc on SELF image

[Detlev Zundel]

Hi Dave,

> Can someone provide a comprehensive guide for building SELF images from
> scratch? More specifically how to install dependency libraries?

There is a mailing list specifically for ELDK and related questions[1].  

Apart from that, if you want to change SELF contents, you can either do
it manually (as you started) or adjust the SELF spec file and rebuild
the target RPM as documented in the DULG.

Apart from that I believe you somehow work with mismatching SELF and
ELDK NFS installations.  The SELF rpm is built from the ELDK NFS
installation, so it is simply not possible to have different versions of
libraries between those two.

Cheers
  Detlev

[1] http://lists.denx.de/mailman/listinfo/eldk

-- 
Ftpd never switches uid and euid, it uses setfsuid(2) instead. The
main reason is that uid switching has been exploited in several
breakins, but the sheer ugliness of uid switching counts too.
                                     -- pure-ftpd(8)

Re: Updating glibc on SELF image

[Dave Cogley]

Thank you for the reply. I did not build the initial SELF image it was
provided to me from the board vendor. I used it as a starting point to
get something up and running on SELF. Can you point me to the
documentation on how to use the SELF RPM system?

Thanks,
Dave

On Wed, 2008-07-02 at 20:26 +0200, Detlev Zundel wrote:
> Hi Dave,
> 
> > Can someone provide a comprehensive guide for building SELF images from
> > scratch? More specifically how to install dependency libraries?
> 
> There is a mailing list specifically for ELDK and related questions[1].  
> 
> Apart from that, if you want to change SELF contents, you can either do
> it manually (as you started) or adjust the SELF spec file and rebuild
> the target RPM as documented in the DULG.
> 
> Apart from that I believe you somehow work with mismatching SELF and
> ELDK NFS installations.  The SELF rpm is built from the ELDK NFS
> installation, so it is simply not possible to have different versions of
> libraries between those two.
> 
> Cheers
>   Detlev
> 
> [1] http://lists.denx.de/mailman/listinfo/eldk
> 

Re: Updating glibc on SELF image

[Detlev Zundel]

Hi Dave,

> Thank you for the reply. I did not build the initial SELF image it was
> provided to me from the board vendor. I used it as a starting point to
> get something up and running on SELF. Can you point me to the
> documentation on how to use the SELF RPM system?

Rebuilding the SELF image boils down to rebuilding the SELF "target
package" having nothing SELF specific in the process.  This is explained
in the DULG[1].

Cheers
  Detlev

[1] http://www.denx.de/wiki/view/DULG/ELDKRebuildingComponents#Section_3.7.2.

-- 
... that every year or so they're going to give you a new release full
of 50 000  additional lines of code all  written  by monkeys.  Because
they generally follow  the  ``million monkeys typing,   and eventually
they'll come up with something useful'' school of system development.
	                                    -- Richard M. Stallman
--
DENX Software Engineering GmbH,      MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich,  Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-40 Fax: (+49)-8142-66989-80 Email: dzu@denx.de