Matt Burgess wrote:
> Yeah, both xz and zlib install their libraries to /lib, but oddly
> enough, kmod still found them after telling it that they were
> in /usr/lib. I guess the linker's searching in /lib by default?
Yes, it should search /lib by default.
(Wandering a bit off topic...)
dummy.log:
Libraries:
LIBRARY_PATH=
1. /usr/lib/gcc/x86_64-unknown-linux-gnu/4.6.1/:
exists
2. /usr/lib/gcc/x86_64-unknown-linux-gnu/4.6.1/../../../../lib64/:
= /usr/lib64/ symlink to /usr/lib
3. /lib/../lib64/:
= /lib64/ symlink to /lib
4. /usr/lib/../lib64/:
= /usr/lib64/ symlink to /usr/lib
5. /usr/lib/gcc/x86_64-unknown-linux-gnu/4.6.1/../../../:
= /usr/lib
6. /lib/:
7. /usr/lib/
1. SEARCH_DIR("/usr/x86_64-unknown-linux-gnu/lib64");
2. SEARCH_DIR("/usr/local/lib64");
3. SEARCH_DIR("/lib64");
4. SEARCH_DIR("/usr/lib64");
5. SEARCH_DIR("/usr/x86_64-unknown-linux-gnu/lib");
6. SEARCH_DIR("/usr/local/lib");
7. SEARCH_DIR("/lib");
8. SEARCH_DIR("/usr/lib");
Note: On my system 1, 2, 4, and 5 do not exist.
3 and 7 are the same.
4 and 8 are the same.
I wonder if it would be useful to try to remove what's not used?
Includes:
ignoring nonexistent directory
"/usr/lib/gcc/x86_64-unknown-linux-gnu/4.6.1/../../../../x86_64-unknown-linux-gnu/include"
Translates to /usr/x86_64-unknown-linux-gnu/include"
#include "..." search starts here:
#include <...> search starts here:
/usr/lib/gcc/x86_64-unknown-linux-gnu/4.6.1/include
/usr/local/include (empty)
/usr/lib/gcc/x86_64-unknown-linux-gnu/4.6.1/include-fixed
/usr/include
I wonder if changing these search paths would make any significant
difference in compile times.
-- Bruce
--
http://linuxfromscratch.org/mailman/listinfo/lfs-dev
FAQ: http://www.linuxfromscratch.org/faq/
Unsubscribe: See the above information page
