All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Anatol Belski" <anbelski@linux.microsoft.com>
To: akuster808 <akuster808@gmail.com>,
	openembedded-devel@lists.openembedded.org
Subject: Re: [oe] [meta-oe][PATCH v2] xmlsec1: Fix configure QA error caused by host lookup path
Date: Fri, 15 Jan 2021 12:10:46 +0100	[thread overview]
Message-ID: <65de5bb9-6d64-b069-1942-9fc2315df036@linux.microsoft.com> (raw)
In-Reply-To: <3c1127ea-1125-3a66-8e66-63be6d87a5ee@gmail.com>

Hi,

On 1/15/2021 3:56 AM, akuster808 wrote:
>
> On 1/14/21 9:36 AM, Anatol Belski wrote:
>> The configure script contains hardcoded lookup paths to /usr and other
>> paths that might interfere with the host. These are overwritten with the
>> staging dir locations for Poky compatibility.
> The QA message has "xmlsec1-1.2.30" so this appears it needs to be
> backported to Gatesgarth and Dunfell.
>
> Please confirm.

Correct, the initial issue is in Dunfell. It should be either backported 
or I was intended to file a patch against Dunfell, whatever is 
preferred. Please let me know. The v2 is the version to be taken.

Thanks

Anatol

>
> -armin
>> Signed-off-by: Anatol Belski <anbelski@linux.microsoft.com>
>> ---
>>   .../xmlsec1/ensure-search-path-non-host.patch | 22 +++++++++++++++++++
>>   .../recipes-support/xmlsec1/xmlsec1_1.2.31.bb |  1 +
>>   2 files changed, 23 insertions(+)
>>   create mode 100644 meta-oe/recipes-support/xmlsec1/xmlsec1/ensure-search-path-non-host.patch
>>
>> diff --git a/meta-oe/recipes-support/xmlsec1/xmlsec1/ensure-search-path-non-host.patch b/meta-oe/recipes-support/xmlsec1/xmlsec1/ensure-search-path-non-host.patch
>> new file mode 100644
>> index 0000000000..a5a298af0d
>> --- /dev/null
>> +++ b/meta-oe/recipes-support/xmlsec1/xmlsec1/ensure-search-path-non-host.patch
>> @@ -0,0 +1,22 @@
>> +xmlsec1: Fix configure QA error caused by host lookup path
>> +
>> +ERROR: mc:my-sdk:xmlsec1-1.2.30-r0 do_configure: QA Issue: This autoconf log indicates errors, it looked at host include and/or library paths while determining system capabilities.
>> +
>> +It will eventually arise after the configure QA as the configure script should only look at the staging sysroot dir, not at the host.
>> +
>> +Upstream-Status: Inappropriate [embedded specific]
>> +Signed-off-by: Anatol Belski <anbelski@linux.microsoft.com>
>> +
>> +--- a/configure.ac.orig   2021-01-13 14:37:42.254991177 +0000
>> ++++ b/configure.ac        2021-01-13 14:40:56.546269330 +0000
>> +@@ -250,8 +250,8 @@
>> + dnl ==========================================================================
>> + dnl Common installation locations
>> + dnl ==========================================================================
>> +-COMMON_INCLUDE_DIR="/usr/include /usr/local/include"
>> +-COMMON_LIB_DIR="/usr/lib /usr/lib64 /usr/local/lib"
>> ++COMMON_INCLUDE_DIR="${STAGING_INCDIR}"
>> ++COMMON_LIB_DIR="${STAGING_LIBDIR}"
>> + case $host in
>> +     i*86-*-linux-gnu)   COMMON_LIB_DIR="$COMMON_LIB_DIR /usr/lib/i386-linux-gnu" ;;
>> +     x86_64-*-linux-gnu) COMMON_LIB_DIR="$COMMON_LIB_DIR /usr/lib/x86_64-linux-gnu" ;;
>> diff --git a/meta-oe/recipes-support/xmlsec1/xmlsec1_1.2.31.bb b/meta-oe/recipes-support/xmlsec1/xmlsec1_1.2.31.bb
>> index 803016c96e..3464f2f43c 100644
>> --- a/meta-oe/recipes-support/xmlsec1/xmlsec1_1.2.31.bb
>> +++ b/meta-oe/recipes-support/xmlsec1/xmlsec1_1.2.31.bb
>> @@ -19,6 +19,7 @@ SRC_URI = "http://www.aleksey.com/xmlsec/download/${BP}.tar.gz \
>>       file://xmlsec1-examples-allow-build-in-separate-dir.patch \
>>       file://0001-nss-nspr-fix-for-multilib.patch \
>>       file://run-ptest \
>> +    file://ensure-search-path-non-host.patch \
>>       "
>>   
>>   SRC_URI[md5sum] = "182f5cbdfb8ddbac535c04470c170dc3"
>>
>> 
>>

      reply	other threads:[~2021-01-15 11:11 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-14 17:36 [meta-oe][PATCH v2] xmlsec1: Fix configure QA error caused by host lookup path Anatol Belski
2021-01-15  2:56 ` [oe] " akuster
2021-01-15 11:10   ` Anatol Belski [this message]

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=65de5bb9-6d64-b069-1942-9fc2315df036@linux.microsoft.com \
    --to=anbelski@linux.microsoft.com \
    --cc=akuster808@gmail.com \
    --cc=openembedded-devel@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 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.