Need to add correct paths for './configure' to find X libraries.
Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
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.
Need to add correct paths for './configure' to find X libraries.
This is about installing the K3B CD/DVD Burning application into a Debian-type desktop (Mepis 8 Lenny).
We are driven into trying to compile from source because the version that arrives from using Synaptic has a bug that always reports a 'Track 1 write error' at the very end of a burn. This bug is not present on K3B in other distros in the PC (Its a multiboot).
So after unpacking the source, and running './configure', it starts checking, ending up with..
Quote:
checking for X... configure: error: Can't find X libraries. Please check your installation and add the correct paths!
Now these paths to libraries, for the use applications, are not at all the same kind of path as in
Distribution: PCLinuxOS2023 Fedora38 + 50+ other Linux OS, for test only.
Posts: 17,511
Rep:
Libs checked for by "configure" will be searched for first
in /usr/lib/ and the suffix is usually .so which is in
the development package. ( libname = libx11.so )
# 'apt-get install libx11-dev' will do ( or use Synaptic )
You will also need 'libxext-dev' 'zlib1g-dev' 'libpng12-dev'
'libjpeg62-dev' 'libqt3-mt-dev' (11 packages) 'kdelibs4-dev'
(35 packages)
Numbers mentioned are interdependecies installed, when
installing libqt3-mt-dev and kdelibs4-dev.
Optional, if cd / DVD-ripping, encoding etc. is a requirement :
'libdvdread' 'libhal-dev' 'libhal-storage-dev'
'libavcodec-dev' 'libavformat-dev'
'libflac++-dev' 'libmpcdec-dev' 'libtag1-dev'
'libmusicbrainz4-dev'
...... and 2 packages, not in the usual repo ?
'liblame0' 'liblame-dev' http://debian-multimedia.org/dists/s...e/liblame0.php
Many Thanks. That was quite a list!
I have found them all and it is all compiling now.
I am not sure why the libx files were in a different directory - maybe thats where Mepis puts them. I just did copy-paste of the apt-get install commands you posted, and it worked.
to find out the MD5 sum.
The MD5 check is correct, even though the K3B burn verification ends with that depressing Wah..Whah sound effect signalling failure.
Life is too short to go after why K3B does this in some locales and not others. I will settle for making my own checksum when I feel it important to.
I know this is quoting my own (old > 6 months) post, but I keep seeing it searched, and I feel it is important to expand it with just one other little hint for those maybe disappointed if they tried it blindly.
Be very sure that the path to the cdrom is right, and that the CDROM is mounted. It may have auto-mounted when you closed the drive tray .. maybe.
It may have a device name something like /dev/scd1 (Ubuntu) instead of /dev/cdrom. The way to know is to open a terminal, and type the "mount" command, and look for the CDROM-related paths.
Note that the "isoinfo" command does not work on a path that is the mounted directory (e.g. /media/cdrom0 or similar). The path must point to a device, and so must begin with "/dev" (e.g. /dev/scd1 ).
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.