Re: /usr/sbin/cron and /usr/sbin/fifolog_{create, reader, writer} winds up in ${DESTDIR}/ during installworld, as of r275212

2014-11-28 Thread Baptiste Daroussin
On Fri, Nov 28, 2014 at 10:59:00PM +0100, Dimitry Andric wrote: > On 28 Nov 2014, at 22:54, Trond Endrestøl > wrote: > > > > Something's wrong in base/head when /usr/sbin/cron and > > /usr/sbin/fifolog_{create,reader,writer} winds up in ${DESTDIR}/ > > during installworld. > > > > Seen on amd64

Re: /usr/sbin/cron and /usr/sbin/fifolog_{create, reader, writer} winds up in ${DESTDIR}/ during installworld, as of r275212

2014-11-28 Thread Dimitry Andric
On 28 Nov 2014, at 22:54, Trond Endrestøl wrote: > > Something's wrong in base/head when /usr/sbin/cron and > /usr/sbin/fifolog_{create,reader,writer} winds up in ${DESTDIR}/ > during installworld. > > Seen on amd64 as of r275212, both with and without DESTDIR set. > > Is it a pilot error on m

Re: /usr/sbin/cron and /usr/sbin/fifolog_{create,reader,writer} winds up in ${DESTDIR}/ during installworld, as of r275212

2014-11-28 Thread Baptiste Daroussin
On Fri, Nov 28, 2014 at 10:54:07PM +0100, Trond Endrestøl wrote: > Something's wrong in base/head when /usr/sbin/cron and > /usr/sbin/fifolog_{create,reader,writer} winds up in ${DESTDIR}/ > during installworld. > > Seen on amd64 as of r275212, both with and without DESTDIR set. > > Is it a pil

/usr/sbin/cron and /usr/sbin/fifolog_{create,reader,writer} winds up in ${DESTDIR}/ during installworld, as of r275212

2014-11-28 Thread Trond Endrestøl
Something's wrong in base/head when /usr/sbin/cron and /usr/sbin/fifolog_{create,reader,writer} winds up in ${DESTDIR}/ during installworld. Seen on amd64 as of r275212, both with and without DESTDIR set. Is it a pilot error on my part? -- +---+

RFT: Please help testing the llvm/clang 3.5.0 import

2014-11-28 Thread Dimitry Andric
Hi, We're working on updating llvm, clang and lldb to 3.5.0 in head. This is quite a big update again, and any help with testing is appreciated. To try this out, ensure you have good backups or snapshots, then build world and kernel from the projects/clang350-import branch [1]. Please use a Sub

Re: Possible bug in softfloat

2014-11-28 Thread Adrian Chadd
You can easily fire up a mips32 / mips64 emulator build - cross-build a world+kernel, build an image, then run qemu-devel to boot it. https://wiki.freebsd.org/FreeBSD/MipsEmulation You should be able to get a 32 bit soft-float mips environment inside there which you can use to trigger it. (And al

Re: Possible bug in softfloat

2014-11-28 Thread Steve Kargl
On Fri, Nov 28, 2014 at 10:54:25AM -0800, Adrian Chadd wrote: > On 28 November 2014 at 10:34, Steve Kargl > wrote: > > In a thread on comp.lang.c, it was pointed out that softfloat > > has a bug and in checking src/lib/libc/softfloat I confimed > > the issue is present in FreeBSD. What I hae not

Re: Possible bug in softfloat

2014-11-28 Thread Adrian Chadd
On 28 November 2014 at 10:34, Steve Kargl wrote: > In a thread on comp.lang.c, it was pointed out that softfloat > has a bug and in checking src/lib/libc/softfloat I confimed > the issue is present in FreeBSD. What I hae not confirmed > is whether or not it is possible to hit this bug. In fact,

Possible bug in softfloat

2014-11-28 Thread Steve Kargl
In a thread on comp.lang.c, it was pointed out that softfloat has a bug and in checking src/lib/libc/softfloat I confimed the issue is present in FreeBSD. What I hae not confirmed is whether or not it is possible to hit this bug. In fact, it may only hit arm and mips. Anyway, here's the patch

Re: [CFR][PATCH] drm2: don't assume that dev->driver->max_ioctl > *dev->driver->compat_ioctls_nr

2014-11-28 Thread Konstantin Belousov
On Fri, Nov 28, 2014 at 04:29:42PM +0300, Eygene Ryabinkin wrote: > Konstantin, *, good day. > > I noticed that the current ioctl processing code for drm2 implicitely > assumes that the number of native ioctls is higher than that of 32-bit > compat ones, so it immediately gives EINVAL when > nr >=

Re: RFC: Remove pty(4)

2014-11-28 Thread Julian Elischer
On 11/28/14, 2:37 AM, Alfred Perlstein wrote: On Nov 27, 2014, at 1:52 AM, Konstantin Belousov wrote: On Wed, Nov 26, 2014 at 04:41:27PM -0800, Davide Italiano wrote: On Mon, Aug 25, 2014 at 12:37 PM, John Baldwin wrote: On Wednesday, August 20, 2014 11:00:14 AM Davide Italiano wrote: One o

witness and modules.

2014-11-28 Thread Julian Elischer
Do we need to compile all modules with witness definitions when linking with a kernel compiled with witness? This was true at one stage but I remember some work was done to make them compatible. ___ freebsd-current@freebsd.org mailing list http://li

[CFR][PATCH] drm2: don't assume that dev->driver->max_ioctl > *dev->driver->compat_ioctls_nr

2014-11-28 Thread Eygene Ryabinkin
Konstantin, *, good day. I noticed that the current ioctl processing code for drm2 implicitely assumes that the number of native ioctls is higher than that of 32-bit compat ones, so it immediately gives EINVAL when nr >= dev->driver->max_ioctl. Seems that in future such assumption may not be true