Re: svn commit: r297435 - head: still problems for stage 3 when gcc 4.2.1 is avoided (powerpc64 self-hosted build)

On Fri, Apr 1, 2016 at 2:25 AM, Dimitry Andric wrote: > On 01 Apr 2016, at 00:44, Warner Losh wrote: > > > >> On Mar 31, 2016, at 4:34 PM, Bryan Drewery > wrote: > >> I didn't realize the ports compiler was defaulting /usr/local/include

Re: accessing a PCIe register from userspace through kmem or other ways ?

On Friday, April 01, 2016 01:07:55 PM Luigi Rizzo wrote: > On Thu, Mar 31, 2016 at 11:55 PM, Ryan Stone wrote: > > > On Thu, Mar 31, 2016 at 4:39 PM, John Baldwin wrote: > > > >> On Wednesday, March 30, 2016 11:20:51 AM Jim Harris wrote: > >> > On Wed, Mar

Re: [FreeBSD-Announce] FreeBSD 2.2.9 Released!

Hi, At Nginx, we are committed to supporting a wide range of BSD-like operating systems and their releases. It's our great pleasure to report that it's now again possible to build current nginx sources with FreeBSD 2.2.9. We know that many highload setups still use this FreeBSD version. On

Re: accessing a PCIe register from userspace through kmem or other ways ?

On Fri, Apr 1, 2016 at 12:31 PM, John Baldwin wrote: > Sorry, I mapped PCIe registers to the PCI-e config space register set. I > am > not sure exactly how libpciaccess handles register access (perhaps it reads > raw bars and maps them via /dev/mem)? However, it would not be

Re: CURRENT slow and shaky network stability

Am Wed, 30 Mar 2016 00:28:39 -0700 (PDT) Don Lewis schrieb: > On 29 Mar, To: ohart...@zedat.fu-berlin.de wrote: > > On 28 Mar, Don Lewis wrote: > >> On 28 Mar, O. Hartmann wrote: > > > >> If I get a chance, I try booting my FreeBSD 11 machine with less RAM to > >>

Re: accessing a PCIe register from userspace through kmem or other ways ?

On Fri, Apr 01, 2016 at 12:48:24PM -0400, Ryan Stone wrote: > That is actually a really good question. I know that with some recent > BIOSes if I enabled allocating 64-bit addresses to BARs, the BAR would > actually be mapped outside of the range of /dev/mem. From a quick glance > at

Re: CURRENT slow and shaky network stability

Am Fri, 1 Apr 2016 13:37:14 -0700 (PDT) Don Lewis schrieb: > On 1 Apr, O. Hartmann wrote: > > Am Wed, 30 Mar 2016 00:28:39 -0700 (PDT) > > Don Lewis schrieb: > > >> Do you use tmpfs? Anything stored in there will get stashed in inactive > >>

Re: CURRENT slow and shaky network stability

On 1 Apr, O. Hartmann wrote: > Am Wed, 30 Mar 2016 00:28:39 -0700 (PDT) > Don Lewis schrieb: >> Do you use tmpfs? Anything stored in there will get stashed in inactive >> memory and/or swap. > [...] > > Yes, /var/run and /tmp are on tmpfs There is probably not enough

/usr/bin/make segmentation fault

Don't know how to debug this and cannot post the Makefile in question but it last worked in 8.4. In 11-CURRENT Var_Value appears to return NULL at /usr/src/contrib/bmake/compat.c:621 Var_Set(IMPSRC, Var_Value(TARGET, gn, ), pgn, 0); which passes the NULL to Var_Set as the second argument

Re: svn commit: r297435 - head: still problems for stage 3 when gcc 4.2.1 is avoided (powerpc64 self-hosted build)

On 01 Apr 2016, at 00:44, Warner Losh wrote: > >> On Mar 31, 2016, at 4:34 PM, Bryan Drewery wrote: >> I didn't realize the ports compiler was defaulting /usr/local/include >> into the search path now. It does not have /usr/local/lib in the >> default

Re: accessing a PCIe register from userspace through kmem or other ways ?

On Thu, Mar 31, 2016 at 11:55 PM, Ryan Stone wrote: > On Thu, Mar 31, 2016 at 4:39 PM, John Baldwin wrote: > >> On Wednesday, March 30, 2016 11:20:51 AM Jim Harris wrote: >> > On Wed, Mar 30, 2016 at 10:47 AM, Luigi Rizzo >> wrote: >> >

Re: 11.0 -r297369: _el_fn_sh_complete missing in buildworld; /usr/obj/. . ./lib/libedit/ has no filecomplete.*

On 3/29/16 6:35 PM, Mark Millard wrote: > Going from 11.0-CURRENT -r297048 to -r297369: buildworld after svnlite update: > /usr/obj/xtoolchain/powerpc.powerpc64/usr/src/. . . ends up with no > filecomplete.* > but the build tries to use what would be some of its contents > (_el_fn_sh_complete) >

Re: svn commit: r297435 - head: still problems for stage 3 when gcc 4.2.1 is avoided (powerpc64 self-hosted build)

[Just a top-post showing what powerpc64-xtoolchain-gcc/powerpc64-gcc has for the default include search places:] powerpc64-xtoolchain-gcc/powerpc64-gcc also looks in /usr/local/include before /usr/include : see below. > # portmaster --list-origins > . . . > devel/powerpc64-xtoolchain-gcc > . .