Current r244916M fails to compile a world with following error:
[...]
cc -O2 -pipe -O3 -march=native
-I/usr/src/contrib/ofed/usr.bin/opensm/../../include/infiniband
-I/usr/src/contrib/ofed/usr.bin/opensm/../../management/opensm/include/
-pthread -DVENDOR_RMPP_SUPPORT -DDUAL_SIDED_RMPP
On Wed, Jan 2, 2013 at 1:21 AM, O. Hartmann ohart...@zedat.fu-berlin.de wrote:
Current r244916M fails to compile a world with following error:
http://www.freebsd.org/cgi/query-pr.cgi?pr=bin/174214 -- not sure
why it hasn't already been committed.
HTH,
-Garrett
On Mon, Dec 31, 2012 at 12:17:27PM +0200, Alexander Motin wrote:
On 31.12.2012 08:17, Luigi Rizzo wrote:
On Sun, Dec 30, 2012 at 04:13:43PM -0700, Ian Lepore wrote:
...
Then I noticed you had a 12_26 patchset so I tested
that (after crudely fixing a couple uninitialized var warnings), and it
On 02.01.2013 12:57, Luigi Rizzo wrote:
On Mon, Dec 31, 2012 at 12:17:27PM +0200, Alexander Motin wrote:
On 31.12.2012 08:17, Luigi Rizzo wrote:
On Sun, Dec 30, 2012 at 04:13:43PM -0700, Ian Lepore wrote:
...
Then I noticed you had a 12_26 patchset so I tested
that (after crudely fixing a
I'd be interested in the general policy on LINKS vs. SYMLINKS
between directories that might end up on different file systems.
There seems to be an assumption that system directories in /usr
(e.g. /usr/bin, /usr/sbin, /usr/libexec) are on the same file
system, but I do not think that this
On Wed, Jan 02, 2013 at 01:24:26PM +0200, Alexander Motin wrote:
On 02.01.2013 12:57, Luigi Rizzo wrote:
...
i am not sure what you mean by extending interval, but i believe the
logic should be the following:
- say user requests a timeout after X seconds and with a tolerance of D
second
02.01.2013 14:28 пользователь Luigi Rizzo ri...@iet.unipi.it написал:
On Wed, Jan 02, 2013 at 01:24:26PM +0200, Alexander Motin wrote:
On 02.01.2013 12:57, Luigi Rizzo wrote:
...
i am not sure what you mean by extending interval, but i believe the
logic should be the following:
- say
On 01/02/13 07:04, Stefan Esser wrote:
I'd be interested in the general policy on LINKS vs. SYMLINKS
between directories that might end up on different file systems.
There seems to be an assumption that system directories in /usr
(e.g. /usr/bin, /usr/sbin, /usr/libexec) are on the same file
On Sun, Dec 30, 2012 at 11:17:10PM +0100, Dimitry Andric wrote:
I have been playing with Stefan's testcase for a while now, and while I
can reproduce the crashes, I am still at a loss about the cause. It
does seem to have something to do with throwing exceptions, but I am
still not sure
On Wed, 2013-01-02 at 15:11 +0200, Alexander Motin wrote:
02.01.2013 14:28 пользователь Luigi Rizzo ri...@iet.unipi.it написал:
On Wed, Jan 02, 2013 at 01:24:26PM +0200, Alexander Motin wrote:
On 02.01.2013 12:57, Luigi Rizzo wrote:
First of all, if you know that there is already a
On 2 January 2013 14:04, Alexander Yerenkow yeren...@gmail.com wrote:
Hello there and please excuse my harshness.
I just installed 9.1, and I tried to set up poudriere with 9/stable.
It took a lot of time compiling kernel and world, and after this it all
failed with message about missing
2013/1/2 Chris Rees cr...@freebsd.org
On 2 January 2013 14:04, Alexander Yerenkow yeren...@gmail.com wrote:
Hello there and please excuse my harshness.
I just installed 9.1, and I tried to set up poudriere with 9/stable.
It took a lot of time compiling kernel and world, and after this it
On Wed, Jan 02, 2013 at 03:11:05PM +0200, Alexander Motin wrote:
...
First of all, if you know that there is already a hardclock/statclock/*
scheduled in [T_X, T_X+D] you just reuse that. This particular bullet
was no event scheduled in [T_X, T_X+D] so you need to generate
a new one.
(While this may not be a strictly CURRENT issue, I asked on questions@,
but have not found a solution.)
Situation:
One of my boxes failed, and for various reasons it became easier to
just scrub and rebuild it. Like its predecessor it will run CURRENT
1) Using BSDinstall, I
My recent upgrading experience led to the installkernel portion of 'make
kernel' failing on the lack of an auditdistd user, for which 'mergemaster
-p' was ample workaround. However, the instructions for to rebuild
everything in UPDATING still have 'mergemaster -p' before installworld
and
On Wed, Jan 02, 2013 at 05:22:06PM +0100, Luigi Rizzo wrote:
On Wed, Jan 02, 2013 at 03:11:05PM +0200, Alexander Motin wrote:
...
First of all, if you know that there is already a hardclock/statclock/*
scheduled in [T_X, T_X+D] you just reuse that. This particular bullet
was no event
On Wed, 2 Jan 2013, Robert Huff wrote:
(While this may not be a strictly CURRENT issue, I asked on
questions@, but have not found a solution.)
Situation:
One of my boxes failed, and for various reasons it became easier to
just scrub and rebuild it. Like its predecessor it will run
.. I'm pretty damned sure we're going to need to enforce a never
earlier than X latency.
Is there a more detailed writeup of calloutng somewhere, besides
David's slides? The wiki page is rather empty.
Eg - I think this work does coalesce wakeups, right? Or it can? So
when in low-power scenarios
On 1/2/2013 12:10 PM, Benjamin Kaduk wrote:
My recent upgrading experience led to the installkernel portion of 'make
kernel' failing on the lack of an auditdistd user, for which
'mergemaster -p' was ample workaround. However, the instructions for
to rebuild everything in UPDATING still have
On Tue, Jan 01, 2013 at 12:42:47PM -0800, Manfred Antar wrote:
M OK
M I tracked it down to revision 244678
M 244677 works
M the files involved are:
M (src)5012}svn up -r 244678
M Updating '.':
M Usys/netinet/in.c
M Usys/netinet6/in6.c
M Updated to revision 244678
M
M It seems like the ip6
On 1/2/2013 1:57 PM, Benjamin Kaduk wrote:
On Wed, 2 Jan 2013, Robert Huff wrote:
For a full clean install, I believe that bsdinstall should prompt about
installing bootcode around here. I don't really understand from your
procedure how bsdinstall was used; there might be some edge case
On Tue, 1 Jan 2013 10:55:58 -0800
Tim Kientzle kient...@freebsd.org wrote:
On Jan 1, 2013, at 8:12 AM, Brett Wynkoop wrote:
Greeting-
The driver is working much better than the driver currently in
head. I have maintained an ssh connection to the BeagleBone for
more than 24 hours!
On 02.01.2013 19:09, Konstantin Belousov wrote:
On Wed, Jan 02, 2013 at 05:22:06PM +0100, Luigi Rizzo wrote:
Probably one way to close this discussion would be to provide
a sysctl so the sysadmin can decide which point in the interval
to pick when there is no suitable callout already scheduled.
On 2 January 2013 08:59, Stefan Farfeleder stef...@freebsd.org wrote:
On Sun, Dec 30, 2012 at 11:17:10PM +0100, Dimitry Andric wrote:
I have been playing with Stefan's testcase for a while now, and while I
can reproduce the crashes, I am still at a loss about the cause. It
does seem to have
On 02.01.2013 18:08, Adrian Chadd wrote:
.. I'm pretty damned sure we're going to need to enforce a never
earlier than X latency.
Do you mean here that we should never wake up before specified time
(just as specified by the most of existing APIs), or that we should not
allow sleep shorter
Ok, so this is my failure. :( Sorry. I will look at it as soon as
I get to decent internet connection. Right now I am on very bad GPRS.
Can you please show your rc.conf (the network related part)?
--
Totus tuus, Glebius.
Here you go:
/etc/hosts:
::1 localhost
TB --- 2013-01-03 00:12:40 - tinderbox 2.10 running on freebsd-current.sentex.ca
TB --- 2013-01-03 00:12:40 - 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 ---
Hello,
I have a similar problem if ifconfig_lo0 line is exist in /etc/rc.conf.
Can you remove lo0 configure line from /etc/rc.conf.
/etc/rc.conf:
ifconfig_lo0=inet 127.0.0.1 # default loopback device
configuration.
--
vi...@elam.kais.kyoto-u.ac.jp
At 07:09 PM 1/2/2013, KAHO Toshikazu wrote:
Hello,
I have a similar problem if ifconfig_lo0 line is exist in /etc/rc.conf.
Can you remove lo0 configure line from /etc/rc.conf.
/etc/rc.conf:
ifconfig_lo0=inet 127.0.0.1 # default loopback device
configuration.
Ok
I commented out
On Wed, Jan 2, 2013 at 2:06 PM, Alexander Motin m...@freebsd.org wrote:
On 02.01.2013 18:08, Adrian Chadd wrote:
.. I'm pretty damned sure we're going to need to enforce a never
earlier than X latency.
Do you mean here that we should never wake up before specified time (just as
specified
30 matches
Mail list logo
