All of lore.kernel.org
 help / color / mirror / Atom feed
From: Trevor Woerner <twoerner@gmail.com>
To: Khem Raj <raj.khem@gmail.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] libcap-ng:upgrade 0.7.9 -> 0.7.10
Date: Fri, 25 Oct 2019 09:22:04 -0400	[thread overview]
Message-ID: <20191025132204.GB19333@linux-uys3> (raw)
In-Reply-To: <20191024230510.smxm7zf3qvpec3xy@apollo.localdomain>

On Thu 2019-10-24 @ 04:05:10 PM, Khem Raj wrote:
> perhaps you need to add -pthread to LDFLAGS

That's what it feels like.
I'll set up a test build.

I'm pretty sure I've stumbled across this in the past, but it seems like
different distros package the crypto things differently, therefore building on
some distros require linking to one set of libraries, and building on other
distros require linking to a different set. Does that seem right?

Is there a mechanism for telling OE to tweak a parameter based on the distro
on which it is building? A distro override of some sort?


  reply	other threads:[~2019-10-25 13:22 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-21  5:50 [PATCH] libcap-ng:upgrade 0.7.9 -> 0.7.10 Zang Ruochen
2019-10-24 13:06 ` Trevor Woerner
2019-10-24 13:37   ` Trevor Gamblin
2019-10-25  0:19     ` akuster808
2019-10-25  5:30       ` zangrc
2019-10-25 13:17         ` Trevor Woerner
2019-10-25 13:31           ` Trevor Gamblin
2019-10-26  9:06         ` Khem Raj
2019-10-24 23:05   ` Khem Raj
2019-10-25 13:22     ` Trevor Woerner [this message]
2019-10-25 13:44       ` Trevor Woerner
2019-10-25 14:37         ` akuster808
2019-10-25 15:16           ` Trevor Woerner
2019-10-25 15:44             ` Trevor Gamblin
2019-10-25 17:22               ` Trevor Woerner
2019-10-25 17:24           ` Trevor Woerner
2019-10-25 21:38             ` Trevor Woerner
2019-10-26  9:35               ` akuster808
2019-10-25 17:01         ` Khem Raj
2019-10-25 17:23           ` Trevor Woerner

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=20191025132204.GB19333@linux-uys3 \
    --to=twoerner@gmail.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=raj.khem@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 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.