linux-gpio.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
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 11:36:40 +0800	[thread overview]
Message-ID: <20241003033640.GB63612@rigel> (raw)
In-Reply-To: <20241003032457.GA63612@rigel>

On Thu, Oct 03, 2024 at 11:24:57AM +0800, Kent Gibson wrote:
> On Wed, Oct 02, 2024 at 07:50:04PM +0200, Bartosz Golaszewski wrote:
> > On Wed, Oct 2, 2024 at 3:31 PM Bartosz Golaszewski <brgl@bgdev.pl> wrote:
> > >
> > > I've just tagged and pushed out the first release candidate for libgpiod v2.2.
> > >
> > > It's a big release that - next to an assortment of smaller
> > > improvements and bug-fixes - brings in a big new feature: D-Bus daemon
> > > and command-line client together with GObject bindings to core
> > > libgpiod.
> > >
> > > It's in good enough shape to now focus on ironing out the creases and
> > > make it available in the following weeks.
> > >
> > > The tarball and git tree are in their usual places[1][2].
> > >
> > > Bart
> > >
> > > [1] https://mirrors.edge.kernel.org/pub/software/libs/libgpiod/
> > > [2] git://git.kernel.org/pub/scm/libs/libgpiod/libgpiod.git
> >
> > Well, that wasn't very good, rc1 had a build issue in the tarball. I
> > had to fix it up and release rc2 which now builds fine in yocto.
> >
>
> I'm trying to do a build without any glib related targets:
>
> ./autogen.sh --prefix=/usr/local --enable-bindings-python --enable-bindings-cxx --enable-tools --enable-tests --enable-gpioset-interactive --enable-examples
>
> but I get:
>
> checking for glib-2.0 >= 2.50... no
> configure: error: Package requirements (glib-2.0 >= 2.50) were not met:
>
> Package 'glib-2.0', required by 'virtual:world', not found
>
>
> Why is glib now required?
>

Similarly (after commenting out the GLIB and GIO checks tripping above):

Making all in gpiosim-glib
make[3]: Entering directory '/home/pi/libgpiod/tests/gpiosim-glib'
  CC       gpiosim-glib.lo
In file included from gpiosim-glib.c:9:
gpiosim-glib.h:7:10: fatal error: gio/gio.h: No such file or directory
    7 | #include <gio/gio.h>
      |          ^~~~~~~~~~~


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.



  reply	other threads:[~2024-10-03  3:36 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 [this message]
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

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=20241003033640.GB63612@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).