LinuxQuestions.org
Visit Jeremy's Blog.
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 09-02-2020, 06:23 AM   #2941
lancsuk
Member
 
Registered: Jul 2019
Location: Burnley / UK
Distribution: Slackware current
Posts: 216

Rep: Reputation: 186Reputation: 186

Hiya,

A couple of days ago I installed Shotcut, but Shotcut crashed with segmentation fault.

I've also tried to build a newer version but version 20.07.11 does not work with mlt-6.16.0.

I spent a lot of time to create scripts for mlt and shotcut, and it works for me.

https://github.com/slackernetuk/xfce/tree/master/mlt

https://github.com/slackernetuk/xfce...master/shotcut

Last edited by lancsuk; 09-02-2020 at 08:59 PM.
 
1 members found this post helpful.
Old 09-05-2020, 06:13 AM   #2942
crts
Senior Member
 
Registered: Jan 2010
Posts: 2,020

Rep: Reputation: 757Reputation: 757Reputation: 757Reputation: 757Reputation: 757Reputation: 757Reputation: 757
Vegastrike for -current

Quote:
Originally Posted by ponce View Post
I'm sorry but I haven't found anything to let vegastrike build on current...
have you tried pinging the maintainer about it?
Hi,

I have not been monitoring this thread very closely and I totally missed that. In any case, I have just updated Vegastrike on Slackbuilds with a few bugfixes. I have also pushed a version that builds on -current to my repository. Click on "My Slackbuilds" in my signature and make sure you checkout the corresponding "current" branch in the vegastrike repository. Let me know if there are any problems.
 
1 members found this post helpful.
Old 09-05-2020, 08:02 AM   #2943
ponce
LQ Guru
 
Registered: Aug 2004
Location: Pisa, Italy
Distribution: Slackware
Posts: 7,068

Original Poster
Rep: Reputation: 4145Reputation: 4145Reputation: 4145Reputation: 4145Reputation: 4145Reputation: 4145Reputation: 4145Reputation: 4145Reputation: 4145Reputation: 4145Reputation: 4145
Quote:
Originally Posted by crts View Post
Hi,

I have not been monitoring this thread very closely and I totally missed that. In any case, I have just updated Vegastrike on Slackbuilds with a few bugfixes. I have also pushed a version that builds on -current to my repository. Click on "My Slackbuilds" in my signature and make sure you checkout the corresponding "current" branch in the vegastrike repository. Let me know if there are any problems.
thanks a lot, pushed!

http://cgit.ponce.cc/slackbuilds/commit/?h=vegastrike
 
Old 09-05-2020, 08:58 AM   #2944
crts
Senior Member
 
Registered: Jan 2010
Posts: 2,020

Rep: Reputation: 757Reputation: 757Reputation: 757Reputation: 757Reputation: 757Reputation: 757Reputation: 757
Quote:
Originally Posted by ponce View Post
One more thing I forgot to mention, I tagged the build in -current with CRTS, since it is not officially on slackbuilds.org. I read a while ago that slackbuilds.org officially only supports the latest stable Slackware release. Please let me know whether this is acceptable or if I need to change this.
 
Old 09-05-2020, 09:09 AM   #2945
ponce
LQ Guru
 
Registered: Aug 2004
Location: Pisa, Italy
Distribution: Slackware
Posts: 7,068

Original Poster
Rep: Reputation: 4145Reputation: 4145Reputation: 4145Reputation: 4145Reputation: 4145Reputation: 4145Reputation: 4145Reputation: 4145Reputation: 4145Reputation: 4145Reputation: 4145
Quote:
Originally Posted by crts View Post
One more thing I forgot to mention, I tagged the build in -current with CRTS, since it is not officially on slackbuilds.org. I read a while ago that slackbuilds.org officially only supports the latest stable Slackware release. Please let me know whether this is acceptable or if I need to change this.
no problem, I changed it back to _SBo for rebasing economy (the less changes I have to rebase every week, the better!).
I also preserved the README and slack-desc files as they're on SBo as you seem to have reverted the latest changes you pushed on SBo in this current branch (I thought it was an oversight).
 
Old 09-05-2020, 09:20 AM   #2946
crts
Senior Member
 
Registered: Jan 2010
Posts: 2,020

Rep: Reputation: 757Reputation: 757Reputation: 757Reputation: 757Reputation: 757Reputation: 757Reputation: 757
Quote:
Originally Posted by ponce View Post
... as you seem to have reverted the latest changes you pushed on SBo in this current branch ...
No, I did not revert. The changes were made by the people on SBo. The README had one typo in it. The rest of the changes in the affected files were just text-formatting issues, e.g., a few lines were just too long. I was asked to adjust this in my repository as well. Just updated and pushed the changes to the "current" branch, too.
 
Old 09-05-2020, 04:26 PM   #2947
sombragris
Member
 
Registered: Jul 2004
Location: Asuncion, Paraguay, South America
Distribution: Slackware
Posts: 844

Rep: Reputation: 383Reputation: 383Reputation: 383Reputation: 383
pinfo fails to compile due to a linking error. Maybe because I use gcc10?

compiler output:

Code:
/bin/sh ../libtool  --tag=CC   --mode=link gcc -D_DEFAULT_SOURCE -D_XOPEN_SOURCE=600 -D_XOPEN_SOURCE=600 -I/usr/include/readline -Wall -Wextra -Wshadow -Werror -DLOCALEDIR=\"/usr/share/locale\" -DCONFIGDIR=\"/etc/pinforc\" -O2 -fPIC  -D_XOPEN_SOURCE=600   -o pinfo pinfo-pinfo.o pinfo-colors.o pinfo-datatypes.o pinfo-filehandling_functions.o pinfo-mainfunction.o pinfo-manual.o pinfo-menu_and_note_utils.o pinfo-parse_config.o pinfo-regexp_search.o pinfo-signal_handler.o pinfo-utils.o pinfo-video.o pinfo-initializelinks.o pinfo-printinfo.o    -lreadline  -lncursesw -ltinfo 
libtool: link: gcc -D_DEFAULT_SOURCE -D_XOPEN_SOURCE=600 -D_XOPEN_SOURCE=600 -I/usr/include/readline -Wall -Wextra -Wshadow -Werror -DLOCALEDIR=\"/usr/share/locale\" -DCONFIGDIR=\"/etc/pinforc\" -O2 -fPIC -D_XOPEN_SOURCE=600 -o pinfo pinfo-pinfo.o pinfo-colors.o pinfo-datatypes.o pinfo-filehandling_functions.o pinfo-mainfunction.o pinfo-manual.o pinfo-menu_and_note_utils.o pinfo-parse_config.o pinfo-regexp_search.o pinfo-signal_handler.o pinfo-utils.o pinfo-video.o pinfo-initializelinks.o pinfo-printinfo.o  -lreadline -lncursesw -ltinfo
/usr/bin/ld: pinfo-colors.o:(.bss+0x34): multiple definition of `use_manual'; pinfo-pinfo.o:(.bss+0x10): first defined here
/usr/bin/ld: pinfo-datatypes.o:(.bss+0x310): multiple definition of `use_manual'; pinfo-pinfo.o:(.bss+0x10): first defined here
/usr/bin/ld: pinfo-filehandling_functions.o:(.bss+0x10): multiple definition of `use_manual'; pinfo-pinfo.o:(.bss+0x10): first defined here
/usr/bin/ld: pinfo-mainfunction.o:(.bss+0x24): multiple definition of `use_manual'; pinfo-pinfo.o:(.bss+0x10): first defined here
/usr/bin/ld: pinfo-manual.o:(.bss+0x40): multiple definition of `use_manual'; pinfo-pinfo.o:(.bss+0x10): first defined here
/usr/bin/ld: pinfo-menu_and_note_utils.o:(.bss+0x0): multiple definition of `use_manual'; pinfo-pinfo.o:(.bss+0x10): first defined here
/usr/bin/ld: pinfo-parse_config.o:(.bss+0x10): multiple definition of `use_manual'; pinfo-pinfo.o:(.bss+0x10): first defined here
/usr/bin/ld: pinfo-regexp_search.o:(.bss+0x0): multiple definition of `use_manual'; pinfo-pinfo.o:(.bss+0x10): first defined here
/usr/bin/ld: pinfo-signal_handler.o:(.bss+0x0): multiple definition of `use_manual'; pinfo-pinfo.o:(.bss+0x10): first defined here
/usr/bin/ld: pinfo-utils.o:(.bss+0x4): multiple definition of `use_manual'; pinfo-pinfo.o:(.bss+0x10): first defined here
/usr/bin/ld: pinfo-video.o:(.bss+0x0): multiple definition of `use_manual'; pinfo-pinfo.o:(.bss+0x10): first defined here
/usr/bin/ld: pinfo-initializelinks.o:(.bss+0x0): multiple definition of `use_manual'; pinfo-pinfo.o:(.bss+0x10): first defined here
/usr/bin/ld: pinfo-printinfo.o:(.bss+0x0): multiple definition of `use_manual'; pinfo-pinfo.o:(.bss+0x10): first defined here
collect2: error: ld returned 1 exit status
make[2]: *** [Makefile:527: pinfo] Error 1
make[2]: Leaving directory '/tmp/SBo/pinfo-0.6.13/src'
make[1]: *** [Makefile:475: all-recursive] Error 1
make[1]: Leaving directory '/tmp/SBo/pinfo-0.6.13'
make: *** [Makefile:405: all] Error 2
 
Old 09-05-2020, 04:37 PM   #2948
ponce
LQ Guru
 
Registered: Aug 2004
Location: Pisa, Italy
Distribution: Slackware
Posts: 7,068

Original Poster
Rep: Reputation: 4145Reputation: 4145Reputation: 4145Reputation: 4145Reputation: 4145Reputation: 4145Reputation: 4145Reputation: 4145Reputation: 4145Reputation: 4145Reputation: 4145
Quote:
Originally Posted by sombragris View Post
pinfo fails to compile due to a linking error. Maybe because I use gcc10?

compiler output:

Code:
/bin/sh ../libtool  --tag=CC   --mode=link gcc -D_DEFAULT_SOURCE -D_XOPEN_SOURCE=600 -D_XOPEN_SOURCE=600 -I/usr/include/readline -Wall -Wextra -Wshadow -Werror -DLOCALEDIR=\"/usr/share/locale\" -DCONFIGDIR=\"/etc/pinforc\" -O2 -fPIC  -D_XOPEN_SOURCE=600   -o pinfo pinfo-pinfo.o pinfo-colors.o pinfo-datatypes.o pinfo-filehandling_functions.o pinfo-mainfunction.o pinfo-manual.o pinfo-menu_and_note_utils.o pinfo-parse_config.o pinfo-regexp_search.o pinfo-signal_handler.o pinfo-utils.o pinfo-video.o pinfo-initializelinks.o pinfo-printinfo.o    -lreadline  -lncursesw -ltinfo 
libtool: link: gcc -D_DEFAULT_SOURCE -D_XOPEN_SOURCE=600 -D_XOPEN_SOURCE=600 -I/usr/include/readline -Wall -Wextra -Wshadow -Werror -DLOCALEDIR=\"/usr/share/locale\" -DCONFIGDIR=\"/etc/pinforc\" -O2 -fPIC -D_XOPEN_SOURCE=600 -o pinfo pinfo-pinfo.o pinfo-colors.o pinfo-datatypes.o pinfo-filehandling_functions.o pinfo-mainfunction.o pinfo-manual.o pinfo-menu_and_note_utils.o pinfo-parse_config.o pinfo-regexp_search.o pinfo-signal_handler.o pinfo-utils.o pinfo-video.o pinfo-initializelinks.o pinfo-printinfo.o  -lreadline -lncursesw -ltinfo
/usr/bin/ld: pinfo-colors.o:(.bss+0x34): multiple definition of `use_manual'; pinfo-pinfo.o:(.bss+0x10): first defined here
/usr/bin/ld: pinfo-datatypes.o:(.bss+0x310): multiple definition of `use_manual'; pinfo-pinfo.o:(.bss+0x10): first defined here
/usr/bin/ld: pinfo-filehandling_functions.o:(.bss+0x10): multiple definition of `use_manual'; pinfo-pinfo.o:(.bss+0x10): first defined here
/usr/bin/ld: pinfo-mainfunction.o:(.bss+0x24): multiple definition of `use_manual'; pinfo-pinfo.o:(.bss+0x10): first defined here
/usr/bin/ld: pinfo-manual.o:(.bss+0x40): multiple definition of `use_manual'; pinfo-pinfo.o:(.bss+0x10): first defined here
/usr/bin/ld: pinfo-menu_and_note_utils.o:(.bss+0x0): multiple definition of `use_manual'; pinfo-pinfo.o:(.bss+0x10): first defined here
/usr/bin/ld: pinfo-parse_config.o:(.bss+0x10): multiple definition of `use_manual'; pinfo-pinfo.o:(.bss+0x10): first defined here
/usr/bin/ld: pinfo-regexp_search.o:(.bss+0x0): multiple definition of `use_manual'; pinfo-pinfo.o:(.bss+0x10): first defined here
/usr/bin/ld: pinfo-signal_handler.o:(.bss+0x0): multiple definition of `use_manual'; pinfo-pinfo.o:(.bss+0x10): first defined here
/usr/bin/ld: pinfo-utils.o:(.bss+0x4): multiple definition of `use_manual'; pinfo-pinfo.o:(.bss+0x10): first defined here
/usr/bin/ld: pinfo-video.o:(.bss+0x0): multiple definition of `use_manual'; pinfo-pinfo.o:(.bss+0x10): first defined here
/usr/bin/ld: pinfo-initializelinks.o:(.bss+0x0): multiple definition of `use_manual'; pinfo-pinfo.o:(.bss+0x10): first defined here
/usr/bin/ld: pinfo-printinfo.o:(.bss+0x0): multiple definition of `use_manual'; pinfo-pinfo.o:(.bss+0x10): first defined here
collect2: error: ld returned 1 exit status
make[2]: *** [Makefile:527: pinfo] Error 1
make[2]: Leaving directory '/tmp/SBo/pinfo-0.6.13/src'
make[1]: *** [Makefile:475: all-recursive] Error 1
make[1]: Leaving directory '/tmp/SBo/pinfo-0.6.13'
make: *** [Makefile:405: all] Error 2
I'm not sure what's happening there but I can confirm that it builds fine here.

Last edited by ponce; 09-05-2020 at 04:38 PM.
 
Old 09-05-2020, 04:51 PM   #2949
sombragris
Member
 
Registered: Jul 2004
Location: Asuncion, Paraguay, South America
Distribution: Slackware
Posts: 844

Rep: Reputation: 383Reputation: 383Reputation: 383Reputation: 383
Quote:
Originally Posted by ponce View Post
I'm not sure what's happening there but I can confirm that it builds fine here.
Indeed, after some Googling I found it's a bug linked to gcc10 or the -fno-common flag. The Gentoo folks provided a patch. Could you consider adding it, please?

https://bugs.gentoo.org/706548

Thanks!
 
Old 09-05-2020, 05:34 PM   #2950
sombragris
Member
 
Registered: Jul 2004
Location: Asuncion, Paraguay, South America
Distribution: Slackware
Posts: 844

Rep: Reputation: 383Reputation: 383Reputation: 383Reputation: 383
Update: simply adding -fcommon to the compiler flags solves the issue and the pinfo builds correctly.
 
Old 09-06-2020, 12:42 PM   #2951
newHeiko
LQ Newbie
 
Registered: May 2020
Distribution: slackware 15.0
Posts: 26

Rep: Reputation: Disabled
Quote:
Originally Posted by drgibbon View Post
The recent guile 3.0 upgrade breaks gnucash 3.8. Apparently compilation requires guile 2.0 or 2.2. Can 2.x and 3.0 be installed concurrently?
Quick note: gnucash-4.1 does not run when building it while guile2.2 is installed. At least for me...

Solved for me by removing guile2.2 and rebuilding gnucash-4.1.

Just in case this may help anyone

Heiko
 
1 members found this post helpful.
Old 09-10-2020, 08:39 PM   #2952
duncan_roe
Member
 
Registered: Nov 2008
Posts: 38

Rep: Reputation: 5
graphviz would not build for me until I followed Pat's advice, to
rm /{,usr/}lib{,64}/*.la
It may be that all SBo builds that create libraries will need updating to include the "Don't ship .la files" stanza that is in most Current SkackBuild files now.
 
Old 09-11-2020, 02:55 AM   #2953
chrisretusn
Senior Member
 
Registered: Dec 2005
Location: Philippines
Distribution: Slackware64-current
Posts: 2,949

Rep: Reputation: 1531Reputation: 1531Reputation: 1531Reputation: 1531Reputation: 1531Reputation: 1531Reputation: 1531Reputation: 1531Reputation: 1531Reputation: 1531Reputation: 1531
Never mind.
 
Old 09-11-2020, 01:17 PM   #2954
qunying
Member
 
Registered: Jun 2002
Distribution: Slackware
Posts: 257

Rep: Reputation: 147Reputation: 147
mixxx-2.2.4 fail to start compiling due the patch could not be applied. Remove the patch and compile fined.
 
Old 09-11-2020, 02:22 PM   #2955
ponce
LQ Guru
 
Registered: Aug 2004
Location: Pisa, Italy
Distribution: Slackware
Posts: 7,068

Original Poster
Rep: Reputation: 4145Reputation: 4145Reputation: 4145Reputation: 4145Reputation: 4145Reputation: 4145Reputation: 4145Reputation: 4145Reputation: 4145Reputation: 4145Reputation: 4145
Quote:
Originally Posted by qunying View Post
mixxx-2.2.4 fail to start compiling due the patch could not be applied. Remove the patch and compile fined.
yes, thanks for reporting! I actually already fixed it a few hours ago, it will go in at the next merge.
 
  


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 12:03 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
Open Source Consulting | Domain Registration