Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 7 Feb 2013 14:38:57 -0500
From:      Eitan Adler <lists@eitanadler.com>
To:        John Hein <jhein@symmetricom.com>
Cc:        x11@freebsd.org, bug-followup <bug-followup@freebsd.org>
Subject:   Re: ports/175935: x11-clocks/xclock links to iconv
Message-ID:  <CAF6rxg=Keq_64%2BoGusQKobCCyzyH9%2BLiS0buAxfytSDgbC2iTw@mail.gmail.com>
In-Reply-To: <201302071930.r17JU2Ot074867@freefall.freebsd.org>
References:  <201302071930.r17JU2Ot074867@freefall.freebsd.org>

next in thread | previous in thread | raw e-mail | index | archive | help
On 7 February 2013 14:30, John Hein <jhein@symmetricom.com> wrote:
> The following reply was made to PR ports/175935; it has been noted by GNATS.
>
> From: John Hein <jhein@symmetricom.com>
> To: <pawel@FreeBSD.org>
> Cc: bug-followup@freebsd.org
> Subject: Re: ports/175935: x11-clocks/xclock links to iconv
> Date: Thu, 7 Feb 2013 12:27:11 -0700
>
>  xclock will use iconv if it's there, but it's optional.

Many ports do this.  This is entirely a bug.  Imagine building on a
different machine than one will be running.

>  From xclock's configure on a system without iconv...

The correct fix is to explicitly disable iconv, explicitly enable it,
or make it an OPTION.

As is though, is buggy.


-- 
Eitan Adler



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAF6rxg=Keq_64%2BoGusQKobCCyzyH9%2BLiS0buAxfytSDgbC2iTw>