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

brobr · 03-03-2016, 03:49 AM

Quote:

Originally Posted by brobr

Hi,

I would like to compile the latest version of bowtie2, which is at the moment at version 2.2.7 (see here).....

Ok, I found a way around it. The SlackBuild needs a couple of more lines to get all the progs copied generated by running make (see attached diff).

Drakeo · 03-05-2016, 05:53 PM

As you will note that Slackbuilds also repackages pre-built packages.
After several attemps to notify maintainers I will bring it here.

Quote:

Delivery to the following recipient failed permanently:

martin_rogge@users.sourceforge.net

Technical details of permanent failure:
Google tried to deliver your message, but it was rejected by the server for the recipient domain users.sourceforge.net by mx.sourceforge.net. [216.34.181.68].

The error that the other server returned was:
550 unknown user

And the mail to them.

Quote:

I have been building the viewer since 2010 I am also a contributor to the Kokua viewer linux.
do to the new cef plugin I maintain for the kokua viewer and the secondlife viewer since Linden labs stop support on the CEF3 media plugin for linux people must use my builds of it for that media.
That said your install script really should be done another way.
1. You want to keep it as close to vanilla as possible and away from the /usr/bin or /usr/lib area. do to preloading certain libraries.
2. for automatic updates it may cause serious issues.
3. fmodex is always set to be used now as default now
4. your last update your unable to use in secondlife. you need 4.7.5 or higher but wait 4.7.7 is
coming out with CEF3
5.when installing we need to set permissons for chrome-sandbox
6. there is no need to create a icon for pix map. this is created at install by running the
firestorm-install/etc/refresh_desktop_app_entry.sh that also creates a Firestorm-dekstop that is then linked to the icon.
7 yes the it will default to /usr/local/share/applications
8 does it really matter every time you run the program as user it also creates and over write the ~/home/.local/share/applications/firestorm-desktop. every time you reboot it will point to that anyway.
I Will submit to you a updated repackage and install Slackbuild script that work out fine.
the new script also handles both arches.

I will push later Ponce when they release stable and yes I will make sure my master is rebased.
TY.

USUARIONUEVO · 03-05-2016, 06:14 PM

latest p7zip no build with GUI=yes

p7zip_15.09

something related to x86_x64 lib dir, but im not in to a x86_x64 ,is a 32 bit system.

Alien Bob · 03-05-2016, 07:40 PM

Quote:

Originally Posted by USUARIONUEVO

latest p7zip no build with GUI=yes

p7zip_15.09

something related to x86_x64 lib dir, but im not in to a x86_x64 ,is a 32 bit system.

I have packages (including GUI) for pzip 15.09, see http://www.slackware.com/~alien/slackbuilds/p7zip/ ... so it can be done.

USUARIONUEVO · 03-05-2016, 08:21 PM

@Alien Bob

your build script works perfectly, include the gui.

Thanks.

willysr · 03-05-2016, 09:33 PM

I have applied some of AlienBOB's work on p7zip and now it builds fine on 32/64 bit

USUARIONUEVO · 03-05-2016, 09:36 PM

Thanks willysr

ponce · 03-06-2016, 12:07 AM

Quote:

Originally Posted by Drakeo

As you will note that Slackbuilds also repackages pre-built packages.
After several attemps to notify maintainers I will bring it here.

hi Drakeo, if the maintainer is unreachable for a couple of weeks or is unreachable (like in this case), please write to the slackbuilds-users mailing list reporting that and saying that you wish to step in for maintainership of firestorm (and of firestorm-opensim?), attaching a tarball to your mail now that submissions are closed (or it would have been better to submit an update through the submission form).

Quote:

And the mail to them.
- - -
I have been building the viewer since 2010 I am also a contributor to the Kokua viewer linux.
do to the new cef plugin I maintain for the kokua viewer and the secondlife viewer since Linden labs stop support on the CEF3 media plugin for linux people must use my builds of it for that media.
That said your install script really should be done another way.
1. You want to keep it as close to vanilla as possible and away from the /usr/bin or /usr/lib area. do to preloading certain libraries.

in this case you should keep away from /usr/local: install in a directory under /opt

Quote:

2. for automatic updates it may cause serious issues.

updates of installed packages outside of pkgtools are not allowed as they produce untraced files in the system.

Quote:

3. fmodex is always set to be used now as default now
4. your last update your unable to use in secondlife. you need 4.7.5 or higher but wait 4.7.7 is
coming out with CEF3
5.when installing we need to set permissons for chrome-sandbox
6. there is no need to create a icon for pix map. this is created at install by running the
firestorm-install/etc/refresh_desktop_app_entry.sh that also creates a Firestorm-dekstop that is then linked to the icon.
7 yes the it will default to /usr/local/share/applications
8 does it really matter every time you run the program as user it also creates and over write the ~/home/.local/share/applications/firestorm-desktop. every time you reboot it will point to that anyway.

you can't package stuff in /usr/local or in the user home that's probably why the previous maintainer did that choice.

Quote:

I Will submit to you a updated repackage and install Slackbuild script that work out fine.
the new script also handles both arches.
- - -

I will push later Ponce when they release stable and yes I will make sure my master is rebased.
TY.

please don't push this stuff on my personal github: look above for the proper channels.

let's continue this discussion on the mailing list as it's not related to the argument of the topic.

willysr · 03-06-2016, 04:21 AM

Quote:

Originally Posted by willysr

I have applied some of AlienBOB's work on p7zip and now it builds fine on 32/64 bit

after some thought, i decided to revert back to 9.20.1 since the new 9.38.1 caused jalview to break when extracting the .bin file. Probably need more time to investigate this problem

orbea · 03-08-2016, 09:19 PM

Quote:

Originally Posted by orbea

Cool, have you tested it much? I tested it a bit more and I'm getting segfaults while playing here.

https://github.com/jonof/jfsw/issues/14

My current hypothesis is that is caused due to C(XX)FLAGS '-fPIC' and '-O2', with just '-O1' it has not segfaulted yet...

https://notabug.org/orbea/SlackBuild...023fcc55642932

Edit: Nope, I can reliably reproduce it by holding down the attack button while dying in the game.

mats_b_tegner · 03-09-2016, 03:52 AM

Hello everyone,
I'm unable to build nvidia-installer, etc. 340.96 from source on
Slackware64-current as of 2016-03-08. The compilation halts with:

Code:

/tmp/SBo/NVIDIA-Linux-x86_64-340.96
  CC           backup.c
  CC           command-list.c
  CC           crc.c
  CC           files.c
  CC           install-from-cwd.c
  CC           kernel.c
  CC           log.c
  CC           misc.c
  CC           nvidia-installer.c
  CC           precompiled.c
  CC           snarf-ftp.c
  CC           snarf-http.c
  CC           snarf.c
  CC           stream-ui.c
  CC           update.c
  CC           user-interface.c
  CC           sanity.c
  CC           manifest.c
  CC           common-utils/nvgetopt.c
  CC           common-utils/common-utils.c
  CC           common-utils/msg.c
  HOST_CC      gen-ui-array.c
  CC           ncurses-ui.c
  LINK         _out/Linux_x86_64/nvidia-installer-ncurses-ui.so
  GEN-UI-ARRAY _out/Linux_x86_64/g_nvidia-installer-ncurses-ui.c
  CC           _out/Linux_x86_64/g_nvidia-installer-ncurses-ui.c
  GEN-UI-ARRAY _out/Linux_x86_64/g_tls_test.c
  CC           _out/Linux_x86_64/g_tls_test.c
  GEN-UI-ARRAY _out/Linux_x86_64/g_tls_test_dso.c
  CC           _out/Linux_x86_64/g_tls_test_dso.c
  GEN-UI-ARRAY _out/Linux_x86_64/g_rtld_test.c
  CC           _out/Linux_x86_64/g_rtld_test.c
  GEN-UI-ARRAY _out/Linux_x86_64/g_tls_test_32.c
  CC           _out/Linux_x86_64/g_tls_test_32.c
  GEN-UI-ARRAY _out/Linux_x86_64/g_tls_test_dso_32.c
  CC           _out/Linux_x86_64/g_tls_test_dso_32.c
  GEN-UI-ARRAY _out/Linux_x86_64/g_rtld_test_32.c
  CC           _out/Linux_x86_64/g_rtld_test_32.c
  CC           _out/Linux_x86_64/g_stamp.c
  LINK         _out/Linux_x86_64/nvidia-installer
/usr/lib64/gcc/x86_64-slackware-linux/5.3.0/../../../../lib64/libpci.a(names-hwdb.o):
In function `pci_id_hwdb_lookup':
names-hwdb.c:(.text+0xb4): undefined reference to
`udev_hwdb_get_properties_list_entry'
names-hwdb.c:(.text+0xc9): undefined reference to `udev_list_entry_get_next'
names-hwdb.c:(.text+0xd9): undefined reference to `udev_list_entry_get_name'
names-hwdb.c:(.text+0xf0): undefined reference to
`udev_list_entry_get_value'
names-hwdb.c:(.text+0x214): undefined reference to `udev_new'
names-hwdb.c:(.text+0x221): undefined reference to `udev_hwdb_new'
/usr/lib64/gcc/x86_64-slackware-linux/5.3.0/../../../../lib64/libpci.a(names-hwdb.o):
In function `pci_id_hwdb_free':
names-hwdb.c:(.text+0x24e): undefined reference to `udev_hwdb_unref'
names-hwdb.c:(.text+0x264): undefined reference to `udev_unref'
collect2: fel: ld returnerade avslutningsstatus 1
Makefile:214: receptet för målet "_out/Linux_x86_64/nvidia-installer"
misslyckades
make: *** [_out/Linux_x86_64/nvidia-installer] Fel 1
root@hp-laptop:/home/mats/Downloads/nvidia-legacy340-driver#

I suspect the latest updates in
ftp://ftp.osuosl.org/pub/slackware/s.../ChangeLog.txt are
the culprits since I have been able to build nvidia-installer, etc.
340.96 in the past month:

Code:

bash-4.3$ ls -l /usr/bin |grep nvidia
-rwxr-xr-x   1 root   root      23K feb 12 02:27 nvidia-bug-report.sh*
-rwxr-xr-x   1 root   root     204K feb 12 02:27 nvidia-debugdump*
-rwxr-xr-x   1 root   root     300K feb 12 02:27 nvidia-installer*
-rwxr-xr-x   1 root   root      26K feb 12 02:28 nvidia-modprobe*
-rwxr-xr-x   1 root   root      33K feb 12 02:29 nvidia-persistenced*
-rwxr-xr-x   1 root   root     1,8M feb 12 02:28 nvidia-settings*
-rwxr-xr-x   1 root   root     245K feb 12 02:27 nvidia-smi*
lrwxrwxrwx   1 root   root       16 nov 16 19:12 nvidia-uninstall ->
nvidia-installer*
-rwxr-xr-x   1 root   root     170K feb 12 02:28 nvidia-xconfig*
bash-4.3$

ponce · 03-09-2016, 05:17 AM

I'm in the realm of wild-guessing but I suppose something broke with the recent update of pciutils as now libpci.a from that package seems not being able to find some udev functions anymore: if you rebuild it as a shared library nvidia-installer builds fine

Code:

--- ./pciutils.SlackBuild.orig  2016-01-04 23:04:22.000000000 +0100
+++ ./pciutils.SlackBuild       2016-03-09 12:13:41.882605284 +0100
@@ -75,7 +75,7 @@
   IDSDIR=/usr/share/hwdata \
   PCI_IDS=pci.ids \
   PCI_COMPRESSED_IDS=0 \
-  SHARED=no \
+  SHARED=yes \
   OPT="$SLKCFLAGS" \
   $NUMJOBS || exit 1
 
@@ -87,7 +87,7 @@
   IDSDIR=/usr/share/hwdata \
   PCI_IDS=pci.ids \
   PCI_COMPRESSED_IDS=0 \
-  SHARED=no \
+  SHARED=yes \
   DESTDIR=$PKG
 
 mkdir -p $PKG/usr/sbin

but maybe this is not the proper fix.

mats_b_tegner · 03-09-2016, 05:53 AM

Quote:

Originally Posted by ponce

I'm in the realm of wild-guessing but I suppose something broke with the recent update of pciutils as now libpci.a from that package seems not being able to find some udev functions anymore: if you rebuild it as a shared library nvidia-installer builds fine

Code:

--- ./pciutils.SlackBuild.orig  2016-01-04 23:04:22.000000000 +0100
+++ ./pciutils.SlackBuild       2016-03-09 12:13:41.882605284 +0100
@@ -75,7 +75,7 @@
   IDSDIR=/usr/share/hwdata \
   PCI_IDS=pci.ids \
   PCI_COMPRESSED_IDS=0 \
-  SHARED=no \
+  SHARED=yes \
   OPT="$SLKCFLAGS" \
   $NUMJOBS || exit 1
 
@@ -87,7 +87,7 @@
   IDSDIR=/usr/share/hwdata \
   PCI_IDS=pci.ids \
   PCI_COMPRESSED_IDS=0 \
-  SHARED=no \
+  SHARED=yes \
   DESTDIR=$PKG
 
 mkdir -p $PKG/usr/sbin

but maybe this is not the proper fix.

Grazie ponce, rebuilding pciutils with SHARED=yes seems to work.

ponce · 03-09-2016, 05:57 AM

the strange thing is that if you build nvidia-installer of a more recent release of the driver, like 352.79 for example, everything goes fine.
this is what, on a second thought, makes me think that the brokeness is in the nvidia-legacy-* stuff instead that in pciutils...

mats_b_tegner · 03-09-2016, 06:03 AM

Quote:

Originally Posted by ponce

the strange thing is that if you build nvidia-installer of a more recent release of the driver, like 352.79 for example, everything goes fine.
this is what, on a second thought, makes me think that the brokeness is in the nvidia-legacy-* stuff instead that in pciutils...

My guess is that nvidia-legacy* is broken as well. I have written an email to nVidia.