SBo scripts not building on current (read 1st post, pls)

burning · 05-17-2021, 06:49 PM

Running -current and using Ponce's repo. I was trying to build and install the google-go-lang package through sbopkg but I keep getting this error:

Code:

Building Go cmd/dist using /usr. (go1.14.6 gccgo (GCC) 10.3.0 linux/386)
Building Go toolchain1 using /usr.
Building Go bootstrap cmd/go (go_bootstrap) using Go toolchain1.
panic: invalid argument

goroutine 1 [running]:
bootstrap..z2fcmd..z2flink..z2finternal..z2fld.Main
        /tmp/SBo/package-google-go-lang/usr/lib/go1.16.3/go/src/cmd/link/internal/ld/main.go:333
main.main
        /tmp/SBo/package-google-go-lang/usr/lib/go1.16.3/go/src/cmd/link/main.go:68
makecontext
        :0

go tool dist: FAILED: /tmp/SBo/package-google-go-lang/usr/lib/go1.16.3/go/pkg/tool/linux_386/link -extld=gcc -o /tmp/SBo/package-google-go-lang/usr/lib/go1.16.3/go/pkg/tool/linux_386/go_bootstrap /tmp/go-tool-dist-382298166/cmd/go/_go_.a: exit status 2
Building Go toolchain2 using go_bootstrap and Go toolchain1.
go tool dist: FAILED: /tmp/SBo/package-google-go-lang/usr/lib/go1.16.3/go/pkg/tool/linux_386/go_bootstrap install -gcflags=all= -ldflags=all= -i
cmd/asm cmd/cgo cmd/compile cmd/link: fork/exec /tmp/SBo/package-google-go-lang/usr/lib/go1.16.3/go/pkg/tool/linux_386/go_bootstrap: exec format
error

google-go-lang:
Would you like to continue processing the rest of the
queue or would you like to abort?  If this failed
package is a dependency of another package in the queue
then it may not make sense to continue.

(Y)es to continue, (N)o to abort, (R)etry the build?:

I'd still consider myself a newbie. I'd really appreciate if someone could help explain what's going on here.

allend · 05-17-2021, 06:51 PM

I found I needed to add --enable-qt5 as a configure option in the lyx.SlackBuild (under office) to build lyx-2.3.6.1 on -current.

enine · 05-17-2021, 08:38 PM

Quote:

Originally Posted by burning

Running -current and using Ponce's repo. I was trying to build and install the google-go-lang package through sbopkg but I keep getting this error:

Code:

Building Go cmd/dist using /usr. (go1.14.6 gccgo (GCC) 10.3.0 linux/386)
Building Go toolchain1 using /usr.
Building Go bootstrap cmd/go (go_bootstrap) using Go toolchain1.
panic: invalid argument

goroutine 1 [running]:
bootstrap..z2fcmd..z2flink..z2finternal..z2fld.Main
        /tmp/SBo/package-google-go-lang/usr/lib/go1.16.3/go/src/cmd/link/internal/ld/main.go:333
main.main
        /tmp/SBo/package-google-go-lang/usr/lib/go1.16.3/go/src/cmd/link/main.go:68
makecontext
        :0

go tool dist: FAILED: /tmp/SBo/package-google-go-lang/usr/lib/go1.16.3/go/pkg/tool/linux_386/link -extld=gcc -o /tmp/SBo/package-google-go-lang/usr/lib/go1.16.3/go/pkg/tool/linux_386/go_bootstrap /tmp/go-tool-dist-382298166/cmd/go/_go_.a: exit status 2
Building Go toolchain2 using go_bootstrap and Go toolchain1.
go tool dist: FAILED: /tmp/SBo/package-google-go-lang/usr/lib/go1.16.3/go/pkg/tool/linux_386/go_bootstrap install -gcflags=all= -ldflags=all= -i
cmd/asm cmd/cgo cmd/compile cmd/link: fork/exec /tmp/SBo/package-google-go-lang/usr/lib/go1.16.3/go/pkg/tool/linux_386/go_bootstrap: exec format
error

google-go-lang:
Would you like to continue processing the rest of the
queue or would you like to abort?  If this failed
package is a dependency of another package in the queue
then it may not make sense to continue.

(Y)es to continue, (N)o to abort, (R)etry the build?:

I'd still consider myself a newbie. I'd really appreciate if someone could help explain what's going on here.

I just gave this a quick try myself and it built fine

Code:

Slackware package /tmp/google-go-lang-1.16.3-x86_64-1_SBo.tgz created.

chrisretusn · 05-17-2021, 08:58 PM

Quote:

Originally Posted by ponce

are you sure? because they don't seem to be in the upstream tarball...

I just checked again, yep, my bust, you are correct.

mea culpa... I checked the date on my package, Jul 14, 2018. It built just fine back then. I just ran my SlackBuild, yep it errors out. Applied the patch, it builds.

willysr · 05-17-2021, 10:29 PM

Quote:

Originally Posted by allend

I found I needed to add --enable-qt5 as a configure option in the lyx.SlackBuild (under office) to build lyx-2.3.6.1 on -current.

Strange, i build just fine here using sbopkg

allend · 05-17-2021, 11:02 PM

Quote:

Strange, i build just fine here using sbopkg

I saw this initially when building on a 32 bit machine after retrieving the SlackBuild files from Ponce's repository. The build stopped suggesting a problem with $QTDIR.
I do not use sbopkg.
I have subsequently built lyx on a 64 bit machine with the added configure option, but I did not try without the added configure option.
I only have qt5 installed. Any chance you have qt4 somewhere?

Ilgar · 05-18-2021, 01:43 AM

Quote:

Originally Posted by willysr

Strange, i build just fine here using sbopkg

Same here. I recently communicated with the maintainer, he had added Qt5 as a dependency for the 14.2 slackbuild, too (while preparing for 15.0). He kindly reverted that (for the 14.2 repo) but the ponce repo version picked up Qt5 and compiled here.

Quote:

Originally Posted by bassmadrigal

I think a qt4 SlackBuild is in the works to be added to SBo for 15.0 to allow all that software that was never updated to qt5 to still be able to be used. If a piece of software can be updated to qt5, it probably should, but if it only supports qt4, removal because of that should only happen if it's found a qt4 SlackBuild isn't going to be added to SBo.

I agree. Since a qt4 build doesn't exist yet I assumed it wouldn't be there. If there is goint to be one, we should keep the Qt4-only software too.

kevmccor · 05-18-2021, 07:16 AM

Quote:

Originally Posted by willysr

Have you make sure that lxml is built with python 2 and 3?

How do you do that?

willysr · 05-18-2021, 12:06 PM

if you use the latest version in git, it will be include both python2 and 3 bindings

cdek · 05-18-2021, 01:09 PM

I get an error trying to build wine. My slackware current system is up to date and multilib is installed through slackpkg+.

The error I get is

Code:

gcc -m32 -c -o dlls/l3codeca.acm/mpegl3.o ../dlls/l3codeca.acm/mpegl3.c -Idlls/l3codeca.acm -I../dlls/l3codeca.acm -Iinclude \
  -I../include -D__WINESRC__ -D_REENTRANT -fno-PIC -fasynchronous-unwind-tables -Wall -pipe \
  -fcf-protection=none -fno-stack-protector -fno-strict-aliasing -Wdeclaration-after-statement \
  -Wempty-body -Wignored-qualifiers -Wno-packed-not-aligned -Wshift-overflow=2 -Wstrict-prototypes \
  -Wtype-limits -Wunused-but-set-parameter -Wvla -Wwrite-strings -Wpointer-arith -Wlogical-op \
  -fno-omit-frame-pointer -O2 -fPIC
tools/winegcc/winegcc -o dlls/l3codeca.acm/l3codeca.acm.so --wine-objdir . -m32 -fno-PIC -fasynchronous-unwind-tables -shared \
  ../dlls/l3codeca.acm/l3codeca.acm.spec dlls/l3codeca.acm/mpegl3.o -lwinmm -luser32 \
  libs/port/libwine_port.a -lmpg123 -L/usr/lib -ldl
/usr/bin/ld: l3codeca.acm-So5nzd.spec.o: warning: relocation in read-only section `.text'
/usr/bin/ld: dlls/l3codeca.acm/mpegl3.o: in function `.L68':
mpegl3.c:(.text+0xe66): undefined reference to `mpg123_param2'
/usr/bin/ld: warning: creating DT_TEXTREL in a shared object
collect2: error: ld returned 1 exit status
winegcc: /usr/bin/gcc failed
make: *** [Makefile:76660: dlls/l3codeca.acm/l3codeca.acm.so] Error 2
Failure encountered while building wine:
  wine.SlackBuild return non-zero

As usual, I have no clue what's going on...

ponce · 05-18-2021, 01:27 PM

please report the build error to the wine maintainer on SBo.

burning · 05-18-2021, 01:53 PM

Quote:

Originally Posted by enine

I just gave this a quick try myself and it built fine

Code:

Slackware package /tmp/google-go-lang-1.16.3-x86_64-1_SBo.tgz created.

Any idea why it's not working on my machine? I'm running 32-bit if it's any consolation.

Ilgar · 05-18-2021, 02:25 PM

Quote:

Originally Posted by Ilgar

Hello,

In the last two days I compiled quite a few packages for -current using ponce's repository. Here are two issues I ran into:

1) gdl, a requirement for inkscape is not in the repo. Using the slackbuild for 14.2 works. Inkscape is at version 1.0 in the repo and versions 1.1 and later do not use gdl. So we either need a version bump in inkscape or the addition of gdl. Since I'm not the decision maker on this I decided to drop it here.

2) qucs is in the repo but apparently it has no Qt5 support yet, and does not compile. It should probably be removed.

There were also build issues with xfce4-xkb-plugin, ktikz, coq, udftools, unetbootin, qcad, aqemu, shaderc. I contacted the maintainers about these. I managed to compile all but the last two by upgrading to the latest versions and/or modifying the slackbuild a little.

Here is an update on the last part:

xfce4-xkb-plugin: An upgrade to 0.8.2 fixes the build (the maintainer is rworkman, he will probably do that).

ktikz: The maintainer will send the updated build when 15.0 comes out. His repo is here.

aqemu: The maintainer said he gave up on this one. I managed to make an updated 0.9.4 version compile with two small patches. I didn't run it, but it is said that aqemu has not been updated to be compatible with the recent versions of qemu, so it may not work properly anyway. Maybe time to remove it?

shaderc: Following the maintainer's (orbea) hint, I installed glslang first and it compiled. glslang is not in ponce's repo right now but the scripts from the 14.2 repo for glslang and its depencencies work without modification.

No reply so far about unetbootin, qcad, or udftools. But one only needs to upgrade these to versions 702, 3.26.2.0 and 3.2, respectively.

For coq, a new package "num" is neded (see here). I tried to compile and install it. make install failed with an error, but I was able to build coq afterwards (I'm yet to hear from the maintainer for this one, too).

enine · 05-18-2021, 02:26 PM

Quote:

Originally Posted by burning

Any idea why it's not working on my machine? I'm running 32-bit if it's any consolation.

I've not used sbopkg, maybe it needs an update for -current? Have you tried just running the slackbuild the normal way?

ponce · 05-18-2021, 04:06 PM

Quote:

Originally Posted by Ilgar

aqemu: The maintainer said he gave up on this one. I managed to make an updated 0.9.4 version compile with two small patches. I didn't run it, but it is said that aqemu has not been updated to be compatible with the recent versions of qemu, so it may not work properly anyway. Maybe time to remove it?

if Edward is ok to remove it I can do it.

Quote:

shaderc: Following the maintainer's (orbea) hint, I installed glslang first and it compiled. glslang is not in ponce's repo right now but the scripts from the 14.2 repo for glslang and its depencencies work without modification.

glslang is already on current as part of vulkan-sdk, if you install another glslang package you overwrite that: if this is not resolvable in another way shaderc will have to be removed.