All of lore.kernel.org
 help / color / mirror / Atom feed
From: orbea <orbea@riseup.net>
To: Bartosz Golaszewski <brgl@bgdev.pl>
Cc: linux-gpio@vger.kernel.org
Subject: Re: [PATCH] bindings: cxx: link using the libtool archives
Date: Wed, 20 Mar 2024 09:00:46 -0700	[thread overview]
Message-ID: <20240320090046.19dc31f5@Akita> (raw)
In-Reply-To: <CAMRc=MezeyGEgVm54HYwPRvdid=r66YEv9dh647jYLuYTAWd9Q@mail.gmail.com>

On Wed, 20 Mar 2024 16:18:38 +0100
Bartosz Golaszewski <brgl@bgdev.pl> wrote:

> On Wed, Mar 20, 2024 at 2:50 PM <orbea@riseup.net> wrote:
> >
> > From: orbea <orbea@riseup.net>
> >
> > When linking with internal dependencies that were built with
> > libtool the most reliable method is to use the libtool archive
> > (.la) files.
> >
> > When building with slibtool it fails when it doesn't find the
> > -lgpiod linker flag, but if libgpiod is already installed to the
> > system it will be built using the system version instead of the
> > newly built libraries.
> >
> > Gentoo issue: https://bugs.gentoo.org/913899
> >
> > Signed-off-by: orbea <orbea@riseup.net>
> > ---  
> 
> Thanks,
> 
> Could you use your real name for the sake of code attribution (if we
> need a license change later on or whatever)?
> 
> Bart

If its possible I would really prefer to not, my change is trivial and
I do not think it is significant enough to claim copyright.

So that I could easily link to it in the Gentoo issue I also made an
github PR which is gpg signed if that helps?

https://github.com/brgl/libgpiod/pull/65

  reply	other threads:[~2024-03-20 16:01 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-20 13:49 [PATCH] bindings: cxx: link using the libtool archives orbea
2024-03-20 15:18 ` Bartosz Golaszewski
2024-03-20 16:00   ` orbea [this message]
2024-03-20 16:42     ` Bartosz Golaszewski
2024-03-20 16:43 ` Bartosz Golaszewski
2024-03-21 13:34   ` orbea
2024-03-21 15:00     ` Bartosz Golaszewski

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=20240320090046.19dc31f5@Akita \
    --to=orbea@riseup.net \
    --cc=brgl@bgdev.pl \
    --cc=linux-gpio@vger.kernel.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 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.