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

USUARIONUEVO · 09-29-2017, 07:19 PM

Quote:

Originally Posted by sombragris

After the last poppler updates, inkscape fails to build.

Since the error log is too big, I uploaded it to this pastebin:

https://hastebin.com/jasetulagi.java

ponce fix this some days ago.

https://github.com/Ponce/slackbuilds...22e48b4df538e2

sombragris · 09-29-2017, 10:04 PM

Thank you!!

USUARIONUEVO · 10-03-2017, 05:10 PM

PLease , remove this slackbuild , cython in current have python2 + python3 bindings

Quote:

python3-Cython

Thanks !

Skaendo · 10-04-2017, 02:33 AM

Hey everyone, I'm having a issue building glade (glade3) on a fresh full install of Slackware64-current (Tue Oct 3 21:06:59 UTC 2017).

Kind of stumped on this one, some help is appreciated. Full log here: https://pastebin.com/rvaczMjZ

ponce · 10-04-2017, 03:05 AM

Hi Skaendo,

modify the SlackBuild files like this to build version 3.20.1

Code:

diff -Naur glade.orig/glade.SlackBuild glade/glade.SlackBuild
--- glade.orig/glade.SlackBuild 2017-10-02 11:18:19.307182415 +0200
+++ glade/glade.SlackBuild      2017-10-04 09:57:00.796254004 +0200
@@ -23,13 +23,13 @@
 #  ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
 
 PRGNAM=glade
-VERSION=${VERSION:-3.18.3}
+VERSION=${VERSION:-3.20.1}
 BUILD=${BUILD:-1}
 TAG=${TAG:-_SBo}
 
 if [ -z "$ARCH" ]; then
   case "$( uname -m )" in
-    i?86) ARCH=i486 ;;
+    i?86) ARCH=i586 ;;
     arm*) ARCH=arm ;;
        *) ARCH=$( uname -m ) ;;
   esac
@@ -41,8 +41,8 @@
 PKG=$TMP/package-$PRGNAM
 OUTPUT=${OUTPUT:-/tmp}
 
-if [ "$ARCH" = "i486" ]; then
-  SLKCFLAGS="-O2 -march=i486 -mtune=i686"
+if [ "$ARCH" = "i586" ]; then
+  SLKCFLAGS="-O2 -march=i586 -mtune=i686"
   LIBDIRSUFFIX=""
 elif [ "$ARCH" = "i686" ]; then
   SLKCFLAGS="-O2 -march=i686 -mtune=i686"
diff -Naur glade.orig/glade.info glade/glade.info
--- glade.orig/glade.info       2017-10-02 11:18:19.307182415 +0200
+++ glade/glade.info    2017-10-04 09:56:29.287253737 +0200
@@ -1,8 +1,8 @@
 PRGNAM="glade"
-VERSION="3.18.3"
+VERSION="3.20.1"
 HOMEPAGE="https://glade.gnome.org"
-DOWNLOAD="https://ftp.gnome.org/pub/GNOME/sources/glade/3.18/glade-3.18.3.tar.xz"
-MD5SUM="6852d6286683728e0ea40ca9b5d2416f"
+DOWNLOAD="https://ftp.gnome.org/pub/GNOME/sources/glade/3.20/glade-3.20.1.tar.xz"
+MD5SUM="60f01ccc4e9a4e5de5a5402d10495dc4"
 DOWNLOAD_x86_64=""
 MD5SUM_x86_64=""
 REQUIRES=""

ponce · 10-04-2017, 03:07 AM

Quote:

Originally Posted by USUARIONUEVO

PLease , remove this slackbuild , cython in current have python2 + python3 bindings

python3-Cython

Thanks !

Thanks to you for reporting!

Skaendo · 10-04-2017, 03:20 AM

Quote:

Originally Posted by ponce

Hi Skaendo,

modify the SlackBuild files like this to build version 3.20.1

LOL, why didn't I think about that. Thanks Ponce.

franzen · 10-05-2017, 03:30 AM

Hi,

in -current, the t1utils are now provided by texlive, so
the t1utils-buildscripts are obsolete now.

This affects following packages:
./graphics/lilypond/lilypond.info:REQUIRES="fontforge t1utils guile1.8"
./graphics/mftrace/mftrace.info:REQUIRES="potrace t1utils"

ponce · 10-05-2017, 03:51 AM

Quote:

Originally Posted by franzen

Hi,

in -current, the t1utils are now provided by texlive, so
the t1utils-buildscripts are obsolete now.

This affects following packages:
./graphics/lilypond/lilypond.info:REQUIRES="fontforge t1utils guile1.8"
./graphics/mftrace/mftrace.info:REQUIRES="potrace t1utils"

thanks franzen, I pushed the removal of the script but I'll avoid removing the string from the REQUIRES lines until SBo will go live with the next major release, as this kind of stuff is really painful to rebase (ATM I'm already rebasing =~ 330 branches every week).

franzen · 10-05-2017, 04:12 AM

Quote:

Originally Posted by ponce

thanks franzen, I pushed the removal of the script but I'll avoid removing the string from the REQUIRES lines until SBo will go live with the next major release, as this kind of stuff is really painful to rebase (ATM I'm already rebasing =~ 330 branches every week).

Ok, and thanks. pdfjam is also obsolete as it's also shipped with texlive(base).

ponce · 10-05-2017, 04:14 AM

thanks again, I pushed that too.

willysr · 10-05-2017, 04:15 AM

I can find pdfjam in texlive, but i can't find t1utils in texlive
do they have different name?

franzen · 10-05-2017, 04:27 AM

Quote:

Originally Posted by willysr

I can find pdfjam in texlive, but i can't find t1utils in texlive
do they have different name?

You can see it in the sources, one of the compiled binaries is e.g. /usr/bin/t1asm

Code:

texlive-20170520-source/utils/t1utils/
texlive-20170520-source/utils/t1utils/version.ac
texlive-20170520-source/utils/t1utils/strerror.c
texlive-20170520-source/utils/t1utils/configure.ac
texlive-20170520-source/utils/t1utils/aclocal.m4
texlive-20170520-source/utils/t1utils/Makefile.am
texlive-20170520-source/utils/t1utils/t1utils-src/
texlive-20170520-source/utils/t1utils/t1utils-src/include/
texlive-20170520-source/utils/t1utils/t1utils-src/include/lcdf/
texlive-20170520-source/utils/t1utils/t1utils-src/include/lcdf/inttypes.h
texlive-20170520-source/utils/t1utils/t1utils-src/include/lcdf/clp.h
texlive-20170520-source/utils/t1utils/t1utils-src/t1binary.1
texlive-20170520-source/utils/t1utils/t1utils-src/t1binary.c
texlive-20170520-source/utils/t1utils/t1utils-src/configure.ac
texlive-20170520-source/utils/t1utils/t1utils-src/t1disasm.c
texlive-20170520-source/utils/t1utils/t1utils-src/Makefile.am
texlive-20170520-source/utils/t1utils/t1utils-src/t1asmhelp.h
texlive-20170520-source/utils/t1utils/t1utils-src/t1utils.spec
texlive-20170520-source/utils/t1utils/t1utils-src/t1asm.1
texlive-20170520-source/utils/t1utils/t1utils-src/t1unmac.1
texlive-20170520-source/utils/t1utils/t1utils-src/t1asm.c
texlive-20170520-source/utils/t1utils/t1utils-src/t1mac.c
texlive-20170520-source/utils/t1utils/t1utils-src/t1lib.h
texlive-20170520-source/utils/t1utils/t1utils-src/t1unmac.c
texlive-20170520-source/utils/t1utils/t1utils-src/config.h.in
texlive-20170520-source/utils/t1utils/t1utils-src/t1disasm.1
texlive-20170520-source/utils/t1utils/t1utils-src/clp.c
texlive-20170520-source/utils/t1utils/t1utils-src/t1lib.c
texlive-20170520-source/utils/t1utils/t1utils-src/NEWS
texlive-20170520-source/utils/t1utils/t1utils-src/INSTALL
texlive-20170520-source/utils/t1utils/t1utils-src/t1ascii.1
texlive-20170520-source/utils/t1utils/t1utils-src/t1ascii.c
texlive-20170520-source/utils/t1utils/t1utils-src/README
texlive-20170520-source/utils/t1utils/t1utils-src/t1mac.1
texlive-20170520-source/utils/t1utils/ChangeLog
texlive-20170520-source/utils/t1utils/TLpatches/
texlive-20170520-source/utils/t1utils/TLpatches/patch-05-getopt
texlive-20170520-source/utils/t1utils/TLpatches/patch-03-warnings
texlive-20170520-source/utils/t1utils/TLpatches/ChangeLog
texlive-20170520-source/utils/t1utils/TLpatches/TL-Changes
texlive-20170520-source/utils/t1utils/TLpatches/patch-04-TL-binary
texlive-20170520-source/utils/t1utils/TLpatches/patch-07-warnings
texlive-20170520-source/utils/t1utils/tests/
texlive-20170520-source/utils/t1utils/tests/Symbol.pfb
texlive-20170520-source/utils/t1utils/tests/Symbol.pfa
texlive-20170520-source/utils/t1utils/tests/Symbol.raw
texlive-20170520-source/utils/t1utils/Makefile.in
texlive-20170520-source/utils/t1utils/config.h.in
texlive-20170520-source/utils/t1utils/configure
texlive-20170520-source/utils/t1utils/ac/
texlive-20170520-source/utils/t1utils/ac/withenable.ac
texlive-20170520-source/utils/t1utils/t1utils.test

ponce · 10-06-2017, 10:25 AM

FYI, many build scripts for perl modules on SBo will break from today on because, since perl-5.26.x, . isn't included in INC anymore: the solution to be able again to create perl packages from these modules, for now, is to export the shell variable PERL_USE_UNSAFE_INC=1 in your build environment, but this won't help if the installed scripts/perl modules will try to use . as an include path at runtime.

I'll wait before patching the interested SlackBuilds as their newer versions might be already patched for this.

obviously this gotcha applies also to every pre-existing perl script that you will try to run with the new perl interpreter in current.

dugan · 10-06-2017, 12:13 PM

May I suggest building vim with Python 3 support, now that Slackware ships Python 3?

I'd imagine that Slackware would want to ship vim with both Python 3 and Python 2 support.

For my own systems, I build in only Python 3 support. I'm very much a vim power user, and I don't miss the Python 2 support.

EDIT: Sorry, I meant to post this in the "what would you like to see in -current?" thread.