You are not logged in.

#26 2019-07-22 02:22:33

jghodd
Member
Registered: 2019-07-14
Posts: 18

Re: [SOLVED] linker error (glibc bug)

@andreas_baumann

well, better news... i'm doing the upstream glibc build using gcc-9.1.0-2.4, gcc-libs-9.1.0-2.4, binutils-2.32-2.76 (all staging versions) and the older glibc-2.29-1.23, and i'm getting no warnings. also tested the same combination on my calamares build - also no warnings.

question: should the glibc config params include '--enable-cet' or '--enable-cet=yes'?

Offline

#27 2019-07-22 10:16:13

deep42thought
Administrator
From: Jena, Germany
Registered: 2017-06-17
Posts: 449

Re: [SOLVED] linker error (glibc bug)

I have built glibc-2.29-4-i686.pkg.tar.xz with your combinatino of packages now (all testing, except gcc,gcc-libs,binutils from staging and the old glibc) - no warnings when compiling test program.
I compiled glibc again with the newly built glibc and everything from staging - also no warnings.
As everything is now on the most recent version, I will manually insert thatglibc into our repositories and schedule a build of it again (so the build master picks up the correct dependencies and everything).

Thanks for tracking that one down!

Offline

#28 2019-07-22 11:59:40

andreas_baumann
Administrator
From: Zurich, Switzerland
Registered: 2017-08-10
Posts: 818
Website

Re: [SOLVED] linker error (glibc bug)

@jghodd: --enable-cet and --enable-cet=yes should do the same thing in glibc, I think (at least how I'm reading configure.ac).

Offline

#29 2019-07-22 12:54:33

deep42thought
Administrator
From: Jena, Germany
Registered: 2017-06-17
Posts: 449

Re: [SOLVED] linker error (glibc bug)

looks like the freshly-built glibc 2.29-3.3 (currently in [staging]) is also bug free. @jghodd: Can you test whether this solves your initial problem, too (and mark this thread as [solved] if it does), please?

regards,
deep42thought

Offline

#30 2019-07-22 18:14:57

jghodd
Member
Registered: 2019-07-14
Posts: 18

Re: [SOLVED] linker error (glibc bug)

@andreas_baumann

thanks, bud. that's what it looked like in configure, but also saw that the else was assigning 'no' to --enable-cet which raised the the question.

@deep42thought

i tested both test builds using binutils-2.32-2.76, gcc-9.1.0-2.4, gcc-libs-9.1.0-2.4 and glibc-2.29-3.3 and no warnings. looks good. i've already pushed this combination to my override repository for my users.

and you're welcome. i know y'all are busy with a whole lot more than just one problematic package and could probably use some extra bandwidth from someone willing to go down a rabbit hole for you. glad i could help.

i went ahead and added a link to this thread to bug FS#82 and requested closure. this thread will indeed be marked solved.

thanks for all your help as well.

Last edited by jghodd (2019-07-22 18:16:18)

Offline

Board footer

Powered by FluxBB