Date: Thu, 3 Nov 2011 12:26:49 +0100 From: Matthias Apitz <guru@unixarea.de> To: Edward Tomasz =?utf-8?Q?Napiera=C5=82a?= <trasz@FreeBSD.org> Cc: freebsd-current@FreeBSD.org, freebsd-ports@FreeBSD.org Subject: Re: 10.0-CUR r226986 && ports (general) Message-ID: <20111103112649.GA1164@tiny> In-Reply-To: <750E14C8-D184-4ECC-9701-27D8E715B773@FreeBSD.org> References: <20111102193606.GA1086@tiny> <20111103061049.GA2273@tinyCurrent> <750E14C8-D184-4ECC-9701-27D8E715B773@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
El día Thursday, November 03, 2011 a las 12:13:31PM +0100, Edward Tomasz Napierała escribió: > > It turns out that the problem is more general! A lot of ./configure > > scripts are detecting in 10-CUR that they can't or should not build > > shared libs; the problem is that the OS is detected now as > > As a temporary workaround, add "WITH_FBSD10_FIX=1" to /etc/make.conf. ports/UPDATING and some of the mails in the archive of -current recommend setting UNAME_r=9.0-CURRENT; is this the same or which method is prefered? Thanks matthias -- Matthias Apitz e <guru@unixarea.de> - w http://www.unixarea.de/ UNIX since V7 on PDP-11, UNIX on mainframe since ESER 1055 (IBM /370) UNIX on x86 since SVR4.2 UnixWare 2.1.2, FreeBSD since 2.2.5
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20111103112649.GA1164>