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

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

[bugzilla at busybox.net]

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.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Buildroot] [Bug 10071] [PATCH] fakeroot: replace hard-coded paths in post install

[bugzilla at busybox.net]

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

--- Comment #1 from Stefan Becker <chemobejk@gmail.com> ---
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.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Buildroot] [Bug 10071] [PATCH] fakeroot: replace hard-coded paths in post install

[bugzilla at busybox.net]

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

Thomas Petazzoni <thomas.petazzoni@free-electrons.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         Resolution|---                         |FIXED
             Status|NEW                         |RESOLVED

--- Comment #2 from Thomas Petazzoni <thomas.petazzoni@free-electrons.com> ---
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.

-- 
You are receiving this mail because:
You are on the CC list for the bug.