[Buildroot] [Bug 7172] Name collision of rpath token expansion and internal variables

bugzilla at busybox.net bugzilla at busybox.net
Sun Jun 8 16:48:49 UTC 2014


https://bugs.busybox.net/show_bug.cgi?id=7172

--- Comment #7 from Samuel Martin <s.martin49 at gmail.com> 2014-06-08 16:48:49 UTC ---
(In reply to comment #6)
> (In reply to comment #5)
> > Is what you wrote here correct? (No copy paste error?) Case one and two are
> > identical?
> > Have you tried four dollar signs? Depending on how things are parsed it may be
> > needed...
> >
> 
> Yup - not what I expected either.*
> 
> Will recheck for cockpit error here and the $$$$ case.

Well, I've already spent hours trying to figure out the right escape
sequence... in vain :-(

I even ended up with some mad sequences of '$' and '\'.
[1] is just an example of the dirty things I tried! My advice: don't go there
;-).

To me, escaping '$' is a dead end (or at least, really hard, except fo
CMake-based packages) because of:
- the make/shell escape character is '$' vs. '\';
- the unpredictable (or hard-to-predict) level/number of make/shell nested,
even for packages using the autotools (Makefile + libtool + ... + custom
commands).

That's why I end up thinking that a solution based on chrpath or patchelf is
the only sane way of handling the '$ORIGIN' support in RPATH (for both target
and host packages).

BTW, this is part of the "relocatable SDK" item, which is somewhere in my todo
list. I have a couple of branches (maybe more than just a couple) in my github
in which I test things from time to time, and that one day, I should gather and
post a real RFC.


[1]
https://github.com/tSed/buildroot/commit/7d53fe664afd3c98b3609994c5bf2addf2f4f692

-- 
Configure bugmail: https://bugs.busybox.net/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.


More information about the buildroot mailing list