From: Alexander Dahl <post@lespocky.de>
To: ptxdist@pengutronix.de
Cc: Jakov Simunic <jakov.simunic@ericsson.com>
Subject: Re: [ptxdist] libblkid
Date: Mon, 11 Jun 2018 09:53:00 +0200 [thread overview]
Message-ID: <20180611075300.lhigwv5wpnltz4b5@falbala.home.lespocky.de> (raw)
In-Reply-To: <HE1PR0702MB3804B0C13CAE9E444A440C5498780@HE1PR0702MB3804.eurprd07.prod.outlook.com>
[-- Attachment #1.1: Type: text/plain, Size: 1595 bytes --]
Hello Jakov
On Mon, Jun 11, 2018 at 07:34:04AM +0000, Jakov Simunic wrote:
> I am confused about rules/libblkid.in, there is no corresponding
> rules/libblkid.make file, I use this to build udev, but it fails
> this way when i do the following:
>
> ./ptxdist clean
> ./ptxdist compile udev
>
> It fails in the configure with the error: checking for BLKID... not found
> However, it builds when i first do this:
>
> ./ptxdist clean
> ./ptxdist targetinstall util-linux-ng
> ./ptxdist compile udev
So udev seems to require libblkid, but for some reason no suitable
libblkid is built before compiling udev.
This may get interesting, because both libblkid and udev are virtual
packages (which lack documentation)?
> So my conclusion is that ptxdist can't build libblkid without a
> corresponding rule/libblkid.make, should one be written?
No.
> Currently I just made udev.make select UTIL_LINUX_NG but it doesn't seem right to me.
Neither to me. In ptxdist master UDEV_LEGACY selects (the virtual)
LIBBLKID and SYSTEMD also selects LIBBLKID. LIBBLKID itself selects
UTIL_LINUX_NG and UTIL_LINUX_NG_LIBBLKID. So that all looks good to
me.
Which ptxdist version are you using? Did you compare the
rules/libblkid.in and rules/udev.in to current master?
Greets
Alex
--
/"\ ASCII RIBBON | »With the first link, the chain is forged. The first
\ / CAMPAIGN | speech censured, the first thought forbidden, the
X AGAINST | first freedom denied, chains us all irrevocably.«
/ \ HTML MAIL | (Jean-Luc Picard, quoting Judge Aaron Satie)
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
[-- Attachment #2: Type: text/plain, Size: 91 bytes --]
_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de
next prev parent reply other threads:[~2018-06-11 7:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-11 7:34 Jakov Simunic
2018-06-11 7:53 ` Alexander Dahl [this message]
2018-06-11 9:29 ` Jakov Simunic
2018-06-11 9:48 ` Alexander Dahl
2018-06-11 14:59 ` Michael Olbrich
2018-06-12 7:14 ` Jakov Simunic
2018-06-12 9:32 ` Michael Olbrich
2018-06-12 11:14 ` Jakov Simunic
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=20180611075300.lhigwv5wpnltz4b5@falbala.home.lespocky.de \
--to=post@lespocky.de \
--cc=jakov.simunic@ericsson.com \
--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