From: Kent Gibson <warthog618@gmail.com>
To: Bartosz Golaszewski <brgl@bgdev.pl>
Cc: "open list:GPIO SUBSYSTEM" <linux-gpio@vger.kernel.org>,
Linus Walleij <linus.walleij@linaro.org>,
Viresh Kumar <viresh.kumar@linaro.org>,
Vincent Fazio <vfazio@gmail.com>
Subject: Re: [ANNOUNCE] libgpiod v2.2-rc2
Date: Thu, 3 Oct 2024 17:16:08 +0800 [thread overview]
Message-ID: <20241003091608.GA246042@rigel> (raw)
In-Reply-To: <CAMRc=Mcut2sGzac6vN2cvGP-DHtgC12BXksTvmcQNBaf_VvpZA@mail.gmail.com>
On Thu, Oct 03, 2024 at 11:06:34AM +0200, Bartosz Golaszewski wrote:
> On Thu, Oct 3, 2024 at 10:55 AM Kent Gibson <warthog618@gmail.com> wrote:
> >
> > On Thu, Oct 03, 2024 at 10:45:35AM +0200, Bartosz Golaszewski wrote:
> > > On Thu, Oct 3, 2024 at 5:36 AM Kent Gibson <warthog618@gmail.com> wrote:
> > > >
> > > >
> > > >
> > > > Why is gpiosim-glib being built? I'm not using glib. I don't have
> > > > glib. I don't want to install glib. But now I can't build. Yay.
> > > >
> > > > Cheers,
> > > > Kent.
> > > >
> > > >
> > >
> > > That wasn't the goal of course. Let me build a vm with minimal
> > > environment and go through each build option individually.
> > >
> >
> > It was the --enable-tests that pulled in glib for core tests - despite
> > --enable-glib not being selected. I was able to build everything else
> > without glib by dropping --enable-tests.
> >
>
> Ah, yes but it has been this way for a long time, the test harness uses GLib.
>
I haven't done a build for quite some time - at least none that
involved --enable-tests, so news to me.
Cheers,
Kent.
prev parent reply other threads:[~2024-10-03 9:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-02 13:31 [ANNOUNCE] libgpiod v2.2-rc1 Bartosz Golaszewski
2024-10-02 17:50 ` [ANNOUNCE] libgpiod v2.2-rc2 Bartosz Golaszewski
2024-10-03 3:24 ` Kent Gibson
2024-10-03 3:36 ` Kent Gibson
2024-10-03 8:45 ` Bartosz Golaszewski
2024-10-03 8:55 ` Kent Gibson
2024-10-03 9:06 ` Bartosz Golaszewski
2024-10-03 9:16 ` Kent Gibson [this message]
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=20241003091608.GA246042@rigel \
--to=warthog618@gmail.com \
--cc=brgl@bgdev.pl \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=vfazio@gmail.com \
--cc=viresh.kumar@linaro.org \
/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;
as well as URLs for NNTP newsgroup(s).