On Jul 11, 2007, at 5:01 AM, Jacky Buyck wrote: > - What is the way to do to include new applications in our distribs ? > > Concider the case of the simple bash interpreter. > A ldd on bash binary show the use of the following libs : > # ldd bin/bash > libreadline.so.5 => not found > libhistory.so.5 => not found > libncursesw.so.5 => /usr/lib/libncursesw.so.5 (0x00d1f000) > libdl.so.2 => /lib/libdl.so.2 (0x00cf4000) > libc.so.6 => /lib/tls/libc.so.6 (0x00bc9000) > /lib/ld-linux.so.2 (0x00bb0000) > > Take the exemple of libncurses > > # ll ./lib/libncursesw.so.5 > lrwxrwxrwx 1 root root 18 Jul 9 15:12 ./lib/libncursesw.so.5 -> > libncursesw.so.5.5 > > We see that libncursesw.so.5 is a link to libncursesw.so.5.5 ! > > > What must I do to include Bash ?! > > Must I integrate the binary and the directly needed lib as a link > to the real one ? > Any other needs ???
The installs usually take care of the links as they do what should be done and run ldconfig so that it is finished and the cache is updated. I'm sure someone else can give reason for the extra work ncurses needs. Bash doesn't install bash libraries. When you build source, the linker will link to the libs on the system. So nothing will include bash libs since that isn't possible. Most configure options will let you enable or disable options, for example you could request to not build with the system readline or ncurses with bash, or you could let it auto detect them, or specifically tell it to use the system readline or ncurses. Most packages will autodetect what is on the system. But if something isn't utilizing what is on the system and it can, then you might have to tell configure to enable the option. For example, grep, during the LFS install can utilize the pcre package. Well if you don't have pcre installed before you use grep, grep won't link to pcre. What I do is install pcre before grep, and then grep will link to pcre. I think that is a better example. Same thing with shadow. Shadow can utilize cracklib, but if you don' have cracklib installed before shadow, shadow will not use and link to cracklib. Once cracklib is installed from shadow and you use --with- libcrack, then shadow will utilize cracklib. Let me know if that doesn't help you understand what is going on. Sincerely, William -- http://linuxfromscratch.org/mailman/listinfo/lfs-chat FAQ: http://www.linuxfromscratch.org/faq/ Unsubscribe: See the above information page
