From: Juergen Borleis <jbe@pengutronix.de>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] Build system doesn't find host compiled packages
Date: Tue, 23 Jun 2015 10:49:23 +0200 [thread overview]
Message-ID: <201506231049.23731.jbe@pengutronix.de> (raw)
In-Reply-To: <201506230912.26642.jbe@pengutronix.de>
Hi Jean-Philippe,
On Tuesday 23 June 2015 09:12:26 Juergen Borleis wrote:
> On Monday 22 June 2015 16:17:38 jean-philippe francois wrote:
> > 2015-06-22 11:33 GMT+02:00 jean-philippe francois <jp.francois@cynove.com>:
> > > I installed 2015.06.0 today, and my project (migrated from a 2011.12
> > > project) now stops when compiling host-fakeroot with the following
> > > message :
> > >
> > > In file included from libfakeroot.c:223:0:
> > > wrapped.h:126:27: error: unknown type name 'cap_user_header_t'
> > > extern int (*next_capset)(cap_user_header_t hdrp, const
> > > cap_user_data_t datap);
>
> Fakeroot's dependency to LIBCAP is part of PTXdist since commit
> 0f43c449de4a6b769d5b49720c48bc57716c1b8b. So I wonder why it fails at your
> side, because it is part of the June release.
>
> > > It is my understanding that this message comes from a missing libcap,
> > > but host-libcap has been succesfuly build.
> > > I have had a similar problem with host-acl that could not find the
> > > just built host-attr. This previous problem was solved by installing
> > > the libattr-devel package, but the point of ptxdist is precisely to
> > > avoid installing system packages.
> > >
> > > Can you help me debug this issue ? I suspect I forgot something when
> > > migrating from the old project.
> >
> > After a ptxdist clean, going straight to ptxdist kernelconfig is not
> > the right thing to do !
>
> Hmm, this should work as expected.
It really should... but it doesn't. You found a bug in PTXdist. It also crashes
here, and only if you start a "ptxdist kernelconfig" on a clean BSP.
> > Starting with ptxdist go instead.
>
> Sounds more like a workaround, not a solution.
You must continue to use this workaround, until we find a solution.
Regards,
Juergen
--
Pengutronix e.K. | Juergen Borleis |
Industrial Linux Solutions | http://www.pengutronix.de/ |
--
ptxdist mailing list
ptxdist@pengutronix.de
next prev parent reply other threads:[~2015-06-23 8:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-22 9:33 jean-philippe francois
2015-06-22 14:17 ` jean-philippe francois
2015-06-23 7:12 ` Juergen Borleis
2015-06-23 8:49 ` Juergen Borleis [this message]
2015-06-23 13:58 ` Juergen Borleis
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=201506231049.23731.jbe@pengutronix.de \
--to=jbe@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