Hi Martin,

On Montag, 16. Februar 2009, Martin Hejnfelt wrote:
> Marc Kleine-Budde <m...@...> writes:
> > When we look at rules/util-linux.in, we see that NCURSES is not always
> > enabled, perhaps we should enable ncurses unconditionally, or least for
> > more.
> >
> > menuconfig UTIL_LINUX
> >
> >         tristate
> >         prompt "util-linux                    "
> >         select NCURSES if UTIL_LINUX_CFDISK
> >         select NCURSES if UTIL_LINUX_SETTERM
> >
> > regarding you logfile, ncurses.h isn't found.
> >
> > Marc
>
> Ok, so the plot thickens... If I do a "ptxdist clean", and then a "ptxdist
> targetinstall util-linux" the package compiles fine. If I then clean do the
> "ptxdist clean" and then a "ptxdist go" it fails in this package with the
> error seen above. Now, if i choose one of the two options that specifically
> chooses ncurses, eg. setterm, it compiles correctly. So the question is why
> this is happening, when it compiles fine on another machine, without
> setterm enabled?

I guess now, it detects any kind of termcap by accident so its buildsystem 
decides to compile text-utils/more.c. Can you check with this patch applied 
on your ptxdist-trunk?

Index: rules/util-linux.make
===================================================================
--- rules/util-linux.make       (Revision 9792)
+++ rules/util-linux.make       (Arbeitskopie)
@@ -42,7 +42,8 @@
 #
 # autoconf
 #
-UTIL_LINUX_AUTOCONF := $(CROSS_AUTOCONF_USR)
+UTIL_LINUX_AUTOCONF := $(CROSS_AUTOCONF_USR) \
+               ac_cv_lib_termcap_tgetnum=no

 
# ----------------------------------------------------------------------------
# Target-Install


Regards,
Juergen

-- 
Pengutronix e.K.                              | Juergen Beisert             |
Linux Solutions for Science and Industry      | Phone: +49-8766-939 228     |
Vertretung Sued/Muenchen, Germany             | Fax:   +49-5121-206917-5555 |
Amtsgericht Hildesheim, HRA 2686              | http://www.pengutronix.de/  |

--
ptxdist mailing list
ptxdist@pengutronix.de

Reply via email to