View Single Post
Old 08-24-2013, 11:31 AM   #234
knc1
Helpdesk Junkie
knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.
 
knc1's Avatar
 
Posts: 7,001
Karma: 6327868
Join Date: Feb 2012
Device: Too many.
Quote:
Originally Posted by knc1 View Post
One of the things that needs to be done is that use of an additional CFLAGS option passed to the cross-compiler when building things:
--with-sysroot=/mnt/us/extensions/system

I haven't (yet) played with the various combinations of options for moving the location requirements out of the standard place, it may be more complex than just that.

But when you do a readelf on a binary built that way, it should report:
requesting /mnt/us/extensions/system/lib/ld-linux.so.xx interpreter

And of course, that loader (interpreter) should be searching /mnt/us/extension/system/lib and /mnt/us/extensions/system/usr/lib on its own, **without** any fooling around with 'LD_LIBRARY_PATH'

And since the loader is built as part of building the C library, **everything** has to be re-built, starting with the C library.

Hello, BuildRoot.
Which, catch-22 style, brings us back to your original question - -

"What is the most recent version of eglibc that can be built with the kernel version we have to run?"

PS: Keep in mind, the **AMAZON** kernel headers - not the mainstream kernel headers.
knc1 is offline   Reply With Quote