Hello again...
Well i replaced the supplied host tools with the original host tools, e.g.:
Quote:
mv /opt/Embedix/bin /opt/Embedix/bin-orig
....
some more (lib, etc, usr, ...)
and
Quote:
cp -r /bin /opt/Embedix/bin
...
The i tried the whole build process again - which looked promising.
Ncurses needs "mawk" (which isnt supplied on FC2 system) so a did a symlink to gawk.
Most of the stuff did build but then i failed: RPM
At the time of making RPM's, the '/opt/Embedix/tools/bin/rpm' version is invoked which chokes badly because of dynamic linker issues (incompatible GLIBC), (i moved (opt/Embedix/lib to /lib-orig before replacing with my host's one)
Its the dreaded dll hell here. The script commands need the newest GLIBC (2.3) in place while some special tools (like the rpm command) need the old /opt/Embedix/lib tree structure.
With
ldd and
strace i could trace some problems...
I wrote a wrapper test script for the tools rpm invokation like
Quote:
#!/bin/sh
exec /lib-orig/ld-linux.so.2 --library-path /lib-orig /tools/bin/rpm-orig -rcfile /bdk/lh79520/build/rpmdir/rpmrc -bi --buildarch --short-circuit /bdk/lh79520/build/rpmdir/spec
But it didnt work ... it segfaults somewhere.
There must be a way to convince the tools to coexist together even with several (incompatible) versions of GLIBC together!
I cant simply replace the tool's rpm with the host one because if incompatible command switch settings ... maybe its a special (cross compiled??) version.
I now begin to understand the requirement for RH 7/8 ... but our host machine is P4 3.x GHz with HT cpu, SATA ... with all that nifty features not supported by older kernels.
If i would have more time i would drop that dreaded embedix stuff and its dependencies and start using some stock (arm.linux) 2.x kernel... and newer toolchain.
Regards