From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Unable to build an image with systemd
Date: Mon, 30 Oct 2017 15:35:10 +0100 [thread overview]
Message-ID: <20171030153510.35066d4a@windsurf> (raw)
In-Reply-To: <CAJCNcEb8aemsJ3YrRwK78mv_XTAOsTx54mWaGBoy22uF6zAynA@mail.gmail.com>
Hello,
On Mon, 30 Oct 2017 13:57:24 +0100, Gorka Lertxundi wrote:
> Yesterday I run into this issue I didn't know how to proceed, can anyone
> help me?
>
> configure: error: *** libmount support required but libraries not found
> package/pkg-generic.mk:217: recipe for target
> '/buildroot-src/output/build/systemd-234/.stamp_configured' failed
> make: *** [/buildroot-src/output/build/systemd-234/.stamp_configured] Error
> 1
Could you please provide a simple Buildroot .config that exhibits the
issue ?
> Cross compiling to ARM using the 2017.08.1 release which supposedly has the
> systemd and libmount issue solved long time ago[1]. I don't know how it's
> possible my build is outputting that all the time.
>
> systemd uses pkg-config to check if libmount exists and, as expected, using
> the host-deployed pkg-config wasn't able to find it.
Why "as expected" ?
> I manually created mount.pc in
> "output/host/arm-buildroot-linux-gnueabihf/sysroot/usr/lib/pkgconfig/mount.pc"
Why would you do this? It should have been installed by util-linux.
When reporting bug reports, please always include a Buildroot .config
file that allows to reproduce the issue. Also, make sure that the
problem is reproducible after a full clean build, i.e when doing "make
clean all".
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2017-10-30 14:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-30 12:57 [Buildroot] Unable to build an image with systemd Gorka Lertxundi
2017-10-30 14:35 ` Thomas Petazzoni [this message]
2017-10-30 15:14 ` Gorka Lertxundi
2017-10-30 22:11 ` Peter Korsgaard
2017-10-30 22:35 ` Gorka Lertxundi
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=20171030153510.35066d4a@windsurf \
--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