daily CVS update output

2014-03-02 Thread NetBSD source update
Updating src tree: P src/crypto/external/bsd/openssl/lib/libcrypto/modes.inc P src/crypto/external/bsd/openssl/lib/libcrypto/sha.inc U src/crypto/external/bsd/openssl/lib/libcrypto/arch/sparc/Makefile U src/crypto/external/bsd/openssl/lib/libcrypto/arch/sparc/aes-sparcv9.S U src/crypto/external/bs

Re: Build broken with new gcc 4.8.3.

2014-03-02 Thread Christos Zoulas
On Mar 2, 3:54pm, t...@panix.com (Thor Lancelot Simon) wrote: -- Subject: Re: Build broken with new gcc 4.8.3. | On Sun, Mar 02, 2014 at 03:36:57PM -0500, Christos Zoulas wrote: | > | > Anything you compile with -g will now need -gdwarf-2 if you are using | > ctf{convert,merge} on them because o

Re: Build broken with new gcc 4.8.3.

2014-03-02 Thread Christos Zoulas
On Mar 2, 9:53pm, mar...@duskware.de (Martin Husemann) wrote: -- Subject: Re: Build broken with new gcc 4.8.3. | My main point is: | | - don't punish the non-dtrace users for the stupid ctf* tools. | - this is not a generic build breaking problem, as the default build |will neither use ctf

Re: Build broken with new gcc 4.8.3.

2014-03-02 Thread Thor Lancelot Simon
On Sun, Mar 02, 2014 at 03:36:57PM -0500, Christos Zoulas wrote: > > Anything you compile with -g will now need -gdwarf-2 if you are using > ctf{convert,merge} on them because our libdwarf understands dwarf-2, > partially dwarf-3 and no dwarf-4 which is the default for gcc-4.8. This looks relevan

Re: Build broken with new gcc 4.8.3.

2014-03-02 Thread Martin Husemann
My main point is: - don't punish the non-dtrace users for the stupid ctf* tools. - this is not a generic build breaking problem, as the default build will neither use ctf* nor -g (unless erroneously, see toolchain/48627) Martin

Re: Build broken with new gcc 4.8.3.

2014-03-02 Thread Christos Zoulas
On Mar 2, 9:08pm, mar...@duskware.de (Martin Husemann) wrote: -- Subject: Re: Build broken with new gcc 4.8.3. | On Sun, Mar 02, 2014 at 04:16:47PM +, Christos Zoulas wrote: | > Yes, we should probably add -gdwarf-2; Even dwarf-3 does not work properly. | | What exactly is affected? Standard

Re: Build broken with new gcc 4.8.3.

2014-03-02 Thread Martin Husemann
On Sun, Mar 02, 2014 at 04:16:47PM +, Christos Zoulas wrote: > Yes, we should probably add -gdwarf-2; Even dwarf-3 does not work properly. What exactly is affected? Standard builds (even with HAVE_GCC=48) are not (I just did one on amd64). Fixing broken tools would be preferable, otherwise at

Re: Build broken with new gcc 4.8.3.

2014-03-02 Thread Christos Zoulas
In article <5312f3af.7000...@t-online.de>, henning petersen wrote: > >/usr/netbsd/tools.amd64/bin/x86_64--netbsd-gcc -O2 >-I/usr/src/external/cddl/osnet/sys >-I/usr/src/external/cddl/osnet/include >-I/usr/src/external/cddl/osnet/dist -I/usr/src/external/cddl/osnet/dist > -I/usr/src/external/cddl

Build broken with new gcc 4.8.3.

2014-03-02 Thread henning petersen
/usr/netbsd/tools.amd64/bin/x86_64--netbsd-gcc -O2 -I/usr/src/external/cddl/osnet/sys -I/usr/src/external/cddl/osnet/include -I/usr/src/external/cddl/osnet/dist -I/usr/src/external/cddl/osnet/dist -I/usr/src/external/cddl/osnet/dist/head -I/usr/src/external/cddl/osnet/dist/tools/ctf/common -I/us

Re: Contradiction in man page for cut(1) ??

2014-03-02 Thread David Laight
On Sat, Mar 01, 2014 at 08:41:43PM -0800, Paul Goyette wrote: > Currently, the man page for cut(1) says > > list is a comma or whitespace separated set of increasing > numbers and/or number ranges.Numbers and number ranges > may be repeated, overlapping, and in any order. >