Re: [bug-ncurses] poll() check and bootstrapping

[Dr. Werner Fink]

On Tue, Oct 06, 2015 at 08:34:46PM -0400, Thomas Dickey wrote:
> On Tue, Oct 06, 2015 at 01:55:45PM +0200, Tomáš Čech wrote:
>  
> > 2] it seems that build fails when submitting
> >   --with-fallbacks='some,terms,here' and when tic is not present in the
> >   system
> 
> It's been a documented requirement of the option for a long time, in the
> INSTALL file:
>  
>       In order to support operation of ncurses programs before the terminfo
>       tree is accessible (that is, in single-user mode or at OS installation
>       time) the ncurses library can be compiled to include an array of
>       pre-fetched fallback entries.  This must be done on a machine which
>       has ncurses' infocmp and terminfo database installed (as well as
>       ncurses' tic and infocmp programs).
> 
> > I know it is not common situation and you usually have older version
> > of ncurses available but sometimes you need to build everything from
> > scratch.
> 
> But building from build-copy of tic has always been an option for a
> packager simply by properly setting the $PATH variable (and possibly
> LD_LIBRARY_PATH, depending on your build configuration).  There's no
> need to do two builds.
> 
> > Maintainer had to generate fallback.c with FALLBACK_LIST="" (not to
> > involve tic), build tinfo and tic to be able to build correct
> > fallback.c to continue with the build.
> > 
> > I think this can be considered as bug.
> 
> no - it's intentionally made simple...
>  
> > Furthermore, it would make sense to expose BUILD_TIC and BUILD_INFOCMP
> > to configure script as option which could help cross compilation in a
> > clean way...
> 
> I think that $PATH is enough
>  

To explain why I do not do it this way: in our build system the package
which is build is *not* part of the virtual build system.  That is that
there is no tic and not infocmp in PATH as well no terminfo data base.

Now to get it work I do simply build tic and infocmp, then I extract
the wanted fallback entries from terminfo.src, set then environment
to get all work togehter from the local topdir.  After this a fallback.c
is generated and saved as a copy to fallback.c.build in the topdir.
Then on every build the fallback.c.build is put as fallback.c on the
correct place.

With this I can bootstrap without using a second step.

That's it.


-- 
  "Having a smoking section in a restaurant is like having
          a peeing section in a swimming pool." -- Edward Burr

signature.asc
Description: Digital signature