From: Rolf Eike Beer <eb@emlix.com>
To: "Masahiro Yamada" <masahiroy@kernel.org>,
"Michal Marek" <michal.lkml@markovi.net>,
linux-kbuild@vger.kernel.org,
"open list" <linux-kernel@vger.kernel.org>,
"Daniel Díaz" <daniel.diaz@linaro.org>
Cc: stable@vger.kernel.org, Naresh Kamboju <naresh.kamboju@linaro.org>
Subject: Re: [PATCH] scripts: Fix linking extract-cert against libcrypto
Date: Thu, 11 Feb 2021 11:29:33 +0100 [thread overview]
Message-ID: <3314666.Em9qtOGRgX@mobilepool36.emlix.com> (raw)
In-Reply-To: <6065587.C4oOSP4HzL@mobilepool36.emlix.com>
[-- Attachment #1: Type: text/plain, Size: 3053 bytes --]
Am Dienstag, 9. Februar 2021, 09:44:33 CET schrieb Rolf Eike Beer:
> Am Dienstag, 9. Februar 2021, 05:59:56 CET schrieb Daniel Díaz:
> > When compiling under OpenEmbedded, the following error is seen
> >
> > as of recently:
> > /srv/oe/build/tmp/hosttools/ld: cannot find /lib/libc.so.6 inside /
> > /srv/oe/build/tmp/hosttools/ld: cannot find /usr/lib/libc_nonshared.a
> >
> > inside / /srv/oe/build/tmp/hosttools/ld: cannot find
> > /lib/ld-linux-x86-64.so.2 inside / collect2: error: ld returned 1 exit
> > status
> >
> > make[2]: *** [scripts/Makefile.host:95: scripts/extract-cert] Error 1
>
> [...]
>
> > As per `make`'s documentation:
> > LDFLAGS
> >
> > Extra flags to give to compilers when they are supposed to
> > invoke the linker, ‘ld’, such as -L. Libraries (-lfoo)
> > should be added to the LDLIBS variable instead.
> >
> > LDLIBS
> >
> > Library flags or names given to compilers when they are
> > supposed to invoke the linker, ‘ld’. LOADLIBES is a
> > deprecated (but still supported) alternative to LDLIBS.
> > Non-library linker flags, such as -L, should go in the
> > LDFLAGS variable.
>
> Correct. And the patch I use for my local 4.19 build actually uses LDLIBS,
> so it must have gone wrong in some rebase for one of the intermediate
> versions.
>
> Acked-by: Rolf Eike Beer <eb@emlix.com>
Ok, now actually with proper testing: no, your patch doesn't work. When
changing LDLIBS to LDFLAGS things do not show up on the commandline at all.
LDLIBS:
gcc -Wp,-MMD,scripts/.sign-file.d -Wall -Wmissing-prototypes -Wstrict-
prototypes -O2 -fomit-frame-pointer -std=gnu89 -I/opt/emlix/test/include
-I ./scripts -o scripts/sign-file /tmp/e2/build/linux-kernel/scripts/sign-
file.c -L/opt/emlix/test/lib -lcrypto -lz -ldl -pthread
LDFLAGS:
gcc -Wp,-MMD,scripts/.sign-file.d -Wall -Wmissing-prototypes -Wstrict-
prototypes -O2 -fomit-frame-pointer -std=gnu89 -I/opt/emlix/test/include
-I ./scripts -o scripts/sign-file /tmp/e2/build/linux-kernel/scripts/sign-
file.c
When looking closely you may notice that this is not entirely the same as
current master would output: I missed the CFLAGS for sign-file in my patch.
When testing your patch I accidentially had a .config that had module
signatures disabled, so I have not tested it actually, that's why I didn't
notice that it doesn't work.
I'm just guessing, but your build error looks like you are also cross-building
the tools, which is wrong. You want them to be host-tools. So don't export
PKG_CONFIG_SYSROOT_DIR, it would then try to link target libraries into a host
binary.
Eike
--
Rolf Eike Beer, emlix GmbH, http://www.emlix.com
Fon +49 551 30664-0, Fax +49 551 30664-11
Gothaer Platz 3, 37083 Göttingen, Germany
Sitz der Gesellschaft: Göttingen, Amtsgericht Göttingen HR B 3160
Geschäftsführung: Heike Jordan, Dr. Uwe Kracke – Ust-IdNr.: DE 205 198 055
emlix - smart embedded open source
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 313 bytes --]
next prev parent reply other threads:[~2021-02-11 10:33 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-09 4:59 [PATCH] scripts: Fix linking extract-cert against libcrypto Daniel Díaz
2021-02-09 8:44 ` Rolf Eike Beer
2021-02-11 8:23 ` Rolf Eike Beer
2021-02-11 10:29 ` Rolf Eike Beer [this message]
2021-02-12 7:44 ` Rolf Eike Beer
2021-02-16 23:53 ` Daniel Díaz
2021-02-11 7:11 ` Masahiro Yamada
2021-02-16 23:51 ` Daniel Díaz
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=3314666.Em9qtOGRgX@mobilepool36.emlix.com \
--to=eb@emlix.com \
--cc=daniel.diaz@linaro.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=masahiroy@kernel.org \
--cc=michal.lkml@markovi.net \
--cc=naresh.kamboju@linaro.org \
--cc=stable@vger.kernel.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