Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Martin Jansa <martin.jansa@gmail.com>
To: Hongxu Jia <hongxu.jia@windriver.com>
Cc: koen.kooi@linaro.org, openembedded-devel@lists.openembedded.org
Subject: Re: [PATCH V4 0/3] efivar: update to 0.23
Date: Tue, 10 May 2016 14:17:40 +0200	[thread overview]
Message-ID: <20160510121740.GA5675@jama> (raw)
In-Reply-To: <1462604487-112658-1-git-send-email-hongxu.jia@windriver.com>

[-- Attachment #1: Type: text/plain, Size: 4560 bytes --]

On Sat, May 07, 2016 at 03:01:24AM -0400, Hongxu Jia wrote:
> 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
> 
> - Sync with latest upsteam
> Hi Martin,
> 
> About your original build failed with:
> | 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/git=/usr/src/efivar
> -fdebug-prefix-map=/home/jenkins/oe/world/shr-core/tmp-glibc/work/i586-oe-linux/efivar/0.23-r0/git=/usr/src/efivar
> -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     -shared \
> | 	  -Wl,-soname,libefivar.so.0 \
> | 	  -o libefivar.so dp.o dp-acpi.o dp-hw.o dp-media.o dp-message.o
> efivarfs.o export.o guid.o guids.o guid-symbols.o lib.o vars.o -ldl
> |
> /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:
> --default-symver: unknown option
> |
> /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:
> use the --help option for usage information
> | collect2: error: ld returned 1 exit status
> | make[1]: *** [libefivar.so] Error 1
> | make[1]: *** Waiting for unfinished jobs....
> 
> I could not reproduce it, but from the log,
> --default-symver is unknown option. And upstream
> has fixed it in the following commit by removing option
> '--default-symver' from gcc.specs
> ....
> commit 975356c9486ff7fa0ec5534ef56cc6f519ad11b4
> Author: Peter Jones <pjones@redhat.com>
> Date:   Wed Mar 2 14:46:15 2016 -0500
> 
>     libefivar: get rid of our variadic mess in efi_set_variable()
> ....
> 
> //Hongxu

No it fails with different unknown option:
http://errors.yoctoproject.org/Errors/Details/61934/
http://errors.yoctoproject.org/Errors/Details/61951/

Maybe it's because my world builds are using gold which could be more
strict when parsing the options.

> 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 (1):
>   efivar: fix do_install failed
> 
> 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 ++++++++++++++
>  ...ptions-not-supported-by-lower-version-gcc.patch | 71 ----------------------
>  .../efivar/{efivar_0.21.bb => efivar_0.23.bb}      | 28 ++++-----
>  7 files changed, 114 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
>  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
> 

-- 
Martin 'JaMa' Jansa     jabber: Martin.Jansa@gmail.com

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 188 bytes --]

  reply	other threads:[~2016-05-10 12:17 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-07  7:01 [PATCH V4 0/3] efivar: update to 0.23 Hongxu Jia
2016-05-10 12:17 ` Martin Jansa [this message]
2016-05-10 15:31   ` Hongxu Jia
  -- strict thread matches above, loose matches on Subject: below --
2016-05-07  7:05 Hongxu Jia
2016-05-07  7:07 ` 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=20160510121740.GA5675@jama \
    --to=martin.jansa@gmail.com \
    --cc=hongxu.jia@windriver.com \
    --cc=koen.kooi@linaro.org \
    --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