[Top][All Lists]

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

Re: libtool pkgsrc DragonFly base ncurses made private

From: Thomas Dickey
Subject: Re: libtool pkgsrc DragonFly base ncurses made private
Date: Sun, 21 Feb 2016 19:59:10 -0500
User-agent: Mutt/1.5.21 (2010-09-15)

On Fri, Feb 19, 2016 at 07:51:59PM -0800, David Shao wrote:
> The problem is that the libdir field in the resulting pkgsrc
> libncurses.la on recent DragonFly alone draws in the build directory
> from DESTDIR in addition to the desired /usr/pkg/lib.
> It appears to me that what is happening is that at least one source
> file in the ncurses subdirectory is being regenerated in the second
> install pass, leading to the wrong DESTDIR being appended to
> libncurses.la libdir.  In the initial pass to make the object files,
> the DESTDIR of "" is what is desired for libdir:

thanks (I think I follow the description - I'll investigate and see how
this works...)
> As a workaround the patch below simply adds another pass into the
> ncurses subdirectory right before the c++ subdirectory is processed.
> This fixes the problem on recent DragonFly using pkgsrc and seems to
> do no harm on FreeBSD 11-current amd64, FreeBSD 10-2-release, NetBSD
> 7.99.26 amd64 native xorg, and NetBSD 7.99.26 amd64 modular xorg.
> However I do not recommend this patch unless there is a general
> problem with systems without public base ncurses trying to install
> ncurses with libtool.  I am a mere user representing no one, and
> pkgsrc is no longer the officially supported ports framework on
> DragonFly.  The officially supported framework dports seems to work
> just fine without this patch.


Thomas E. Dickey <address@hidden>

Attachment: signature.asc
Description: Digital signature

reply via email to

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