From: Michael Olbrich <m.olbrich@pengutronix.de>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] libnl3 -dev.tar.gz package polluted with host tools
Date: Mon, 24 Oct 2016 09:34:52 +0200 [thread overview]
Message-ID: <20161024073452.3ovwh7hwnj4gsfsw@pengutronix.de> (raw)
In-Reply-To: <alpine.DEB.2.10.1610211134240.7667@jring-w510-7m3g.gridpoint.com>
On Fri, Oct 21, 2016 at 11:37:24AM -0400, Jon Ringle wrote:
> On Fri, 21 Oct 2016, Jon Ringle wrote:
> > I ran into a problem building libnl3 with ptxdist-2016.10.0
> > My build uses the *-dev.tar.gz packages to avoid having to build
> > everything. However, it appears that m4 that was built on different
> > machine is being used with the absolute path to m4 that is not valid on
> > the laptop I am building on.
I didn't get this mail. Was this sent to the list?
> I worked around this with `ptxdist clean host-flex` and deleting the
> host-flex-2.5.39-arm-*-dev.tar.gz package that was built from the other
> machine.
It would be great if we could figure out why this breaks. Can you check? If
this cannot be fixed we should set 'HOST_FLEX_DEVPKG := NO'.
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:[~2016-10-24 7:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <alpine.DEB.2.10.1610210836040.7667@jring-w510-7m3g.gridpoint.com>
2016-10-21 15:37 ` Jon Ringle
2016-10-24 7:34 ` 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=20161024073452.3ovwh7hwnj4gsfsw@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