[Buildroot] commit bf4465 (ncurses: fix hanging installation due to old version of tic)

[Buildroot] commit bf4465 (ncurses: fix hanging installation due to old version of tic)

[Trevor Woerner]

Now that ncurses depends on host-ncurses I was wondering if it also
needs to depend on host-automake and/or host-pkg-config?

Could $(call AUTOTARGETS,host) be tweaked to automatically include
host-automake implicitly?

[Buildroot] commit bf4465 (ncurses: fix hanging installation due to old version of tic)

[Thomas Petazzoni]

Le Thu, 24 Nov 2011 15:47:23 -0500,
Trevor Woerner <twoerner@gmail.com> a ?crit :

> Now that ncurses depends on host-ncurses I was wondering if it also
> needs to depend on host-automake and/or host-pkg-config?
> 
> Could $(call AUTOTARGETS,host) be tweaked to automatically include
> host-automake implicitly?

It already does if <pkg>_AUTORECONF = YES.

Thomas
-- 
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com

[Buildroot] commit bf4465 (ncurses: fix hanging installation due to old version of tic)

[Trevor Woerner]

On Thu, Nov 24, 2011 at 3:57 PM, Thomas Petazzoni
<thomas.petazzoni@free-electrons.com> wrote:
> Le Thu, 24 Nov 2011 15:47:23 -0500,
> Trevor Woerner <twoerner@gmail.com> a ?crit :
>> Could $(call AUTOTARGETS,host) be tweaked to automatically include
>> host-automake implicitly?
>
> It already does if <pkg>_AUTORECONF = YES.

Ah, and the ncurses packages does not. Shouldn't it?

[Buildroot] commit bf4465 (ncurses: fix hanging installation due to old version of tic)

[Thomas Petazzoni]

Le Thu, 24 Nov 2011 16:08:47 -0500,
Trevor Woerner <twoerner@gmail.com> a ?crit :

> Ah, and the ncurses packages does not. Shouldn't it?

Not if autoreconfiguring the package is not needed.

Thomas
-- 
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com

[Buildroot] commit bf4465 (ncurses: fix hanging installation due to old version of tic)

[Trevor Woerner]

I have a configuration where I'm:
- using an external toolchain
- not using busybox
- selecting a very small number of starter packages

When I record the build and look at the steps involved it starts off
looking like the following:
>>> ncurses 5.7 Extracting
>>> ncurses 5.7 Patching package//ncurses
>>> ncurses 5.7  Updating config.sub and config.guess
>>> ncurses 5.7 Patching libtool
>>> host-ncurses 5.7 Extracting
>>> host-ncurses 5.7 Patching package//ncurses
>>> host-ncurses 5.7  Updating config.sub and config.guess
>>> host-ncurses 5.7 Patching libtool
>>> host-ncurses 5.7 Configuring
>>> host-ncurses 5.7 Building
>>> host-ncurses 5.7 Installing to host directory
>>> ncurses 5.7 Configuring
>>> ncurses 5.7 Building
>>> ncurses 5.7 Installing to staging directory
>>> ncurses 5.7 Installing to target
...

Since ncurses and host-ncurses use the autotools I was just wondering
if it was an oversight that they're not first building and using
host-autotools.

[Buildroot] commit bf4465 (ncurses: fix hanging installation due to old version of tic)

[Thomas De Schampheleire]

On Thu, Nov 24, 2011 at 10:59 PM, Trevor Woerner <twoerner@gmail.com> wrote:
> I have a configuration where I'm:
> - using an external toolchain
> - not using busybox
> - selecting a very small number of starter packages
>
> When I record the build and look at the steps involved it starts off
> looking like the following:
>>>> ncurses 5.7 Extracting
>>>> ncurses 5.7 Patching package//ncurses
>>>> ncurses 5.7 ?Updating config.sub and config.guess
>>>> ncurses 5.7 Patching libtool
>>>> host-ncurses 5.7 Extracting
>>>> host-ncurses 5.7 Patching package//ncurses
>>>> host-ncurses 5.7 ?Updating config.sub and config.guess
>>>> host-ncurses 5.7 Patching libtool
>>>> host-ncurses 5.7 Configuring
>>>> host-ncurses 5.7 Building
>>>> host-ncurses 5.7 Installing to host directory
>>>> ncurses 5.7 Configuring
>>>> ncurses 5.7 Building
>>>> ncurses 5.7 Installing to staging directory
>>>> ncurses 5.7 Installing to target
> ...
>
> Since ncurses and host-ncurses use the autotools I was just wondering
> if it was an oversight that they're not first building and using
> host-autotools.

The autoconf and automake script are only needed to recreate the
configure script and Makefiles, after you manually changed any of the
input files (configure.ac or Makefile.am). In most cases, you do not
change these files, and the configure script and Makefile files
distributed with the package are in line with the corresponding input
files. So, host-autoconf and host-automake are not built.

The <pkg>_AUTORECONF variable can be set to YES to force recreation of
the configure script and Makefiles, in which case these tools will be
built.

Best regards,
Thomas