linux-gpio.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Seamus de Mora <seamusdemora@gmail.com>
To: Kent Gibson <warthog618@gmail.com>
Cc: linux-gpio@vger.kernel.org
Subject: Re: [libgpiod] help with GPIOSET_INTERACTIVE
Date: Fri, 29 Dec 2023 19:50:21 -0600	[thread overview]
Message-ID: <CAJ8C1XP2xeTRvJRpvmd8VD4RGYQTH4qWQdMocmNVgRWkmSDscQ@mail.gmail.com> (raw)
In-Reply-To: <20231229155837.GA103278@rigel>

On Fri, Dec 29, 2023 at 9:58 AM Kent Gibson <warthog618@gmail.com> wrote:
>
> On Fri, Dec 29, 2023 at 03:14:04AM -0600, Seamus de Mora wrote:
> > I'm trying to add the 'GPIOSET_INTERACTIVE' definition to 'gpioset.c':
> > I've installed 'libeditline-dev' and 'libedit-dev' via apt; each
> > separately, and then both
> >
> > Can someone explain how to add GPIOSET_INTERACTIVE & compile successfully?

> You don't specify your platform and what you've done to get this far -
> you provide the output you are seeing but not the inputs.
> It is apparently a Pi, but the distro and version would be helpful,
> as well as the build commands themselves.
>
> Have you read the BUILDING section of the README?
> How are you performing the build? I would expect autoconf to choke
> if it can't find the required headers before it even gets to the actual
> compile step.

Yes - I read the BUILDING section of the README. When I initially
installed this, I was trying to follow "the RPi way" of doing things,
and I used these commands:

$ ./autogen.sh --enable-tools=yes --prefix=/usr/lib/arm-linux-gnueabihf
$ make
$ sudo make install

This was done on an RPi 3A+, running "raspbian/RPi OS", release
"bullseye", kernel ver "6.1.21-v7+"
Why '/usr/lib/arm-linux-gnueabihf'?
    Because that's where the older ver 1.6.X version of 'libgpiod' &
the "tools" were installed.
Of course that had no effect on my issue, but just so you know.

Also: I was trying to re-compile 'gpioset' from the
'~/libgpiod-2.1/tools' folder, using 'make' - as explained below.

> This works for me on a Pi, both bullseye and bookworm:
>
> $ ./autogen.sh --enable-tools --enable-gpioset-interactive
> $ make

That option ('--enable-gpioset-interactive') seems to have gotten the
job done. I had to back out of 'libgpiod-2.1/tools' to
'~/libgpiod-2.1', and let './autogen.sh' take care of the '#define'...
instead of me trying to add it manually to 'gpioset.c' via '#define
GPIOSET_INTERACTIVE'.  I do have **all** the packages you listed below
installed, so why my manual addition didn't work is still a mystery to
me - but not one worth fretting over.

> That is with the following packages installed:
>  autoconf
>  autoconf-archive
>  libtool
>  m4
>  libedit-dev

Thanks for your help!   :)
~S

  reply	other threads:[~2023-12-30  1:51 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-29  9:14 help with GPIOSET_INTERACTIVE Seamus de Mora
2023-12-29 15:58 ` [libgpiod] " Kent Gibson
2023-12-30  1:50   ` Seamus de Mora [this message]
2023-12-30  2:21     ` Kent Gibson
2023-12-30  4:43       ` Seamus de Mora
2023-12-30  5:03         ` Kent Gibson
2023-12-30  5:45           ` Seamus de Mora
2023-12-30  5:53             ` Kent Gibson
2023-12-30  6:25               ` Seamus de Mora
2023-12-30  6:29                 ` Kent Gibson
2023-12-30  6:36                   ` Seamus de Mora
2023-12-30  6:43                     ` Kent Gibson
2023-12-30  6:49                       ` Seamus de Mora
2023-12-30  6:51                         ` Kent Gibson
2023-12-30  6:56                           ` Seamus de Mora

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=CAJ8C1XP2xeTRvJRpvmd8VD4RGYQTH4qWQdMocmNVgRWkmSDscQ@mail.gmail.com \
    --to=seamusdemora@gmail.com \
    --cc=linux-gpio@vger.kernel.org \
    --cc=warthog618@gmail.com \
    /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).