From mboxrd@z Thu Jan 1 00:00:00 1970 From: Andreas Schwab Date: Mon, 14 Aug 2023 15:15:44 +0200 Subject: [PATCH] Makefile: Force GNU hashing In-Reply-To: <2c6d3c9c-d0b4-f00a-e3c9-68df02c9d22d@ventanamicro.com> (Jeff Law's message of "Mon, 14 Aug 2023 07:11:00 -0600") References: <20230814043959.390101-1-mchitale@ventanamicro.com> <5c7a4dce-60fe-e61f-1596-20378d5204d1@ventanamicro.com> <2c6d3c9c-d0b4-f00a-e3c9-68df02c9d22d@ventanamicro.com> Message-ID: List-Id: To: opensbi@lists.infradead.org MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit On Aug 14 2023, Jeff Law wrote: > On 8/14/23 07:08, Andreas Schwab wrote: >> On Aug 14 2023, Jeff Law wrote: >> >>> On 8/14/23 01:40, Andreas Schwab wrote: >>>> On Aug 14 2023, Mayuresh Chitale wrote: >>>> >>>>> The Yocto QA step verifies that binaries and DSOs use DT_GNU_HASH rather than >>>>> DT_HASH. If the linker is called directly, then we need to make sure to pass in >>>>> the hashing style. >>>> Why does it matter? The ultimate output is a flat binary. >>> It matters because the Yocto QA step will fail. >> Why does it even look at it? It's only an intermediate build product. > Because that's how Yocto works? Whatever Yocto is, it must be doing something strange. -- Andreas Schwab, SUSE Labs, schwab at suse.de GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE 1748 E4D4 88E3 0EEA B9D7 "And now for something completely different."