configure fails with: *snip* checking for Terminfo... yes checking for the slang library and header files ... no configure: error: unable to find the slang library and header file slang.h but then, when running the same configure command with --with-slang=/usr/ at the end, it works perfectly. I looked at bug 16678 , but find /usr/lib/gcc/x86_64-pc-linux-gnu/3.4.6/ -name "slang*" finds nothing. Hardened box, all USE flags for jed are off.
emerge --info and config.log are missing.
What is the output of the following commands: emerge -pv slang jed locate slang.h locate libslang.so locate libslang.a
Created attachment 151969 [details] config.log
Created attachment 151971 [details] emerge --info
(In reply to comment #2) # emerge -pv slang jed [ebuild R ] sys-libs/slang-2.1.3-r1 USE="readline -cjk -pcre -png" 0 kB [ebuild N ] app-editors/jed-0.99.18 USE="-X -gpm -truetype" 0 kB # locate slang.h /usr/include/slang.h # locate libslang. /usr/lib64/libslang.a /usr/lib64/libslang.so /usr/lib64/libslang.so.2 /usr/lib64/libslang.so.2.1.3
(In reply to comment #0) > checking for the slang library and header files ... no > configure: error: unable to find the slang library and header file slang.h I cannot reproduce the problem and I have no idea why configure wouldn't find these files. They are in their standard locations. > but then, when running the same configure command with --with-slang=/usr/ > at the end, it works perfectly. I'm tempted just to add this to econf. But it would be nice if we would understand what is going on here.
I know nothing about configure generation, but configure line 6283: lib_library_dirs="\ $jd_prefix_libdir \ /usr/local/lib \ /usr/local/lib/slang \ /usr/local/slang/lib \ /usr/lib \ /usr/lib/slang \ /usr/slang/lib \ /opt/lib \ /opt/lib/slang \ /opt/slang/lib" I checked on the other amd64 box, to find that /usr/lib symlinks to lib64 there (and jed builds fine), and I wonder if that doesn't make the script find what it's looking for. On the box that it fails on, /usr/lib is a dir on it's own; don't know whether that's specific to hardened or just wrong and should be fixed (deleted and symlinked).
(In reply to comment #7) > I checked on the other amd64 box, to find that /usr/lib symlinks to lib64 > there (and jed builds fine), and I wonder if that doesn't make the script > find what it's looking for. On the box that it fails on, /usr/lib is a dir > on it's own; don't know whether that's specific to hardened or just wrong > and should be fixed (deleted and symlinked). /usr/lib should be a symlink to lib64, so you should move its contents to /usr/lib64 and symlink it. (Better backup your system before. ;-) I've asked the hardened team about it; they tell me that this was a known problem at least with the 2006.0 hardened (non-multilib) stage3. See bug 125034. Resolving as invalid. Feel free to reopen if this is still a problem after you've fixed the symlink.
