> On 2012-12-17 (Monday) 17:02:06 Chris H wrote:
>> > On 12/17/2012 1:35 AM, Chris H wrote:
>> >>> hi all,
>> >>>
>> >>> I run FreeBSD 9.0-STABLE #1: Sun Apr 15 21:08:51 UTC 2012 amd64
>> >>>
>> >>> yesterday I have cvsup-ed src and was trying to buildkernel
>> >>> bellow is error I receive:
>> >>
On 2012-12-17 (Monday) 17:02:06 Chris H wrote:
> > On 12/17/2012 1:35 AM, Chris H wrote:
> >>> hi all,
> >>>
> >>> I run FreeBSD 9.0-STABLE #1: Sun Apr 15 21:08:51 UTC 2012 amd64
> >>>
> >>> yesterday I have cvsup-ed src and was trying to buildkernel
> >>> bellow is error I receive:
> >>> --- [ c
> On 12/17/2012 1:35 AM, Chris H wrote:
>>> hi all,
>>>
>>> I run FreeBSD 9.0-STABLE #1: Sun Apr 15 21:08:51 UTC 2012 amd64
>>>
>>> yesterday I have cvsup-ed src and was trying to buildkernel
>>> bellow is error I receive:
>>> --- [ cut ]
>>> ---
> On 12/17/2012 1:35 AM, Chris H wrote:
>>> hi all,
>>>
>>> I run FreeBSD 9.0-STABLE #1: Sun Apr 15 21:08:51 UTC 2012 amd64
>>>
>>> yesterday I have cvsup-ed src and was trying to buildkernel
>>> bellow is error I receive:
>>> --- [ cut ]
>>> ---
On 2012-12-17 07:08, Zeus Panchenko wrote:
I run FreeBSD 9.0-STABLE #1: Sun Apr 15 21:08:51 UTC 2012 amd64
yesterday I have cvsup-ed src and was trying to buildkernel
bellow is error I receive:
...
cc -c -x assembler-with-cpp -DLOCORE -O2 -frename-registers -pipe
-fno-strict-aliasing -std=c9
On 12/17/2012 1:35 AM, Chris H wrote:
hi all,
I run FreeBSD 9.0-STABLE #1: Sun Apr 15 21:08:51 UTC 2012 amd64
yesterday I have cvsup-ed src and was trying to buildkernel
bellow is error I receive:
--- [ cut ]
--
On 12/17/2012 1:35 AM, Chris H wrote:
hi all,
I run FreeBSD 9.0-STABLE #1: Sun Apr 15 21:08:51 UTC 2012 amd64
yesterday I have cvsup-ed src and was trying to buildkernel
bellow is error I receive:
--- [ cut ]
--
> hi all,
>
> I run FreeBSD 9.0-STABLE #1: Sun Apr 15 21:08:51 UTC 2012 amd64
>
> yesterday I have cvsup-ed src and was trying to buildkernel
> bellow is error I receive:
> --- [ cut ]
> -
> ...
> cc
hi all,
I run FreeBSD 9.0-STABLE #1: Sun Apr 15 21:08:51 UTC 2012 amd64
yesterday I have cvsup-ed src and was trying to buildkernel
bellow is error I receive:
--- [ cut ]
-
...
cc -c -O2 -frename-
On 01/22/2012 11:00, clift...@volcano.org wrote:
> On 12.01.2012 15:52, Doug Barton wrote:
chflags -R noschg /usr/obj/usr
rm -rf /usr/obj/usr
>>
>> It's much faster to do:
>>
>> /bin/rm -rf ${obj}/* 2> /dev/null || /bin/chflags -R 0 ${obj}/* &&
>> /bin/rm -rf ${obj}/*
>
> If I could just
On Sun, Jan 22, 2012 at 01:00:46PM -0600, clift...@volcano.org wrote:
> On 12.01.2012 15:52, Doug Barton wrote:
> >>> chflags -R noschg /usr/obj/usr
> >>> rm -rf /usr/obj/usr
> > It's much faster to do:
> > /bin/rm -rf ${obj}/* 2> /dev/null || /bin/chflags -R 0 ${obj}/* &&
> > /bin/rm -rf ${obj}/
On 22.01.2012 13:16, Matthew Seaman wrote:
On 22/01/2012 19:00, clift...@volcano.org wrote:
If rm had an option to take files from standard input, or if
there's another program I'm not aware of which does this, it
could serve as the right-hand side of this.
xargs(1) -- generic solution to taki
On 22/01/2012 19:00, clift...@volcano.org wrote:
> If rm had an option to take files from standard input, or if
> there's another program I'm not aware of which does this, it
> could serve as the right-hand side of this.
xargs(1) -- generic solution to taking a list of command arguments from
a fil
On 12.01.2012 15:52, Doug Barton wrote:
chflags -R noschg /usr/obj/usr
rm -rf /usr/obj/usr
It's much faster to do:
/bin/rm -rf ${obj}/* 2> /dev/null || /bin/chflags -R 0 ${obj}/* &&
/bin/rm -rf ${obj}/*
If I could just add one thing here, for those who might be tempted
to immediately cut and
On Sat, 14 Jan 2012 23:37:50 -0800
Jeremy Chadwick wrote:
> On Sun, Jan 15, 2012 at 02:24:41AM -0500, Rob Clark wrote:
> > On Thu, 12 Jan 2012 08:15:50 -0500
> > John Baldwin wrote:
> >
> > > On Wednesday, January 11, 2012 4:11:10 pm Rob Clark wrote:
> > > > System: Dell 600sc
> > > > Currently
On Sun, Jan 15, 2012 at 02:24:41AM -0500, Rob Clark wrote:
> On Thu, 12 Jan 2012 08:15:50 -0500
> John Baldwin wrote:
>
> > On Wednesday, January 11, 2012 4:11:10 pm Rob Clark wrote:
> > > System: Dell 600sc
> > > Currently running: 8.2-RELEASE
> > >
> > > In attempting to update this system to
On Thu, 12 Jan 2012 08:15:50 -0500
John Baldwin wrote:
> On Wednesday, January 11, 2012 4:11:10 pm Rob Clark wrote:
> > System: Dell 600sc
> > Currently running: 8.2-RELEASE
> >
> > In attempting to update this system to 8-STABLE I did
> > what I usually do to update a system (see below).
> > ma
On Thu, 12 Jan 2012 21:37:27 -0600, Joe Ennis wrote:
On Thu, 12 Jan 2012 19:11:54 -0800
Garrett Cooper wrote:
On Thu, Jan 12, 2012 at 5:52 PM, Doug Barton
wrote:
>
>>> chflags -R noschg /usr/obj/usr
>>> rm -rf /usr/obj/usr
>
> It's much faster to do:
>
> /bin/rm -rf ${obj}/* 2> /dev/null ||
On 01/12/2012 20:10, Garrett Cooper wrote:
> When I did
> stuff in parallel (have 8 regular cores, 8 SMT cores), the process
> took less than an hour to complete.
Sounds like you should get to work figuring out how to optimize rm to
take advantage of this. :)
Doug
--
You can observe a
On Thu, Jan 12, 2012 at 7:23 PM, Stephen Montgomery-Smith
wrote:
> On 01/12/2012 09:11 PM, Garrett Cooper wrote:
>
>> +1. And it's faster yet when you can run parallel copies of rm on
>> different portions of the directory tree (e.g. xargs, find [..] -exec)
>> as rm is O(n).
>
>
> I have always wo
On Thu, 12 Jan 2012 19:11:54 -0800
Garrett Cooper wrote:
> On Thu, Jan 12, 2012 at 5:52 PM, Doug Barton
> wrote:
> >
> >>> chflags -R noschg /usr/obj/usr
> >>> rm -rf /usr/obj/usr
> >
> > It's much faster to do:
> >
> > /bin/rm -rf ${obj}/* 2> /dev/null || /bin/chflags -R 0 ${obj}/* &&
> > /bin/
On 01/12/2012 09:11 PM, Garrett Cooper wrote:
+1. And it's faster yet when you can run parallel copies of rm on
different portions of the directory tree (e.g. xargs, find [..] -exec)
as rm is O(n).
I have always wondered about that! I thought that the main bottleneck
in "rm -r" might be dele
On Thu, Jan 12, 2012 at 5:52 PM, Doug Barton wrote:
>
>>> chflags -R noschg /usr/obj/usr
>>> rm -rf /usr/obj/usr
>
> It's much faster to do:
>
> /bin/rm -rf ${obj}/* 2> /dev/null || /bin/chflags -R 0 ${obj}/* &&
> /bin/rm -rf ${obj}/*
+1. And it's faster yet when you can run parallel copies of rm
>> chflags -R noschg /usr/obj/usr
>> rm -rf /usr/obj/usr
It's much faster to do:
/bin/rm -rf ${obj}/* 2> /dev/null || /bin/chflags -R 0 ${obj}/* &&
/bin/rm -rf ${obj}/*
--
You can observe a lot just by watching. -- Yogi Berra
Breadth of IT experience, and depth of knowledg
On Thu, 12 Jan 2012 08:15:50 -0500
John Baldwin wrote:
> On Wednesday, January 11, 2012 4:11:10 pm Rob Clark wrote:
> > System: Dell 600sc
> > Currently running: 8.2-RELEASE
> >
> > In attempting to update this system to 8-STABLE I did
> > what I usually do to update a system (see below).
> > ma
On Wed, 11 Jan 2012 21:52:28 -0600
Andre Goree wrote:
> On Wed, Jan 11, 2012 at 3:11 PM, Rob Clark wrote:
>
> > System: Dell 600sc
> > Currently running: 8.2-RELEASE
> >
> > In attempting to update this system to 8-STABLE I did
> > what I usually do to update a system (see below).
> > make buil
On Wednesday, January 11, 2012 4:11:10 pm Rob Clark wrote:
> System: Dell 600sc
> Currently running: 8.2-RELEASE
>
> In attempting to update this system to 8-STABLE I did
> what I usually do to update a system (see below).
> make buildworld completes successfully, but make
> buildkernel does not.
On Wed, Jan 11, 2012 at 3:11 PM, Rob Clark wrote:
> System: Dell 600sc
> Currently running: 8.2-RELEASE
>
> In attempting to update this system to 8-STABLE I did
> what I usually do to update a system (see below).
> make buildworld completes successfully, but make
> buildkernel does not. I usuall
System: Dell 600sc
Currently running: 8.2-RELEASE
In attempting to update this system to 8-STABLE I did
what I usually do to update a system (see below).
make buildworld completes successfully, but make
buildkernel does not. I usually create a custom
kernel, but for this system I went with GENERIC
On Wed, Feb 13, 2008 at 12:22:57PM -0600, Doug Poland wrote:
> Hello,
>
> I'm attempting to build a GENERIC kernel for 6.3-STABLE and am getting
> the following error message:
>
> cc -c -O -pipe -Wall -Wredundant-decls -Wnested-externs
> -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arit
Hello,
I'm attempting to build a GENERIC kernel for 6.3-STABLE and am getting
the following error message:
cc -c -O -pipe -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes
-Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions
-std=c99 -g -nostdinc -I- -
I add these lines in my kernel config file:
device mmcsd
device mmc
then I got:
cc -c -O2 -pipe -fno-strict-aliasing -Wall -Wredundant-decls
-Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith
-Winline -Wcast-qual -fformat-extensions -std=c99 -nostdinc
cc -O2 -fno-strict-aliasing -pipe -march=prescott -Werror -D_KERNEL
-DKLD_MODULE -nostdinc -I-
-I/usr/src/sys/modules/acpi/acpi/../../../contrib/dev/acpica
-DHAVE_KERNEL_OPTION_HEADERS -include
/usr/obj/usr/src/sys/SPAMTOASTER/opt_global.h -I. -I@ -I@/contrib/altq
-I@/../include -finline-limi
Hello Dominic,
Monday, July 4, 2005, 6:13:57 PM, you wrote:
DM> On Monday 04 July 2005 15:22, misael wrote:
>> Hello freebsd-stable,
>>
>> i'm trying to update/upgrade my box from 5.3 STABLE to the latest
>> version of 5 branch.
>> but when i'm doing make buildkernel i bumped in to some errors,
misael wrote:
# Debugging for use in -current
#optionsDDB #Enable the kernel debugger
#optionsINVARIANTS #Enable calls of extra sanity checking
options INVARIANT_SUPPORT #Extra sanity checks of internal
structures, required by INVAR
On Monday 04 July 2005 15:22, misael wrote:
> Hello freebsd-stable,
>
> i'm trying to update/upgrade my box from 5.3 STABLE to the latest
> version of 5 branch.
> but when i'm doing make buildkernel i bumped in to some errors,
Sometimes it is worth trying to cvsup against a different cvsup mirror
s to me like you've removed something you shouldn't have
>>
>> GL> -Original Message-
>> GL> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of misael
>> GL> Sent: 04 July 2005 15:23
>> GL> To: freebsd-stable@freebsd.org
>
-Original Message-
> GL> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of misael
> GL> Sent: 04 July 2005 15:23
> GL> To: freebsd-stable@freebsd.org
> GL> Subject: 5.3 STABLE to 5.4 buildkernel error
>
> GL> Hello freebsd-stable,
>
> GL>
sael
GL> Sent: 04 July 2005 15:23
GL> To: freebsd-stable@freebsd.org
GL> Subject: 5.3 STABLE to 5.4 buildkernel error
GL> Hello freebsd-stable,
GL> i'm trying to update/upgrade my box from 5.3 STABLE to the latest version
of 5 branch.
GL> but when i'm doing make build
BLE to 5.4 buildkernel error
Hello freebsd-stable,
i'm trying to update/upgrade my box from 5.3 STABLE to the latest version of 5
branch.
but when i'm doing make buildkernel i bumped in to some errors, here it is the
error messages:
>&g
Hello freebsd-stable,
i'm trying to update/upgrade my box from 5.3 STABLE to the latest
version of 5 branch.
but when i'm doing make buildkernel i bumped in to some errors,
here it is the error messages:
>>> stage 2.3: build tools
--
cd
On Thu, Jun 20, 2002 at 05:56:37AM -0700, Korey Pelton wrote:
> Hello,
>
> I did a cvsup on 6-19-02 (yesterday) using the src-all
> setting in my cvsupfile. Buildkernel errors out with
> the following:
>
> cc -c -O -pipe -Wall -Wredundant-decls
> -Wnested-externs -Wstrict-prototypes -W
> miss
Hello all,
I just installed 4.0R from a Walnut Creek CD with no trouble
whatsoever. I was able to get on the net, top, ps etc fine. At this point
I decided to go for 4.0S, so I cvsupped with the following tag file:
*default host=cvsup4.FreeBSD.org
*default base=/usr/local/etc/cvsup
*defa
43 matches
Mail list logo
