From: ChenQi <Qi.Chen@windriver.com>
To: Saul Wold <sgw@linux.intel.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 1/1] libgcrypt: fix compile error with '-O2' in sysroot path
Date: Fri, 6 Dec 2013 09:30:32 +0800 [thread overview]
Message-ID: <52A128B8.9050300@windriver.com> (raw)
In-Reply-To: <52A1011A.8080809@linux.intel.com>
On 12/06/2013 06:41 AM, Saul Wold wrote:
> On 12/05/2013 12:55 AM, Qi.Chen@windriver.com wrote:
>> From: Chen Qi <Qi.Chen@windriver.com>
>>
>> Characters like '-O2' or '-Ofast' will be replaced by '-O1' when
>> compiling cipher. If we are cross compiling libgcrypt and sysroot
>> contains such characters, we would get compile errors because the
>> sysroot path has been modified.
>>
>> Fix this by adding whitespaces before and after the original matching
>> pattern in the sed command.
>>
>> [YOCTO #5628]
>>
>> Signed-off-by: Chen Qi <Qi.Chen@windriver.com>
>> ---
>> ...fix-compile-error-with-O2-in-sysroot-path.patch | 46
>> ++++++++++++++++++++
>> meta/recipes-support/libgcrypt/libgcrypt.inc | 3 +-
>> 2 files changed, 48 insertions(+), 1 deletion(-)
>> create mode 100644
>> meta/recipes-support/libgcrypt/files/fix-compile-error-with-O2-in-sysroot-path.patch
>>
>> diff --git
>> a/meta/recipes-support/libgcrypt/files/fix-compile-error-with-O2-in-sysroot-path.patch
>> b/meta/recipes-support/libgcrypt/files/fix-compile-error-with-O2-in-sysroot-path.patch
>>
>> new file mode 100644
>> index 0000000..6b1f119
>> --- /dev/null
>> +++
>> b/meta/recipes-support/libgcrypt/files/fix-compile-error-with-O2-in-sysroot-path.patch
>> @@ -0,0 +1,46 @@
>> +Upstream-Status: Pending
>> +
>> +libgcrypt: fix building error with '-O2' in sysroot path
>> +
>> +Characters like '-O2' or '-Ofast' will be replaced by '-O1' when
>> compiling cipher.
>> +If we are cross compiling libgcrypt and sysroot contains such
>> characters, we would
>> +get compile errors because the sysroot path has been modified.
>> +
>> +Fix this by adding blank spaces before and after the original
>> matching pattern in the
>> +sed command.
>> +
>> +Signed-off-by: Chen Qi <Qi.Chen@windriver.com>
>> +---
>> + cipher/Makefile.am | 2 +-
>> + cipher/Makefile.in | 2 +-
>> + 2 files changed, 2 insertions(+), 2 deletions(-)
>> +
>> +diff --git a/cipher/Makefile.am b/cipher/Makefile.am
>> +index 76cdc96..9a89792 100644
>> +--- a/cipher/Makefile.am
>> ++++ b/cipher/Makefile.am
>> +@@ -69,7 +69,7 @@ rfc2268.c \
>> + camellia.c camellia.h camellia-glue.c
>> +
>> + if ENABLE_O_FLAG_MUNGING
>> +-o_flag_munging = sed -e 's/-O\([2-9s][2-9s]*\)/-O1/' -e
>> 's/-Ofast/-O1/g'
>> ++o_flag_munging = sed -e 's/ -O\([2-9s][2-9s]*\) / -O1 /' -e 's/
>> -Ofast / -O1 /g'
>> + else
>> + o_flag_munging = cat
>> + endif
>> +diff --git a/cipher/Makefile.in b/cipher/Makefile.in
>> +index 1394d15..6080d59 100644
>> +--- a/cipher/Makefile.in
>> ++++ b/cipher/Makefile.in
>
> Why do we need to patch Makefile.in if we are already patching the
> Makefile.am which will re-generate the Makefile.in
>
> Sau!
>
I thought it would do no harm. And I will send this patch to upstream,
so it might be a little strange that I only modify the Makefile.am file
even if Makefile.in has the same problem.
Best Regards,
Chen Qi
>> +@@ -314,7 +314,7 @@ rfc2268.c \
>> + camellia.c camellia.h camellia-glue.c
>> +
>> + @ENABLE_O_FLAG_MUNGING_FALSE@o_flag_munging = cat
>> +-@ENABLE_O_FLAG_MUNGING_TRUE@o_flag_munging = sed -e
>> 's/-O\([2-9s][2-9s]*\)/-O1/' -e 's/-Ofast/-O1/g'
>> ++@ENABLE_O_FLAG_MUNGING_TRUE@o_flag_munging = sed -e 's/
>> -O\([2-9s][2-9s]*\) / -O1 /' -e 's/ -Ofast / -O1 /g'
>> + all: all-am
>> +
>> + .SUFFIXES:
>> +--
>> +1.7.9.5
>> +
>> diff --git a/meta/recipes-support/libgcrypt/libgcrypt.inc
>> b/meta/recipes-support/libgcrypt/libgcrypt.inc
>> index e0dfec2..9383e17 100644
>> --- a/meta/recipes-support/libgcrypt/libgcrypt.inc
>> +++ b/meta/recipes-support/libgcrypt/libgcrypt.inc
>> @@ -11,7 +11,8 @@ LIC_FILES_CHKSUM =
>> "file://COPYING;md5=94d55d512a9ba36caa9b7df079bae19f \
>> DEPENDS = "libgpg-error libcap"
>>
>> SRC_URI =
>> "ftp://ftp.gnupg.org/gcrypt/libgcrypt/libgcrypt-${PV}.tar.gz \
>> - file://add-pkgconfig-support.patch"
>> + file://add-pkgconfig-support.patch \
>> + file://fix-compile-error-with-O2-in-sysroot-path.patch"
>>
>> inherit autotools binconfig pkgconfig
>>
>>
>
>
next prev parent reply other threads:[~2013-12-06 1:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-05 8:55 [PATCH 0/1] libgcrypt: fix compile error with '-O2' in sysroot path Qi.Chen
2013-12-05 8:55 ` [PATCH 1/1] " Qi.Chen
2013-12-05 22:41 ` Saul Wold
2013-12-06 1:30 ` ChenQi [this message]
2013-12-10 11:37 ` Richard Purdie
2013-12-10 11:40 ` Burton, Ross
2013-12-11 2:59 ` ChenQi
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=52A128B8.9050300@windriver.com \
--to=qi.chen@windriver.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=sgw@linux.intel.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