Am 2024-11-22 18:19, schrieb Shawn Webb:
On Fri, Nov 22, 2024 at 04:20:42PM +0100, Alexander Leidinger wrote:
Am 2024-11-22 15:31, schrieb Alexander Leidinger:
> Am 2024-11-22 14:08, schrieb Ed Maste:
> > On Thu, 21 Nov 2024 at 04:43, Alexander Leidinger
> > <alexan...@leidinger.net> wrote:
> > >
> > > Hi,
> > >
> > > I get:
> > > ld: error: version script assignment of 'FBSD_1.5' to symbol
> > > 'getentropy' failed: symbol not defined
> > > cc: error: linker command failed with exit code 1 (use -v to see
> > > invocation)
> > >
> > > This is with src from 2024-11-20 1:39pm UTC. My last build / running
> > > world is from 2024-11-13 18:34pm UTC.
> >
> > I modified getentropy in that window to remove fallback code --
> > 62dab3d016a on Nov 16. It builds and Jenkins was happy though so
> > perhaps something odd in your environment?
>
> I'm running a bisect on unmodified code (master). So there is a failure,
> and I can't tell right now which commit it is. Anyway, as this is master
> without my local changes, it has to me src.conf or similar:
>
> src.conf:
> ---snip---
> WITHOUT_PROFILE=yes
> CFLAGS+=-DFTP_COMBINE_CWDS
> MALLOC_PRODUCTION=yes
> WITH_MALLOC_PRODUCTION=yes
> WITHOUT_LLVM_ASSERTIONS=yes
> KERNCONF=ANDROMEDA
> WITH_RETPOLINE=yes
> WITH_BIND_NOW=yes
> WITHOUT_CLEAN=yes
> FORTIFY_SOURCE=2       ## <------- maybe this? if yes: regression!

Sorry Ed, but your commit fails fast, and the commit before that builds now
since much longer than the failed build.

Here is a bit more info

Building
/space/system/usr_obj/space/system/usr_src/amd64.amd64/lib/libc/libc_pic.a
building static c library
building shared library libc.so.7
building special pic c library
ld: error: version script assignment of 'FBSD_1.5' to symbol 'getentropy'
failed: symbol not defined
cc: error: linker command failed with exit code 1 (use -v to see invocation) Building /space/system/usr_obj/space/system/usr_src/amd64.amd64/lib/libc/libc_nossp_pic.a
*** [libc.so.7.full] Error code 1

So the pic-build seems to be an issue.

I try to get some time to check which build option may play a role here, but
I'm not sure how much of that I can do in the next 24h.

I'm getting the same build error. I'm building HardenedBSD
15-CURRENT/amd64 with a clean /usr/obj.

A world builds successfully without the FORTIFY_SOURCE=2. So this is a regression there.

Bye,
Alexander.

--
http://www.Leidinger.net alexan...@leidinger.net: PGP 0x8F31830F9F2772BF
http://www.FreeBSD.org    netch...@freebsd.org  : PGP 0x8F31830F9F2772BF

Attachment: signature.asc
Description: OpenPGP digital signature

Reply via email to