Building unbound fails - Githubissues

RossComputerGuy commented 2 years ago

I tried this on my fork for ExpidusOS and a completely clean clone of this repository. I ran ./xbps-src -N -j32 -a aarch64 pkg base-system and after a few hours, I was met with number 19 error in xbps-src. This happens while building unbound which is needed somewhere for GCC.

=> unbound-1.15.0_1: installing target dependencies: libevent-devel-2.1.12_2 expat-devel-2.4.4_1 libsodium-devel-1.0.18_1 ...
=> unbound-1.15.0_1: removing autodeps, please wait...
=> unbound-1.15.0_1: removing autocrossdeps, please wait...
=> ERROR: unbound-1.15.0_1: failed to install target dependencies! (error 19)
MISSING: libssp>=4.4.0_1
Transaction aborted due to unresolved dependencies.
=> ERROR: Please see above for the real error, exiting...

Chocimier commented 2 years ago

You should bootstrap before building base-system, did you?

Showing log with order of all packages build would help a lot to identify issue.

RossComputerGuy commented 2 years ago

I ran binary-bootstrap beforehand. This is the output.

Anachron commented 2 years ago

Is your git repo up to date with upstream?

RossComputerGuy commented 2 years ago

I ran the script I made to sync it yesterday. https://github.com/ExpidusOS/void-packages 28 commits behind. I'm headed to work now so I can't do anything until later today.

RossComputerGuy commented 2 years ago

I tested this yesterday on a clean pull and both upstream and my fork are affected.

Chocimier commented 2 years ago

Can't find libspp in dep tree of unbound.

Please show output with tip of https://github.com/Chocimier/void-packages-org/commits/debug-xbps-install applied.

Anachron commented 2 years ago

You did modify this line two days ago though:

+ --enable-libssp \

(Was disabled before)

That may be the culprit.

RossComputerGuy commented 2 years ago

I reverted those lines which ended up not fixing it. Adding those lines fixed this same error for x86_64 builds.

Chocimier commented 2 years ago

Reverting build style is not enough, you need to throw away all packages built since the change.

Anachron commented 2 years ago

I'm new to cross compiling and gcc so others are welcome to correct me here.

You enabled libssp in the cross toolchain, yet your template does not build it..?

https://github.com/ExpidusOS/void-packages/blob/stable/srcpkgs/gcc6/template#L156

And then you're wondering why its complaining about missing packages?

Edit: Also see the comment above. Clean your builddir and rebootstrap. Then build from beginning.

RossComputerGuy commented 2 years ago

I did rebuild everything after reverting it

Sent from ProtonMail mobile

-------- Original Message -------- On Feb 18, 2022, 8:59 AM, Piotr wrote:

Reverting build style is not enough, you need to throw away all packages built since the change.

— Reply to this email directly, view it on GitHub, or unsubscribe. Triage notifications on the go with GitHub Mobile for iOS or Android. You are receiving this because you authored the thread.Message ID: @.***>

RossComputerGuy commented 2 years ago

That's the wrong GCC package. And that's how it is set up upstream.

Sent from ProtonMail mobile

-------- Original Message -------- On Feb 18, 2022, 9:01 AM, Anachron wrote:

I'm new to cross compiling and gcc so others are welcome to correct me here.

You enabled libssp in the cross toolchain, yet your template does not build it..?

https://github.com/ExpidusOS/void-packages/blob/stable/srcpkgs/gcc6/template#L156

And then you're wondering why its complaining about missing packages?

— Reply to this email directly, view it on GitHub, or unsubscribe. Triage notifications on the go with GitHub Mobile for iOS or Android. You are receiving this because you authored the thread.Message ID: @.***>

Anachron commented 2 years ago

But did you clean up the builddir and hostdir and ran another bootstrap before?

q66 commented 2 years ago

not a void bug, please don't report issues specific to your fork into void-packages

RossComputerGuy commented 2 years ago

I am using the same bootstrap I used to build x86_64.

Sent from ProtonMail mobile

-------- Original Message -------- On Feb 18, 2022, 9:26 AM, Anachron wrote:

But did you clean up the builddir and hostdir and ran another bootstrap before?

— Reply to this email directly, view it on GitHub, or unsubscribe. Triage notifications on the go with GitHub Mobile for iOS or Android. You are receiving this because you authored the thread.Message ID: @.***>

RossComputerGuy commented 2 years ago

But this happens upstream

Sent from ProtonMail mobile

-------- Original Message -------- On Feb 18, 2022, 9:28 AM, Daniel Kolesa wrote:

Closed #35672.

— Reply to this email directly, view it on GitHub, or unsubscribe. Triage notifications on the go with GitHub Mobile for iOS or Android. You are receiving this because you authored the thread.Message ID: @.***>

Chocimier commented 2 years ago

Then show us the error that happens without influence of your fork with debug info taken with what I posted above. What you posted up to now is not an Void problem.

RossComputerGuy commented 2 years ago

https://pastebin.com/z4VSSB4V I just got off work and used the debug info and got these results.

Anachron commented 2 years ago

@RossComputerGuy like already said 3 times now... is the build directory and everything else clean?

Maybe clone the directory somewhere else and run another bootstrap from there and try to build again.

(Why is it so hard to debug this with you... you're barely helping)

RossComputerGuy commented 2 years ago

Yes, I cleaned everything.

RossComputerGuy commented 2 years ago

And I re-ran that after waiting 2 hours so I can get that shortened log.

RossComputerGuy commented 2 years ago

Recompiling it from scratch for the 3rd time with debug. Will have the results in about 2 hours.

Anachron commented 2 years ago

We're talking about a build based off void-linux/void-packages, right?

RossComputerGuy commented 2 years ago

Yes, with debug.

RossComputerGuy commented 2 years ago

The log was too big but I uploaded it to my server. https://repo.expidusos.com/log.txt

RossComputerGuy commented 2 years ago

=> libsodium-1.0.18_1: running pre-pkg hook: 03-rewrite-python-shebang ...
=> libsodium-1.0.18_1: running pre-pkg hook: 04-generate-runtime-deps ...
   SONAME: libssp.so.0 <-> libssp>=4.4.0_1
   SONAME: libpthread.so.0 <-> glibc>=2.32_1
   SONAME: libc.so.6 <-> glibc>=2.32_1
=> libsodium-1.0.18_1: running pre-pkg hook: 05-prepare-32bit ...
=> libsodium-1.0.18_1: running pre-pkg hook: 06-shlib-provides ...
   SONAME libsodium.so.23 from /usr/lib/libsodium.so.23.3.0
=> libsodium-1.0.18_1: running pre-pkg hook: 90-set-timestamps ...
=> libsodium-1.0.18_1: setting mtimes to Fri Feb 18 04:40:10 PM UTC 2022
=> libsodium-1.0.18_1: running pre-pkg hook: 99-pkglint-subpkgs ...
=> libsodium-1.0.18_1: running pre-pkg hook: 99-pkglint ...
=> libsodium-1.0.18_1: running pre-pkg hook: 999-collected-rdeps ...
   libssp>=4.4.0_1 glibc>=2.32_1 
=> libsodium-devel-1.0.18_1: running do-pkg hook: 00-gen-pkg ...
=> Creating libsodium-devel-1.0.18_1.aarch64.xbps for repository /host/binpkgs/debug-xbps-install ...
=> libsodium-devel-1.0.18_1: running post-pkg hook: 00-register-pkg ...
=> libsodium-1.0.18_1: running do-pkg hook: 00-gen-pkg ...
=> Creating libsodium-1.0.18_1.aarch64.xbps for repository /host/binpkgs/debug-xbps-install ...
=> libsodium-1.0.18_1: running post-pkg hook: 00-register-pkg ...
=> Registering new packages to /host/binpkgs/debug-xbps-install
index: added `libsodium-1.0.18_1' (aarch64).
index: added `libsodium-devel-1.0.18_1' (aarch64).
index: 96 packages registered.

I think this is the cause of the libssp error. It is also listed in the pastebin: [DEBUG] libsodium-1.0.18_1: requires dependency 'libssp>=4.4.0_1': not installed.

Chocimier commented 2 years ago

Okay, reproduced.

git worktree add ../libssp
cd ../libssp
echo XBPS_MAKEJOBS=$(( $(nproc) - 1 )) > etc/conf
./xbps-src binary-bootstrap
./xbps-src pkg libsodium -a aarch64 -N

=> libsodium-1.0.18_1: running pre-pkg hook: 04-generate-runtime-deps ...
   SONAME: libssp.so.0 <-> libssp>=4.4.0_1
   SONAME: libpthread.so.0 <-> glibc>=2.32_1
   SONAME: libc.so.6 <-> glibc>=2.32_1

Xlaits commented 2 years ago

Is there any word on this? This has been driving me bonkers for at least a week now.

RossComputerGuy commented 2 years ago

@Xlaits Same, I've tried several fixes. None of them worked so I had to submitted this issue.

Xlaits commented 2 years ago

I've been trying other methods while I have been waiting, as I am rather impatient. I'm getting close, but it's only because of outside toolchains and not actually having xbps-src working.

Chocimier commented 2 years ago

@paper42 suggested to add --disable-ssp to libsodium configure_args. @RossComputerGuy, could you check if this solves your issue?

Xlaits commented 2 years ago

I can confirm that --disable-ssp did not fix my issues at least.

On Mon, Jul 4, 2022 at 3:08 PM Piotr @.***> wrote:

@paper42 https://github.com/paper42 suggested to add --disable-ssp to libsodium configure_args. @RossComputerGuy https://github.com/RossComputerGuy, could you check if this solves your issue?

— Reply to this email directly, view it on GitHub https://github.com/void-linux/void-packages/issues/35672#issuecomment-1174111673, or unsubscribe https://github.com/notifications/unsubscribe-auth/AHX2YDL5R7VR4SWR2WQWMXTVSMZDXANCNFSM5OWHX3SA . You are receiving this because you were mentioned.Message ID: @.***>

Chocimier commented 2 years ago

I can confirm that --disable-ssp did not fix my issues at least.

Okay. Please remove your hostdir/binpkgs, build again and link here full build log.

void-linux / void-packages

Building unbound fails #35672