On 06/22/2014 05:50 PM, Ken Moffat wrote:
On Sun, Jun 22, 2014 at 04:27:16PM -0500, Dan McGhee wrote:
In building LFS-7.5 and as is my habit, I was trying to install Vim-7.4 into
/tools before I started Ch. 6. I did this at the same point last year when
I built LFS-7.4, and all went well. I like having vim available right at
the beginning of Ch. 6 in the chroot environment. However, this time
vim-7.4 failed to configure with the following terminal output:
After Ken's response, I checked CLFS and using his suggestions have
tried to build vim-7.4 again. With added configure options, and both as
user and root in chroot the compile fails with this terminal output:
checking --with-tlib argument... ncurses
checking for linking with ncurses library... configure: error: FAILED
I am using this configure command:
CPPFLAGS=-I/toolz/include LDFLAGS=-L/toolz/lib ./configure
--prefix=/toolz --exec-prefix=/toolz --enable-multibyte
--with-tlib={ncurses,/toolz/lib/libncursesw.so}
The {ncurses,/toolz/lib/libncursesw.so} is there too show that I used
both options two separate times.
checking for tgetent in -ltermlib... no
checking for tgetent in -ltermcap... no
checking for tgetent in -lcurses... no
no terminal library found
checking for tgetent()... configure: error: NOT FOUND!
You need to install a terminal library; for example ncurses.
Or specify the name of the library with --with-tlib.
This was the original excerpt from the configure log. When I started
using --with-tlib=/<one of the two options above>, the configure log, at
the same point, showed:
3242 configure:10345: checking --with-tlib argument
3243 configure:10354: result: ncurses
3244 configure:10357: checking for linking with ncurses library
3245 configure:10370: gcc -o conftest -g -O2 -I/toolz/include
-I/usr/local/include
-L/toolz/lib -L/usr/local/lib conftest.c -lnsl -lncurses >&5
3246
/toolz/lib/gcc/x86_64-unknown-linux-gnu/4.8.2/../../../../x86_64-unknown-linu
x-gnu/bin/ld: cannot find -lncurses
AFIK this is a reasonable "english translation" of the configure script
starting at line 10345. I left the following in for those who may not
have seen my first post.
The use of "/toolz" is not a type-o. It is my trying to recover from the
major error that I made in building LFS-7.4 in which the links from
/usr/lib/{libgcc_s.so*,libstdc++*} to /tools/lib--established at the
beginning of Ch. 6--did not get removed. I am reasonably sure, checked and
double-checked, that I got "/toolz" everywhere "/tools" was indicated.
However........... The sanity checks of Ch. 5 passed and I have reread the
book and don't believe I have missed or interchanged any major steps.
However.............
I know that I can use vim in a separate shell while working in Ch. 6,
but because of the error I made in LFS-7.4, I want to be confident that
my temporary tool chain is rock solid. Right now I'm not. It looks
like the problem has identified the linker as the culprit, but I don't
know how to troubleshoot it. I was thinking of running
`gcc -v -o conftest -g -O2 -I/toolz/include -L/toolz/lib conftest.c
-lnsl -l/toolz/lib/libncursesw.so`
as user lfs, but I'm a "gcc dummy" and am concerned that I might screw
something up.
I know I'm operating outside of "the book," and some results may not be
predictable. I have no special reason, other than convenience, to use
vim during the chroot phase in another shell. I'm going through this
exercise to develop confidence in my tool chain.
I might add here that all the sanity checks of Ch. 5 were successful.
I'm looking for verification of running the above command or any other
troubleshooting that people who know more than I can recommend.
Good luck, and enjoy the learning.
I am. Have never looked this hard at gcc or had any other experience at
setting environment variables for make or configure than "copy and
paste." Thanks for the help.
And thanks to others who may choose to add to this discussion.
Dan
--
http://lists.linuxfromscratch.org/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
