From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] package/fontconfig: Fix UUIDD dependency
Date: Tue, 24 Dec 2019 15:08:30 +0100 [thread overview]
Message-ID: <20191224150830.64614643@windsurf> (raw)
In-Reply-To: <CAOf5uwmcedGDiFR5mXAT16siS0XTd=mYW8dwR20_y8BwNWAzAg@mail.gmail.com>
On Tue, 24 Dec 2019 14:39:12 +0100
Michael Nazzareno Trimarchi <michael@amarulasolutions.com> wrote:
> I created the config in two steps. Now I'm thinking that was only
> happen after I have added the XORG
> and OPENJDK. I have added this two components without re-build from
> scratch. Basically libconfig was looking for uuid and fail
> to find in the filesystem. I was thinking looking at the config.in
> that the right thing to do is adding
> that one instead of LIBUIID. I'm checking now
This feels like you did some partial build: util-linux was first build
with libuuid, and then you enabled something that needed libuuid,
without doing a full rebuild, or at least without forcing the rebuild
of util-linux.
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2019-12-24 14:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-24 11:23 [Buildroot] [PATCH] package/fontconfig: Fix UUIDD dependency Michael Trimarchi
2019-12-24 12:45 ` Thomas Petazzoni
2019-12-24 12:56 ` Michael Nazzareno Trimarchi
2019-12-24 13:36 ` Thomas Petazzoni
2019-12-24 13:39 ` Michael Nazzareno Trimarchi
2019-12-24 14:08 ` Thomas Petazzoni [this message]
2019-12-24 14:12 ` Michael Nazzareno Trimarchi
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=20191224150830.64614643@windsurf \
--to=thomas.petazzoni@bootlin.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.