From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Building Network Manager fails at configure due to uuid package requirements error
Date: Tue, 23 May 2017 15:26:52 +0200 [thread overview]
Message-ID: <20170523152652.0b449cbe@free-electrons.com> (raw)
In-Reply-To: <CADj18OV=YojdFc_mYeHjf0zuQzec3e=ivO=B78=m9T1NVqeEnQ@mail.gmail.com>
Hello,
On Tue, 23 May 2017 08:35:52 +0000, Pascal K wrote:
> Here some console output:
> $make
> ...
> build/buildroot-config/conf --silentoldconfig Config.in
> >>> network-manager 1.4.2 Configuring
> ...
> checking for LIBNL... yes
> checking for UUID... no
> configure: error: Package requirements (uuid) were not met:
>
> Package uuid was not found in the pkg-config search path.
> Perhaps you should add the directory containing `uuid.pc'
> to the PKG_CONFIG_PATH environment variable
> Package 'uuid', required by 'world', not found
>
> Consider adjusting the PKG_CONFIG_PATH environment variable if you
> installed software in a non-standard prefix.
>
> Alternatively, you may set the environment variables UUID_CFLAGS
> and UUID_LIBS to avoid the need to call pkg-config.
> See the pkg-config man page for more details.
>
> Parts of my config, which I thought should do the trick with the uuid:
> BR2_PACKAGE_UTIL_LINUX=y
> BR2_PACKAGE_UTIL_LINUX_LIBBLKID=y
> # BR2_PACKAGE_UTIL_LINUX_LIBMOUNT is not set
> # BR2_PACKAGE_UTIL_LINUX_LIBSMARTCOLS is not set
> BR2_PACKAGE_UTIL_LINUX_LIBUUID=y
Can you reproduce after a full rebuild, i.e "make clean all" ?
If so, could you please provide a complete .config file that reproduces
the issue ?
Thanks,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2017-05-23 13:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-23 8:35 [Buildroot] Building Network Manager fails at configure due to uuid package requirements error Pascal K
2017-05-23 13:26 ` Thomas Petazzoni [this message]
2017-05-23 14:40 ` Pascal K
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=20170523152652.0b449cbe@free-electrons.com \
--to=thomas.petazzoni@free-electrons.com \
--cc=buildroot@busybox.net \
/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