Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 10071] New: [PATCH] fakeroot: replace hard-coded paths in post install
Date: Fri, 14 Jul 2017 19:17:27 +0000	[thread overview]
Message-ID: <bug-10071-163@https.bugs.busybox.net/> (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.

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

             reply	other threads:[~2017-07-14 19:17 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-14 19:17 bugzilla at busybox.net [this message]
2017-07-14 21:04 ` [Buildroot] [Bug 10071] [PATCH] fakeroot: replace hard-coded paths in post install bugzilla at busybox.net
2017-08-02 20:48 ` bugzilla at busybox.net

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-10071-163@https.bugs.busybox.net/ \
    --to=bugzilla@busybox.net \
    --cc=buildroot@busybox.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox