LinuxQuestions.org
Help answer threads with 0 replies.
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 01-01-2019, 09:25 PM   #196
1337_powerslacker
Member
 
Registered: Nov 2009
Distribution: Slackware64-current
Posts: 778
Blog Entries: 9

Rep: Reputation: 510Reputation: 510Reputation: 510Reputation: 510Reputation: 510Reputation: 510

Quote:
Originally Posted by montagdude View Post
Not CMakeLists.txt, but CMakeCache.txt, in the build/ directory. It looks like libconfig++ is built correctly from your other output, so I'm curious as to why it is not linking.
Oops. I misread that. Sorry about that. The output returned is:

Code:
LIBCONFIG++_LIBRARY:FILEPATH=/usr/lib64/libconfig++.so
 
Old 01-01-2019, 09:55 PM   #197
montagdude
Senior Member
 
Registered: Apr 2016
Distribution: Slackware
Posts: 1,743

Original Poster
Rep: Reputation: 1334Reputation: 1334Reputation: 1334Reputation: 1334Reputation: 1334Reputation: 1334Reputation: 1334Reputation: 1334Reputation: 1334Reputation: 1334
Well, that looks correct too, and I just tried building both libconfig++ and sboui on a clean, up-to-date -current, and it works fine, so I'm kind of stumped here. You are building the latest, version 2.0.1, and not setting any unusual environment variables that might change the compiler or linker, correct? All I can think of to try now would be:

1) Rebuild both libconfig and sboui and see if that fixes it.
2) In sboui.SlackBuild, add VERBOSE=1 after $BUILDCMD on line 101. When you build again, the linking line should look something like this. Note in particular the -lconfig++ at the end:

Code:
/usr/bin/cmake -E cmake_link_script CMakeFiles/sboui.dir/link.txt --verbose=1
/usr/bin/c++  -O2 -fPIC -O2 -fopenmp  -rdynamic CMakeFiles/sboui.dir/src/AbstractListBox.cpp.o CMakeFiles/sboui.dir/src/Blacklist.cpp.o CMakeFiles/sboui.dir/src/BuildActionBox.cpp.o CMakeFiles/sboui.dir/src/BuildListBox.cpp.o CMakeFiles/sboui.dir/src/BuildListItem.cpp.o CMakeFiles/sboui.dir/src/BuildOptionsBox.cpp.o CMakeFiles/sboui.dir/src/BuildOrderBox.cpp.o CMakeFiles/sboui.dir/src/CLOParser.cpp.o CMakeFiles/sboui.dir/src/CategoryListBox.cpp.o CMakeFiles/sboui.dir/src/CategoryListItem.cpp.o CMakeFiles/sboui.dir/src/Color.cpp.o CMakeFiles/sboui.dir/src/ColorTheme.cpp.o CMakeFiles/sboui.dir/src/ComboBox.cpp.o CMakeFiles/sboui.dir/src/ComboBoxList.cpp.o CMakeFiles/sboui.dir/src/CursesWidget.cpp.o CMakeFiles/sboui.dir/src/DefaultOptionsBox.cpp.o CMakeFiles/sboui.dir/src/DirListBox.cpp.o CMakeFiles/sboui.dir/src/DirListing.cpp.o CMakeFiles/sboui.dir/src/FilterBox.cpp.o CMakeFiles/sboui.dir/src/HelpItem.cpp.o CMakeFiles/sboui.dir/src/HelpWindow.cpp.o CMakeFiles/sboui.dir/src/InputBox.cpp.o CMakeFiles/sboui.dir/src/InputItem.cpp.o CMakeFiles/sboui.dir/src/InstallBox.cpp.o CMakeFiles/sboui.dir/src/KeyHelpWindow.cpp.o CMakeFiles/sboui.dir/src/Label.cpp.o CMakeFiles/sboui.dir/src/ListBox.cpp.o CMakeFiles/sboui.dir/src/ListItem.cpp.o CMakeFiles/sboui.dir/src/MainWindow.cpp.o CMakeFiles/sboui.dir/src/Menubar.cpp.o CMakeFiles/sboui.dir/src/MenubarList.cpp.o CMakeFiles/sboui.dir/src/MenubarListItem.cpp.o CMakeFiles/sboui.dir/src/MessageBox.cpp.o CMakeFiles/sboui.dir/src/MouseEvent.cpp.o CMakeFiles/sboui.dir/src/MouseHelpWindow.cpp.o CMakeFiles/sboui.dir/src/OptionsWindow.cpp.o CMakeFiles/sboui.dir/src/PackageInfoBox.cpp.o CMakeFiles/sboui.dir/src/QuickSearch.cpp.o CMakeFiles/sboui.dir/src/ScrollBox.cpp.o CMakeFiles/sboui.dir/src/SearchBox.cpp.o CMakeFiles/sboui.dir/src/SelectionBox.cpp.o CMakeFiles/sboui.dir/src/ShellReader.cpp.o CMakeFiles/sboui.dir/src/TagList.cpp.o CMakeFiles/sboui.dir/src/TextInput.cpp.o CMakeFiles/sboui.dir/src/ToggleInput.cpp.o CMakeFiles/sboui.dir/src/backend.cpp.o CMakeFiles/sboui.dir/src/filters.cpp.o CMakeFiles/sboui.dir/src/requirements.cpp.o CMakeFiles/sboui.dir/src/sboui.cpp.o CMakeFiles/sboui.dir/src/settings.cpp.o CMakeFiles/sboui.dir/src/signals.cpp.o CMakeFiles/sboui.dir/src/string_util.cpp.o  -o sboui -lncursesw -lform -lconfig++

Last edited by montagdude; 01-01-2019 at 09:57 PM.
 
Old 01-01-2019, 10:25 PM   #198
1337_powerslacker
Member
 
Registered: Nov 2009
Distribution: Slackware64-current
Posts: 778
Blog Entries: 9

Rep: Reputation: 510Reputation: 510Reputation: 510Reputation: 510Reputation: 510Reputation: 510
Quote:
Originally Posted by montagdude View Post
Well, that looks correct too, and I just tried building both libconfig++ and sboui on a clean, up-to-date -current, and it works fine, so I'm kind of stumped here. You are building the latest, version 2.0.1, and not setting any unusual environment variables that might change the compiler or linker, correct? All I can think of to try now would be:

1) Rebuild both libconfig and sboui and see if that fixes it.
2) In sboui.SlackBuild, add VERBOSE=1 after $BUILDCMD on line 101. When you build again, the linking line should look something like this. Note in particular the -lconfig++ at the end:

Code:
/usr/bin/cmake -E cmake_link_script CMakeFiles/sboui.dir/link.txt --verbose=1
/usr/bin/c++  -O2 -fPIC -O2 -fopenmp  -rdynamic CMakeFiles/sboui.dir/src/AbstractListBox.cpp.o CMakeFiles/sboui.dir/src/Blacklist.cpp.o CMakeFiles/sboui.dir/src/BuildActionBox.cpp.o CMakeFiles/sboui.dir/src/BuildListBox.cpp.o CMakeFiles/sboui.dir/src/BuildListItem.cpp.o CMakeFiles/sboui.dir/src/BuildOptionsBox.cpp.o CMakeFiles/sboui.dir/src/BuildOrderBox.cpp.o CMakeFiles/sboui.dir/src/CLOParser.cpp.o CMakeFiles/sboui.dir/src/CategoryListBox.cpp.o CMakeFiles/sboui.dir/src/CategoryListItem.cpp.o CMakeFiles/sboui.dir/src/Color.cpp.o CMakeFiles/sboui.dir/src/ColorTheme.cpp.o CMakeFiles/sboui.dir/src/ComboBox.cpp.o CMakeFiles/sboui.dir/src/ComboBoxList.cpp.o CMakeFiles/sboui.dir/src/CursesWidget.cpp.o CMakeFiles/sboui.dir/src/DefaultOptionsBox.cpp.o CMakeFiles/sboui.dir/src/DirListBox.cpp.o CMakeFiles/sboui.dir/src/DirListing.cpp.o CMakeFiles/sboui.dir/src/FilterBox.cpp.o CMakeFiles/sboui.dir/src/HelpItem.cpp.o CMakeFiles/sboui.dir/src/HelpWindow.cpp.o CMakeFiles/sboui.dir/src/InputBox.cpp.o CMakeFiles/sboui.dir/src/InputItem.cpp.o CMakeFiles/sboui.dir/src/InstallBox.cpp.o CMakeFiles/sboui.dir/src/KeyHelpWindow.cpp.o CMakeFiles/sboui.dir/src/Label.cpp.o CMakeFiles/sboui.dir/src/ListBox.cpp.o CMakeFiles/sboui.dir/src/ListItem.cpp.o CMakeFiles/sboui.dir/src/MainWindow.cpp.o CMakeFiles/sboui.dir/src/Menubar.cpp.o CMakeFiles/sboui.dir/src/MenubarList.cpp.o CMakeFiles/sboui.dir/src/MenubarListItem.cpp.o CMakeFiles/sboui.dir/src/MessageBox.cpp.o CMakeFiles/sboui.dir/src/MouseEvent.cpp.o CMakeFiles/sboui.dir/src/MouseHelpWindow.cpp.o CMakeFiles/sboui.dir/src/OptionsWindow.cpp.o CMakeFiles/sboui.dir/src/PackageInfoBox.cpp.o CMakeFiles/sboui.dir/src/QuickSearch.cpp.o CMakeFiles/sboui.dir/src/ScrollBox.cpp.o CMakeFiles/sboui.dir/src/SearchBox.cpp.o CMakeFiles/sboui.dir/src/SelectionBox.cpp.o CMakeFiles/sboui.dir/src/ShellReader.cpp.o CMakeFiles/sboui.dir/src/TagList.cpp.o CMakeFiles/sboui.dir/src/TextInput.cpp.o CMakeFiles/sboui.dir/src/ToggleInput.cpp.o CMakeFiles/sboui.dir/src/backend.cpp.o CMakeFiles/sboui.dir/src/filters.cpp.o CMakeFiles/sboui.dir/src/requirements.cpp.o CMakeFiles/sboui.dir/src/sboui.cpp.o CMakeFiles/sboui.dir/src/settings.cpp.o CMakeFiles/sboui.dir/src/signals.cpp.o CMakeFiles/sboui.dir/src/string_util.cpp.o  -o sboui -lncursesw -lform -lconfig++
Well, it appears I goofed. I was using the SlackBuild for 1.0, and when I tried to extract the .tar.gz for the SlackBuild into the existing directory to update the SlackBuild, I accidentally made a subdirectory of sboui instead of overwriting and updating the files already there. It worked perfectly this time. Sorry for all the trouble. Goofiness on my part.

Last edited by 1337_powerslacker; 01-01-2019 at 10:48 PM.
 
1 members found this post helpful.
Old 01-01-2019, 10:49 PM   #199
montagdude
Senior Member
 
Registered: Apr 2016
Distribution: Slackware
Posts: 1,743

Original Poster
Rep: Reputation: 1334Reputation: 1334Reputation: 1334Reputation: 1334Reputation: 1334Reputation: 1334Reputation: 1334Reputation: 1334Reputation: 1334Reputation: 1334
Quote:
Originally Posted by 1337_powerslacker View Post
Well, it appears I goofed. I was using the SlackBuild for 1.0, and when I tried to extract the .tar.gz for the SlackBuild into the existing directory to update the SlackBuild, I accidentally made a subdirectory of sboui instead of overwriting and updating the files already there. It worked perfectly this time. Sorry for all the trouble. Goofiness on my part.
Great, I'm glad it's working.
 
Old 01-17-2019, 08:30 PM   #200
Gordie
Member
 
Registered: Aug 2007
Location: Nolalu, Ontario, Canada
Distribution: Slackware Linux
Posts: 599

Rep: Reputation: 221Reputation: 221Reputation: 221
Not really sure this is the place for this but here goes.
Sboui is the only place this problem (if it actually is a problem) shows up. I have an icon for sboui and it brings up a dialog box for "KDE su" with a place for root's password and a checkbox for "remember password".
For a short time it will actually remember the password but frequently it forgets. Not because I reboot or even logout/login. Maybe because zscreensaver came on?
Is this normal? If not, what can I do to change things?
 
Old 01-17-2019, 08:45 PM   #201
montagdude
Senior Member
 
Registered: Apr 2016
Distribution: Slackware
Posts: 1,743

Original Poster
Rep: Reputation: 1334Reputation: 1334Reputation: 1334Reputation: 1334Reputation: 1334Reputation: 1334Reputation: 1334Reputation: 1334Reputation: 1334Reputation: 1334
That would be an issue (or perhaps a "feature") of kdesu. This thread seems relevant:

https://forum.kde.org/viewtopic.php?f=66&t=89825
 
1 members found this post helpful.
Old 01-17-2019, 09:23 PM   #202
Gordie
Member
 
Registered: Aug 2007
Location: Nolalu, Ontario, Canada
Distribution: Slackware Linux
Posts: 599

Rep: Reputation: 221Reputation: 221Reputation: 221
Quote:
Originally Posted by montagdude View Post
That would be an issue (or perhaps a "feature") of kdesu. This thread seems relevant:

https://forum.kde.org/viewtopic.php?f=66&t=89825
Thanks montagdude. In this house it is strange for me. One user nly on "my" computer, ME and my wife doesn't give a hoot about Linux and she stays on her own computer so no security issues. Just seemed strange is all. Thanks again.

By the way, I just love sboui

Last edited by Gordie; 01-17-2019 at 09:46 PM.
 
Old 01-17-2019, 09:51 PM   #203
montagdude
Senior Member
 
Registered: Apr 2016
Distribution: Slackware
Posts: 1,743

Original Poster
Rep: Reputation: 1334Reputation: 1334Reputation: 1334Reputation: 1334Reputation: 1334Reputation: 1334Reputation: 1334Reputation: 1334Reputation: 1334Reputation: 1334
Quote:
Originally Posted by Gordie View Post
Thanks montagdude. In this house it is strange for me. One user nly on "my" computer, ME and my wife doesn't give a hoot about Linux and she stays on her own computer so no security issues. Just seemed strange is all. Thanks again.
If you want this feature, you might give gksu (available on SlackBuilds.org) a try instead of kdesu. It also has an option to remember the password, but with two sub-options: save for this session, or save in the keyring. I think the latter would make it remember it forever, or until you remove it from the keyring. I don't use that feature myself. To make the desktop file launch sboui via gksu instead of kdesu, rebuild sboui with the build option GRAPHICAL_SU=gksu.

Quote:
Originally Posted by Gordie View Post
By the way, I just love sboui
I'm glad you like it. I'm rather fond of it myself.
 
1 members found this post helpful.
Old 01-17-2019, 10:27 PM   #204
Gordie
Member
 
Registered: Aug 2007
Location: Nolalu, Ontario, Canada
Distribution: Slackware Linux
Posts: 599

Rep: Reputation: 221Reputation: 221Reputation: 221
Smile

Quote:
Originally Posted by montagdude View Post
If you want this feature, you might give gksu (available on SlackBuilds.org) a try instead of kdesu. It also has an option to remember the password, but with two sub-options: save for this session, or save in the keyring. I think the latter would make it remember it forever, or until you remove it from the keyring. I don't use that feature myself. To make the desktop file launch sboui via gksu instead of kdesu, rebuild sboui with the build option GRAPHICAL_SU=gksu.

I'm glad you like it. I'm rather fond of it myself.
Oh boy does gksu ever change things for the better for me. Thank you so much
 
Old 05-20-2020, 08:39 PM   #205
dchmelik
Member
 
Registered: Nov 2008
Location: Washington state, USA
Distribution: FreeBSD Unix, Slackware, FreeSlack GNU/Linux, OpenBSD Unix, FreeDOS
Posts: 460

Rep: Reputation: 51
I tried sboui about when it came out, love the idea, but couldn't figure out configuration. Now I think I did--for SlackBuilds.org (SBo) only--but might want to use other repositories. Currently I'm on Slackware-current and want to use SBo-git (i.e., sbo-current) but sboui is saying I'm using 14.2... is that not the case, or can anyone explain what's different or how the configuration should be?

Last edited by dchmelik; 05-21-2020 at 04:27 AM.
 
Old 05-20-2020, 10:36 PM   #206
montagdude
Senior Member
 
Registered: Apr 2016
Distribution: Slackware
Posts: 1,743

Original Poster
Rep: Reputation: 1334Reputation: 1334Reputation: 1334Reputation: 1334Reputation: 1334Reputation: 1334Reputation: 1334Reputation: 1334Reputation: 1334Reputation: 1334
Quote:
Originally Posted by dchmelik View Post
I tried sboui about when it came out, love the idea, but couldn't figure out configuration. Now I think I did--for SllackBuilds.org (SBo) only--but might want to use other repositories. Currently I'm on Slackware-current and want to use SBo-git (i.e., sbo-current) but sboui is saying I'm using 14.2... is that not the case, or can anyone explain what's different or how the configuration should be?
First off, if you aren't already doing this, for -current it is better to build sboui from the latest commit to master rather than the 2.1 release. The 2.1 release will still work on -current, but master has some additional improvements that are helpful.

Just for some background information, you may or may not already be aware, but sboui is designed as an interface that can work with a number of backend package managers, including the built-in one (a.k.a. sboui-backend), sbopkg, or sbotools. Configuration of sboui to use Ponce's repository for -current is mainly a matter of configuring the backend package manager. Personally, I use the built-in one and run -current. Here is my sboui-backend.conf:
Code:
#                                                                               
# Configuration file for sboui-backend                                          
#                                                                               
                                                                                
# Repository to use. Note Ponce repo is for -current only.                      
#REPO=git://git.slackbuilds.org/slackbuilds.git                                 
REPO=git://github.com/Ponce/slackbuilds.git                                     
                                                                                
# Branch (not applicable to Ponce repo). e.g., master, 14.2, 14.1, etc.         
BRANCH=14.2                                                                     
                                                                                
# Location to clone git repository                                              
REPO_DIR=/var/lib/sboui/repo                                                    
                                                                                
# Whether to remove built package after installing (yes/no)                     
CLEAN_PACKAGE=no                                                                
                                                                                
# Whether to remove temporary source and package directories after building     
CLEAN_TMP=no
I haven't tried using sbopkg or sbotools with -current, so I don't know how to configure them to use Ponce's repo, but I do believe that both of them have the capability. If you stick with the built-in package manager as the backend, then you can just use the above.

Last edited by montagdude; 05-20-2020 at 10:38 PM.
 
1 members found this post helpful.
Old 05-23-2020, 05:45 PM   #207
bamunds
Member
 
Registered: Sep 2013
Location: Mounds View MN
Distribution: Slackware64-14.2 XDM_Themes/WMaker
Posts: 705

Rep: Reputation: 225Reputation: 225Reputation: 225
@montagdude did you ever consider ktsuss (keep the su simple, stupid) integration rathter than gksu or kdesu? I am interested in the systray update notifier, but not really interested in all the cascade of libraries for gksu and python. I too love sboui and the integration with sbotools for build. There is still one feature enhancment I'm interested in which is to continue a build if the MD5SUM or SHA fail, like sbopkg allows. This is helpful when attempting to build from source a package version newer than what is in SBo. I simple modify slackbuild and info, then say yes proceed with build when the hash check is different, since I KNOW it will be different. Just curious, Cheers, BrianA_MN
 
Old 05-23-2020, 11:21 PM   #208
dchmelik
Member
 
Registered: Nov 2008
Location: Washington state, USA
Distribution: FreeBSD Unix, Slackware, FreeSlack GNU/Linux, OpenBSD Unix, FreeDOS
Posts: 460

Rep: Reputation: 51
Quote:
Originally Posted by montagdude View Post
First off, if you aren't already doing this, for -current it is better to build sboui from the latest commit to master rather than the 2.1 release. The 2.1 release will still work on -current, but master has some additional improvements that are helpful. [...]
Thanks for all that, but shouldn't sboui commits be added to SBo-git? I finally got sbopkg, sbotools setup to use SBo-git... but don't have sboui-git...
 
Old 05-23-2020, 11:34 PM   #209
montagdude
Senior Member
 
Registered: Apr 2016
Distribution: Slackware
Posts: 1,743

Original Poster
Rep: Reputation: 1334Reputation: 1334Reputation: 1334Reputation: 1334Reputation: 1334Reputation: 1334Reputation: 1334Reputation: 1334Reputation: 1334Reputation: 1334
Quote:
Originally Posted by bamunds View Post
@montagdude did you ever consider ktsuss (keep the su simple, stupid) integration rathter than gksu or kdesu? I am interested in the systray update notifier, but not really interested in all the cascade of libraries for gksu and python. I too love sboui and the integration with sbotools for build. There is still one feature enhancment I'm interested in which is to continue a build if the MD5SUM or SHA fail, like sbopkg allows. This is helpful when attempting to build from source a package version newer than what is in SBo. I simple modify slackbuild and info, then say yes proceed with build when the hash check is different, since I KNOW it will be different. Just curious, Cheers, BrianA_MN
I think ktsuss should work. Check the README for a build flag to tell it which one you intend to use at compile time. I think it is GRAPHICAL_SU=ktsuss, but I don't remember for sure off the top of my head.

Your suggestion about an option to allow the build to proceed if the MD5sum fails seems like a good one. I will add that to the TODO list. Thanks.
 
Old 05-23-2020, 11:36 PM   #210
montagdude
Senior Member
 
Registered: Apr 2016
Distribution: Slackware
Posts: 1,743

Original Poster
Rep: Reputation: 1334Reputation: 1334Reputation: 1334Reputation: 1334Reputation: 1334Reputation: 1334Reputation: 1334Reputation: 1334Reputation: 1334Reputation: 1334
Quote:
Originally Posted by dchmelik View Post
Thanks for all that, but shouldn't sboui commits be added to SBo-git? I finally got sbopkg, sbotools setup to use SBo-git... but don't have sboui-git...
I will eventually pull in the changes into a new release. The changes aren't significant enough to warrant ponce's branch pointing to a different version. For now, just use the same build script that is already in the repo but change the version number to match the link I gave you, and put the tarball in the build directory.

Last edited by montagdude; 05-23-2020 at 11:37 PM.
 
  


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] Call for Testers: MATE 1.17 willysr Slackware 25 04-21-2017 12:55 PM
[SOLVED] Call for Testers: MATE 1.14 for -Current willysr Slackware 13 05-27-2016 08:08 AM
Updating w3af to version 1.6.49 in SBo, need testers mralk3 Slackware 3 12-12-2015 05:54 PM
Call for Testers: MATE 1.8 willysr Slackware 137 08-06-2014 01:50 AM
ncurses-5.2-28 conflicts with file from package ncurses-5.2-12 tubby Linux - Software 4 06-16-2002 12:00 AM

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

All times are GMT -5. The time now is 12:51 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