TB --- 2010-06-19 06:10:00 - tinderbox 2.6 running on freebsd-current.sentex.ca
TB --- 2010-06-19 06:10:00 - starting HEAD tinderbox run for arm/arm
TB --- 2010-06-19 06:10:00 - cleaning the object tree
TB --- 2010-06-19 06:10:14 - cvsupping the source tree
TB --- 2010-06-19 06:10:14 - /usr/bin/csu
Hello, Lawrence.
You wrote 19 июня 2010 г., 07:27:30:
> Amount of feedback received thus far: nichts, nil, nada
I wanted to help you, but here is one problem: I dont have any
traffic-loaded 9-CURRENT machines. I have some not-so-critical 7.x and
8.x machines with noticeable traffic (f
Amount of feedback received thus far: nichts, nil, nada
*sings "I'm so ronery" in his best Kim Jong-il voice* [4]
Just like Uncle Sam [5], Uncle Lawrence needs you too - yes, I'm
pointing at YOU!
More specifically, people out there running current with 10-15 mins to
spare for some testing, p
On Jun 18, 2010, at 9:11 AM, Alexander Best muenster.de> wrote:
On Mon, Jun 7, 2010 at 3:57 PM, John Baldwin wrote:
On Saturday 05 June 2010 2:54:15 pm Jille Timmermans wrote:
Scott Long schreef:
On Jun 4, 2010, at 4:35 PM, Alexander Best wrote:
hi there. running HEAD, amd64 and r208806 i
Im using the Samsung F3 disks, which can do 140MB/s sequentially. I have
tried different raids raid0 will do just as bad as raid5. I even tried
one disk which performed as expected 100MB/s+ reads and writes so I'm
not sure anymore what could be the problem. Maybe the controller hates
samsung di
On 18 June 2010 10:08, oizs wrote:
> I've seen people with the same configuration doing 160MB/s writes and
> 250MB/s+ reads with raid5 so I still think something isn't right. And using
> raid10 with 4 disks is a rather large waste of capacity.
>
> -zsozso
>
>
> On 2010.06.18. 1:55, Chuck Swiger w
On Jun 18, 2010, at 2:08 AM, oizs wrote:
> I've seen people with the same configuration doing 160MB/s writes and
> 250MB/s+ reads with raid5 so I still think something isn't right.
How is that being measured?
> And using raid10 with 4 disks is a rather large waste of capacity.
If you value perf
In message <201006181955.o5ijtcvy095...@hergotha.csail.mit.edu>, Garrett Wollma
n writes:
>In general, the addition of "const" to C in 1989 was a bit of a botch: [...]
>That's water under the bridge now, of course.
Does that sentiment mean that it will not be fixed it in C1X ?
--
Poul-Henning
On 06/18/10 11:20, Alex Dupre wrote:
Update: the signer plugin (that requires libassuan) will be removed in
opensc 0.12 release.
Thanks for this update, and thanks to Dima too for clarifying the kdepim
situation. I'm not just making changes willy-nilly. :)
Doug
--
... and that's j
In article <86bpba7nc1@ds4.des.no>, d...@des.no writes:
>This means you can't, say, read data from a file into a buffer and then
>pass that buffer to iconv, because the buffer is not const (otherwise
>you couldn't have read data into it). That seems like a pretty
>fundamental flaw.
But it's
TB --- 2010-06-18 18:54:21 - tinderbox 2.6 running on freebsd-current.sentex.ca
TB --- 2010-06-18 18:54:21 - starting HEAD tinderbox run for sparc64/sun4v
TB --- 2010-06-18 18:54:21 - cleaning the object tree
TB --- 2010-06-18 18:54:32 - cvsupping the source tree
TB --- 2010-06-18 18:54:32 - /usr/b
TB --- 2010-06-18 18:34:08 - tinderbox 2.6 running on freebsd-current.sentex.ca
TB --- 2010-06-18 18:34:08 - starting HEAD tinderbox run for sparc64/sparc64
TB --- 2010-06-18 18:34:08 - cleaning the object tree
TB --- 2010-06-18 18:34:20 - cvsupping the source tree
TB --- 2010-06-18 18:34:20 - /usr
Alexander Best writes:
> indeed it worked. :) thanks a bunch. however it seems that CC/CXX/CPP
> have to be set in make.conf. setting them in src.conf breaks
> buildworld.
Yes, I noticed - you can't set CFLAGS in src.conf either. I don't know
why.
> maybe this should go into src.conf(5)?
I'll
TB --- 2010-06-18 18:10:06 - tinderbox 2.6 running on freebsd-current.sentex.ca
TB --- 2010-06-18 18:10:06 - starting HEAD tinderbox run for powerpc/powerpc
TB --- 2010-06-18 18:10:06 - cleaning the object tree
TB --- 2010-06-18 18:10:18 - cvsupping the source tree
TB --- 2010-06-18 18:10:18 - /usr
Kevin Oberman ha scritto:
5. opensc ale@ has indicated that he would prefer to wait to update his
port until a new version that supports assuan 2.0.0 is released.
Update: the signer plugin (that requires libassuan) will be removed in
opensc 0.12 release.
OK. I see dirmgr and gnupg are
TB --- 2010-06-18 16:28:53 - tinderbox 2.6 running on freebsd-current.sentex.ca
TB --- 2010-06-18 16:28:53 - starting HEAD tinderbox run for ia64/ia64
TB --- 2010-06-18 16:28:53 - cleaning the object tree
TB --- 2010-06-18 16:29:06 - cvsupping the source tree
TB --- 2010-06-18 16:29:06 - /usr/bin/c
> Date: Thu, 17 Jun 2010 14:56:35 -0700
> From: Doug Barton
>
> [ FYI, this message should have gone to freebsd-po...@freebsd.org ... ]
>
> On 06/17/10 11:20, Kevin Oberman wrote:
> > 2.0.0 should be the preferred version, but its API is incompatible with
> > the old one. Many ports using libass
on 18/06/2010 18:18 m...@freebsd.org said the following:
> On Fri, Jun 18, 2010 at 8:11 AM, Alexander Best
> wrote:
>> On Mon, Jun 7, 2010 at 3:57 PM, John Baldwin wrote:
>>> It can happen because the print buffer size thing is not line-buffered, it
>>> is
>>> printf-invocation buffered.
>> hmmm
On Fri, Jun 18, 2010 at 8:11 AM, Alexander Best
wrote:
> On Mon, Jun 7, 2010 at 3:57 PM, John Baldwin wrote:
>> It can happen because the print buffer size thing is not line-buffered, it is
>> printf-invocation buffered.
>
> hmmm...can this somehow be fixed? i'm not sure this is specific to
> scs
On Mon, Jun 7, 2010 at 3:57 PM, John Baldwin wrote:
> On Saturday 05 June 2010 2:54:15 pm Jille Timmermans wrote:
>> Scott Long schreef:
>> > On Jun 4, 2010, at 4:35 PM, Alexander Best wrote:
>> >
>> >> hi there. running HEAD, amd64 and r208806 i get this dmesg output
>> >> which doesn't look righ
2010/6/15 Dag-Erling Smørgrav :
> Alexander Best writes:
>> Dag-Erling Smørgrav writes:
>> > The problem is that "/usr/src/" is not a prefix of "/usr/src".
>> ah i see. would something like
>>
>> empty(.CURDIR:M/usr/src*) instead of empty(.aCURDIR:M/usr/src/*) work?
>
> I think so. My hypothesis
On Thu, Jun 17, 2010 at 9:43 PM, Gabor Kovesdan wrote:
>
>> ok. after installing world i get this when bootingt up:
>>
>> Starting powerd.
>> Starting musicpd.
>> path: invalid filesystem charset: ISO-8859-15
>> /usr/lib/i18n/libiconv_std.so.4: unsupported file
>> layout/usr/lib/i18n/libiconv_std.
AK-san,
PseudoCylon wrote:
> - Original Message
>
>>> From: Ganbold
>>> To: PseudoCylon
>>> Cc: freebsd-current@freebsd.org; Ganbold Tsagaankhuu
>>> Sent: Wed, June 16, 2010 6:33:47 AM
>>> Subject: Re: CALL for TEST [HOSTAP] run(4) ralink usb wireless
>>>
>>> AK-san,
>>>
>> P
On 06/18/2010 04:50, Anton Shterenlikht wrote:
>
> sorry, I probably didn't get you.
>
> I tried
>
> make -DALWAYS_CHECK_MAKE buildworld
>
> and got the same erorr.
>
> What do you mean by "updating your headers"?
cd /usr/src/include && make obj && make depend && make all && make instal
On 18 Jun 2010, at 12:40, Kostik Belousov wrote:
> On Fri, Jun 18, 2010 at 04:26:19AM +, FreeBSD Tinderbox wrote:
>> TB --- 2010-06-18 03:09:26 - tinderbox 2.6 running on
>> freebsd-current.sentex.ca
>> TB --- 2010-06-18 03:09:26 - starting HEAD tinderbox run for sparc64/sparc64
>> TB --- 20
On Friday 18 June 2010 18:46:49 Jan Henrik Sylvester wrote:
> On 01/-10/-28163 20:59, Doug Barton wrote:
> > 3. kdepim4 My understanding is that the version currently under
> > development has support for libassuan 2.0.0, and will be released in
> > August. The kde@ folks have indicated that if the
On Fri, Jun 18, 2010 at 04:26:19AM +, FreeBSD Tinderbox wrote:
> TB --- 2010-06-18 03:09:26 - tinderbox 2.6 running on
> freebsd-current.sentex.ca
> TB --- 2010-06-18 03:09:26 - starting HEAD tinderbox run for sparc64/sparc64
> TB --- 2010-06-18 03:09:26 - cleaning the object tree
> TB --- 201
On 01/-10/-28163 20:59, Doug Barton wrote:
3. kdepim4 My understanding is that the version currently under
development has support for libassuan 2.0.0, and will be released in
August. The kde@ folks have indicated that if there is a need to update
it sooner they can most likely do that based on p
I've seen people with the same configuration doing 160MB/s writes and
250MB/s+ reads with raid5 so I still think something isn't right. And
using raid10 with 4 disks is a rather large waste of capacity.
-zsozso
On 2010.06.18. 1:55, Chuck Swiger wrote:
On Jun 17, 2010, at 4:50 PM, oizs wrote:
On Thu, Jun 17, 2010 at 08:13:46AM -0400, jhell wrote:
> On 06/17/2010 06:15, Anton Shterenlikht wrote:
> > I've r209203 kernel on ia64 box.
> > Now I'm trying to rebuild world to r209240.
> > I get these errors.
> >
> > Please advise
> >
>
> grep -rn lzma_physmem /usr/include ?
> /usr/include/l
30 matches
Mail list logo
