[SOLVED] A cpl of issues with sbopkg/ponce on slackware current
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.
Building software like this is always fun...at least Linux shows you were it goes wrong.
Looking at the warnings you see that you are missing specific versions of the libicuuc and libicudata libraries on your system. Those two are present in the icu4c-compat package build by Alienbob that is present in his repository. I use slackpkg file-search <library-name> to see this.
For that reason I would install icu4c-compat from the alienbob repository to get rid of those two warnings, which might fix this problem seeing that all the symbols following those warnings have the library number at the end.
btw) Note that the fact that your are at the linker stage means that you are really close. The code itself seems to compile now.
we still do use, configure, make , make install on slackware, just look at a slackbuild
Candelabrus was referring to simply running ./configure && make && make install without any modification or setting a DESTDIR which would allow you to create a Slackware package.
It is much better to create packages with your programs so you can easily upgrade or remove programs and you can find out what files belong to what packages. It's nice to not have untracked files in /usr/
moesasji
Building software like this is always fun...at least Linux shows you were it goes wrong.
YES it is! and i had forgotten about it. It has been around 4yrs since I last compiled and installed a package with ./configure && make && make install.
Quote:
moesasji
Looking at the warnings you see that you are missing specific versions of the libicuuc and libicudata libraries on your system. Those two are present in the icu4c-compat package
after installing it, make completed successfully. Although, i didn't quite grasp this
Quote:
...build by Alienbob that is present in his repository. I use slackpkg file-search <library-name> to see this.
Where do you use the slackpkg file-search? Command line? (if so, I also tried and didn't return the same search) or Bob's repo?
Anyway, i am left with the install now. I do remember that make install DOES make a big salad in your installed package tree, various directories, etc. so, I think i will try to build a package.tgz.
Now, I have never done this (as sbopkg has made me lazy)
1) I have created a app.slackbuild shell script file, using the slackbuild template,
2) edited the first part of the file with app name, version, etc.,
3) execute ./app.slackbuild
4) tar: /home/professor/pckgs/aeskulap/aeskulap/aeskulap-0.2.2.tar.gz: Cannot open: No such file or directory
tar: Error is not recoverable: exiting now
bash-5.0#
I believe that I should edit this line in the app.slackbuild
Code:
rm -rf $PKG
mkdir -p $TMP $PKG $OUTPUT
cd $TMP
rm -rf $PRGNAM-$VERSION
tar xvf $CWD/$PRGNAM-$VERSION.tar.gz
cd $PRGNAM-$VERSION
chown -R root:root .
but i really have no idea what to write as the aeskulap directory i have, was git cloned and there is no tar.gz archive. Do i need to create one?
I know that to use slackbuild I need the package source which is usually given in file.tar.gz.
configure --prefix=/usr/local
configure --prefix/usr
make
make install
the only thing using this is ,that you will need to keep a copy of your source somewhere so you can remove it if you want or need to. That is only if the Makefile has an uninstall included or added to it.
makes for a lot of having to keep tack of your source code if you only install like this.
hence the slackbuild that does the same using ./configure --prefix=/usr adding the needed arch and such then putting it into a nice little tar ball package to install, then one just needs to know the commands to add and remove, and what not.
I still for some of my stuff just use configure make make install. Because if I make a slackbuild for it it just gets lost among all of my stuff, and it is faster to just download untar then run the install steps. but this is just little stuff, like dockapps, if i go bigger or use someone elses on slackbuilds I'll add to it.
e16 for example it has docs themes and epplets, I downloaded epplats modifed some of to update and curtail them to what I want them to be upon install, tar them back up, then modifed the e16.Slackbuild off of slackbulds to put everything into one package.
so really might be able to get the deps and slackbuilds then just put everything into one main slackbuild to compile and make install all of the deps first then the main all into one package.
Thanks for your fast and helpful, but not effective, reply.
./autogen.sh helped in creating a configure file (smiling again),
./configure was successful (getting excited now),
make failed (blood pressure to the sky)
Not sure whether it is a matter of bad luck, but I have the same guts feeling that i mentioned earlier: the package does NOT compile on slackware current; (i believe that those bolded libraries are part of dcmtk <dicomtoolkit> not required according to https://aur.archlinux.org/packages/aeskulap/ eventhough I installed the workaround dcmtk3.6.3 version).
Thanks
I think you need to check your installed packages. You appear to be missing libicuuc and libicudata version 56 which is needed by libdcmjpeg. Look and see what version of these libraries you have installed.
OK then, make install it is and whohala... Voilą.
Impressed (if i were a little younger I would definitely learn coding)
I may not confirm that aeskulap 0.2.2 <medical image and DICOM viewer> (available at https://github.com/jenslody/aeskulap ) runs on slackware current.
Thank you every one.
I think you need to check your installed packages. You appear to be missing libicuuc and libicudata version 56 which is needed by libdcmjpeg. Look and see what version of these libraries you have installed.
The version in -current of those libraries (which are in the icu4c package is already at 63.1 so a much older version of icu4c would be needed. Or a newer one of libdcmjpeg, of course!
The version in -current of those libraries (which are in the icu4c package is already at 63.1 so a much older version of icu4c would be needed. Or a newer one of libdcmjpeg, of course!
During the "love-making" process, I searched for libdcmjpeg everywhere and couldn't find it.
nevertheless, all it's good now (i am trying a DICOM disc to see if it actually works as it used to)
Where do you use the slackpkg file-search? Command line? (if so, I also tried and didn't return the same search) or Bob's repo?
Excellent news that you got things to work in the end.
For future work: with slackpkgplus as a plugin you are able to use non-official repos and it indeed works from the command-line. I have alienbobs repo enabled on my systems for things that are really painful to build from source like VLC. That is which is why I could see that he had the libraries you needed packaged up in the icu4c-compat package.
Excellent news that you got things to work in the end.
For future work: with slackpkgplus as a plugin you are able to use non-official repos and it indeed works from the command-line. I have alienbobs repo enabled on my systems for things that are really painful to build from source like VLC. That is which is why I could see that he had the libraries you needed packaged up in the icu4c-compat package.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
