Thread: RPATHS - edit them by hand? a helpful tool
View Single Post
Old 09-01-2012, 10:24 AM   #8
knc1
Going Viral
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: 17,212
Karma: 18210809
Join Date: Feb 2012
Location: Central Texas
Device: No K1, PW2, KV, KOA
Quote:
Originally Posted by twobob View Post
Fair enough. I closed the error with relevant grovelling.

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

: )
You hit them at just the right time, the BR release is less that 24 hours old:
http://git.buildroot.net/buildroot/

What usually happens next, is that the branch buildroot-next will get merged to mainline ;
And then the things that accumulated while trying to get the release made will get a closer read.

If you are subscribed to the mailing list - you should be getting copies of all bug-report postings.

{brag}
That was my idea, to register the mailing list as a follower of all bug-reports.
{/brag}

EDIT:
Here is one patch already that would effect anyone using the Linaro tool chain posted in the DIY-KeK resource pool:
http://git.buildroot.net/buildroot/c...3d64d12b24469e
Last edited by knc1; 09-01-2012 at 10:29 AM.
knc1 is offline   Reply With Quote