LinuxQuestions.org
Share your knowledge at the LQ Wiki.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices


Reply
  Search this Thread
Old 02-24-2018, 07:20 AM   #976
USUARIONUEVO
Member
 
Registered: Apr 2015
Posts: 868

Rep: Reputation: 258Reputation: 258Reputation: 258

Some new packages enter to current , need remove

python-notify2
fluidsynth

cause now are current stock packages
 
Old 02-24-2018, 07:52 AM   #977
USUARIONUEVO
Member
 
Registered: Apr 2015
Posts: 868

Rep: Reputation: 258Reputation: 258Reputation: 258
Hi again ..

mlt fails to build if opencv are present , two ways to solve

1 - add disable-opencv to the curren mlt slackbuild version
2 - upgrade mlt to 6.6.0 builds fine with opencv

Thanks!
 
Old 02-24-2018, 08:17 AM   #978
ponce
Senior Member
 
Registered: Aug 2004
Location: Pisa, Italy
Distribution: Slackware
Posts: 4,200

Original Poster
Rep: Reputation: 2139Reputation: 2139Reputation: 2139Reputation: 2139Reputation: 2139Reputation: 2139Reputation: 2139Reputation: 2139Reputation: 2139Reputation: 2139Reputation: 2139
Quote:
Originally Posted by USUARIONUEVO View Post
Some new packages enter to current , need remove

python-notify2
fluidsynth

cause now are current stock packages
thanks for reporting, but they have been already removed from the repository

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

Quote:
Originally Posted by USUARIONUEVO View Post
mlt fails to build if opencv are present , two ways to solve

1 - add disable-opencv to the curren mlt slackbuild version
2 - upgrade mlt to 6.6.0 builds fine with opencv
I'm not sure if whatever has mlt as a dependency will be compatible with the upgrade.
can you please report this to the mlt maintainer and the mailing list? it doesn't seem to be current-specific...

Last edited by ponce; 02-24-2018 at 08:20 AM.
 
Old 02-24-2018, 11:20 AM   #979
dugan
LQ Guru
 
Registered: Nov 2003
Location: Canada
Distribution: Slackware
Posts: 8,155

Rep: Reputation: 3287Reputation: 3287Reputation: 3287Reputation: 3287Reputation: 3287Reputation: 3287Reputation: 3287Reputation: 3287Reputation: 3287Reputation: 3287Reputation: 3287
Quote:
l/SDL2_mixer-2.0.2-i586-2.txz: Rebuilt.
Recompiled to use FluidSynth.
l/fluidsynth-1.1.9-i586-1.txz: Added.
l/sdl-1.2.15-i586-6.txz: Rebuilt.
Recompiled so that libSDL_mixer will use FluidSynth.
AWESOME! Thank you so much Pat!

The PC retrogaming community thanks you.

Last edited by dugan; 02-24-2018 at 11:27 AM.
 
1 members found this post helpful.
Old 02-26-2018, 04:39 PM   #980
orbea
Senior Member
 
Registered: Feb 2015
Distribution: Slackware64-current
Posts: 1,143

Rep: Reputation: Disabled
glm no longer builds on current so I found this gentoo patch which fixes the build.
Code:
diff -ur glm-0.9.8.5.orig/glm/simd/platform.h glm-0.9.8.5/glm/simd/platform.h
--- glm-0.9.8.5.orig/glm/simd/platform.h	2017-08-16 05:15:24.000000000 -0700
+++ glm-0.9.8.5/glm/simd/platform.h	2018-01-26 15:38:57.584130263 -0800
@@ -111,7 +111,8 @@
 #define GLM_COMPILER_GCC70			0x02000A00
 #define GLM_COMPILER_GCC71			0x02000B00
 #define GLM_COMPILER_GCC72			0x02000C00
-#define GLM_COMPILER_GCC80			0x02000D00
+#define GLM_COMPILER_GCC73			0x02000D00
+#define GLM_COMPILER_GCC80			0x02000E00
 
 // CUDA
 #define GLM_COMPILER_CUDA			0x10000000
@@ -283,6 +284,8 @@
 #		define GLM_COMPILER (GLM_COMPILER_GCC71)
 #	elif (__GNUC__ == 7) && (__GNUC_MINOR__ == 2)
 #		define GLM_COMPILER (GLM_COMPILER_GCC72)
+#	elif (__GNUC__ == 7) && (__GNUC_MINOR__ == 3)
+#		define GLM_COMPILER (GLM_COMPILER_GCC73)
 #	elif (__GNUC__ >= 8)
 #		define GLM_COMPILER (GLM_COMPILER_GCC80)
 #	else
diff -ur glm-0.9.8.5.orig/test/core/core_setup_message.cpp glm-0.9.8.5/test/core/core_setup_message.cpp
--- glm-0.9.8.5.orig/test/core/core_setup_message.cpp	2017-08-16 05:15:24.000000000 -0700
+++ glm-0.9.8.5/test/core/core_setup_message.cpp	2018-01-26 15:37:56.953298475 -0800
@@ -86,6 +86,9 @@
 		case GLM_COMPILER_GCC72:
 			std::printf("GCC 7.2\n");
 			break;
+		case GLM_COMPILER_GCC73:
+			std::printf("GCC 7.3\n");
+			break;
 		case GLM_COMPILER_GCC80:
 			std::printf("GCC 8.0\n");
 			break;
https://gitweb.gentoo.org/repo/gento...lm-gcc73.patch

Additionally this patch works for both the 0.9.8.4 source available at SBo and the newer 0.9.8.5 release from upstream which both have this problem. It is fixed in their github repo's master branch, but isolating where it was fixed seems like a lot of pain as it was broken and fixed several times since these releases...
 
Old 02-27-2018, 02:28 AM   #981
ponce
Senior Member
 
Registered: Aug 2004
Location: Pisa, Italy
Distribution: Slackware
Posts: 4,200

Original Poster
Rep: Reputation: 2139Reputation: 2139Reputation: 2139Reputation: 2139Reputation: 2139Reputation: 2139Reputation: 2139Reputation: 2139Reputation: 2139Reputation: 2139Reputation: 2139
thanks! pushed in my SBo branch together with the update to 0.9.8.5 (and another update for gource).
 
Old 02-27-2018, 05:14 PM   #982
Qury
Member
 
Registered: Feb 2004
Location: Dublin
Distribution: Slackware
Posts: 115

Rep: Reputation: 84
docker not building

Hi guys,

docker is not building on slackware64-current (2018-02-27)

i'm using sbopkg to build the queue for this (generated by sqg), all requirements were built successfully.


Code:
docker-ce-17.09.1-ce/components/packaging/rpm/fedora-26/docker-ce.spec
docker-ce-17.09.1-ce/components/packaging/rpm/gen-rpm-ver
docker-ce-17.09.1-ce/components/packaging/rpm/systemd/
docker-ce-17.09.1-ce/components/packaging/rpm/systemd/docker.service
docker-ce-17.09.1-ce/components/packaging/static/
docker-ce-17.09.1-ce/components/packaging/static/Makefile
docker-ce-17.09.1-ce/components/packaging/static/hash_files
# WARNING! I don't seem to be running in a Docker container.
# The result of this command might be an incorrect build, and will not be
# officially supported.
#
# Try this instead: make all
#

---> Making bundle: dynbinary (in bundles/17.09.1-ce/dynbinary)
Building: bundles/17.09.1-ce/dynbinary-daemon/dockerd-17.09.1-ce
go build: when using gccgo toolchain, please pass linker flags using -gccgoflags, not -ldflags
# github.com/docker/docker/cmd/dockerd
/tmp/go-build267133874/github.com/docker/docker/vendor/github.com/stevvooe/continuity/libsysx.a(_go_.o): In function `sysx.llistxattr':
/tmp/SBo/docker-ce-17.09.1-ce/build/src/github.com/docker/docker/vendor/github.com/stevvooe/continuity/sysx/xattr_linux_amd64.go:26: undefined reference to `github_com_docker_docker_vendor_github_com_stevvooe_continuity_sysx.use'
/tmp/go-build267133874/github.com/docker/docker/vendor/github.com/stevvooe/continuity/libsysx.a(_go_.o): In function `sysx.lremovexattr':
/tmp/SBo/docker-ce-17.09.1-ce/build/src/github.com/docker/docker/vendor/github.com/stevvooe/continuity/sysx/xattr_linux_amd64.go:48: undefined reference to `github_com_docker_docker_vendor_github_com_stevvooe_continuity_sysx.use'
/tmp/SBo/docker-ce-17.09.1-ce/build/src/github.com/docker/docker/vendor/github.com/stevvooe/continuity/sysx/xattr_linux_amd64.go:49: undefined reference to `github_com_docker_docker_vendor_github_com_stevvooe_continuity_sysx.use'
/tmp/go-build267133874/github.com/docker/docker/vendor/github.com/stevvooe/continuity/libsysx.a(_go_.o): In function `sysx.lsetxattr':
/tmp/SBo/docker-ce-17.09.1-ce/build/src/github.com/docker/docker/vendor/github.com/stevvooe/continuity/sysx/xattr_linux_amd64.go:76: undefined reference to `github_com_docker_docker_vendor_github_com_stevvooe_continuity_sysx.use'
/tmp/SBo/docker-ce-17.09.1-ce/build/src/github.com/docker/docker/vendor/github.com/stevvooe/continuity/sysx/xattr_linux_amd64.go:77: undefined reference to `github_com_docker_docker_vendor_github_com_stevvooe_continuity_sysx.use'
/tmp/go-build267133874/github.com/docker/docker/vendor/github.com/stevvooe/continuity/libsysx.a(_go_.o):/tmp/SBo/docker-ce-17.09.1-ce/build/src/github.com/docker/docker/vendor/github.com/stevvooe/continuity/sysx/xattr_linux_amd64.go:104: more undefined references to `github_com_docker_docker_vendor_github_com_stevvooe_continuity_sysx.use' follow
collect2: error: ld returned 1 exit status

docker:
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?:
 
Old 02-27-2018, 07:46 PM   #983
willysr
Senior Member
 
Registered: Jul 2004
Location: Jogja, Indonesia
Distribution: Slackware-Current
Posts: 3,804

Rep: Reputation: 1075Reputation: 1075Reputation: 1075Reputation: 1075Reputation: 1075Reputation: 1075Reputation: 1075Reputation: 1075
Did you use "su -" instead of just regular "su" ?
 
Old 02-27-2018, 11:53 PM   #984
ponce
Senior Member
 
Registered: Aug 2004
Location: Pisa, Italy
Distribution: Slackware
Posts: 4,200

Original Poster
Rep: Reputation: 2139Reputation: 2139Reputation: 2139Reputation: 2139Reputation: 2139Reputation: 2139Reputation: 2139Reputation: 2139Reputation: 2139Reputation: 2139Reputation: 2139
Quote:
Originally Posted by Qury View Post
Hi guys,

docker is not building on slackware64-current (2018-02-27)

i'm using sbopkg to build the queue for this (generated by sqg), all requirements were built successfully.


Code:
docker-ce-17.09.1-ce/components/packaging/rpm/fedora-26/docker-ce.spec
docker-ce-17.09.1-ce/components/packaging/rpm/gen-rpm-ver
docker-ce-17.09.1-ce/components/packaging/rpm/systemd/
docker-ce-17.09.1-ce/components/packaging/rpm/systemd/docker.service
docker-ce-17.09.1-ce/components/packaging/static/
docker-ce-17.09.1-ce/components/packaging/static/Makefile
docker-ce-17.09.1-ce/components/packaging/static/hash_files
# WARNING! I don't seem to be running in a Docker container.
# The result of this command might be an incorrect build, and will not be
# officially supported.
#
# Try this instead: make all
#

---> Making bundle: dynbinary (in bundles/17.09.1-ce/dynbinary)
Building: bundles/17.09.1-ce/dynbinary-daemon/dockerd-17.09.1-ce
go build: when using gccgo toolchain, please pass linker flags using -gccgoflags, not -ldflags
# github.com/docker/docker/cmd/dockerd
/tmp/go-build267133874/github.com/docker/docker/vendor/github.com/stevvooe/continuity/libsysx.a(_go_.o): In function `sysx.llistxattr':
/tmp/SBo/docker-ce-17.09.1-ce/build/src/github.com/docker/docker/vendor/github.com/stevvooe/continuity/sysx/xattr_linux_amd64.go:26: undefined reference to `github_com_docker_docker_vendor_github_com_stevvooe_continuity_sysx.use'
/tmp/go-build267133874/github.com/docker/docker/vendor/github.com/stevvooe/continuity/libsysx.a(_go_.o): In function `sysx.lremovexattr':
/tmp/SBo/docker-ce-17.09.1-ce/build/src/github.com/docker/docker/vendor/github.com/stevvooe/continuity/sysx/xattr_linux_amd64.go:48: undefined reference to `github_com_docker_docker_vendor_github_com_stevvooe_continuity_sysx.use'
/tmp/SBo/docker-ce-17.09.1-ce/build/src/github.com/docker/docker/vendor/github.com/stevvooe/continuity/sysx/xattr_linux_amd64.go:49: undefined reference to `github_com_docker_docker_vendor_github_com_stevvooe_continuity_sysx.use'
/tmp/go-build267133874/github.com/docker/docker/vendor/github.com/stevvooe/continuity/libsysx.a(_go_.o): In function `sysx.lsetxattr':
/tmp/SBo/docker-ce-17.09.1-ce/build/src/github.com/docker/docker/vendor/github.com/stevvooe/continuity/sysx/xattr_linux_amd64.go:76: undefined reference to `github_com_docker_docker_vendor_github_com_stevvooe_continuity_sysx.use'
/tmp/SBo/docker-ce-17.09.1-ce/build/src/github.com/docker/docker/vendor/github.com/stevvooe/continuity/sysx/xattr_linux_amd64.go:77: undefined reference to `github_com_docker_docker_vendor_github_com_stevvooe_continuity_sysx.use'
/tmp/go-build267133874/github.com/docker/docker/vendor/github.com/stevvooe/continuity/libsysx.a(_go_.o):/tmp/SBo/docker-ce-17.09.1-ce/build/src/github.com/docker/docker/vendor/github.com/stevvooe/continuity/sysx/xattr_linux_amd64.go:104: more undefined references to `github_com_docker_docker_vendor_github_com_stevvooe_continuity_sysx.use' follow
collect2: error: ld returned 1 exit status

docker:
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?:
there has been a similar report a few post above, I think the issue might be the same for you

https://www.linuxquestions.org/quest...ml#post5823140
 
1 members found this post helpful.
Old 03-01-2018, 02:26 AM   #985
brodo
Member
 
Registered: Jan 2004
Location: Poland, Poznan
Distribution: Slackware current 32
Posts: 301

Rep: Reputation: 19
Instead of Brlcad that actually refused to compile, I compiled succesfully FreeCAD 0.16.

But that's all, unfortunately, it does not want to load examples - freezes at that point.

How can it be investigated and - happily - resolved ?
 
Old 03-01-2018, 03:09 AM   #986
RadicalDreamer
Member
 
Registered: Jul 2016
Location: USA
Distribution: Slackware64-Current
Posts: 670

Rep: Reputation: 293Reputation: 293Reputation: 293
Quote:
Originally Posted by brodo View Post
Instead of Brlcad that actually refused to compile, I compiled succesfully FreeCAD 0.16.

But that's all, unfortunately, it does not want to load examples - freezes at that point.

How can it be investigated and - happily - resolved ?
For FreeCAD I recommend using the AppImage and save often: https://www.freecadweb.org/wiki/Download

BRL-CAD and current. I have no idea. I tried it. I think Slackware Stable is probably required for it.
 
Old 03-01-2018, 04:48 AM   #987
Qury
Member
 
Registered: Feb 2004
Location: Dublin
Distribution: Slackware
Posts: 115

Rep: Reputation: 84
Quote:
Originally Posted by ponce View Post
there has been a similar report a few post above, I think the issue might be the same for you

https://www.linuxquestions.org/quest...ml#post5823140
Thanks Ponce, that was it.
 
Old 03-01-2018, 05:31 AM   #988
ponce
Senior Member
 
Registered: Aug 2004
Location: Pisa, Italy
Distribution: Slackware
Posts: 4,200

Original Poster
Rep: Reputation: 2139Reputation: 2139Reputation: 2139Reputation: 2139Reputation: 2139Reputation: 2139Reputation: 2139Reputation: 2139Reputation: 2139Reputation: 2139Reputation: 2139
Quote:
Originally Posted by brodo View Post
Instead of Brlcad that actually refused to compile, I compiled succesfully FreeCAD 0.16.

But that's all, unfortunately, it does not want to load examples - freezes at that point.

How can it be investigated and - happily - resolved ?
have you tried launching FreeCAD from the command line in a terminal and see if there's any output there when you try to open the examples?
Does this happen with all the examples or just with some of them?
Does this happen also on slackware stable?
maybe it's better if you open a dedicated topic on the matter here or on the SBo mailing list as, IMHO, this doesn't look related to the argument of this topic.

Last edited by ponce; 03-01-2018 at 05:50 AM.
 
1 members found this post helpful.
Old 03-01-2018, 02:02 PM   #989
qunying
Member
 
Registered: Jun 2002
Distribution: Slackware
Posts: 127

Rep: Reputation: 61
pdftk could not be built due to GCC no longer support Java.
Some of the functionality of it could be done with mutool from mupdf though.
 
1 members found this post helpful.
Old 03-01-2018, 02:56 PM   #990
kjhambrick
Senior Member
 
Registered: Jul 2005
Location: Round Rock, TX
Distribution: Slackware64 14.2 + Multilib
Posts: 1,313

Rep: Reputation: 707Reputation: 707Reputation: 707Reputation: 707Reputation: 707Reputation: 707Reputation: 707
Quote:
Originally Posted by qunying View Post
pdftk could not be built due to GCC no longer support Java.
Some of the functionality of it could be done with mutool from mupdf though.
Ouch !

We will sorely miss pdftk where I work.

Perhaps khronosschoty's gcclegacy494.SlackBuild could be altered to build gcc-java and libgcj ?

If not, I suppose I'll keep a Slackware 14.2 Box alive to build a pdftk SBo Package with gcc 5.5.0 ...

I see on the pdftk HomePage that pdftk version 1.2 can be built with gcc version 3.3 or older ...

So maybe the upstream pdftk developers will release an update to pdftk version 2.2 that is not dependent on gcc-java and libgcj ?

Thanks for the head's up gunying.

-- kjh
 
  


Reply

Tags
current, sbo, sbopkg, slackrepo


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
[SOLVED] Error building gst1-plugins-good 1.4.1 from SBO l0rddarkf0rce Slackware 4 10-06-2014 05:58 PM
[SOLVED] Failure building nvidia-kernel Slackbuild from SBo sysfce2 Slackware 7 07-02-2011 01:10 AM
problems building fontforge from SBo gtludwig Slackware 7 05-12-2010 01:52 PM
Pls help me take my 1st step! verysoon Fedora - Installation 2 12-12-2005 07:49 AM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware

All times are GMT -5. The time now is 06:50 AM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration