Re: 10.0-CUR r226986 && ports (general)

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
_______________________________________________
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"