Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Koen Kooi <koen@dominion.thruhere.net>,
	openembedded-core@lists.openembedded.org
Cc: Koen Kooi <koen.kooi@linaro.org>
Subject: Re: [PATCH 2/3] bind: fix openSSL detection when using multiarch
Date: Mon, 09 Apr 2018 17:36:32 +0100	[thread overview]
Message-ID: <1523291792.2942.100.camel@linuxfoundation.org> (raw)
In-Reply-To: <20180409115657.16651-2-koen.kooi@linaro.org>

On Mon, 2018-04-09 at 13:56 +0200, Koen Kooi wrote:
> In multiarch /usr/include and /usr/lib/<tuple/ are not on the same
> level anymore. This change will pass a correct includedir, but a
> wrong libdir, but the linker picks it up anyway.
> 
> Tested on multiarch and regular build.

How far off working is mulitarch for OE-Core?

The reason I ask is I'd like to understand the scope of the changes
needed to support it. It also influences whether these are sumo or post
2.5 changes.

Cheers,

Richard


  reply	other threads:[~2018-04-09 16:36 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-09 11:56 [PATCH 1/3] libcap: fix (base_)libdir usage Koen Kooi
2018-04-09 11:56 ` [PATCH 2/3] bind: fix openSSL detection when using multiarch Koen Kooi
2018-04-09 16:36   ` Richard Purdie [this message]
2018-04-11  9:25     ` Koen Kooi
2018-04-12  9:47       ` Koen Kooi
2018-04-09 11:56 ` [PATCH 3/3] python 2.7: fix multilib patch to accept multiarch style paths Koen Kooi
2018-04-09 12:33   ` Koen Kooi
2018-04-10 13:13 ` [PATCH 1/3] libcap: fix (base_)libdir usage Burton, Ross

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=1523291792.2942.100.camel@linuxfoundation.org \
    --to=richard.purdie@linuxfoundation.org \
    --cc=koen.kooi@linaro.org \
    --cc=koen@dominion.thruhere.net \
    --cc=openembedded-core@lists.openembedded.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