From: Michael Olbrich <m.olbrich@pengutronix.de>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] targetinstall fails
Date: Thu, 8 Jan 2015 12:33:22 +0100 [thread overview]
Message-ID: <20150108113322.GC31136@pengutronix.de> (raw)
In-Reply-To: <CAMwGMjwfgRpUqR3WgcckF0GpnCXYiyeL+psw2w-TDHPyJ8d3Lw@mail.gmail.com>
On Fri, Jan 02, 2015 at 09:36:10AM -0500, Jon Ringle wrote:
> On Fri, Jan 2, 2015 at 9:28 AM, Jon Ringle <jon@ringle.org> wrote:
>
> > On Wed, Dec 31, 2014 at 7:55 AM, Michael Olbrich <m.olbrich@pengutronix.de
> > > wrote:
> >
> >> On Wed, Dec 31, 2014 at 01:57:17AM -0500, Jon Ringle wrote:
> >> > Changing the /bin/sh link to point to bash instead of dash fixed this
> >> for me
> >> >
> >> > On Tue, Dec 30, 2014 at 2:02 PM, Jon Ringle <jon@ringle.org> wrote:
> >> >
> >> > > I'm setting up a new machine with Ubuntu-14.04 where I'll be doing
> >> ptxdist
> >> > > builds. I'm running into a problem where the targetinstall step fails
> >> on
> >> > > all packages with something like the following (I added 'set -x' to
> >> the
> >> > > fakeroot script for debugging purposes):
> >> [...]
> >>
> >> I think I saw this at some point, but then it worked again and I never
> >> made
> >> a patch. Does this help?
> >>
> >> Michael
> >>
> >> diff --git a/rules/host-fakeroot.make b/rules/host-fakeroot.make
> >> index 53236194a582..3fb699a56759 100644
> >> --- a/rules/host-fakeroot.make
> >> +++ b/rules/host-fakeroot.make
> >> @@ -30,6 +30,10 @@ HOST_FAKEROOT_DIR :=
> >> $(HOST_BUILDDIR)/$(HOST_FAKEROOT)
> >> # Prepare
> >> #
> >> ----------------------------------------------------------------------------
> >>
> >> +HOST_FAKEROOT_CONF_ENV := \
> >> + $(HOST_ENV) \
> >> + CONFIG_SHELL=/bin/bash
> >> +
> >> HOST_FAKEROOT_CONF_TOOL := autoconf
> >> HOST_FAKEROOT_CONF_OPT := \
> >> $(HOST_AUTOCONF) \
> >>
> >
> > I reproduced the problem by restoring the sh link to point back to dash
> > again and then applied this patch. Starting a build after a complete clean
> > again, this patch did not help :(
> >
> >
> Ahh... however, I just realized that I had a host-fakeroot-*-dev.tar.gz
> package that my build was using. After removing that so that ptxdist would
> rebuild host-fakeroot again, it is now having a positive effect :)
I've pushed a patch for this. Thanks for testing.
Michael
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
--
ptxdist mailing list
ptxdist@pengutronix.de
prev parent reply other threads:[~2015-01-08 11:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-30 19:02 Jon Ringle
2014-12-31 6:57 ` Jon Ringle
2014-12-31 12:55 ` Michael Olbrich
2015-01-02 14:28 ` Jon Ringle
2015-01-02 14:36 ` Jon Ringle
2015-01-08 11:33 ` Michael Olbrich [this message]
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=20150108113322.GC31136@pengutronix.de \
--to=m.olbrich@pengutronix.de \
--cc=ptxdist@pengutronix.de \
/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