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:
>
> >checking --with-tlib argument... empty: automatic terminal library
> >selection
> >checking for tgetent in -ltinfo... no
> >checking for tgetent in -lncurses... no
Based on what you say after this, I think you probably need to try
something like --with-tlib=/toolz/lib/libncursesw.so : the book
doesn't need non-wide libncurses in /tools, so (from a quick look at
my logs) we don't install it there.
> >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 failure occurs, with identical output, whether I build as user lfs or
> as root in the chroot environment.
>
> This, without all the other stuff, is what the configure log gives:
>
> >3560 configure:10388: checking for tgetent in -lcurses
> > 3561 configure:10413: gcc -o conftest -g -O2 -I/usr/local/include
> >-L/usr/local/l
> >ib conftest.c -lcurses -lnsl >&5
> > 3562
> > /toolz/lib/gcc/x86_64-unknown-linux-gnu/4.8.2/../../../../x86_64-unknown-linu
> >x-gnu/bin/ld: cannot find -lcurses
> > 3563 collect2: error: ld returned 1 exit status
>
> As I said this did not happen the last time I tried to do this. I used
> `.configure --prefix=/toolz --enable-multibyte`
>
> 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.............
>
> Because of this error, I want to make sure that my temporary tool chain
> works without error. At this point, now, I am not sure. `./configure
> --help` indicates that I can use the switch "--with-tlib=library" but I
> don't know what to put there. I'd like some guidance to see if it works.
>
> Depending on the results of this troubleshooting, I could scrap my build so
> far and start over. My instincts tell me that I made a mistake, but so far
> I haven't been able to figure it out. I'm asking for help to resolve this
> situation.
>
> Thanks,
> Dan
>
Your approach sounds good, but any problems you find will probably
not be common to the rest of us. ISTR that at one time /tools was
hardcoded in at least one gcc patch, but I think that using your own
prefix (with corresponding name in /mnt/lfs) has probably worked for
a few years now.
When you are developing on your own, do not be too ready to scrap a
build. Yes, sometimes that is necessary, but it is often useful to
get everything out of the build (i.e. look at what exists, look at
configure scripts, try to identify why things do not work) before
you trash it.
In this case, building vim in /tools is already outside the book (a
reasonable idea, particularly for manual builds, but if I need to
edit things I get root on the host system to edit the chroot file),
so most of us do not have any idea about what might go wrong there,
even before using /toolz. If my suggestion above for tlib does not
fix this, I suggest that you take a look at cross-lfs : the details
are probably very different, but ISTR that vim got built somewhere
before chroot - perhaps only in the 'boot' option. Of course,
whatever they do (or don't do) might not help here. And also take a
look at vim's configure script in case the likely fix is fairly
obvious (some configure scripts are mostly _fairly_ easy to parse,
others are not - I have no idea what the tlib part of vim's
configure looks like).
Good luck, and enjoy the learning.
Also, if pointing tlib to libncursesw does let it compile, it needs
to be tested at run time (i.e. in chroot) to see if you can do
adequate edits : I guess that ASCII is the only thing needed before
vim has been built in chroot.
ĸen
--
Nanny Ogg usually went to bed early. After all, she was an old lady.
Sometimes she went to bed as early as 6 a.m.
--
http://lists.linuxfromscratch.org/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
