bug-ncurses
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Problem with compiling ncurses under FreeBSD 7.2


From: Kevin Monceaux
Subject: Re: Problem with compiling ncurses under FreeBSD 7.2
Date: Tue, 21 Jul 2009 18:06:40 -0500
User-agent: Mutt/1.5.18 (2008-05-17)

On Tue, Jul 21, 2009 at 02:11:18PM +0000, michael green wrote:
> 
> I am using FreeBSD 7.2-RELEASE. Generic kernel. Full install.
> 
> I wanted to install ncurses because MS FoxPro Unix needs a terminfo
> database.

Are you sure it's not already installed on your system?  If you
performed a full install it should be there.  I just took a look on my
7.2 box and I have libncurses.so.7 and libncursesw.so.7 under /lib
with various symlinks under /usr/lib pointing to them.

> I read INSTALL and README.
> 
> I ran ./configure in the appropriate directory
> (/usr/src/contrib/ncurses). The messages stopped with the following
> error: config.status: error: cannot find input file:
> test/Makefile.in

On my box I have no test directory at all under
/usr/src/contrib/ncurses.  Is it perhaps /usr/src/lib/ncurses you're
aiming for?  I **think** with the FreeBSD base system sources one can
just run make followed by make install from the appropriate directory
without running configure.  Under /usr/src/lib/ncurses on my box
there's no configure script.  There is a Makefile.  I usually build
everything when updating via make buildworld/make installworld from
/usr/src as opposed to trying to build individual bits.

If FoxPro isn't happy with the system ncurses there's also a copy of
ncurses available in the ports tree.  If you have a copy of the ports
tree installed you can go to /usr/ports/devel/ncurses and issue a:

make
make install
make clean

to install that version, which will get installed under /usr/local.  


-- 

Kevin
http://www.RawFedDogs.net
http://www.WacoAgilityGroup.org
Bruceville, TX

Si hoc legere scis nimium eruditionis habes.
Longum iter est per praecepta, breve et efficax per exempla!!!





reply via email to

[Prev in Thread] Current Thread [Next in Thread]