[SOLVED] runc from slackbuilds.org does not build on Slackware 15.0

M0M0 · 04-08-2022, 12:27 PM

I always had issues with building runc on slackware post 14.2 current. But also the new script for Slackware 15.0 still fails.

Code:

runc-1.0.2/vendor/modules.txt
go build -trimpath "-mod=vendor" "-buildmode=pie"  -tags "seccomp" -ldflags "-X main.gitCommit=12644e614e25b05da6fd08a38ffa0cfe1903fdec -X main.version=1.0.2 " -o runc .
go build: when using gccgo toolchain, please pass linker flags using -gccgoflags, not -ldflags
# github.com/opencontainers/runc
/usr/bin/ld: $WORK/b001/_pkg1_.a(_cgo_defun.o): relocation R_X86_64_32 against `.rodata' can not be used when making a PIE object; recompile with -fPIE
/usr/bin/ld: $WORK/b001/_pkg2_.a(_cgo_defun.o): relocation R_X86_64_32 against `.rodata' can not be used when making a PIE object; recompile with -fPIE
/usr/bin/ld: $WORK/b001/_pkg3_.a(_cgo_defun.o): relocation R_X86_64_32 against `.rodata' can not be used when making a PIE object; recompile with -fPIE
collect2: Fehler: ld gab 1 als Ende-Status zurück
make: *** [Makefile:34: runc] Fehler 2

Windu · 04-08-2022, 01:55 PM

This works for me on 15.0 without error: https://slackware.uk/people/alien/sl...ds/runc/build/
It is for runc-1.0.3 whereas SBo has 1.0.2 but the bump in 'microversion' should not make such a big difference.

But I think this is your real issue:

Code:

go build: when using gccgo toolchain, please pass linker flags using -gccgoflags, not -ldflags

Either you forgot to install google-go-lang, or you did not logout/login after installing it.

M0M0 · 04-09-2022, 12:50 PM

Quote:

Originally Posted by Windu

Either you forgot to install google-go-lang, or you did not logout/login after installing it.

No, I made sure that google-go-lang is installed and even after rebooting my computer I get the same error.

M0M0 · 04-09-2022, 12:55 PM

Quote:

Originally Posted by Windu

This works for me on 15.0 without error: https://slackware.uk/people/alien/sl...ds/runc/build/

I get the exact same issue with alien's script

Windu · 04-09-2022, 12:58 PM

What 'go' is foremost in your $PATH ?

If it is google's go then you would see:

Code:

$ go version
go version go1.17.5 linux/amd64

But if you invoke GCC go:

Code:

$ go version
go version go1.16.5 gccgo (GCC) 11.2.0 linux/amd64

The Google version of go should be placed first in your $PATH by the profile script "/etc/profile.d/go.sh" which should be executable... and you would have to be running a Bash-compatible shell of course. There's also "/etc/profile.d/go.csh" if you use a C-shell compatible shell.

ponce · 04-09-2022, 01:03 PM

also, when you build scripts from SlackBuilds.org, you should do it in a root login shell or, as user, becoming root with "su -" (note the trailing slash) or it won't source the scripts in /etc/profile.d: it's explained in the HOWTO (at step 4) and it's also explained in google-go-lang's README.

M0M0 · 04-09-2022, 01:09 PM

Ok, I get the same issue with all go programs... They always try to use gccgo and not go. Even when I move gccgo they try to is it instead of go. Rebooting or logging in and out again does not solve. Rebuilding google-go-lang does also not help

M0M0 · 04-09-2022, 01:11 PM

Quote:

Originally Posted by ponce

also, when you build scripts from SlackBuilds.org, you should do it in a root login shell or, as user, becoming root with "su -" (note the trailing slash) or it won't source the scripts in /etc/profile.d: it's explained in the HOWTO (at step 4) and it's also explained in google-go-lang's README.

I know and did that

M0M0 · 04-09-2022, 01:13 PM

Quote:

Originally Posted by Windu

What 'go' is foremost in your $PATH ?

But if you invoke GCC go:

Code:

$ go version
go version go1.16.5 gccgo (GCC) 11.2.0 linux/amd64

This is indeed what I see

Quote:

Originally Posted by Windu

The Google version of go should be placed first in your $PATH by the profile script "/etc/profile.d/go.sh" which should be executable... and you would have to be running a Bash-compatible shell of course. There's also "/etc/profile.d/go.csh" if you use a C-shell compatible shell.

After running this script, which does exist and is executable I still see:

Code:

$ go version
go version go1.16.5 gccgo (GCC) 11.2.0 linux/amd64

M0M0 · 04-09-2022, 01:20 PM

Quote:

Originally Posted by ponce

... (note the trailing slash)

OK, I have to apologize it seemed that I indeed forgot to add the trailing slash. Sorry about that and thanks for reminding me

ponce · 04-09-2022, 02:04 PM

Quote:

Originally Posted by M0M0

OK, I have to apologize it seemed that I indeed forgot to add the trailing slash. Sorry about that and thanks for reminding me

I wanted to write "dash" but I wrote "slash" (*facepalm*).

Quote:

Originally Posted by M0M0

After running this script, which does exist and is executable I still see:

Code:

$ go version
go version go1.16.5 gccgo (GCC) 11.2.0 linux/amd64

you shouldn't run those scripts in /etc/profile.d, you have to source them, like

Code:

. /etc/profile.d/go.sh

or

Code:

source /etc/profile.d/go.sh

chris.willing · 04-30-2022, 07:51 PM

Quote:

Originally Posted by ponce

...., you have to source them, like

Code:

. /etc/profile.d/go.sh

or

Code:

source /etc/profile.d/go.sh

A line like that {c,sh}ould be included early the runc.SlackBuild to avoid the problem.

chris

chris.willing · 04-30-2022, 11:40 PM

Further to the need to source /etc/profile.d/go.sh, it would be really helpful if any SlackBuild which requires go, either directly or indirectly through some other dependency, were to have a line something like:

Code:

[ -z "$GOROOT" ] && source /etc/profile.d/go.sh

I see there's no go-template.SlackBuild available at SBo and I don't know enough about go based packaging to know if it makes sense to have such a thing. If so, I'd like to see a check like that included.

chris

tasty_donut · 05-10-2024, 03:34 PM

I was pulling my hair out with this too. I did what you said about using su with the - rather than just su and it was perfect . Thank you for the solution.

tasty_donut · 05-10-2024, 03:37 PM

I had the same issue on Slackware 15. Was pulling my hair out and was annoyed for the whole day. Came across this post and did what was suggested about being root. Not just su but su - after doing this it was perfect. Thank you for the solution.