Subject: Re: buildlink vs. real gcc ?!
To: Hubert Feyrer <>
From: Lubomir Sedlacik <>
List: tech-pkg
Date: 03/04/2003 15:57:41
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable


On Tue, Mar 04, 2003 at 03:40:43PM +0100, Hubert Feyrer wrote:
> Trying to pkg something, I get a weird error with USE_BUILDLINK2 set:
> 	miyu% make
> 	=3D=3D=3D> Building for slurm-0.2.1
> 	gcc -g -O2 -D_HAVE_NCURSES -I/usr/pkg/include -DVERSION=3D'"0.2.1"' slur=
> 	-L/usr/pkg/lib -Wl,-R/usr/pkg/lib  -lncurses -o slurm
> 	/var/tmp/ccHf9TWs.o: In function `chcolor':
> 	/usr/cvs/pkgsrc/net/
> 	undefined reference to `use_default_colors'
> 	collect2: ld returned 1 exit status
> 	*** Error code 1
> Doing the same thing manually, it works:
> 	miyu% cd work.i386/slurm-0.2.1/
> 	miyu% gcc -g -O2 -D_HAVE_NCURSES -I/usr/pkg/include -DVERSION=3D'"0.2.1"'
> 	slurm.c -L/usr/pkg/lib -Wl,-R/usr/pkg/lib  -lncurses -o slurm
> 	miyu%
> The pkg Makefile uas USE_BUILDLINK2 set and pulls in the ncurses
> file. Knowing that buildlink2 uses some wrappers for gcc
> etc. (and that I do NOT want to look inside them), I wonder what's going
> on here. Shouldn't the same gcc command work in both cases? Seems
> confusing to me.
> FWIW, there is no libncurses* in the buildlink dir...

so it means that libcurses was used instead because it satisfied the
dependency (INCOMPAT_CURSES) in ncurses/

use_default_colors() is mising in 1.6. see also archives for related
discussion about use_default_colors/use_default_color (tech-userlevel?).

you will need to check when use_default_colors() appeared in our curses
and set INCOMPAT_CURSES accordingly in the package's Makefile. (with a
comment that it's due use_default_colors()).


-- Lubomir Sedlacik <>                   --
--                  <>                   --

Content-Type: application/pgp-signature
Content-Disposition: inline

Version: GnuPG v1.2.1 (NetBSD)