Quote:
Originally Posted by NiLuJe
@knc1: Yeah, that sounds right, but at that rate, better to simply pass the linker the proper rpath at link-time and be done with it (which is how I handle that kind of stuff in my builds).
Sure, you lose a bit of flexibility, but it's not like we really need it anyway  . |
But that was my point, the build system will not pass ${ORIGIN} and the build system can not be fixed.
All they could do was document the limitation in the manual.
- - - -
But now I recall what it was I did (other than bitch at the maintainers of buildroot) - -
I came up with a layout that could be passed.
So that is 'worked around', I.E: "good enough".
And if I wasn't locked out of bitbucket - I'd fix the documents.
- - - -
They have since fixed up the "srcdir override" mechanisum, it should be 'fixed' at least good enough for our use.
- - - -
It was the release of about a year ago that they included the build of patchelf as one of the host tools.
(It seems some of there packages have an "rpath problem" that is hard to fix from within the build system.)
- - - -
One thing not (yet) in Buildroot to support after-market firmware for the Kindles - -
Deal with the ro root file system.
But there are a couple of choices on that point to choose from, I just haven't gotten around to deciding on one of them.
- - - -
So my goal of being able to run anything from Ubuntu 14.04LTS in USB storage is very close to being real.
And no one will have to depend on my being around to provide LTS - all they will need is a few (three? four?) config files and the ability to download buildroot to duplicate what I do.
someday - RSN (RSN == a few months)
- - - -
I sure do miss my #1 helper - but he had to get on with his own life.