Identity Guarded <[EMAIL PROTECTED]> wrote Sun, Jul 16, 2006:
> On Sunday 16 July 2006 5:13 am, Jonas Fonseca fonseca-at-diku.dk |ELinks_ML| 
> wrote:
> > Guarded Identity <[EMAIL PROTECTED]> wrote Fri, Jul 07, 2006:
> >
> > > [...]
> > > My problem is that your Makefile
> > > seems to call for some small amount of compilation during the
> > > installation.
> > > [...]
> >
> > I think this should be mostly sorted out in the current git repo thanks
> > to Witold.
> 
> I was really enthused about this.  But it seems that there are still 
> compilations occurring with a "make install" despite Witold's changes.  I've 
> attached a file that shows what I see what I try compile Elinks in my chroot.
> 
> Not all of the warnings are critical.  My chroot really has a minimal set of 
> packages installed in it (assumedly because not much should be required for a 
> simple installation -- cp, install, rm, etc.).  But it seems there's still a 
> lot of activity going on with "make install".  If you guys concede that this 
> is just impossible to change, then I guess I'll just gulp it down and install 
> it the traditional way.  However, maybe streamlining your installation 
> process isn't such a bad idea if it's possible.

Reading the build log you attached it seems that you didn't build ELinks
completely first ...

> make[2]: Entering directory `/home/tnks/elinks/src/bfu'
>       [CC]   src/bfu/button.o
> make[2]: Leaving directory `/home/tnks/elinks/src/bfu'

... since this object needs to be created. Of course this is the first
object file that will be build and therefore something different could
be the reason for it being rebuild.

Don't know if it could be caused by system headers not existing or
having different timestamps in you chroot environment or something.

I am wondering why you cannot install into a subdirectory (using make
DESTDIR=build/ install) and then either just cp/rsync that
subdirectory into your chroot environment much like package systems
work.

> make[1]: Leaving directory `/home/tnks/elinks/src'
> "rxvt"
> tput: unknown terminal "rxvt"
[...line repeated...]

Several information from your system are gathered during ./configure and
saved in Makefile.config and some of the tools may not be available
later. We absolutely need to be able to rely on these tools also being
available during install. Of course this particular thing causing a
warning is the colored make output, a thing that probably should be
disabled by default, or at least be possible to disable even if tput
is found.

-- 
Jonas Fonseca
_______________________________________________
elinks-dev mailing list
[email protected]
http://linuxfromscratch.org/mailman/listinfo/elinks-dev

Reply via email to