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

willysr · 01-24-2020, 01:24 PM

It seems the situation is more complex as luajit must be compiled in Lua 5.2 mode in order to use the system's lua.

willysr · 01-24-2020, 01:31 PM

works fine here on cryptography in current. No need to install wheel

ponce · 01-24-2020, 01:47 PM

hi unInstance,

have you by any chance read the first post of the thread?

Quote:

Originally Posted by unInstance

How to build openresolv:
Open openresolv.SlackBuild and remove

Code:

cp README $PKG/usr/doc/$PRGNAM-$VERSION

this is an issue not current-specific, you should report it to the openresolv maintainer: there's actually no README in the tarball, but there's a README.md...

Quote:

How to build neomutt:
Open neomutt.SlackBuild in vim and apply the following command

Code:

:%s/PRGNAM/PKGNAM/g

this builds fine here, I have no idea why you have to do that there...

unInstance · 01-24-2020, 02:55 PM

Quote:

Originally Posted by ponce

this builds fine here, I have no idea why you have to do that there...

This is what I am facing with while trying to build:

Code:

neomutt.SlackBuild.build: line 111: PKGNAM: unbound variable

bassmadrigal · 01-24-2020, 03:26 PM

Quote:

Originally Posted by unInstance

How to build openresolv:
Open openresolv.SlackBuild and remove

Code:

cp README $PKG/usr/doc/$PRGNAM-$VERSION

Quote:

Originally Posted by ponce

this is an issue not current-specific, you should report it to the openresolv maintainer: there's actually no README in the tarball, but there's a README.md...

I'm the maintainer of openresolv. I forgot about this issue when I submitted my last update. I fixed the script and submitted a pull request to fix it today.

ponce · 01-24-2020, 11:33 PM

Quote:

Originally Posted by unInstance

This is what I am facing with while trying to build:

Code:

neomutt.SlackBuild.build: line 111: PKGNAM: unbound variable

I think you are using an old version of the repository: this has been fixed eight days ago.

rworkman · 01-25-2020, 01:38 AM

Quote:

Originally Posted by ponce

it seems that there are problems in the headers generated by glib-mkenums (a generated line starts with a backslash) and build breaks at the start, but I wasn't able to find a solution yet...

Well, just crap. If I'd read this about thirty minutes ago, I could have saved the last thirty minutes I've spent figuring out that very thing. However, I think it's a problem with the new make-4.3:

Code:

* WARNING: Backward-incompatibility!
  Number signs (#) appearing inside a macro reference or function invocation
  no longer introduce comments and should not be escaped with backslashes:
  thus a call such as:
    foo := $(shell echo '#')
  is legal.  Previously the number sign needed to be escaped, for example:
    foo := $(shell echo '\#')
  Now this latter will resolve to "\#".  If you want to write makefiles
  portable to both versions, assign the number sign to a variable:
    H := \#
    foo := $(shell echo '$H')
  This was claimed to be fixed in 3.81, but wasn't, for some reason.
  To detect this change search for 'nocomment' in the .FEATURES variable.

I too was unable to fix it, at least not without breaking something else that made the build fail. :/

Tonus · 01-25-2020, 01:38 AM

Indeed, for neomutt I reported it to maintainer who fixed it ;-)

ponce · 01-25-2020, 02:01 AM

Quote:

Originally Posted by Nille_kungen

I had problems building cryptography.
It needs wheel as dependency on current.
Cryptography also needs version 2.8 to build with python 3.8
https://cryptography.io/en/latest/changelog/#v2-8

as willysr said the old version seems to build fine here too, but if also upstream says that version 2.8 is needed by python 3.8 I suppose it's better to bump it: yes, according to pyproject.toml, it actually needs wheel as a dependency...

thanks for the report!

ponce · 01-25-2020, 03:09 AM

Quote:

Originally Posted by rworkman

Well, just crap. If I'd read this about thirty minutes ago, I could have saved the last thirty minutes I've spent figuring out that very thing. However, I think it's a problem with the new make-4.3:

Code:

* WARNING: Backward-incompatibility!
  Number signs (#) appearing inside a macro reference or function invocation
  no longer introduce comments and should not be escaped with backslashes:
  thus a call such as:
    foo := $(shell echo '#')
  is legal.  Previously the number sign needed to be escaped, for example:
    foo := $(shell echo '\#')
  Now this latter will resolve to "\#".  If you want to write makefiles
  portable to both versions, assign the number sign to a variable:
    H := \#
    foo := $(shell echo '$H')
  This was claimed to be fixed in 3.81, but wasn't, for some reason.
  To detect this change search for 'nocomment' in the .FEATURES variable.

I too was unable to fix it, at least not without breaking something else that made the build fail. :/

reporting it upstream will be difficult because they moved to meson removing all the make stuff...

...but that seems to help here too indeed: I've tried to switch to meson and gst-plugins-bad seems to build fine!

Skaendo · 01-25-2020, 01:56 PM

Quote:

Originally Posted by ponce

reporting it upstream will be difficult because they moved to meson removing all the make stuff...

...but that seems to help here too indeed: I've tried to switch to meson and gst-plugins-bad seems to build fine!

Thanks for the meson tip, works here as well.

Only problem is now reading the log and figuring out what is getting built is EXTREMELY more difficult. Instead of a nice list of what is getting built after the config process, you need to read through the entire config process and see what is found and being built. Great job freedesktop.org!

lioh · 01-28-2020, 08:58 AM

gedit is not building. It fails with the following error:

Code:

if ! test -d ar/; then mkdir ar/; fi
if [ -f "C/gedit.xml" ]; then d="../"; else d="/tmp/SBo/gedit-2.30.4/help/"; fi; \
mo="ar/ar.mo"; \
if [ -f "${mo}" ]; then mo="../${mo}"; else mo="/tmp/SBo/gedit-2.30.4/help/${mo}"; fi; \
(cd ar/ && \
  `which xml2po` -m docbook -e -t "${mo}" \
    "${d}C/gedit.xml" > gedit.xml.tmp && \
    cp gedit.xml.tmp gedit.xml && rm -f gedit.xml.tmp)
Traceback (most recent call last):
  File "/usr/bin/xml2po", line 191, in <module>
    main(sys.argv[1:])
  File "/usr/bin/xml2po", line 88, in main
    from xml2po import Main
ModuleNotFoundError: No module named 'xml2po'
make[2]: *** [Makefile:756: ar/gedit.xml] Error 1
make[2]: Leaving directory '/tmp/SBo/gedit-2.30.4/help'
make[1]: *** [Makefile:445: all-recursive] Error 1
make[1]: Leaving directory '/tmp/SBo/gedit-2.30.4'
make: *** [Makefile:374: all] Error 2

Didier Spaier · 01-28-2020, 12:19 PM

Quote:

Originally Posted by lioh

gedit is not building. It fails with the following error:

Code:

if ! test -d ar/; then mkdir ar/; fi
if [ -f "C/gedit.xml" ]; then d="../"; else d="/tmp/SBo/gedit-2.30.4/help/"; fi; \
mo="ar/ar.mo"; \
if [ -f "${mo}" ]; then mo="../${mo}"; else mo="/tmp/SBo/gedit-2.30.4/help/${mo}"; fi; \
(cd ar/ && \
  `which xml2po` -m docbook -e -t "${mo}" \
    "${d}C/gedit.xml" > gedit.xml.tmp && \
    cp gedit.xml.tmp gedit.xml && rm -f gedit.xml.tmp)
Traceback (most recent call last):
  File "/usr/bin/xml2po", line 191, in <module>
    main(sys.argv[1:])
  File "/usr/bin/xml2po", line 88, in main
    from xml2po import Main
ModuleNotFoundError: No module named 'xml2po'
make[2]: *** [Makefile:756: ar/gedit.xml] Error 1
make[2]: Leaving directory '/tmp/SBo/gedit-2.30.4/help'
make[1]: *** [Makefile:445: all-recursive] Error 1
make[1]: Leaving directory '/tmp/SBo/gedit-2.30.4'
make: *** [Makefile:374: all] Error 2

You have linuxdox-tools installed, right?

USUARIONUEVO · 01-28-2020, 12:38 PM

ModuleNotFoundError: No module named 'xml2po'

bassmadrigal · 01-28-2020, 01:05 PM

The problem is xml2po is compiled as a python2 package in the linuxdoc-tools package, but /usr/bin/xml2po expects it to by python3. The reason behind this is an issue is the ./configure for gnome-doc-utils will autodetect the default python version, which on Slackware, is python2. If you set PYTHON=python3 when running ./configure for it, it will then compile xml2po as a python3 module.

Code:

--- ./trackbuild.linuxdoc-tools
+++ ./trackbuild.linuxdoc-tools
@@ -1047,6 +1047,7 @@
 CFLAGS="$SLKCFLAGS" \
 CXXFLAGS="$SLKCFLAGS" \
 CPPFLAGS="$SLKCFLAGS" \
+PYTHON=python3 \
 ./configure \
   --prefix=/usr \
   --libdir=/usr/lib${LIBDIRSUFFIX} \