From: "Gerd Hoffmann" <kraxel@redhat.com>
To: Pedro Falcato <pedro.falcato@gmail.com>
Cc: edk2-devel-groups-io <devel@edk2.groups.io>
Subject: Re: [edk2-devel] [PATCH 00/24] CryptoPkg/openssl: update openssl submodule to v3.0
Date: Tue, 1 Feb 2022 10:39:53 +0100 [thread overview]
Message-ID: <20220201093953.upbjfarkuk6t6gvu@sirius.home.kraxel.org> (raw)
In-Reply-To: <CAKbZUD1CUDS11eE=7T2aHit28OE7uXQwt9qz1Oo5fd3t0c=dOg@mail.gmail.com>
On Fri, Jan 28, 2022 at 03:54:00PM +0000, Pedro Falcato wrote:
> Gerd,
>
> As I mentioned earlier, abort() is one of 5 functions GCC expects in
> freestanding mode (plus memset, mempy and two others).
>
> Is there any floating point enabled somewhere? I really don't remember
> having seen those undefined references to fprintf, ever.
That is one of the things I havn't figured yet ...
libgcc is basically a collection of object files, and the linker should
cherry-pick those which it needs (for example add the _divdi3.o object
to resolve the __divdi3 symbol) and ignore everything else.
The "ignore everything else" part seems to not work though:
> > /usr/bin/ld: /usr/lib/gcc/x86_64-redhat-linux/11/libgcc.a(_absvsi2.o): in
> > function `__absvdi2':
> > (.text+0x18): undefined reference to `abort'
Nothing in edk2 needs __absvdi2. Nevertheless the linker looks at
_absvsi2.o and tries to resolve the symbols used.
Unpacking libgcc, cherry-picking the object files actually needed, then
packing the picked object files into a library and use that works. But
IMHO that is something the linker should be able to figure on its own.
take care,
Gerd
next prev parent reply other threads:[~2022-02-01 9:40 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-28 14:07 [edk2-devel] [PATCH 00/24] CryptoPkg/openssl: update openssl submodule to v3.0 Gerd Hoffmann
2022-01-28 14:14 ` Gerd Hoffmann
2022-01-28 15:54 ` Pedro Falcato
2022-02-01 9:39 ` Gerd Hoffmann [this message]
2022-01-28 16:00 ` Pedro Falcato
2022-01-28 16:12 ` Kilian Kegel
2022-02-01 9:50 ` Gerd Hoffmann
-- strict thread matches above, loose matches on Subject: below --
2021-12-03 16:07 Gerd Hoffmann
2021-12-03 16:32 ` [edk2-devel] " Michael D Kinney
2021-12-03 16:42 ` Yao, Jiewen
2022-01-17 11:46 ` Gerd Hoffmann
2022-01-18 11:12 ` Yao, Jiewen
2022-01-18 16:12 ` Michael D Kinney
2022-01-21 8:33 ` Gerd Hoffmann
2022-01-21 16:34 ` Michael D Kinney
2022-01-21 8:30 ` Gerd Hoffmann
2022-01-21 16:38 ` Michael D Kinney
2022-01-24 16:24 ` Kilian Kegel
2022-01-24 17:28 ` Michael D Kinney
2022-01-24 19:58 ` Pedro Falcato
2022-01-26 11:02 ` Gerd Hoffmann
2022-01-27 22:26 ` Kilian Kegel
2022-01-28 0:55 ` Andrew Fish
2022-01-28 9:06 ` Pedro Falcato
2022-01-28 10:14 ` Gerd Hoffmann
2022-01-28 11:23 ` Pedro Falcato
2022-01-28 9:51 ` Gerd Hoffmann
2022-01-30 20:17 ` Kilian Kegel
2022-02-01 9:55 ` Gerd Hoffmann
2022-02-02 12:07 ` Kilian Kegel
2022-01-25 20:05 ` Kilian Kegel
2022-01-23 8:41 ` Yao, Jiewen
2021-12-06 8:05 ` Gerd Hoffmann
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-list 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=20220201093953.upbjfarkuk6t6gvu@sirius.home.kraxel.org \
--to=devel@edk2.groups.io \
/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