Symbol problem libc.so.6. How to imclude or export?

Kreuzuebersetzer, Diskussion über Änderungen im Tuxbox-CDK und Tuxbox-CVS
pedrag2
Neugieriger
Neugieriger
Beiträge: 5
Registriert: Mittwoch 6. Februar 2013, 09:21

Symbol problem libc.so.6. How to imclude or export?

Beitrag von pedrag2 »

Hello:

Sorry for the previous message,. I hope I do not break anything rules now.

I do not know if this is the right subforum, sorry if it is not. Also sorry for my English, I'm using google translator.

I compiled my own image for dm500s with Linux Kernel2.6.9. glibc 2.3.2 and gcc 3.4.4.
The sources, here

git://git.code.sf.net/p/tuxbox-cvs/$f $f

The prepare file

Code: Alles auswählen

#!/bin/bash
cd .. && CURRENT_PATH=`pwd`;
cd cdk
./autogen.sh;
# boxtype dm500 dm56x0 or dm7000
TYPE=$1
if test -z "$TYPE"; then
    TYPE=dm500
fi
./configure \
    --with-boxtype="dreambox" \
    --with-boxmodel=$TYPE \
    --with-webif=expert \
    --prefix=$CURRENT_PATH/root \
    --with-cvsdir=$CURRENT_PATH \
    --enable-maintainer-mode \
    --with-epg=standard \
    --with-mhw-epg=yes \
    --with-flashtool=standard \
    --with-ext-flashtool=yes \
    --with-enigma-debug=yes \
    --enable-ide \
    --enable-dropbear \
    --enable-kernel26 \
    --with-filesystems=ext3
I compile my dm500 image with: make flash-enigma-squashfs
Everything went perfect but I have problems with symbols in the library libc.so.6 when I execute, any program or plugin.

The error is: relocation error, symbol not defined GLIBC_2.0 in libc.so.6

In the static library file (libc.a) in root/cdkroot /lib/ the objects or symbol that I need exists. (ar x libc.a) Also this objects exists in libc-2.3.2.so (readelf -s libc-2.3.2.so)

Where should I change the settings so that this symbol is included in file libc.so.6
Is there any other method or way to do this? or am I doing something wrong?

Thanks

Edit: by doc
BBCode eingefügt
seife
Developer
Beiträge: 4189
Registriert: Sonntag 2. November 2003, 12:36

Re: Symbol problem libc.so.6. How to imclude or export?

Beitrag von seife »

All unused symbols (which are not used by anything in the flashroot(?)) are stripped by mklibs. This is why they might still be in cdkroot, but gone from flash.
I think the reason for this is the very limited FLASH space of the old boxes.
pedrag2
Neugieriger
Neugieriger
Beiträge: 5
Registriert: Mittwoch 6. Februar 2013, 09:21

Re: Symbol problem libc.so.6. How to imclude or export?

Beitrag von pedrag2 »

Thanks for your answer

I will seek the mklibs. I will try to see how to include these symbols in libc.so.6

I thought that something good and needed to build something more different

Also be included in libc.so.6 unusual symbols, modifying mklibs.

I thought it should to compile something different.

Space in flash should not be the problem, complete.img file is 5 MB

Thank you very match. I'll try and comment the results
msrx111
Interessierter
Interessierter
Beiträge: 95
Registriert: Dienstag 14. Juni 2011, 16:50
Image: eigenkompilat neutrino
Image: eigenkompilat neutrino

Re: Symbol problem libc.so.6. How to imclude or export?

Beitrag von msrx111 »

If a Programm you need is in your flashroot while the libs are stripped then the symbols will be there afterwards......
pedrag2
Neugieriger
Neugieriger
Beiträge: 5
Registriert: Mittwoch 6. Februar 2013, 09:21

Re: Symbol problem libc.so.6. How to imclude or export?

Beitrag von pedrag2 »

msrx111 hat geschrieben:If a Programm you need is in your flashroot while the libs are stripped then the symbols will be there afterwards......
Thank you very much, I dont know this

I 'll try
pedrag2
Neugieriger
Neugieriger
Beiträge: 5
Registriert: Mittwoch 6. Februar 2013, 09:21

Re: Symbol problem libc.so.6. How to imclude or export?

Beitrag von pedrag2 »

Thanks for all answer

All OK
MastaG
Interessierter
Interessierter
Beiträge: 20
Registriert: Montag 6. Mai 2013, 10:17

Re: Symbol problem libc.so.6. How to imclude or export?

Beitrag von MastaG »

Sorry to bring up this old thread.
But in my destination dir I have:

cdkroot/
cdkflash/root
cdkflash/root-enigma
cdkflash/root-enigma-squashfs
cdkflash/root-squashfs
cdkflash/var-enigma

Each directory features the baselayout of the filesystem.

I want to place a binary requiring certain symbols, but I do NOT want to include the binary in the actual image.
I just wan't mklibs to check the binary requiments and keep symbols for it in libc.
Where should I place it?

Thanks in advance
GetAway
Contributor
Beiträge: 1509
Registriert: Donnerstag 27. Dezember 2007, 12:59

Re: Symbol problem libc.so.6. How to imclude or export?

Beitrag von GetAway »

Hi,

if you build a Squashfs-Image:

In root-local.sh

Code: Alles auswählen

cp -vf /mypath/myfile $1/root/bin/
In root-enigma-squashfs-local.sh the binary will be deleted after mklibs.py

Code: Alles auswählen

rm -vf $1/root-enigma-squashfs/bin/myfile
MastaG
Interessierter
Interessierter
Beiträge: 20
Registriert: Montag 6. Mai 2013, 10:17

Re: Symbol problem libc.so.6. How to imclude or export?

Beitrag von MastaG »

Thanks alot GetAway,

It works beautifully.
Using these scripts I can edit almost everything prior to building the images.

Is there also a localscript for adjusting the /var partition?
I support something like:

var-enigma-local.sh

Code: Alles auswählen

cp -vf /mycables.xml $1/var-enigma/etc/cables.xml
GetAway
Contributor
Beiträge: 1509
Registriert: Donnerstag 27. Dezember 2007, 12:59

Re: Symbol problem libc.so.6. How to imclude or export?

Beitrag von GetAway »

Yes.

Code: Alles auswählen

root-local.sh
root-enigma-local.sh
root-enigma-squashfs-local.sh
root-squashfs-local.sh
var-enigma-local.sh

Zurück zu „Tuxbox-SD Buildsystem“