Date: Fri, 29 Oct 2010 22:16:20 +0000 From: "Philip M. Gollucci" <pgollucci@p6m7g8.com> To: Erwin Lansing <erwin@freebsd.org> Cc: perl@freebsd.org Subject: Re: [ports-i386@FreeBSD.org: p5-Coro-5.23_1,1 failed on i386 9] Message-ID: <4CCB47B4.9090000@p6m7g8.com> In-Reply-To: <20101029220930.GQ99336@droso.net> References: <20101029220930.GQ99336@droso.net>
next in thread | previous in thread | raw e-mail | index | archive | help
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 This is b/c of the underlying libev update. The committer missed the api/abi break. On 10/29/10 22:09, Erwin Lansing wrote: > > FYI; can you please investigate and/or report to the developers? If > you are already aware of this problem but do not yet have a fix, > please mark the port BROKEN in the appropriate case, so that users do > not unexpectedly encounter it. > > See http://pointyhat.freebsd.org for the full log. > > Thanks, > -erwin > > ----- Forwarded message from User Ports-i386 <ports-i386@FreeBSD.org> ----- > > Date: Fri, 29 Oct 2010 21:05:35 GMT > From: User Ports-i386 <ports-i386@FreeBSD.org> > To: erwin@FreeBSD.org, miwi@FreeBSD.org, itetcu@FreeBSD.org > Subject: p5-Coro-5.23_1,1 failed on i386 9 > > You can also find this build log at > > http://pointyhat.freebsd.org/errorlogs/i386-errorlogs/a.9.20101029175938/p5-Coro-5.23_1,1.log > > building p5-Coro-5.23_1,1 on gohan53.freebsd.org > in directory /x/tmp/9/20101029175938/chroot/260 > building for: 9.0-CURRENT i386 > maintained by: perl@FreeBSD.org > port directory: /usr/ports/devel/p5-Coro > Makefile ident: $FreeBSD: ports/devel/p5-Coro/Makefile,v 1.44 2010/09/24 00:44:19 pgollucci Exp $ > build started at Fri Oct 29 20:59:45 UTC 2010 > FETCH_DEPENDS= > PATCH_DEPENDS=perl-5.10.1_2.tbz > EXTRACT_DEPENDS=perl-5.10.1_2.tbz > BUILD_DEPENDS=p5-AnyEvent-5.271.tbz p5-AnyEvent-AIO-1.1.tbz p5-EV-4.00,1.tbz p5-Event-1.13.tbz p5-Guard-1.021.tbz p5-IO-AIO-3.65.tbz p5-common-sense-3.3.tbz perl-5.10.1_2.tbz > RUN_DEPENDS=p5-AnyEvent-5.271.tbz p5-AnyEvent-AIO-1.1.tbz p5-EV-4.00,1.tbz p5-Event-1.13.tbz p5-Guard-1.021.tbz p5-IO-AIO-3.65.tbz p5-common-sense-3.3.tbz perl-5.10.1_2.tbz > prefixes: LOCALBASE=usr/local > add_pkg > ================================================================ > ====================<phase 1: make checksum>==================== > ===> License check disabled, port has not defined LICENSE > => Coro-5.23.tar.gz doesn't seem to exist in /tmp/distfiles/. > => Attempting to fetch from ftp://ftp-master.freebsd.org/pub/FreeBSD/ports/distfiles/. > Coro-5.23.tar.gz 150 kB 182 kBps > => SHA256 Checksum OK for Coro-5.23.tar.gz. > ================================================================ > ====================<phase 2: make extract>==================== > add_pkg perl-5.10.1_2.tbz > adding dependencies > pkg_add perl-5.10.1_2.tbz > Removing stale symlinks from /usr/bin... > Skipping /usr/bin/perl > Skipping /usr/bin/perl5 > Done. > Creating various symlinks in /usr/bin... > Symlinking /usr/local/bin/perl5.10.1 to /usr/bin/perl > Symlinking /usr/local/bin/perl5.10.1 to /usr/bin/perl5 > Done. > Cleaning up /etc/make.conf... Done. > Spamming /etc/make.conf... Done. > Cleaning up /etc/manpath.config... Done. > Spamming /etc/manpath.config... Done. > ===> License check disabled, port has not defined LICENSE > ===> Extracting for p5-Coro-5.23_1,1 > => SHA256 Checksum OK for Coro-5.23.tar.gz. > ===> p5-Coro-5.23_1,1 depends on file: /usr/local/bin/perl5.10.1 - found > Deleting perl-5.10.1_2 > Removing stale symlinks from /usr/bin... > Removing /usr/bin/perl > Removing /usr/bin/perl5 > Done. > Cleaning up /etc/make.conf... Done. > Cleaning up /etc/manpath.config... Done. > ================================================================ > ====================<phase 3: make patch>==================== > add_pkg perl-5.10.1_2.tbz > adding dependencies > pkg_add perl-5.10.1_2.tbz > Removing stale symlinks from /usr/bin... > Skipping /usr/bin/perl > Skipping /usr/bin/perl5 > Done. > Creating various symlinks in /usr/bin... > Symlinking /usr/local/bin/perl5.10.1 to /usr/bin/perl > Symlinking /usr/local/bin/perl5.10.1 to /usr/bin/perl5 > Done. > Cleaning up /etc/make.conf... Done. > Spamming /etc/make.conf... Done. > Cleaning up /etc/manpath.config... Done. > Spamming /etc/manpath.config... Done. > ===> Patching for p5-Coro-5.23_1,1 > ===> p5-Coro-5.23_1,1 depends on file: /usr/local/bin/perl5.10.1 - found > ===> Applying FreeBSD patches for p5-Coro-5.23_1,1 > Deleting perl-5.10.1_2 > Removing stale symlinks from /usr/bin... > Removing /usr/bin/perl > Removing /usr/bin/perl5 > Done. > Cleaning up /etc/make.conf... Done. > Cleaning up /etc/manpath.config... Done. > ================================================================ > ====================<phase 4: make build>==================== > add_pkg p5-AnyEvent-5.271.tbz p5-AnyEvent-AIO-1.1.tbz p5-EV-4.00,1.tbz p5-Event-1.13.tbz p5-Guard-1.021.tbz p5-IO-AIO-3.65.tbz p5-common-sense-3.3.tbz perl-5.10.1_2.tbz > adding dependencies > pkg_add p5-AnyEvent-5.271.tbz > Removing stale symlinks from /usr/bin... > Skipping /usr/bin/perl > Skipping /usr/bin/perl5 > Done. > Creating various symlinks in /usr/bin... > Symlinking /usr/local/bin/perl5.10.1 to /usr/bin/perl > Symlinking /usr/local/bin/perl5.10.1 to /usr/bin/perl5 > Done. > Cleaning up /etc/make.conf... Done. > Spamming /etc/make.conf... Done. > Cleaning up /etc/manpath.config... Done. > Spamming /etc/manpath.config... Done. > pkg_add p5-AnyEvent-AIO-1.1.tbz > pkg_add p5-EV-4.00,1.tbz > pkg_add p5-Event-1.13.tbz > pkg_add p5-Guard-1.021.tbz > pkg_add p5-IO-AIO-3.65.tbz > pkg_add p5-common-sense-3.3.tbz > skipping p5-common-sense-3.3, already added > pkg_add perl-5.10.1_2.tbz > skipping perl-5.10.1_2, already added > ===> p5-Coro-5.23_1,1 depends on package: p5-Event>=1.08 - found > ===> p5-Coro-5.23_1,1 depends on package: p5-Guard>=0.5 - found > ===> p5-Coro-5.23_1,1 depends on package: p5-AnyEvent>=5.0 - found > ===> p5-Coro-5.23_1,1 depends on package: p5-AnyEvent-AIO>=1.0 - found > ===> p5-Coro-5.23_1,1 depends on package: p5-EV>=3.3 - found > ===> p5-Coro-5.23_1,1 depends on package: p5-common-sense>=0 - found > ===> p5-Coro-5.23_1,1 depends on package: p5-IO-AIO>=3.1 - found > ===> p5-Coro-5.23_1,1 depends on file: /usr/local/bin/perl5.10.1 - found > ===> p5-Coro-5.23_1,1 depends on file: /usr/local/bin/perl5.10.1 - found > ===> Configuring for p5-Coro-5.23_1,1 > *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** > > > Event version 1.13 found, building Event support. > > > EV version 4.00 found, building EV support. > > Checking if your kit is complete... > Looks good > > *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** > > Coro has a number of configuration options. Due to its maturity, the > defaults that Coro chooses are usually fine, so you can decide to skip > these questions. Only if something went wrong you should select 'n' > here and manually configure Coro, and, of course, report this to the > maintainer :) > > Skip further questions and use defaults (y/n)? [y] y > > *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** > > Coro can use a number of methods to implement coroutines at the C > level. The default chosen is based on your current confguration and is > correct in most cases, but you still can chose between these alternatives: > > u The unix 'ucontext.h' functions are relatively new and not implemented > or well-tested in older unices. They allow very fast coroutine creation > and reasonably fast switching. They are, however, usually slower than > the other alternatives due to an extra syscall done by swapcontext. And > while nominally most portable (it's the only POSIX-standardised > interface for coroutines), ucontext functions are, as usual, broken on > most/all BSDs. > > s If the ucontext functions are not working or you don't want > to use them for other reasons you can try a workaround using > setjmp/longjmp/sigaltstack (also standard unix functions). Coroutine > creation is rather slow, but switching is very fast (often much faster > than with the ucontext functions). Unfortunately, glibc-2.1 and > below don't even feature a working sigaltstack. You cannot use this > implementation if some other code uses SIGUSR2 or you plan to create > coroutines from an alternative signal stack, as both are being used for > coroutine creation. > > a Handcoded assembly. This is the fastest and most compatible method, > with the least side effects, if it works, that is. It has been tested > on GNU/Linux x86 and x86_64 systems and should work on all x86/x86_64 > systems using the SVR ELF ABI (it is also reported to be working on > Strawberry Perl for Windows using MinGW). This is the recommended > method on supported platforms. When it doesn't work, use another > method, such as (s)etjmp/longjmp. > > l GNU/Linux. Very old GNU/Linux systems (glibc-2.1 and below) need > this hack. Since it is very linux-specific it is also quite fast and > recommended even for newer versions; when it works, that is (currently > x86 and a few others only. If it compiles, it's usually ok). Newer > glibc versions (>= 2.5) stop working with this implementation however. > > i IRIX. For some reason, SGI really does not like to follow POSIX (does > that surprise you?), so this workaround might be needed (it's fast), > although [s] and [u] should also work now. > > w Microsoft Windows. Try this on Microsoft Windows when using Cygwin or > the MSVC compilers (e.g. ActiveState Perl, but see "a" for Strawberry > Perl), although, as there is no standard on how to do this under > windows, different environments might work differently. Doh. > > p Use pthread API. Try to avoid this option, it was only created to > make a point about the programming language shootout. It is unlikely > to work with perls that have windows process emulation enabled ("perl > threads"). It is also likely the slowest method of implementing > coroutines. It might work fine as a last resort, however, as the > pthread API is slightly better tested than ucontext functions for > example. Of course, not on BSDs, who usually have very broken pthread > implementations. > > Coro tries hard to come up with a suitable default for most systems, > so pressing return at the prompt usually does the right thing. If you > experience problems (e.g. make test fails) then you should experiment with > this setting. > > Use which implementation, > <s>etjmp, <u>ctx, <a>sm, <i>rix, <l>inux, <w>indows or <p>threads? [a] a > > Using handcoded assembler implementation > > > *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** > > Per-context stack size factor: Depending on your settings, Coro tries to > share the C stacks is creates as much as possible, but sometimes it needs > to allocate a new one. This setting controls the maximum size that gets > allocated, and should not be set too high, as memory and address space > still is wasted even if it's not fully used. The value entered will be > multiplied by sizeof(long), which is usually 4 on 32-bit systems, and 8 on > 64-bit systems. > > A setting of 16384 (the default) therefore corresponds to a 64k..128k > stack, which usually is ample space (you might even want to try 8192 or > lower if your program creates many coroutines). > > On systems supporting mmap and dynamic memory management, the actual > memory usually gets allocated on demand, but with many large stacks you > can still run out of address space on your typical 32 bit platform (not to > forget the pagetables). > > Some perls (mostly threaded ones and perl compiled under linux 2.6) and > some programs (inefficient regexes can use a lot of stack space) may > need much, much more: If Coro segfaults with weird backtraces (e.g. in a > function prologue) or in t/10_bugs.t, you might want to increase this to > 65536 or more. > > The default should be fine, and can be changed at runtime with > Coro::State::cctx_stacksize. > > C stack size factor? [16384] 16384 > using a stacksize of 16384 * sizeof(long) > > *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** > > Coro can optionally put a guard area before each stack segment: When the > stack is too small and the access is not too far outside the stack (i.e. > within the guard area), then the program will safely segfault instead of > running into other data. The cost is some additional overhead with is > usually negligible, and extra use of address space. > > The guard area size currently needs to be specified in pages (typical > pagesizes are 4k and 8k). The guard area is only enabled on a few > hardcoded architectures and is ignored on others. The actual preprocessor > expression disables this feature if: > > !__i386 && !__x86_64 && !__powerpc && !__m68k > && !__alpha && !__mips && !__sparc64 > > The default, as usual, should be just fine. > > Number of guard pages (0 disables)? [4] 4 > > *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** > > Coro can tell valgrind about its stacks and so reduce spurious warnings > where valgrind would otherwise complain about possible stack switches. > > Enabling this does not incur noticable runtime or memory overhead, but it > requires that you have the <valgrind/valgrind.h> header file available. > > Valgrind support is completely optional, so disabling it is the safe > choice. > > Enable valgrind support (y/n)? [n] n > > *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** > > Coro can use (or even trick) some perl functions into doing what it needs > instead of relying on (some) of its own functions. This might increase > chances that it compiles and works, but it could just as well result in > memory leaks, crashes or silent data corruption. It certainly does result > in slightly slower speed and higher memory consumption, though, so YOU > SHOULD ENABLE THIS OPTION ONLY AS A LAST RESORT. > > Prefer perl functions over coro functions (y/n)? [n] n > > *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** > > Coro has experimental support for cloning states. This can be used > to implement a scheme-like call/cc. However, this doesn't add to the > expressiveness in general, and is likely perl-version specific (and perl > 5.12 deliberately removed support for it). As such, it is disabled by > default. Enable it when you want to play around with it, but note that it > isn't supported, and unlikely ever will be. It exists mainly to prove that > it could be done - if only it were useful for something. > > Implement Coro::State->clone method (y/n)? [n] n > > *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** > > Writing Makefile for Coro::State > Writing Makefile for Coro::Event > Writing Makefile for Coro::EV > Writing Makefile for Coro > ===> Building for p5-Coro-5.23_1,1 > cp Coro/Select.pm blib/lib/Coro/Select.pm > cp Coro/State.pm blib/lib/Coro/State.pm > cp Coro/Debug.pm blib/lib/Coro/Debug.pm > cp Coro/RWLock.pm blib/lib/Coro/RWLock.pm > cp Coro/LWP.pm blib/lib/Coro/LWP.pm > cp Coro/Semaphore.pm blib/lib/Coro/Semaphore.pm > cp Coro/Timer.pm blib/lib/Coro/Timer.pm > cp Coro/CoroAPI.h blib/lib/Coro/CoroAPI.h > cp Coro.pm blib/lib/Coro.pm > cp Coro/Signal.pm blib/lib/Coro/Signal.pm > cp Coro/AnyEvent.pm blib/lib/Coro/AnyEvent.pm > cp Coro/BDB.pm blib/lib/Coro/BDB.pm > cp Coro/SemaphoreSet.pm blib/lib/Coro/SemaphoreSet.pm > cp Coro/Storable.pm blib/lib/Coro/Storable.pm > cp Coro/Util.pm blib/lib/Coro/Util.pm > cp Coro/AIO.pm blib/lib/Coro/AIO.pm > cp Coro/Handle.pm blib/lib/Coro/Handle.pm > cp Coro/Specific.pm blib/lib/Coro/Specific.pm > cp Coro/Socket.pm blib/lib/Coro/Socket.pm > cp Coro/Channel.pm blib/lib/Coro/Channel.pm > cp Coro/MakeMaker.pm blib/lib/Coro/MakeMaker.pm > Skip ../blib/lib/Coro/Channel.pm (unchanged) > Skip ../blib/lib/Coro/Util.pm (unchanged) > Skip ../blib/lib/Coro/Specific.pm (unchanged) > Skip ../blib/lib/Coro/BDB.pm (unchanged) > Skip ../blib/lib/Coro/AnyEvent.pm (unchanged) > Skip ../blib/lib/Coro/LWP.pm (unchanged) > Skip ../blib/lib/Coro/SemaphoreSet.pm (unchanged) > Skip ../blib/lib/Coro/MakeMaker.pm (unchanged) > Skip ../blib/lib/Coro/Semaphore.pm (unchanged) > Skip ../blib/lib/Coro/Timer.pm (unchanged) > Skip ../blib/lib/Coro/AIO.pm (unchanged) > Skip ../blib/lib/Coro/Debug.pm (unchanged) > Skip ../blib/lib/Coro/Socket.pm (unchanged) > Skip ../blib/lib/Coro/State.pm (unchanged) > Skip ../blib/lib/Coro/RWLock.pm (unchanged) > Skip ../blib/lib/Coro/Signal.pm (unchanged) > cp Intro.pod ../blib/lib/Coro/Intro.pod > Skip ../blib/lib/Coro/Handle.pm (unchanged) > Skip ../blib/lib/Coro/Storable.pm (unchanged) > Skip ../blib/lib/Coro/Select.pm (unchanged) > /usr/local/bin/perl5.10.1 /usr/local/lib/perl5/5.10.1/ExtUtils/xsubpp -typemap /usr/local/lib/perl5/5.10.1/ExtUtils/typemap -typemap typemap State.xs > State.xsc && mv State.xsc State.c > cc -c -DAPPLLIB_EXP="/usr/local/lib/perl5/5.10.1/BSDPAN" -DHAS_FPSETMASK -DHAS_FLOATINGPOINT_H -fno-strict-aliasing -pipe -fstack-protector -I/usr/local/include -O2 -pipe -fno-strict-aliasing -DVERSION=\"5.23\" -DXS_VERSION=\"5.23\" -DPIC -fPIC "-I/usr/local/lib/perl5/5.10.1/mach/CORE" -DHAVE_MMAP -DCORO_ASM -DCORO_STACKSIZE=16384 -DCORO_STACKGUARD=4 State.c > State.xs: In function 'boot_Coro__State': > State.xs:3458: warning: cast from pointer to integer of different size > Running Mkbootstrap for Coro::State () > chmod 644 State.bs > rm -f ../blib/arch/auto/Coro/State/State.so > cc -shared -L/usr/local/lib -fstack-protector State.o -o ../blib/arch/auto/Coro/State/State.so > chmod 755 ../blib/arch/auto/Coro/State/State.so > cp State.bs ../blib/arch/auto/Coro/State/State.bs > chmod 644 ../blib/arch/auto/Coro/State/State.bs > Manifying ../blib/man3/Coro::Util.3 > Manifying ../blib/man3/Coro::Channel.3 > Manifying ../blib/man3/Coro::Specific.3 > Manifying ../blib/man3/Coro::BDB.3 > Manifying ../blib/man3/Coro::LWP.3 > Manifying ../blib/man3/Coro::AnyEvent.3 > Manifying ../blib/man3/Coro::SemaphoreSet.3 > Manifying ../blib/man3/Coro::MakeMaker.3 > Manifying ../blib/man3/Coro::Semaphore.3 > Manifying ../blib/man3/Coro::Timer.3 > Manifying ../blib/man3/Coro::AIO.3 > Manifying ../blib/man3/Coro::Debug.3 > Manifying ../blib/man3/Coro::Socket.3 > Manifying ../blib/man3/Coro::State.3 > Manifying ../blib/man3/Coro::RWLock.3 > Manifying ../blib/man3/Coro::Signal.3 > Manifying ../blib/man3/Coro::Intro.3 > Manifying ../blib/man3/Coro::Handle.3 > Manifying ../blib/man3/Coro::Select.3 > Manifying ../blib/man3/Coro::Storable.3 > cp Event.pm ../blib/lib/Coro/Event.pm > /usr/local/bin/perl5.10.1 /usr/local/lib/perl5/5.10.1/ExtUtils/xsubpp -typemap /usr/local/lib/perl5/5.10.1/ExtUtils/typemap Event.xs > Event.xsc && mv Event.xsc Event.c > cc -c -I/usr/local/lib/perl5/site_perl/5.10.1/mach/Event -DAPPLLIB_EXP="/usr/local/lib/perl5/5.10.1/BSDPAN" -DHAS_FPSETMASK -DHAS_FLOATINGPOINT_H -fno-strict-aliasing -pipe -fstack-protector -I/usr/local/include -O2 -pipe -fno-strict-aliasing -DVERSION=\"5.23\" -DXS_VERSION=\"5.23\" -DPIC -fPIC "-I/usr/local/lib/perl5/5.10.1/mach/CORE" -DHAVE_EVENT=1 -DHAVE_EV=1 Event.c > Event.xs: In function 'boot_Coro__Event': > Event.xs:82: warning: cast to pointer from integer of different size > Event.xs:83: warning: cast to pointer from integer of different size > Running Mkbootstrap for Coro::Event () > chmod 644 Event.bs > rm -f ../blib/arch/auto/Coro/Event/Event.so > cc -shared -L/usr/local/lib -fstack-protector Event.o -o ../blib/arch/auto/Coro/Event/Event.so > chmod 755 ../blib/arch/auto/Coro/Event/Event.so > cp Event.bs ../blib/arch/auto/Coro/Event/Event.bs > chmod 644 ../blib/arch/auto/Coro/Event/Event.bs > Manifying ../blib/man3/Coro::Event.3 > cp EV.pm ../blib/lib/Coro/EV.pm > /usr/local/bin/perl5.10.1 /usr/local/lib/perl5/5.10.1/ExtUtils/xsubpp -typemap /usr/local/lib/perl5/5.10.1/ExtUtils/typemap EV.xs > EV.xsc && mv EV.xsc EV.c > cc -c -I/usr/local/lib/perl5/site_perl/5.10.1/mach/EV -I/usr/local/lib/perl5/site_perl/5.10.1/mach -DAPPLLIB_EXP="/usr/local/lib/perl5/5.10.1/BSDPAN" -DHAS_FPSETMASK -DHAS_FLOATINGPOINT_H -fno-strict-aliasing -pipe -fstack-protector -I/usr/local/include -O2 -pipe -fno-strict-aliasing -DVERSION=\"5.23\" -DXS_VERSION=\"5.23\" -DPIC -fPIC "-I/usr/local/lib/perl5/5.10.1/mach/CORE" -DHAVE_EVENT=1 -DHAVE_EV=1 EV.c > EV.xs: In function 'XS_Coro__EV__loop_oneshot': > EV.xs:327: error: 'EVLOOP_ONESHOT' undeclared (first use in this function) > EV.xs:327: error: (Each undeclared identifier is reported only once > EV.xs:327: error: for each function it appears in.) > EV.xs: In function 'boot_Coro__EV': > EV.xs:287: warning: cast to pointer from integer of different size > EV.xs:288: warning: cast to pointer from integer of different size > *** Error code 1 > > Stop in /work/a/ports/devel/p5-Coro/work/Coro-5.23/EV. > *** Error code 1 > > Stop in /work/a/ports/devel/p5-Coro/work/Coro-5.23. > *** Error code 1 > > Stop in /a/ports/devel/p5-Coro. > ================================================================ > build of /usr/ports/devel/p5-Coro ended at Fri Oct 29 21:05:29 UTC 2010 > > !DSPAM:4ccb3732230291675514410! > > > ----- End forwarded message ----- - -- - ------------------------------------------------------------------------ 1024D/DB9B8C1C B90B FBC3 A3A1 C71A 8E70 3F8C 75B8 8FFB DB9B 8C1C Philip M. Gollucci (pgollucci@p6m7g8.com) c: 703.336.9354 VP Apache Infrastructure; Member, Apache Software Foundation Committer, FreeBSD Foundation Consultant, P6M7G8 Inc. Sr. System Admin, Ridecharge Inc. Work like you don't need the money, love like you'll never get hurt, and dance like nobody's watching. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.16 (FreeBSD) iD8DBQFMy0ezdbiP+9ubjBwRAr1eAJ4jd5wxjTFr1EfMah0VKGseWwOJ3ACfcmX4 oZLVoqb1FHlSd3NooVZKORQ= =4oOW -----END PGP SIGNATURE-----
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4CCB47B4.9090000>