Skip to contentSkip to conversation

New: [PATCH] fakeroot: replace hard-coded paths in post install

Buildroot New bugzilla at busybox.net 1 participant 3 messages Jul 14, 2017 – Aug 2, 2017

lore
Share & tools
lore
#0 lore raw

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

Bug ID: 10071
Summary: [PATCH] fakeroot: replace hard-coded paths in post
install
Product: buildroot
Version: unspecified
Hardware: All
OS: Linux
Status: NEW
Severity: normal
Priority: P5
Component: Other
Assignee: unassigned at buildroot.uclibc.org
Reporter: chemobejk at gmail.com
CC: buildroot at uclibc.org
Target Milestone: ---

Created attachment 7116
--> https://bugs.busybox.net/attachment.cgi?id=7116&action=edit
patch for branch master

fakeroot script has the absolute path to the host tools directory encoded in it. It will therefore fail if a developer downloads a build e.g. from an automated build system and unpacks it at a different location locally.

The attached patch for branch "master" adds a host post install step that replaces the absolute path with ${HOST_DIR}. The same solution should be easy to backport to older branches too.

Signature · 2 lines
You are receiving this mail because:
You are on the CC list for the bug.
#1 lore raw

PATCH 1/1 fakeroot: replace hard-coded paths in post install

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

--- Comment #1 from Stefan Becker <[email protected]> --- Created attachment 7121
--> https://bugs.busybox.net/attachment.cgi?id=7121&action=edit
patch for branch 2017.05.x (and older)

Older branches install fakeroot into ${HOST_DIR}/usr/bin instead of ${HOST_DIR}/bin.

Signature · 2 lines
You are receiving this mail because:
You are on the CC list for the bug.
#2 lore raw

PATCH 1/1 fakeroot: replace hard-coded paths in post install

In reply to bugzilla at busybox.net

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

Thomas Petazzoni <[email protected]> changed:

What |Removed |Added
----------------------------------------------------------------------------

         Resolution|---                         |FIXED
             Status|NEW                         |RESOLVED

--- Comment #2 from Thomas Petazzoni <[email protected]> --- This issue has been fixed by the relocatable SDK work. The idea is that after a build, you run "make sdk", which prepares the SDK to be relocable. Then you can move the contents of output/host/ around, you can tarball it and share it with other developers. output/host contains a relocate-sdk.sh script, which one must run before using the SDK. This script will adjust the hardcoded paths as needed.

Signature · 2 lines
You are receiving this mail because:
You are on the CC list for the bug.