SBo scripts not building on current (read 1st post, pls)
SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Thank you for confirming ponce and bassmadrigal! It must be somethig on my end then. I'm going to do a clean 64-current install of my system.
Yesterday, after removing everything I had installed and doing a complete system upgrade (with --reinstall), I launched discord... and it still froze without error. After poking around it the /tmp/ folder, i found a strange discord-ipc-0= file. I figured, why not, and I deleted it, and voila, discord launched and everything worked. I chalked it up to my own ignorance and moved on with my life. Today, I built vlc from scratch, and then went to launch discord, and it froze again. I found the a stray file in /tmp/ deleted it, relaunched, and still... nothing. Now I'm getting frustrated. I clear out the discord folder in .config, delete the (again) stray file, launch discord. Frozen. I start uninstalling vlc dependencies that I'm guessing could be culprits, first jdk, then qt5, still nothing. Upon a ps -u av2zeal, I see a crazy amount of open xdg-mime processes, but I don't have a file browser or web browser open, so I kill them. I then had a thought... what if discord is querying xdg-mime but it is hanging or discord doesn't like the response it's getting. So, I run discord and kill xdg-mime and... everything works. My question is now, what could possibly be happening here? Do I need to reinstall xdg-utils? Does discord have some sort of bug? Is my configuration just unstable? Regardless, I thought I would post this for posterity in case anyone else runs across this problem, so that they don't need to spend hours troubleshooting something so silly. Also, any thoughts about how to fix this instead of killing xdg-mime when I run discord would be appreciated. Sorry for the long rant.
Was there a change to the man2html script that causes it not to exit? I'm trying to build an SBo that is calling it but since the script never exits, the SBo hangs when man2html is called.
Was there a change to the man2html script that causes it not to exit? I'm trying to build an SBo that is calling it but since the script never exits, the SBo hangs when man2html is called.
the man2html file (a perl script) seems to have changed last time more than one year ago... which script from SBo are you trying to build?
that hasn't been upgraded since a long time: I wrote the maintainer and he told me that he hasn't time to maintain it anymore so it will be removed from the repository.
the version on SBo for 14.2 is probably incompatible with the newer perl in current.
The version of avr-gcc in current requires a version of avr-libc newer than 1.8.1 as even the simplest C program will not link. avr-libc 2.0.0 contains the necessary files for successful linking.
that hasn't been upgraded since a long time: I wrote the maintainer and he told me that he hasn't time to maintain it anymore so it will be removed from the repository.
the version on SBo for 14.2 is probably incompatible with the newer perl in current.
After editing the available scripts one can compile version 3.5.0.33 of the nx-libs (and they work in the sense that I get my X2go-client connected to a ubuntu-based x2go server at work) and the 4.1.0.1 X2go-client. (I have never tried to use the server)
The newest version of the library (nx-libs-3.5.99.17-1) fails on this error (after entering nxcompshad):
Quote:
libtool: error: error: cannot install 'libXcompshad.la' to a directory not ending in /usr/local/lib
possibly because of these lines:
Quote:
PREFIX ?= /usr/local
..
LIBDIR ?= $(PREFIX)/lib
in the MakeFile. The Slackbuild changes all these lines, also in the scripts, but possibly need to do that somewhere else as well.
(Note: apart from version no, one has to edit the Slackbuild so that the work-directory that will be removed and cd-ed into, becomes "nx-libs-HEAD")
Using the lite-version of the library (only needed for the client; nx-libs-3.5.99.17-1-lite), compiling works with the same script. But communication with the x2go-server (version 4.1.0.3) at work does not complete and I do not get a desktop (maybe the version of the client I can use does not match sufficiently that of the newest library)
The version of avr-gcc in current requires a version of avr-libc newer than 1.8.1 as even the simplest C program will not link. avr-libc 2.0.0 contains the necessary files for successful linking.
Thanks,
Randy
Thanks for reporting, Randy!
I just pushed updates on github for avr-binutils, avr-gcc and avr-libc: they will go in the main branch at the next merge (most probably next weekend).
thunar-dropbox (currently at 0.2.1) no longer builds. This is no fault of SBO; it appears that its upstream maintainer has gone MIA. The issue is, it is no longer compatible with the gtk3 version of Thunar, which is shipped with Slackware Current.
The attached patch gets it to build; however, the app itself seems quite buggy. Quaere whether it's worth continuing to include in SBO or if it should just be cut as unmaintained software.
After editing the available scripts one can compile version 3.5.0.33 of the nx-libs (and they work in the sense that I get my X2go-client connected to a ubuntu-based x2go server at work) and the 4.1.0.1 X2go-client. (I have never tried to use the server)
The newest version of the library (nx-libs-3.5.99.17-1) fails on this error (after entering nxcompshad):
possibly because of these lines:
in the MakeFile. The Slackbuild changes all these lines, also in the scripts, but possibly need to do that somewhere else as well.
(Note: apart from version no, one has to edit the Slackbuild so that the work-directory that will be removed and cd-ed into, becomes "nx-libs-HEAD")
Using the lite-version of the library (only needed for the client; nx-libs-3.5.99.17-1-lite), compiling works with the same script. But communication with the x2go-server (version 4.1.0.3) at work does not complete and I do not get a desktop (maybe the version of the client I can use does not match sufficiently that of the newest library)
The latest version of the X2go-client (4.1.2.1) as well as version 4.1.1.0 fail on
If only I was a bit more knowledgeable of C-programming/compiling ..... maybe someone else is able to make this work
Thanks for the info, I was able to version bump the server script to 4.1.0.3, revert to a previous man2html and make enough changes to get it to build, but when I tried to do the same for the client 4.1.2.1, I ran into compile errors as well. Between this and the maintainer not wanting to update it, I gave up. I ended up using x11vnc (SBo) for the server and tigervnc (/extra) for the client.
SFML 2.4.2 does not build on -current, it fails with conflicting variable declarations in glx. I was able to fix it by version bumping to 2.5.1 and commenting out the FindSFML.cmake file move section (since it is no longer included?).
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.