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

2011-11-03 Thread Chris Rees
On 3 Nov 2011 06:11, "Matthias Apitz" wrote: > > El día Wednesday, November 02, 2011 a las 08:36:07PM +0100, Matthias Apitz escribió: > > > > > Hello, > > > > I fetched 10-CUR from SVN as r226986 and /usr/ports from CVS on November > > 1st; > > > > The ports/audio/jack seems installing fine, but t

Re: dconf gconf wtfconf ?

2011-11-03 Thread Koop Mast
On Thu, 2011-11-03 at 00:21 -0400, Jason Hellenthal wrote: > Can anyone explain the difference or need for both of these ? > > ports/devel/gconf <-( Should'nt this be the only one needed ? ) > ports/devel/dconf > > I just noticed dconf installed on my system. Well it is true that dconf is the re

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

2011-11-03 Thread Matthias Apitz
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

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

2011-11-03 Thread Alexander Best
On Thu Nov 3 11, Matthias Apitz wrote: > El día Wednesday, November 02, 2011 a las 08:36:07PM +0100, Matthias Apitz > escribió: > > > > > Hello, > > > > I fetched 10-CUR from SVN as r226986 and /usr/ports from CVS on November > > 1st; > > > > The ports/audio/jack seems installing fine, but th

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

2011-11-03 Thread Edward Tomasz Napierała
Wiadomość napisana przez Matthias Apitz w dniu 3 lis 2011, o godz. 07:10: > El día Wednesday, November 02, 2011 a las 08:36:07PM +0100, Matthias Apitz > escribió: >> Hello, >> >> I fetched 10-CUR from SVN as r226986 and /usr/ports from CVS on November >> 1st; >> >> The ports/audio/jack seems ins

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

2011-11-03 Thread Edward Tomasz Napierała
Wiadomość napisana przez Matthias Apitz w dniu 3 lis 2011, o godz. 12:26: > 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

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

2011-11-03 Thread Matthias Apitz
El día Thursday, November 03, 2011 a las 11:28:47AM +, Alexander Best 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 > > >

Re: dconf gconf wtfconf ?

2011-11-03 Thread Ruslan Mahmatkhanov
Koop Mast wrote on 03.11.2011 13:01: On Thu, 2011-11-03 at 00:21 -0400, Jason Hellenthal wrote: Can anyone explain the difference or need for both of these ? ports/devel/gconf<-( Should'nt this be the only one needed ? ) ports/devel/dconf I just noticed dconf installed on my system. Well it

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

2011-11-03 Thread Alexander Best
On Thu Nov 3 11, Matthias Apitz wrote: > El día Thursday, November 03, 2011 a las 11:28:47AM +, Alexander Best > 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;

Re: dconf gconf wtfconf ?

2011-11-03 Thread Michal Varga
On Thu, 2011-11-03 at 00:21 -0400, Jason Hellenthal wrote: > Can anyone explain the difference or need for both of these ? > > ports/devel/gconf <-( Should'nt this be the only one needed ? ) > ports/devel/dconf > > I just noticed dconf installed on my system. > > Both of these have the same WWW:

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

2011-11-03 Thread b. f.
> > > 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. > > port

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

2011-11-03 Thread O. Hartmann
Am 11/03/11 18:42, schrieb b. f.: 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

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

2011-11-03 Thread b. f.
On 11/3/11, O. Hartmann wrote: > Am 11/03/11 18:42, schrieb b. f.: >So I presume the WITH_FBSD10_FIX flag is set in /etc/make.conf, right? You can set it in a number of local Makefiles that are automatically included during a port build. That includes make.conf, and the others mentioned in por

Re: 10.0-CUR r226986 && ports/net-mgmt/net-snmp

2011-11-03 Thread Matthias Apitz
El día Thursday, November 03, 2011 a las 01:42:50PM -0400, b. f. escribió: > No, it is not the same. You can either masquerade, by setting UNAME_r > and OSVERSION, or by editing the headers and scripts that define them; > or you can use WITH_FBSD10_FIX for ports that define HAS_CONFIGURE > (which

Re: 10.0-CUR r226986 && ports/net-mgmt/net-snmp

2011-11-03 Thread Garrett Cooper
On Nov 3, 2011, at 8:25 PM, Matthias Apitz wrote: > El día Thursday, November 03, 2011 a las 01:42:50PM -0400, b. f. escribió: > >> No, it is not the same. You can either masquerade, by setting UNAME_r >> and OSVERSION, or by editing the headers and scripts that define them; >> or you can use WI

Re: 10.0-CUR r226986 && ports/security/cyrus-sasl2-saslauthd

2011-11-03 Thread Matthias Apitz
El día Thursday, November 03, 2011 a las 01:42:50PM -0400, b. f. escribió: > No, it is not the same. You can either masquerade, by setting UNAME_r > and OSVERSION, or by editing the headers and scripts that define them; > or you can use WITH_FBSD10_FIX for ports that define HAS_CONFIGURE > (which