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 04-22-2019, 11:37 AM   #1816
ponce
Senior Member
 
Registered: Aug 2004
Location: Pisa, Italy
Distribution: Slackware
Posts: 4,754

Original Poster
Rep: Reputation: Disabled

Quote:
Originally Posted by AlleyTrotter View Post
I have been experimentally running 64-current on a spare SSD with Aliens plasma5 setup for quite some time. Along with a few sbopkgs without issue. I'm now getting serious and will be building many more SBO Packages.
My question being would this be the proper place to report any issues with that setup or is this thread strictly for pure current installs?
Thanks in advance for any response.
John
Hi John,
I'm sorry but like I have explained in the first post unfortunately I have not the resources to support building stuff on a variety of systems running current (also with Alien's plasma packages some versions are different) so this thread should be dedicated only to whatever is not building on a full and pristine installation of slackware current.
this doesn't mean, obviously, that you cannot open a new thread describing issues building stuff from SBo on your specific setup (and receive support there).

Last edited by ponce; 04-22-2019 at 11:38 AM.
 
1 members found this post helpful.
Old 04-22-2019, 12:06 PM   #1817
Skaendo
Member
 
Registered: Dec 2014
Location: West Texas, USA
Distribution: Slackware64-14.2
Posts: 881

Rep: Reputation: Disabled
Quote:
Originally Posted by ponce View Post
I think this happens on his system because he has already installed the nvidia drivers: most probably configure enables nvdec because it finds those but it doesn't seem to check for cuda toolkit too.
I haven't tested on 14.2 with version 1.6.0 but I think this new optional dependency (nvidia drivers) has been introduced with the newer versions: I'll add a note to the README.
I built gst-plugins-bad and -ugly 1.16.0 on a clean -current install (Intel hardware) 2 days ago when Pat upgraded base and good with no problems.
 
Old 04-22-2019, 01:42 PM   #1818
Bindestreck
Member
 
Registered: Jul 2011
Location: Sweden
Distribution: Slackware
Posts: 559

Rep: Reputation: 210Reputation: 210Reputation: 210
Quote:
Originally Posted by Skaendo View Post
I built gst-plugins-bad and -ugly 1.16.0 on a clean -current install (Intel hardware) 2 days ago when Pat upgraded base and good with no problems.
I don't understand this type of comment, how many of us in real life, are using a "clean" install of Slackware? Is there anyone here that is only using a clean install and never install anything else?

For the NVIDIA driver, I am using the NVIDIA installer from the NVIDIA itself. Disabling the NVIDIA lookup during configure helped. Thank you!
 
Old 04-22-2019, 02:06 PM   #1819
ponce
Senior Member
 
Registered: Aug 2004
Location: Pisa, Italy
Distribution: Slackware
Posts: 4,754

Original Poster
Rep: Reputation: Disabled
Quote:
Originally Posted by Bindestreck View Post
I don't understand this type of comment, how many of us in real life, are using a "clean" install of Slackware? Is there anyone here that is only using a clean install and never install anything else?
that's not the what he meant, I think, because you can build your packages on virtual machines/containers and they can be as clean as you want: I actually build my packages only on virtual machines.

Last edited by ponce; 04-22-2019 at 02:26 PM.
 
Old 04-22-2019, 05:22 PM   #1820
Skaendo
Member
 
Registered: Dec 2014
Location: West Texas, USA
Distribution: Slackware64-14.2
Posts: 881

Rep: Reputation: Disabled
Quote:
Originally Posted by ponce View Post
that's not the what he meant, I think, because you can build your packages on virtual machines/containers and they can be as clean as you want: I actually build my packages only on virtual machines.
Yes, you are correct Ponce. I was only providing some feedback from when I built them a few days ago on a fresh install I just happened to be building them on to possibly help debug Bindestreck's issue.

I don't like virtual machines. I think that they take up too much space, you have to keep replacing them and they're too complicated in the first place. I do most of my testing with Idlemoor's Slackrepo with customized configs on a virgin install. But I use more than one PC, so I have one for my personal package repo and one that I build/test/debug on. (nerves start acting up as I am patiently awaiting the release of 15.0 )
 
Old 04-22-2019, 07:12 PM   #1821
orbea
Senior Member
 
Registered: Feb 2015
Distribution: Slackware64-current
Posts: 1,596

Rep: Reputation: Disabled
lightspark and likely other programs that use cmake no longer build after boost-1.70.0.

Code:
-- Found Boost 1.70.0 at /usr/lib64/cmake/Boost-1.70.0
--   Requested configuration: QUIET REQUIRED COMPONENTS filesystem;system
-- Found boost_headers 1.70.0 at /usr/lib64/cmake/boost_headers-1.70.0
-- Found boost_filesystem 1.70.0 at /usr/lib64/cmake/boost_filesystem-1.70.0
-- No suitable boost_filesystem variant has been identified!
--   libboost_filesystem.so.1.70.0 (shared, BUILD_SHARED_LIBS not ON, set Boost_USE_STATIC_LIBS=OFF to override)
CMake Error at /usr/lib64/cmake/Boost-1.70.0/BoostConfig.cmake:95 (find_package):
  Found package configuration file:

    /usr/lib64/cmake/boost_filesystem-1.70.0/boost_filesystem-config.cmake

  but it set boost_filesystem_FOUND to FALSE so package "boost_filesystem" is
  considered to be NOT FOUND.  Reason given by package:

  No suitable build variant has been found.

Call Stack (most recent call first):
  /usr/lib64/cmake/Boost-1.70.0/BoostConfig.cmake:124 (boost_find_dependency)
  /usr/share/cmake-3.14/Modules/FindBoost.cmake:266 (find_package)
  CMakeLists.txt:274 (find_package)


-- Configuring incomplete, errors occurred!
See also "/tmp/SBo/lightspark-0.8.1/build/CMakeFiles/CMakeOutput.log".
See also "/tmp/SBo/lightspark-0.8.1/build/CMakeFiles/CMakeError.log".
This a yet unresolved cmake and boost issue, but it can be worked around by using this cmake argument.

Code:
-DBoost_NO_BOOST_CMAKE=ON
Relevant upstream issues.

https://gitlab.kitware.com/cmake/cmake/issues/18865
https://github.com/lightspark/lightspark/issues/344
 
1 members found this post helpful.
Old 04-22-2019, 08:17 PM   #1822
AlleyTrotter
Member
 
Registered: Jun 2002
Location: Coal Township PA
Distribution: Slackware64-14.2 (5.1.3) UEFI enabled (LFS-8.4 when Slackware becomes too easy)
Posts: 534

Rep: Reputation: 192Reputation: 192
Quote:
Originally Posted by ponce View Post
Hi John,
I'm sorry but like I have explained ...so this thread should be dedicated only to whatever is not building on a full and pristine installation of slackware current.
Thanks Ponce
Wish Pat would make up his mind on the Kde issue.
As an aside might I inquire what desktop you use if I may?

thanks again
 
Old 04-23-2019, 04:38 AM   #1823
ponce
Senior Member
 
Registered: Aug 2004
Location: Pisa, Italy
Distribution: Slackware
Posts: 4,754

Original Poster
Rep: Reputation: Disabled
Quote:
Originally Posted by orbea View Post
lightspark and likely other programs that use cmake no longer build after boost-1.70.0.

Code:
-- Found Boost 1.70.0 at /usr/lib64/cmake/Boost-1.70.0
--   Requested configuration: QUIET REQUIRED COMPONENTS filesystem;system
-- Found boost_headers 1.70.0 at /usr/lib64/cmake/boost_headers-1.70.0
-- Found boost_filesystem 1.70.0 at /usr/lib64/cmake/boost_filesystem-1.70.0
-- No suitable boost_filesystem variant has been identified!
--   libboost_filesystem.so.1.70.0 (shared, BUILD_SHARED_LIBS not ON, set Boost_USE_STATIC_LIBS=OFF to override)
CMake Error at /usr/lib64/cmake/Boost-1.70.0/BoostConfig.cmake:95 (find_package):
  Found package configuration file:

    /usr/lib64/cmake/boost_filesystem-1.70.0/boost_filesystem-config.cmake

  but it set boost_filesystem_FOUND to FALSE so package "boost_filesystem" is
  considered to be NOT FOUND.  Reason given by package:

  No suitable build variant has been found.

Call Stack (most recent call first):
  /usr/lib64/cmake/Boost-1.70.0/BoostConfig.cmake:124 (boost_find_dependency)
  /usr/share/cmake-3.14/Modules/FindBoost.cmake:266 (find_package)
  CMakeLists.txt:274 (find_package)


-- Configuring incomplete, errors occurred!
See also "/tmp/SBo/lightspark-0.8.1/build/CMakeFiles/CMakeOutput.log".
See also "/tmp/SBo/lightspark-0.8.1/build/CMakeFiles/CMakeError.log".
This a yet unresolved cmake and boost issue, but it can be worked around by using this cmake argument.

Code:
-DBoost_NO_BOOST_CMAKE=ON
Relevant upstream issues.

https://gitlab.kitware.com/cmake/cmake/issues/18865
https://github.com/lightspark/lightspark/issues/344
thanks orbea, pushed.
 
Old 04-27-2019, 03:57 AM   #1824
Nille_kungen
Member
 
Registered: Jul 2005
Posts: 493

Rep: Reputation: 164Reputation: 164
Has anyone with current multilib and wine-4.0-x86_64-1alien been able to build wine-nine-standalone from SBo?
 
Old 04-27-2019, 08:15 AM   #1825
orbea
Senior Member
 
Registered: Feb 2015
Distribution: Slackware64-current
Posts: 1,596

Rep: Reputation: Disabled
What build error are you running into? First make sure your meson is fully updated with the version in current, there was a regression in meson that broke wine-nine-standalone for sometime.
 
Old 04-27-2019, 09:48 AM   #1826
Nille_kungen
Member
 
Registered: Jul 2005
Posts: 493

Rep: Reputation: 164Reputation: 164
Quote:
Originally Posted by orbea View Post
What build error are you running into? First make sure your meson is fully updated with the version in current, there was a regression in meson that broke wine-nine-standalone for sometime.
https://pastebin.com/NWqb7a0n
https://pastebin.com/8fQbK9Ut

Quote:
Checking for function "dladdr" with dependency -ldl: YES
Pkg-config binary for MachineChoice.HOST is not cached.
Pkg-config binary for MachineChoice.HOST specified from cross file, native file, or env var as ['i586-slackware-linux-gnu-pkg-config']
Trying pkg-config binary i586-slackware-linux-gnu-pkg-config for machine MachineChoice.HOST at [None]
Did not find pkg-config by name 'i586-slackware-linux-gnu-pkg-config'
Found Pkg-config: NO
Pkg-config binary for machine MachineChoice.HOST not found. Giving up.
CMake binary for MachineChoice.HOST is not cached
CMake binary missing from cross or native file, or env var undefined.
Found CMake: NO
No CMake binary for machine MachineChoice.HOST not found. Giving up.
Cross dependency d3d found: NO (tried pkgconfig and cmake)
Message: trying alternative name for d3d...
Pkg-config binary for MachineChoice.HOST is cached as not found.
Pkg-config binary for machine MachineChoice.HOST not found. Giving up.
CMake binary for MachineChoice.HOST is cached as not found
No CMake binary for machine MachineChoice.HOST not found. Giving up.
Cross dependency d3dadapter9 found: NO


meson.build:78:2: ERROR: Pkg-config binary for machine MachineChoice.HOST not found. Giving up.
I think it's meson related, but meson is a new territory for me.
https://github.com/mesonbuild/meson/issues/5102

Last edited by Nille_kungen; 04-27-2019 at 09:55 AM.
 
Old 04-27-2019, 10:10 AM   #1827
orbea
Senior Member
 
Registered: Feb 2015
Distribution: Slackware64-current
Posts: 1,596

Rep: Reputation: Disabled
Just to confirm this is Slackware64-current with multilib?

The problem is that you are missing i586-slackware-linux-gnu-pkg-config which you would find in a compat32 package for pkg-config, I thought Alien Bob provided this, but apparently I was mistaken.

Can you try to download this package.

http://mirrors.slackware.com/slackwa...9.2-i586-2.txz

And run this command on the downloaded package.

Code:
convertpkg-compat32 -i pkg-config-0.29.2-i586-2.txz
And install the new compat32 package, you will need to export this variable before building wine-nine-standalone.

Code:
export PATH="/usr/bin/32:$PATH"
 
Old 04-27-2019, 11:42 AM   #1828
Skaendo
Member
 
Registered: Dec 2014
Location: West Texas, USA
Distribution: Slackware64-14.2
Posts: 881

Rep: Reputation: Disabled
Quote:
Originally Posted by USUARIONUEVO View Post
Hi , i found the patch for libtorrent-rasterbar + boost-1.70
libtorrent-rasterbar-1.1.13 has been released. I have not tested it yet, but quickly looking through it, it looks like it has been updated for boost 1.70.
 
Old 04-27-2019, 11:48 AM   #1829
Nille_kungen
Member
 
Registered: Jul 2005
Posts: 493

Rep: Reputation: 164Reputation: 164
Quote:
Originally Posted by orbea View Post
Just to confirm this is Slackware64-current with multilib?

The problem is that you are missing i586-slackware-linux-gnu-pkg-config which you would find in a compat32 package for pkg-config, I thought Alien Bob provided this, but apparently I was mistaken.

Can you try to download this package.

http://mirrors.slackware.com/slackwa...9.2-i586-2.txz

And run this command on the downloaded package.

Code:
convertpkg-compat32 -i pkg-config-0.29.2-i586-2.txz
And install the new compat32 package, you will need to export this variable before building wine-nine-standalone.

Code:
export PATH="/usr/bin/32:$PATH"
Thank you that took me a bit longer but i still can't compile it.
I was thinking about making a 32-bit pkg-config but i also thought it should be there already but i didn't think about updating the path since i normally use 32dev.sh, scripts that do things for me makes me think less.
https://pastebin.com/htQ9BeeX
 
Old 04-27-2019, 12:34 PM   #1830
orbea
Senior Member
 
Registered: Feb 2015
Distribution: Slackware64-current
Posts: 1,596

Rep: Reputation: Disabled
That is unfortunate...I'll have to try to reproduce this later. Since SBo does not officially support multilib I only tested it with clean 32-bit and 64-bit installs before submitting it and missed this problem.

In the meantime you should be able to get it to work with using pkgconf instead of pkg-config which works here at least.

https://slackbuilds.org/repository/1...pment/pkgconf/

Please make sure to read the README if you follow this route as it replaces the default pkg-config package.
 
  


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 07:53 PM.

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