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

ponce · 01-18-2021, 12:03 AM

Quote:

Originally Posted by drgibbon

No go with arpack-ng:

Code:

patching file m4/ax_blas.m4
Hunk #1 succeeded at 119 (offset 3 lines).
patching file SRC/cgetv0.f
Reversed (or previously applied) patch detected!  Assume -R? [n]
Apply anyway? [n]
Skipping patch.

[...]

patching file SRC/zngets.f
Reversed (or previously applied) patch detected!  Assume -R? [n]
Apply anyway? [n]
Skipping patch.
1 out of 1 hunk ignored -- saving rejects to file SRC/zngets.f.rej
Failures:
  arpack-ng: arpack-ng.SlackBuild return non-zero

etc.

yes, that happens because it has been updated on SBo and now the patch for gcc >= 10.x is most probably not necessary anymore...
thanks for the report!

drgibbon · 01-18-2021, 01:15 AM

Ah yep, builds fine on -current without the two patch lines.

Dan Suson · 01-19-2021, 08:03 PM

GraphicsMagic does not build. It is a very strange compilation error:

Code:

Checking if your kit is complete...
Looks good
Warning (mostly harmless): No library found for -lGraphicsMagick
Generating a Unix-style Makefile
Writing Makefile for Graphics::Magick
Writing MYMETA.yml and MYMETA.json
cp Magick.pm blib/lib/Graphics/Magick.pm
AutoSplitting blib/lib/Graphics/Magick.pm (blib/lib/auto/Graphics/Magick)
Running Mkbootstrap for Magick ()
chmod 644 "Magick.bs"
"/usr/bin/perl5.32.0" -MExtUtils::Command::MM -e 'cp_nonempty' -- Magick.bs blib/arch/auto/Graphics/Magick/Magick.bs 644
"/usr/bin/perl5.32.0" "/usr/share/perl5/ExtUtils/xsubpp"  -typemap '/usr/share/perl5/ExtUtils/typemap' -typemap '/tmp/SBo/GraphicsMagick-1.3.35/PerlMagick/typemap'  Magick.xs > Magick.xsc
mv Magick.xsc Magick.c
gcc -c  -I../ -I.. -I/usr/include/freetype2 -I/usr/include/libxml2 -D_REENTRANT -D_GNU_SOURCE -fwrapv -fno-strict-aliasing -pipe -fstack-protector-strong -I/usr/local/include -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -D_FORTIFY_SOURCE=2 -fopenmp -O2 -fPIC -Wall -pthread -O2 -fPIC   -DVERSION=\"1.3.35\" -DXS_VERSION=\"1.3.35\" -fPIC "-I/usr/lib64/perl5/CORE"  -D_LARGE_FILES=1 -DHAVE_CONFIG_H Magick.c
In file included from Magick.xs:57:
/usr/lib64/perl5/CORE/perl.h:1363:12: fatal error: netdb.h: No such file or directory
 1363 | #  include <netdb.h>
      |            ^~~~~~~~~
compilation terminated.

When I tried to follow this, netdb.h is a part of glibc and perl.h is coming from the perl 5.32.0 package. I'm not sure how to fix this! Any help would be appreciated.

ponce · 01-20-2021, 01:18 AM

Quote:

Originally Posted by Dan Suson

GraphicsMagic does not build. It is a very strange compilation error:

Code:

Checking if your kit is complete...
Looks good
Warning (mostly harmless): No library found for -lGraphicsMagick
Generating a Unix-style Makefile
Writing Makefile for Graphics::Magick
Writing MYMETA.yml and MYMETA.json
cp Magick.pm blib/lib/Graphics/Magick.pm
AutoSplitting blib/lib/Graphics/Magick.pm (blib/lib/auto/Graphics/Magick)
Running Mkbootstrap for Magick ()
chmod 644 "Magick.bs"
"/usr/bin/perl5.32.0" -MExtUtils::Command::MM -e 'cp_nonempty' -- Magick.bs blib/arch/auto/Graphics/Magick/Magick.bs 644
"/usr/bin/perl5.32.0" "/usr/share/perl5/ExtUtils/xsubpp"  -typemap '/usr/share/perl5/ExtUtils/typemap' -typemap '/tmp/SBo/GraphicsMagick-1.3.35/PerlMagick/typemap'  Magick.xs > Magick.xsc
mv Magick.xsc Magick.c
gcc -c  -I../ -I.. -I/usr/include/freetype2 -I/usr/include/libxml2 -D_REENTRANT -D_GNU_SOURCE -fwrapv -fno-strict-aliasing -pipe -fstack-protector-strong -I/usr/local/include -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -D_FORTIFY_SOURCE=2 -fopenmp -O2 -fPIC -Wall -pthread -O2 -fPIC   -DVERSION=\"1.3.35\" -DXS_VERSION=\"1.3.35\" -fPIC "-I/usr/lib64/perl5/CORE"  -D_LARGE_FILES=1 -DHAVE_CONFIG_H Magick.c
In file included from Magick.xs:57:
/usr/lib64/perl5/CORE/perl.h:1363:12: fatal error: netdb.h: No such file or directory
 1363 | #  include <netdb.h>
      |            ^~~~~~~~~
compilation terminated.

When I tried to follow this, netdb.h is a part of glibc and perl.h is coming from the perl 5.32.0 package. I'm not sure how to fix this! Any help would be appreciated.

Hi Dan,

I just tested building GraphicsMagick on a clean and full installation of the latest Slackware current and everything went fine: if I were you I would try reinstalling glibc but if this won't solve please open a dedicated topic for this issue.

Dan Suson · 01-20-2021, 04:44 PM

Quote:

Originally Posted by ponce

Hi Dan,

I just tested building GraphicsMagick on a clean and full installation of the latest Slackware current and everything went fine: if I were you I would try reinstalling glibc but if this won't solve please open a dedicated topic for this issue.

I noticed that glibc has gone from version 2.30 in what I downloaded on 1-2-21 to 2.32 as of 1-18-21. Can I just upgrade this package or do I have to treat this as a complete upgrade (as outlined in UPGRADE.TXT). Just trying to figure out the level of work that I'll have to redo.

Lockywolf · 01-20-2021, 08:18 PM

Quote:

Originally Posted by newHeiko

virtualbox-kernel does not build on 5.10.x - anyone working on that yet?

Here's upstream information: https://www.virtualbox.org/ticket/20055

Cheers,
Heiko

New (2020-01-19) VirtualBox fixes 5.10 support.

ponce · 01-21-2021, 01:24 AM

Quote:

Originally Posted by Dan Suson

I noticed that glibc has gone from version 2.30 in what I downloaded on 1-2-21 to 2.32 as of 1-18-21. Can I just upgrade this package or do I have to treat this as a complete upgrade (as outlined in UPGRADE.TXT). Just trying to figure out the level of work that I'll have to redo.

if you are tracking current you have to upgrade everything, you cannot upgrade just single packages and this is even more recommended in case of glibc that is part of the system's toolchain.
another consequence of tracking current is that, occasionally, you have to rebuild some packages from the third party repositories (like this one) when their dependencies are upgraded in current.

you can also decide to not upgrade anything installing current at a specific moment and forget any upgrade but, besides security problems and bugs that a system installed at a specific moment and not upgraded may have, also third party repositories that instead keep tracking current may become soon incompatible with your system.

ponce · 01-21-2021, 01:26 AM

Quote:

Originally Posted by newHeiko

virtualbox-kernel does not build on 5.10.x - anyone working on that yet?

Here's upstream information: https://www.virtualbox.org/ticket/20055

Quote:

Originally Posted by Lockywolf

New (2020-01-19) VirtualBox fixes 5.10 support.

I pushed it yesterday, it will go in the main branch at the next global update.

http://cgit.ponce.cc/slackbuilds/refs/heads

Lockywolf · 01-21-2021, 01:45 AM

transmission-remote-gtk needs:

Code:

sed -i '163i-fcommon \\' configure.ac
autoreconf -i

btw, it seems to ignore CFLAGS, if I am not mistaken.

ponce · 01-21-2021, 01:57 AM

Quote:

Originally Posted by Lockywolf

transmission-remote-gtk needs:

Code:

sed -i '163i-fcommon \\' configure.ac
autoreconf -i

it seems there's actually an upstream commit for that...
thanks for the report!

Lockywolf · 01-21-2021, 02:02 AM

I thought that this repo is about making existing slackbuilds compile. Who knows when and if upstream gets into SBo?

ponce · 01-21-2021, 02:06 AM

Quote:

Originally Posted by Lockywolf

I thought that this repo is about making existing slackbuilds compile. Who knows when and if upstream gets into SBo?

...but you can patch the code with the upstream commit so that it compiles, like this

http://cgit.ponce.cc/slackbuilds/com...ion-remote-gtk

a patch is usually prefered to -fcommon because it actually fixes the code instead of workaround what is considered bad practice from gcc >= 10.x on.

Lockywolf · 01-21-2021, 02:29 AM

Indeed, but isn't Slackware's principle "keep it as close to the origin as possible"? At least, if things go wrong, chances are they are going to go wrong identically on 14.2 and on current.

One can argue for the opposite point though.

jostber · 01-21-2021, 02:36 AM

Installing the nagios SlackBuild errors out with this:

Code:

/usr/bin/ld: xstatusdata-cgi.o:(.bss+0xd0): multiple definition of `daemon_mode'; ../common/shared.o:(.bss+0x38): first defined here
/usr/bin/ld: xstatusdata-cgi.o:(.bss+0x94): multiple definition of `nagios_pid'; ../common/shared.o:(.bss+0x3c): first defined here
collect2: error: ld returned 1 exit status
make[1]: *** [Makefile:177: archivejson.cgi] Error 1
make[1]: Leaving directory '/tmp/SBo/nagios-4.3.4/cgi'
make: *** [Makefile:74: all] Error 2

ponce · 01-21-2021, 02:54 AM

Quote:

Originally Posted by jostber

Installing the nagios SlackBuild errors out with this:

Code:

/usr/bin/ld: xstatusdata-cgi.o:(.bss+0xd0): multiple definition of `daemon_mode'; ../common/shared.o:(.bss+0x38): first defined here
/usr/bin/ld: xstatusdata-cgi.o:(.bss+0x94): multiple definition of `nagios_pid'; ../common/shared.o:(.bss+0x3c): first defined here
collect2: error: ld returned 1 exit status
make[1]: *** [Makefile:177: archivejson.cgi] Error 1
make[1]: Leaving directory '/tmp/SBo/nagios-4.3.4/cgi'
make: *** [Makefile:74: all] Error 2

modify the CFLAGS line line this

Code:

--- ./nagios.SlackBuild.orig    2021-01-21 09:53:49.863404725 +0100
+++ ./nagios.SlackBuild 2021-01-21 09:53:06.057404725 +0100
@@ -105,7 +105,7 @@
  \( -perm 666 -o -perm 664 -o -perm 640 -o -perm 600 -o -perm 444 \
   -o -perm 440 -o -perm 400 \) -exec chmod 644 {} \;
 
-CFLAGS="$SLKCFLAGS" \
+CFLAGS="$SLKCFLAGS -w -Wl,--allow-multiple-definition" \
   ./configure \
   --prefix=/usr \
   --sbindir=/usr/sbin/$PRGNAM \

thanks for reporting!