Re: AFFECTS: 10-CURRENT users with any port depending on converters/libiconv

On Sat, 07 Sep 2013 02:10:50 +0400 Boris Samorodov wrote: > 07.09.2013 01:51, O. Hartmann пишет: > > On Fri, 06 Sep 2013 21:11:26 +0400 > > Boris Samorodov wrote: > > > >> 06.09.2013 20:44, O. Hartmann пишет: > >>> On Fri, 06 Sep 2013 20:08:59 +0400 > >>> Boris Samorodov wrote: > >>> > 06

Re: [RFC][CFT] GEOM direct dispatch and fine-grained CAM locking

On 07.09.2013 02:02, Jeremie Le Hen wrote: On Fri, Sep 06, 2013 at 11:29:11AM +0300, Alexander Motin wrote: On 06.09.2013 11:06, Jeremie Le Hen wrote: On Fri, Sep 06, 2013 at 12:46:27AM +0200, Olivier Cochard-Labbé wrote: On Thu, Sep 5, 2013 at 11:38 PM, Alexander Motin wrote: I've found and

Re: AFFECTS: 10-CURRENT users with any port depending on converters/libiconv

On 09/06/13 05:16, AN wrote: Hi: I am posting to both lists because this problem affects users of current and ports, and I didn't know which would be more appropriate so please forgive me. # uname -a FreeBSD FBSD10 10.0-CURRENT FreeBSD 10.0-CURRENT #80 r255129: Sun Sep 1 16:01:36 CDT 2013

Re: AFFECTS: 10-CURRENT users with any port depending on converters/libiconv

06.09.2013 07:16, AN пишет: > Hi: > > I am posting to both lists because this problem affects users of current > and ports, and I didn't know which would be more appropriate so please > forgive me. > > # uname -a > FreeBSD FBSD10 10.0-CURRENT FreeBSD 10.0-CURRENT #80 r255129: Sun Sep 1 > 16:0

Re: New iSCSI stack.

On Fri, Sep 6, 2013 at 1:50 AM, Edward Tomasz Napierała wrote: > New patch, updated for Capsicum changes, is here: > > http://people.freebsd.org/~trasz/cfiscsi-20130906.diff > > Bravo patched, compiled successfully and tested a lun using ctld cfiscsi_ioctl_handoff: new conn

Re: [RFC][CFT] GEOM direct dispatch and fine-grained CAM locking

On Fri, Sep 06, 2013 at 12:46:27AM +0200, Olivier Cochard-Labbé wrote: > On Thu, Sep 5, 2013 at 11:38 PM, Alexander Motin wrote: > > I've found and fixed possible double request completion, that could cause > > such symptoms if happened. Updated patch located as usual: > > http://people.freebsd.or

Re: [RFC][CFT] GEOM direct dispatch and fine-grained CAM locking

On 06.09.2013 11:06, Jeremie Le Hen wrote: On Fri, Sep 06, 2013 at 12:46:27AM +0200, Olivier Cochard-Labbé wrote: On Thu, Sep 5, 2013 at 11:38 PM, Alexander Motin wrote: I've found and fixed possible double request completion, that could cause such symptoms if happened. Updated patch located a

Re: New iSCSI stack.

Wiadomość napisana przez Outback Dingo w dniu 6 wrz 2013, o godz. 09:46: > On Fri, Sep 6, 2013 at 1:50 AM, Edward Tomasz Napierała > wrote: > New patch, updated for Capsicum changes, is here: > > http://people.freebsd.org/~trasz/cfiscsi-20130906.diff > > > Bra

Re: AFFECTS: 10-CURRENT users with any port depending on converters/libiconv

On Fri, 6 Sep 2013, Guido Falsi wrote: On 09/06/13 05:16, AN wrote: Hi: I am posting to both lists because this problem affects users of current and ports, and I didn't know which would be more appropriate so please forgive me. # uname -a FreeBSD FBSD10 10.0-CURRENT FreeBSD 10.0-CURRENT #80

Re: AFFECTS: 10-CURRENT users with any port depending on converters/libiconv

On Fri, 06 Sep 2013 11:35:35 +0400 Boris Samorodov wrote: > 06.09.2013 07:16, AN пишет: > > Hi: > > > > I am posting to both lists because this problem affects users of > > current and ports, and I didn't know which would be more > > appropriate so please forgive me. > > > > # uname -a > > Free

Re: AFFECTS: 10-CURRENT users with any port depending on converters/libiconv

On 09/06/13 17:26, AN wrote: On Fri, 6 Sep 2013, Guido Falsi wrote: On 09/06/13 05:16, AN wrote: Hi: I am posting to both lists because this problem affects users of current and ports, and I didn't know which would be more appropriate so please forgive me. # uname -a FreeBSD FBSD10 10.0-CU

Re: AFFECTS: 10-CURRENT users with any port depending on converters/libiconv

On 09/06/13 17:32, O. Hartmann wrote: On Fri, 06 Sep 2013 11:35:35 +0400 Boris Samorodov wrote: 06.09.2013 07:16, AN пишет: Hi: I am posting to both lists because this problem affects users of current and ports, and I didn't know which would be more appropriate so please forgive me. # uname

Re: AFFECTS: 10-CURRENT users with any port depending on converters/libiconv

On Fri, 06 Sep 2013 11:35:35 +0400 Boris Samorodov wrote: > 06.09.2013 07:16, AN пишет: > > Hi: > > > > I am posting to both lists because this problem affects users of > > current and ports, and I didn't know which would be more > > appropriate so please forgive me. > > > > # uname -a > > Free

[head tinderbox] failure on ia64/ia64

TB --- 2013-09-06 13:57:08 - tinderbox 2.10 running on freebsd-current.sentex.ca TB --- 2013-09-06 13:57:08 - FreeBSD freebsd-current.sentex.ca 8.3-PRERELEASE FreeBSD 8.3-PRERELEASE #0: Mon Mar 26 13:54:12 EDT 2012 d...@freebsd-current.sentex.ca:/usr/obj/usr/src/sys/GENERIC amd64 TB --- 2013

Re: AFFECTS: 10-CURRENT users with any port depending on converters/libiconv

On 09/06/13 17:04, O. Hartmann wrote: Using portmaster, I'm higly adviced to use option -f, otherwise every second port I try to update gets interrupted due to missing libiconv.so.3. It is impossible to update a system unattended and this is a mess with 200 or even 680 ports to be updated. A was

Re: AFFECTS: 10-CURRENT users with any port depending on converters/libiconv

06.09.2013 19:44, O. Hartmann пишет: > Here we go. It is the config.log from one of the failing machines, > failing in print/cups-client. Please, show the output of following commands (at the host in question): # svn info /usr/ports/ # svn svn st /usr/ports/print/cups* -- WBR, Boris Samorodov (

[head tinderbox] failure on mips64/mips

TB --- 2013-09-06 16:23:41 - tinderbox 2.10 running on freebsd-current.sentex.ca TB --- 2013-09-06 16:23:41 - FreeBSD freebsd-current.sentex.ca 8.3-PRERELEASE FreeBSD 8.3-PRERELEASE #0: Mon Mar 26 13:54:12 EDT 2012 d...@freebsd-current.sentex.ca:/usr/obj/usr/src/sys/GENERIC amd64 TB --- 2013

Re: Cross-buildkernel (i386->amd64) is broken?

On Fri, Sep 06, 2013 at 10:08:20AM -0700, hiren panchasara wrote: > On Fri, Sep 6, 2013 at 8:12 AM, Alexey Dokuchaev wrote: > > Hi there, > > > > I've been trying to cross-build an amd64 kernel on i386 host on recent > > -CURRENT for a while, and it fails like this: > > Not entirely sure but you

Re: AFFECTS: 10-CURRENT users with any port depending on converters/libiconv

On 09/06/13 19:52, Ricardo Campos Passanezi wrote: On Fri, Sep 06, 2013 at 10:45:42AM -0700, John-Mark Gurney wrote: See `config.log' for more details ===> Script "configure" failed unexpectedly. Please report the problem to c.petrik.s...@gmail.com [maintainer] and attach the "/usr/ports/p

Re: AFFECTS: 10-CURRENT users with any port depending on converters/libiconv

On Fri, 06 Sep 2013 17:33:09 +0200 Guido Falsi wrote: > On 09/06/13 17:32, O. Hartmann wrote: > > On Fri, 06 Sep 2013 11:35:35 +0400 > > Boris Samorodov wrote: > > > >> 06.09.2013 07:16, AN пишет: > >>> Hi: > >>> > >>> I am posting to both lists because this problem affects users of > >>> curren

Re: AFFECTS: 10-CURRENT users with any port depending on converters/libiconv

On Fri, Sep 06, 2013 at 10:45:42AM -0700, John-Mark Gurney wrote: > > See `config.log' for more details > > ===> Script "configure" failed unexpectedly. > > Please report the problem to c.petrik.s...@gmail.com [maintainer] and > > attach the "/usr/ports/print/cups-client/work/cups-1.5.4/confi

HEADS UP: No gcc by default in -HEAD on platforms where clang is cc

Hi Everyone, As of r255321, we are no longer building gcc or libstdc++ as part of the default install on platforms where clang is cc. If you are using gcc, you have two options: 1) Install one of the lang/gcc* ports (Warner has been working on separating out the patches to our GCC, so these sh

Re: clang+libc++ using missing powl

On 6 Sep 2013, at 16:59, Steve Kargl wrote: > Well, your commit has pre-empted any discussion on whether > there would have been a better kludge. Oh well. I'm very happy for it to be replaced by something better (and would be ecstatic for it to go away completely and for all of the functions t

Re: clang+libc++ using missing powl

On Fri, Sep 6, 2013 at 11:59 AM, Steve Kargl < s...@troutmask.apl.washington.edu> wrote: > On Fri, Sep 06, 2013 at 07:54:46AM +0100, David Chisnall wrote: > > > > On 5 Sep 2013, at 22:09, Steve Kargl > wrote: > > > > > On Thu, Sep 05, 2013 at 09:52:13AM +0100, David Chisnall wrote: > > >> On 4 Se

Re: AFFECTS: 10-CURRENT users with any port depending on converters/libiconv

On Fri, 06 Sep 2013 20:08:59 +0400 Boris Samorodov wrote: > 06.09.2013 19:44, O. Hartmann пишет: > > > Here we go. It is the config.log from one of the failing machines, > > failing in print/cups-client. > > Please, show the output of following commands (at the host in > question): # svn info /

Re: AFFECTS: 10-CURRENT users with any port depending on converters/libiconv

On Fri, 06 Sep 2013 21:11:26 +0400 Boris Samorodov wrote: > 06.09.2013 20:44, O. Hartmann пишет: > > On Fri, 06 Sep 2013 20:08:59 +0400 > > Boris Samorodov wrote: > > > >> 06.09.2013 19:44, O. Hartmann пишет: > >> > >>> Here we go. It is the config.log from one of the failing machines, > >>> fa

Re: AFFECTS: 10-CURRENT users with any port depending on converters/libiconv

07.09.2013 01:51, O. Hartmann пишет: > On Fri, 06 Sep 2013 21:11:26 +0400 > Boris Samorodov wrote: > >> 06.09.2013 20:44, O. Hartmann пишет: >>> On Fri, 06 Sep 2013 20:08:59 +0400 >>> Boris Samorodov wrote: >>> 06.09.2013 19:44, O. Hartmann пишет: > Here we go. It is the config.log

Re: New iSCSI stack.

On Fri, Sep 6, 2013 at 2:18 PM, Alfred Perlstein wrote: > On 9/5/13 3:27 AM, Edward Tomasz Napierała wrote: > >> Hello. At >> http://people.freebsd.org/~**trasz/cfiscsi-20130904.diffyou'll >> find >> a patch which adds the new iSCSI initi

Re: AFFECTS: 10-CURRENT users with any port depending on converters/libiconv

O. Hartmann wrote this message on Fri, Sep 06, 2013 at 17:32 +0200: > On Fri, 06 Sep 2013 11:35:35 +0400 > Boris Samorodov wrote: > > > 06.09.2013 07:16, AN ??: > > > Hi: > > > > > > I am posting to both lists because this problem affects users of > > > current and ports, and I didn't kn

Re: Cross-buildkernel (i386->amd64) is broken?

Alexey Dokuchaev wrote this message on Sat, Sep 07, 2013 at 00:29 +0700: > On Fri, Sep 06, 2013 at 10:08:20AM -0700, hiren panchasara wrote: > > On Fri, Sep 6, 2013 at 8:12 AM, Alexey Dokuchaev wrote: > > > Hi there, > > > > > > I've been trying to cross-build an amd64 kernel on i386 host on recen

Re: dirmngr won't link with liblber.so?

I filled a PR on this: Ports/181230. - Justin On Sep 6, 2013 12:23 PM, "Michael Butler" wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > On 09/06/13 15:17, Baptiste Daroussin wrote: > > On Fri, Sep 06, 2013 at 03:14:05PM -0400, Michael Butler wrote: > > What's up with this? I recompi

Re: New iSCSI stack.

On Fri, Sep 6, 2013 at 4:03 PM, Outback Dingo wrote: > > > > On Fri, Sep 6, 2013 at 2:18 PM, Alfred Perlstein wrote: > >> On 9/5/13 3:27 AM, Edward Tomasz Napierała wrote: >> >>> Hello. At >>> http://people.freebsd.org/~**trasz/cfiscsi-20130904.diff

Re: AFFECTS: 10-CURRENT users with any port depending on converters/libiconv

On 09/07/13 00:10, Boris Samorodov wrote: 07.09.2013 01:51, O. Hartmann пишет: On Fri, 06 Sep 2013 21:11:26 +0400 Boris Samorodov wrote: 06.09.2013 20:44, O. Hartmann пишет: On Fri, 06 Sep 2013 20:08:59 +0400 Boris Samorodov wrote: 06.09.2013 19:44, O. Hartmann пишет: Here we go. It is

Re: AFFECTS: 10-CURRENT users with any port depending on converters/libiconv

On Fri, Sep 06, 2013 at 11:51:32PM +0200, O. Hartmann wrote: > On Fri, 06 Sep 2013 21:11:26 +0400 > Boris Samorodov wrote: > > > 06.09.2013 20:44, O. Hartmann пишет: > > > On Fri, 06 Sep 2013 20:08:59 +0400 > > > Boris Samorodov wrote: > > > > > >> 06.09.2013 19:44, O. Hartmann пишет: > > >> >

Re: dirmngr won't link with liblber.so?

On Fri, Sep 06, 2013 at 03:14:05PM -0400, Michael Butler wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > What's up with this? I recompiled openldap-client; I can do a 'nm > liblber-2.4.so.8' without error but .. dirmngr won't link it? > > cc -I/usr/local/include -O2 -pipe -march=pent

dirmngr won't link with liblber.so?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 What's up with this? I recompiled openldap-client; I can do a 'nm liblber-2.4.so.8' without error but .. dirmngr won't link it? cc -I/usr/local/include -O2 -pipe -march=pentium4 -DLDAP_DEPRECATED - -fno-strict-aliasing -Wall -Wno-pointer-sign -L/usr/

Re: AFFECTS: 10-CURRENT users with any port depending on converters/libiconv

On Fri, 06 Sep 2013 17:31:48 +0200 Guido Falsi wrote: > On 09/06/13 17:26, AN wrote: > > > > > > On Fri, 6 Sep 2013, Guido Falsi wrote: > > > >> On 09/06/13 05:16, AN wrote: > >>> Hi: > >>> > >>> I am posting to both lists because this problem affects users of > >>> current and ports, and I didn'

Re: AFFECTS: 10-CURRENT users with any port depending on converters/libiconv

On Fri, 06 Sep 2013 17:35:27 +0200 Guido Falsi wrote: > On 09/06/13 17:04, O. Hartmann wrote: > > > Using portmaster, I'm higly adviced to use option -f, otherwise > > every second port I try to update gets interrupted due to missing > > libiconv.so.3. It is impossible to update a system unatten

Re: dirmngr won't link with liblber.so?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 09/06/13 15:17, Baptiste Daroussin wrote: > On Fri, Sep 06, 2013 at 03:14:05PM -0400, Michael Butler wrote: > What's up with this? I recompiled openldap-client; I can do a 'nm > liblber-2.4.so.8' without error but .. dirmngr won't link it? [ .. sn

Re: [RFC][CFT] GEOM direct dispatch and fine-grained CAM locking

On Fri, Sep 06, 2013 at 11:29:11AM +0300, Alexander Motin wrote: > On 06.09.2013 11:06, Jeremie Le Hen wrote: > > On Fri, Sep 06, 2013 at 12:46:27AM +0200, Olivier Cochard-Labbé wrote: > >> On Thu, Sep 5, 2013 at 11:38 PM, Alexander Motin wrote: > >>> I've found and fixed possible double request c

Re: AFFECTS: 10-CURRENT users with any port depending on converters/libiconv

On Fri, Sep 06, 2013 at 05:59:42PM +0200, O. Hartmann wrote: > On Fri, 06 Sep 2013 17:35:27 +0200 > Guido Falsi wrote: > > > On 09/06/13 17:04, O. Hartmann wrote: > > > > > Using portmaster, I'm higly adviced to use option -f, otherwise > > > every second port I try to update gets interrupted du

Re: clang+libc++ using missing powl

On Fri, Sep 06, 2013 at 03:02:18PM -0400, Mehmet Erol Sanliturk wrote: > On Fri, Sep 6, 2013 at 11:59 AM, Steve Kargl < > s...@troutmask.apl.washington.edu> wrote: > > > > PS: I have working erfl and erfcl for ld80 archs. I'm still > > testing and refining the code. It turns out that computing >

[head tinderbox] failure on armv6/arm

TB --- 2013-09-06 20:50:25 - tinderbox 2.10 running on freebsd-current.sentex.ca TB --- 2013-09-06 20:50:25 - FreeBSD freebsd-current.sentex.ca 8.3-PRERELEASE FreeBSD 8.3-PRERELEASE #0: Mon Mar 26 13:54:12 EDT 2012 d...@freebsd-current.sentex.ca:/usr/obj/usr/src/sys/GENERIC amd64 TB --- 2013

[head tinderbox] failure on arm/arm

TB --- 2013-09-06 20:50:25 - tinderbox 2.10 running on freebsd-current.sentex.ca TB --- 2013-09-06 20:50:25 - FreeBSD freebsd-current.sentex.ca 8.3-PRERELEASE FreeBSD 8.3-PRERELEASE #0: Mon Mar 26 13:54:12 EDT 2012 d...@freebsd-current.sentex.ca:/usr/obj/usr/src/sys/GENERIC amd64 TB --- 2013

Re: AFFECTS: 10-CURRENT users with any port depending on converters/libiconv

On 09/06/13 17:51, O. Hartmann wrote: On Fri, 06 Sep 2013 17:31:48 +0200 Guido Falsi wrote: On 09/06/13 17:26, AN wrote: On Fri, 6 Sep 2013, Guido Falsi wrote: On 09/06/13 05:16, AN wrote: Hi: I am posting to both lists because this problem affects users of current and ports, and I didn

Re: Cross-buildkernel (i386->amd64) is broken?

On Fri, Sep 6, 2013 at 8:12 AM, Alexey Dokuchaev wrote: > Hi there, > > I've been trying to cross-build an amd64 kernel on i386 host on recent > -CURRENT for a while, and it fails like this: > Not entirely sure but you _probably_ need to make toolchain first? cheers, Hiren > > $ cd /usr/src &

Interesting panic from the Yahoo builder (10-current)

Our "yBSD" builder needs to mount a disk image temporarily that has a dos partition (for openstack-ish things) to put configs into it. It seems that under high stress, we can squeeze a panic out of it in namei(). Sean Unread portion of the kernel message buffer: panic: namei: nameiop contaminat

Re: clang+libc++ using missing powl

On Fri, Sep 06, 2013 at 07:54:46AM +0100, David Chisnall wrote: > > On 5 Sep 2013, at 22:09, Steve Kargl > wrote: > > > On Thu, Sep 05, 2013 at 09:52:13AM +0100, David Chisnall wrote: > >> On 4 Sep 2013, at 23:38, Baptiste Daroussin wrote: > >> > >>> As a result we have a lot of fallouts of p

Re: New iSCSI stack.

On 9/5/13 3:27 AM, Edward Tomasz Napierała wrote: Hello. At http://people.freebsd.org/~trasz/cfiscsi-20130904.diff you'll find a patch which adds the new iSCSI initiator and target, against 10-CURRENT. To use the new initiator, start with "man iscsictl". For the target - "man ctld". All feedba

Re: AFFECTS: 10-CURRENT users with any port depending on converters/libiconv

06.09.2013 20:44, O. Hartmann пишет: > On Fri, 06 Sep 2013 20:08:59 +0400 > Boris Samorodov wrote: > >> 06.09.2013 19:44, O. Hartmann пишет: >> >>> Here we go. It is the config.log from one of the failing machines, >>> failing in print/cups-client. >> >> Please, show the output of following comma

Re: AFFECTS: 10-CURRENT users with any port depending on converters/libiconv

On 9/6/13 5:04 PM, "O. Hartmann" wrote: >On Fri, 06 Sep 2013 11:35:35 +0400 >Boris Samorodov wrote: > >> 06.09.2013 07:16, AN пишет: >> > Hi: >> > >> > I am posting to both lists because this problem affects users of >> > current and ports, and I didn't know which would be more >> > appropriate

Cross-buildkernel (i386->amd64) is broken?

Hi there, I've been trying to cross-build an amd64 kernel on i386 host on recent -CURRENT for a while, and it fails like this: $ cd /usr/src && make buildkernel TARGET=amd64 TARGET_ARCH=amd64 [...] In file included from /usr/src/sys/amd64/amd64/genassym.c:46: In file included from /usr/sr

Re: AFFECTS: 10-CURRENT users with any port depending on converters/libiconv

Am 07.09.2013 00:07, schrieb Baptiste Daroussin: > On Fri, Sep 06, 2013 at 11:51:32PM +0200, O. Hartmann wrote: >> On Fri, 06 Sep 2013 21:11:26 +0400 >> Boris Samorodov wrote: >> >>> 06.09.2013 20:44, O. Hartmann пишет: On Fri, 06 Sep 2013 20:08:59 +0400 Boris Samorodov wrote: