Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Hongxu Jia <hongxu.jia@windriver.com>
To: Martin Jansa <martin.jansa@gmail.com>
Cc: koen.kooi@linaro.org, openembedded-devel@lists.openembedded.org
Subject: Re: [PATCH V5 0/5] efivar: upgrade to 0.23
Date: Wed, 11 May 2016 09:33:46 +0800	[thread overview]
Message-ID: <57328BFA.90609@windriver.com> (raw)
In-Reply-To: <20160510211057.GE5675@jama>

On 05/11/2016 05:10 AM, Martin Jansa wrote:
> On Tue, May 10, 2016 at 12:19:34PM -0400, Hongxu Jia wrote:
>> Changed in V5:
>> - Fix unknown option while gold linker used
> Still fails in world builds:
>
> http://errors.yoctoproject.org/Errors/Details/62248/
>
> i586-oe-linux-gcc  -m32 -march=i586 --sysroot=/home/jenkins/oe/world/shr-core/tmp-glibc/sysroots/qemux86  -O2 -pipe -g -feliminate-unused-debug-types -fdebug-prefix-map=/home/jenkins/oe/world/shr-core/tmp-glibc/work/i586-oe-linux/efivar/0.23-r0=/usr/src/debug/efivar/0.23-r0 -fdebug-prefix-map=/home/jenkins/oe/world/shr-core/tmp-glibc/sysroots/x86_64-linux= -fdebug-prefix-map=/home/jenkins/oe/world/shr-core/tmp-glibc/sysroots/qemux86=  -I/home/jenkins/oe/world/shr-core/tmp-glibc/work/i586-oe-linux/efivar/0.23-r0/git/src/include/efivar/  -specs=/home/jenkins/oe/world/shr-core/tmp-glibc/work/i586-oe-linux/efivar/0.23-r0/git/gcc.specs  -L.  -Wl,-O1 -Wl,--hash-style=gnu -Wl,--as-needed     -o efivar efivar.c -lefivar -ldl -lpopt
> /home/jenkins/oe/world/shr-core/tmp-glibc/sysroots/x86_64-linux/usr/libexec/i586-oe-linux/gcc/i586-oe-linux/5.3.0/ld: fatal error: -f/--auxiliary may not be used without -shared
> collect2: error: ld returned 1 exit status

Oh, sorry, the fix was not include:
- Use 'pie' to replace 'PIE'

//Hongxu


>
>> Changed in V4:
>> - Fix one failed with:
>> | install -d -m 755 efivar/0.23-r0/image/usr/lib/pkgconfig/
>> | install -m 644 efivar.pc efivar/0.23-r0/image/usr/lib/pkgconfig/
>> ;  install -m 644 efiboot.pc efivar/0.23-r0/image/usr/lib/pkgconfig/
>> ;
>> | install: cannot stat 'efivar.pc': No such file or directory
>> | install: cannot stat 'efiboot.pc': No such file or directory
>> | make[1]: *** [install] Error 1
>> | make[1]: Leaving directory `efivar/0.23-r0/git/src'
>> | make: *** [install] Error 2
>> | ERROR: oe_runmake failed
>>
>> //Hongxu
>>
>> The following changes since commit a6c172e2713f0018c5ebac0f957cff28b7ac2630:
>>
>>    poppler: add --std=c++11 to fix build with Qt 5.7 (2016-05-06 12:40:28 +0200)
>>
>> are available in the git repository at:
>>
>>    git://git.openembedded.org/openembedded-core-contrib hongxu/fix-efivar
>>    http://cgit.openembedded.org/cgit.cgi/openembedded-core-contrib/log/?h=hongxu/fix-efivar
>>
>> Hongxu Jia (3):
>>    efivar: fix do_install failed
>>    efibootmgr: sync with upstream while efivar upgraded to 0.23
>>    efivar: fix unknown option while gold linker used
>>
>> Koen Kooi (2):
>>    efivar: update to 0.23
>>    efibootmgr: update and unblacklist
>>
>>   .../recipes-extended/efibootmgr/efibootmgr_0.12.bb | 14 ++---
>>   .../efibootmgr/files/ldflags.patch                 | 17 ------
>>   .../efivar/0001-efivar-fix-for-cross-compile.patch | 28 +++++----
>>   .../efivar/efivar/0002-disable-static-build.patch  | 33 ++++++++++
>>   .../efivar/0003-efivar-fix-for-cross-compile.patch | 44 ++++++++++++++
>>   .../0004-fix-unknow-option-for-gold-linker.patch   | 40 ++++++++++++
>>   ...ptions-not-supported-by-lower-version-gcc.patch | 71 ----------------------
>>   .../efivar/{efivar_0.21.bb => efivar_0.23.bb}      | 29 ++++-----
>>   8 files changed, 155 insertions(+), 121 deletions(-)
>>   delete mode 100644 meta-oe/recipes-extended/efibootmgr/files/ldflags.patch
>>   create mode 100644 meta-oe/recipes-extended/efivar/efivar/0002-disable-static-build.patch
>>   create mode 100644 meta-oe/recipes-extended/efivar/efivar/0003-efivar-fix-for-cross-compile.patch
>>   create mode 100644 meta-oe/recipes-extended/efivar/efivar/0004-fix-unknow-option-for-gold-linker.patch
>>   delete mode 100644 meta-oe/recipes-extended/efivar/efivar/efivar-drop-options-not-supported-by-lower-version-gcc.patch
>>   rename meta-oe/recipes-extended/efivar/{efivar_0.21.bb => efivar_0.23.bb} (46%)
>>
>> -- 
>> 2.8.1
>>



  reply	other threads:[~2016-05-11  1:33 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-10 16:19 [PATCH V5 0/5] efivar: upgrade to 0.23 Hongxu Jia
2016-05-10 16:19 ` [PATCH 1/5] efivar: update " Hongxu Jia
2016-05-10 16:19 ` [PATCH 2/5] efibootmgr: update and unblacklist Hongxu Jia
2016-05-10 16:19 ` [PATCH 3/5] efivar: fix do_install failed Hongxu Jia
2016-05-10 16:19 ` [PATCH 4/5] efibootmgr: sync with upstream while efivar upgraded to 0.23 Hongxu Jia
2016-05-10 16:19 ` [PATCH 5/5] efivar: fix unknown option while gold linker used Hongxu Jia
2016-05-10 21:10 ` [PATCH V5 0/5] efivar: upgrade to 0.23 Martin Jansa
2016-05-11  1:33   ` Hongxu Jia [this message]
2016-05-11  1:39 ` [PATCH V6] efivar: fix unknown option while gold linker used Hongxu Jia
2016-05-17 15:28   ` Hongxu Jia
2016-05-17 15:35     ` Martin Jansa
2016-05-19  1:36       ` Hongxu Jia

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=57328BFA.90609@windriver.com \
    --to=hongxu.jia@windriver.com \
    --cc=koen.kooi@linaro.org \
    --cc=martin.jansa@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox