[SOLVED] Jack not building properly from slackbuilds.org
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.
I’ve been looking for a solution for the problem I’m having but all of my searching hasn’t given proper results, so here I am posting.
So basically I have a very very fresh installation of Slackware 15 and I’m in the process of installing all the packages that are necessary for my work. One of these packages is jack.
So, I go on slackbuilds.org, I download all the necessary files I untar, I compile and everything sento be going smoothly, except no jackd program gets installed in the usr/bin directory (or any of the usr directories).
I tried to su root, to su -l root but nothing changes
The same happened with the fluidr3 sound font package. It didn’t get installed in the usr/share/sounds directory.
For what it's worth, jack compiles fine for me. I additionally use the optional requirement celt (which itself has no dependencies).
Code:
$ cat /var/lib/pkgtools/packages/jack-1.9.19-x86_64-1_SBo
PACKAGE NAME: jack-1.9.19-x86_64-1_SBo
COMPRESSED PACKAGE SIZE: 544K
UNCOMPRESSED PACKAGE SIZE: 2.8M
PACKAGE LOCATION: ./audio/jack/jack-1.9.19-x86_64-1_SBo.txz
PACKAGE DESCRIPTION:
jack: jack (realtime low-latency sound server)
jack:
jack: JACK is a system for handling real-time, low latency audio and MIDI.
jack: It can connect a number of different applications to an audio device,
jack: as well as allowing them to share audio between themselves.
jack:
jack: Its clients can run in their own processes (ie. as normal apps), or
jack: within the JACK server (ie. as a "plugin"). JACK also has support
jack: for distributing audio processing across a network, both fast &
jack: reliable LANs as well as slower, less reliable WANs.
jack:
FILE LIST:
./
install/
install/doinst.sh
install/slack-desc
usr/
usr/bin/
usr/bin/alsa_in
usr/bin/alsa_out
usr/bin/jack_alias
usr/bin/jack_bufsize
usr/bin/jack_connect
usr/bin/jack_control
usr/bin/jack_cpu
usr/bin/jack_cpu_load
usr/bin/jack_evmon
usr/bin/jack_freewheel
usr/bin/jack_iodelay
usr/bin/jack_latent_client
usr/bin/jack_load
usr/bin/jack_lsp
usr/bin/jack_metro
usr/bin/jack_midi_dump
usr/bin/jack_midi_latency_test
usr/bin/jack_midiseq
usr/bin/jack_midisine
usr/bin/jack_monitor_client
usr/bin/jack_multiple_metro
usr/bin/jack_net_master
usr/bin/jack_net_slave
usr/bin/jack_netsource
usr/bin/jack_property
usr/bin/jack_rec
usr/bin/jack_samplerate
usr/bin/jack_server_control
usr/bin/jack_session_notify
usr/bin/jack_showtime
usr/bin/jack_simdtests
usr/bin/jack_simple_client
usr/bin/jack_simple_session_client
usr/bin/jack_test
usr/bin/jack_thru
usr/bin/jack_transport
usr/bin/jack_unload
usr/bin/jack_wait
usr/bin/jack_zombie
usr/bin/jackd
usr/bin/jackdbus
usr/doc/
usr/doc/jack-1.9.19/
usr/doc/jack-1.9.19/jack.SlackBuild
usr/include/
usr/include/jack/
usr/include/jack/control.h
usr/include/jack/intclient.h
usr/include/jack/jack.h
usr/include/jack/jslist.h
usr/include/jack/metadata.h
usr/include/jack/midiport.h
usr/include/jack/net.h
usr/include/jack/ringbuffer.h
usr/include/jack/session.h
usr/include/jack/statistics.h
usr/include/jack/systemdeps.h
usr/include/jack/thread.h
usr/include/jack/transport.h
usr/include/jack/types.h
usr/include/jack/uuid.h
usr/include/jack/weakjack.h
usr/include/jack/weakmacros.h
usr/lib64/
usr/lib64/jack/
usr/lib64/jack/audioadapter.so
usr/lib64/jack/inprocess.so
usr/lib64/jack/jack_alsa.so
usr/lib64/jack/jack_alsarawmidi.so
usr/lib64/jack/jack_dummy.so
usr/lib64/jack/jack_loopback.so
usr/lib64/jack/jack_net.so
usr/lib64/jack/jack_netone.so
usr/lib64/jack/jack_proxy.so
usr/lib64/jack/netadapter.so
usr/lib64/jack/netmanager.so
usr/lib64/jack/profiler.so
usr/lib64/libjack.so.0.1.0
usr/lib64/libjacknet.so.0.1.0
usr/lib64/libjackserver.so.0.1.0
usr/lib64/pkgconfig/
usr/lib64/pkgconfig/jack.pc
usr/man/
usr/man/man1/
usr/man/man1/alsa_in.1.gz
usr/man/man1/alsa_out.1.gz
usr/man/man1/jack_bufsize.1.gz
usr/man/man1/jack_connect.1.gz
usr/man/man1/jack_disconnect.1.gz
usr/man/man1/jack_freewheel.1.gz
usr/man/man1/jack_impulse_grabber.1.gz
usr/man/man1/jack_iodelay.1.gz
usr/man/man1/jack_load.1.gz
usr/man/man1/jack_lsp.1.gz
usr/man/man1/jack_metro.1.gz
usr/man/man1/jack_monitor_client.1.gz
usr/man/man1/jack_netsource.1.gz
usr/man/man1/jack_property.1.gz
usr/man/man1/jack_samplerate.1.gz
usr/man/man1/jack_showtime.1.gz
usr/man/man1/jack_simple_client.1.gz
usr/man/man1/jack_transport.1.gz
usr/man/man1/jack_unload.1.gz
usr/man/man1/jack_wait.1.gz
usr/man/man1/jackd.1.gz
usr/man/man1/jackrec.1.gz
usr/share/
usr/share/dbus-1/
usr/share/dbus-1/services/
usr/share/dbus-1/services/org.jackaudio.service
Also apologies if this seems like a silly question, but it's not clear from your post: You realize that the SlackBuild only builds a Slackware package, and you then have to install it using installpkg, right?
Also apologies if this seems like a silly question, but it's not clear from your post: You realize that the SlackBuild only builds a Slackware package, and you then have to install it using installpkg, right?
Omg I feel like e complete idiot! I’m sorry. Must be the hot fever I’m running right now.
Distribution: Slackware 64 -current multilib from AlienBob's LiveSlak MATE
Posts: 1,072
Rep:
I can confirm what drumz already wrote - building jack with the buildscript from SBo results in a working program that installs properly.
After downloading and extracting the Slackbuilds jack.tar.gz file and downloading the source file jack2-1.9.19.tar.gz I ran the slackbuild script (as root) and the build process went smoothly. I then (after first uninstalling my already present jack package) ran (again as root) installpkg /tmp/jack-1.9.19-x86_64-1_SBo.tgz and after that the jackd file was present (and executable) in the /usr/bin/ folder.
I can confirm what drumz already wrote - building jack with the buildscript from SBo results in a working program that installs properly.
After downloading and extracting the Slackbuilds jack.tar.gz file and downloading the source file jack2-1.9.19.tar.gz I ran the slackbuild script (as root) and the build process went smoothly. I then (after first uninstalling my already present jack package) ran (again as root) installpkg /tmp/jack-1.9.19-x86_64-1_SBo.tgz and after that the jackd file was present (and executable) in the /usr/bin/ folder.
Don't feel badly, tonyleva. I often use the saying "learn from the mistakes of others. You won't live long enough to make them all yourself".
I keep telling myself that I should do something to automate moving the built package out of /tmp and back into a permanent location - typically where I store the build script and the source. I spent all that time downloading and building - why would I want the package to be "temporary"?
But then I remember that if I try to automate everything, I'll reach a place were automatiion is doing something I don't want - and I can't shut it off. [cough]Microsoft[cough]
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.