Linux From ScratchThis Forum is for the discussion of LFS.
LFS is a project that provides you with the steps necessary to build your own custom Linux system.
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.
# Begin /etc/ld.so.conf
/usr/local/lib
/opt/lib
/usr/lib
/usr/include
# End /etc/ld.so.conf
in the imlib directory, I do the following (first running ldconfig):
./configure --prefix=/usr --includedir=/usr/include && make && make install
which aborts with:
checking for sys/ipc.h... no
checking for sys/shm.h... no
checking X11/extensions/XShm.h... yes
checking for jpeg_destroy_decompress in -ljpeg... yes
checking for jpeglib.h... no
configure: error: *** JPEG header file not found ***
So with jpeglib.h sitting in both /usr/include and copied just in case to /usr/lib, why can't imlib see it?
-w Inhibits all warning messages.
I assume you are compiling with a more recent version of gcc which will give an extra warning message which confuses the configure script. By disabling warning messages it continues without problems.
This thread is more than two years old. It's unlikely that you're having the same problem. Why don't you start your own thread and give more detail about what you did and what error message you got.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.