LinuxQuestions.org
Latest LQ Deal: Latest LQ Deals
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-11-2020, 03:15 PM   #1
USUARIONUEVO
Senior Member
 
Registered: Apr 2015
Posts: 1,464

Rep: Reputation: 462Reputation: 462Reputation: 462Reputation: 462Reputation: 462
Its too dangerous upgrade cmake under slackware-14.2 ?


Hi , i test build audacity 2.4.2 under 14.2 , its fine now after some point releases of audacity , the only thing we need is a more new cmake package.

Its a big risk upgrade this package ? (cmake) , i think no , cause is only a build system , no have libs to link binaries , but im not sure.


For slackware 14.2 users , can build audacity 2.4.2 upgrading cmake , using kit from current , and later to ensure, can downgrade cmake again to the stock , but i start thinking make this permanent on my system.

risk ?
 
Old 09-11-2020, 04:27 PM   #2
dugan
LQ Guru
 
Registered: Nov 2003
Location: Canada
Distribution: distro hopper
Posts: 9,764

Rep: Reputation: 4408Reputation: 4408Reputation: 4408Reputation: 4408Reputation: 4408Reputation: 4408Reputation: 4408Reputation: 4408Reputation: 4408Reputation: 4408Reputation: 4408
Don't replace it. Just download a binary CMake package, untar it somewhere, and build stuff with "/path/to/cmake .."
 
Old 09-11-2020, 05:18 PM   #3
lovemeslk
LQ Newbie
 
Registered: Feb 2020
Location: none of your business
Distribution: Slackware
Posts: 17

Rep: Reputation: Disabled
I have been using Cmake from current for the last 12 years use it on stable do to ++9 +++11 ++14 and going to deal with ++17 stuff So relax just build it from current you will be ok and anything you build for stable will be fine. It is a macro thing not a library thing.
 
Old 09-11-2020, 05:22 PM   #4
montagdude
Senior Member
 
Registered: Apr 2016
Distribution: Slackware
Posts: 1,790

Rep: Reputation: 1370Reputation: 1370Reputation: 1370Reputation: 1370Reputation: 1370Reputation: 1370Reputation: 1370Reputation: 1370Reputation: 1370Reputation: 1370
I wouldn't say it's dangerous. It's not like anything links against it. Worst case scenario you just reinstall the old version again if something else doesn't build right with the new one. But, as dugan said, the best solution is just to install it elsewhere rather than upgrading the existing one.
 
Old 09-11-2020, 05:53 PM   #5
Daedra
Senior Member
 
Registered: Dec 2005
Location: Springfield, MO
Distribution: Slackware64-14.2
Posts: 1,620

Rep: Reputation: 424Reputation: 424Reputation: 424Reputation: 424Reputation: 424
Quote:
Originally Posted by dugan View Post
Don't replace it. Just download a binary CMake package, untar it somewhere, and build stuff with "/path/to/cmake .."
+1 for what Dugan said, or you can upgrade cmake in a throw away 14.2 VM and build the package there. That is what I have been doing with some packages that require newer cmake.

Last edited by Daedra; 09-11-2020 at 05:54 PM.
 
Old 09-11-2020, 05:58 PM   #6
Didier Spaier
LQ Addict
 
Registered: Nov 2008
Location: Paris, France
Distribution: Slint64-14.2.1.2 on Lenovo Thinkpad W520
Posts: 9,479

Rep: Reputation: Disabled
I don't think so it's dangerous:
Code:
Tuesday 8 September 2020
cmake-3.18.2-x86_64-1slint: Added.
  Cross-platform, open-source make system.
  Included in Slint and upgraded vs the Slackware package to allow build the new
  mumble package.
mumble-gitc5cc9fc0-x86_64-1slint: Upgraded.
  Brings support for stereo.
  Thanks to Storm Dragon for the help to build the package.
+--------------------------+

Last edited by Didier Spaier; 09-11-2020 at 06:00 PM.
 
Old 09-12-2020, 05:57 AM   #7
GazL
LQ Guru
 
Registered: May 2008
Distribution: CRUX
Posts: 5,547
Blog Entries: 14

Rep: Reputation: 3388Reputation: 3388Reputation: 3388Reputation: 3388Reputation: 3388Reputation: 3388Reputation: 3388Reputation: 3388Reputation: 3388Reputation: 3388Reputation: 3388
Does cmake ever break backward compatibility? I guess that's the question to ask with regard to whether it's worth doing parallel installs or not.


aside: I think this proliferation of build systems is getting out of hand. First we had make, then imake (weird X11 thing), then comes GNU Autotools, cmake, meson, ninja, and probably some others that I've forgotten or am unaware of. It's getting silly.
 
3 members found this post helpful.
Old 09-12-2020, 10:15 AM   #8
orbea
Senior Member
 
Registered: Feb 2015
Distribution: Slackware64-current
Posts: 1,933

Rep: Reputation: Disabled
I hypothesize you are more likely to find new builds that do not work with old cmake than old builds that don't work with new cmake.
 
  


Reply


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] problem with newer cmake options run on slackware cmake 3.5.2 timsoft Slackware 6 05-31-2020 07:51 AM
Hi all, i am new to cmake in linux so i am trying to design a c++ project that connects to mariadb using cmake, but i run into an error. Naptar Linux - Newbie 0 01-19-2019 11:46 AM
Slackware-current: /usr/share/cmake and /usr/share/cmake-3.3 directories igor29768 Slackware 1 11-07-2015 12:37 AM
CMake Strange "Install" behaviour with home-grown software [Linux x86_64, CMake 2.8] ajschaeffer Programming 0 10-24-2011 03:21 AM
cmake: Using find_package(Boost) when FindBoost.cmake is not in the default location damien_d Programming 3 10-27-2010 03:40 PM

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

All times are GMT -5. The time now is 08:37 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
Open Source Consulting | Domain Registration