From: Michael Olbrich <m.olbrich@pengutronix.de>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] libblkid
Date: Mon, 11 Jun 2018 16:59:12 +0200 [thread overview]
Message-ID: <20180611145912.7aim6rdvbms25xyl@pengutronix.de> (raw)
In-Reply-To: <HE1PR0702MB3804B0C13CAE9E444A440C5498780@HE1PR0702MB3804.eurprd07.prod.outlook.com>
Hi,
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 my conclusion is that ptxdist can't build libblkid without a corresponding
> rule/libblkid.make, should one be written?
> Currently I just made udev.make select UTIL_LINUX_NG but it doesn't seem
> right to me.
udev.in not udev.make, right? For your PTXdist version that's the correct
solution. At least I think so, I barely remember that this version ever
existed... ;-)
Regards,
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
next prev parent reply other threads:[~2018-06-11 14:59 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
2018-06-11 9:29 ` Jakov Simunic
2018-06-11 9:48 ` Alexander Dahl
2018-06-11 14:59 ` Michael Olbrich [this message]
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=20180611145912.7aim6rdvbms25xyl@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