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.
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.
Hi, I have recently completed installing my LFS (version 5.0) and decided to add a few programs to it. However, when I downloaded GNU Screen < gnu/software/screen/ (I cannot post an URL due to my post count) > and tried to configure it, the configure script appears unable to find certain required library functions. It finds the header files that these functions appear in, and other programs that use these functions have been able to compile successfully without any changes. Does anybody have any idea what may cause this?
Thank you for your help. I tried the LFS irc, but nobody seemed interested.
I have fixed the problem now, so I do not need any help. I have listed what the problem was and how I solved here though, in case anybody has similar issues.
As a note, I installed PAM and recompiled Shadow from the BLFS book.
Basically, as Screen was configuring itself it appears to have attempted to test out some of the shadow libraries. However, even with --enable-pam, it does not appear to link in pam at this point. This causes ld to fail to resolve the pam references within shadow, and the whole program to die. All I needed to do was LDFLAGS="-lpam" while configuring it. It now works fine.
Originally posted by cjcuk I tried the LFS irc, but nobody seemed interested.
Just thought I would correct this as well, last night no-one seemed interested. Today the room was very willing to help, but unfortunately could not see what was causing the problem =(... though several users compiled screen on their systems purely to check if they had similar problems for me.