Hello,
On 2/19/16 5:40 PM, Dewayne Geraghty wrote:
On 20 February 2016 at 09:01, Bryan Drewery mailto:bdrew...@freebsd.org>> wrote:
On 2/6/2016 6:21 AM, Jim Ohlstein wrote:
> Hello,
>
> First noticed:
>
> root@rubicon:/usr/src # svn info
> Path: .
> Workin
On 20 February 2016 at 09:01, Bryan Drewery wrote:
> On 2/6/2016 6:21 AM, Jim Ohlstein wrote:
> > Hello,
> >
> > First noticed:
> >
> > root@rubicon:/usr/src # svn info
> > Path: .
> > Working Copy Root Path: /usr/src
> > URL: https://svn.freebsd.org/base/stable/10
> > Relative URL: ^/stable/10
>
On 2/6/2016 6:21 AM, Jim Ohlstein wrote:
> Hello,
>
> First noticed:
>
> root@rubicon:/usr/src # svn info
> Path: .
> Working Copy Root Path: /usr/src
> URL: https://svn.freebsd.org/base/stable/10
> Relative URL: ^/stable/10
> Repository Root: https://svn.freebsd.org/base
> Repository UUID: ccf9f
Hello,
First noticed:
root@rubicon:/usr/src # svn info
Path: .
Working Copy Root Path: /usr/src
URL: https://svn.freebsd.org/base/stable/10
Relative URL: ^/stable/10
Repository Root: https://svn.freebsd.org/base
Repository UUID: ccf9f872-aa2e-dd11-9fc8-001c23d0bc1f
Revision: 295341
Node Kind: di
On Aug 26 17:35, Chris H wrote:
On Wed, 26 Aug 2015 18:38:46 +0100 Matt Smith wrote
On Aug 26 12:27, Matt Smith wrote:
>On Aug 26 13:10, Slawa Olhovchenkov wrote:
Hardware error or memory exhausted
>>>
>>>It does appear to be something along those lines. It's not memory
>>>exhaustion as it
On Wed, 26 Aug 2015 18:38:46 +0100 Matt Smith wrote
> On Aug 26 12:27, Matt Smith wrote:
> >On Aug 26 13:10, Slawa Olhovchenkov wrote:
> Hardware error or memory exhausted
> >>>
> >>>It does appear to be something along those lines. It's not memory
> >>>exhaustion as it has around 2GB free at
On Wed, Aug 26, 2015 at 06:38:46PM +0100, Matt Smith wrote:
> ...
> So, been doing some testing. It looks like a -j4 problem with the latest
> sources. If I buildworld with -j1 then it compiles with no issues at
> all. If I compile r286908 with -j4 then it compiles with no issues at
> all. If I
On Aug 26 12:27, Matt Smith wrote:
On Aug 26 13:10, Slawa Olhovchenkov wrote:
Hardware error or memory exhausted
It does appear to be something along those lines. It's not memory
exhaustion as it has around 2GB free at the point it fails. However I've
deleted /usr/obj and started the buildworl
On Aug 26 13:10, Slawa Olhovchenkov wrote:
>Hardware error or memory exhausted
It does appear to be something along those lines. It's not memory
exhaustion as it has around 2GB free at the point it fails. However I've
deleted /usr/obj and started the buildworld again and it failed in a
different
On Wed, Aug 26, 2015 at 10:48:29AM +0100, Matt Smith wrote:
> On Aug 26 11:09, Slawa Olhovchenkov wrote:
> >On Wed, Aug 26, 2015 at 08:01:25AM +0100, Matt Smith wrote:
> >
> >> Trying to do a buildworld from the latest stable seems to result in a
> >> failure within openssl. Anyone else seen this?
--- Original message ---
From: "Matt Smith"
Date: 26 August 2015, 12:48:51
On Aug 26 11:09, Slawa Olhovchenkov wrote:
>On Wed, Aug 26, 2015 at 08:01:25AM +0100, Matt Smith wrote:
>
>> Trying to do a buildworld from the latest stable seems to result in a
>> failure within openssl. Anyone el
On Aug 26 11:09, Slawa Olhovchenkov wrote:
On Wed, Aug 26, 2015 at 08:01:25AM +0100, Matt Smith wrote:
Trying to do a buildworld from the latest stable seems to result in a
failure within openssl. Anyone else seen this?
--- ocsp_ext.o ---
cc -O2 -pipe -DTERMIOS -DANSI_SOURCE
-I/usr/src/sec
On Wed, Aug 26, 2015 at 08:01:25AM +0100, Matt Smith wrote:
> Trying to do a buildworld from the latest stable seems to result in a
> failure within openssl. Anyone else seen this?
>
> --- ocsp_ext.o ---
> cc -O2 -pipe -DTERMIOS -DANSI_SOURCE
> -I/usr/src/secure/lib/libcrypto/../../../crypt
Trying to do a buildworld from the latest stable seems to result in a
failure within openssl. Anyone else seen this?
--- ocsp_ext.o ---
cc -O2 -pipe -DTERMIOS -DANSI_SOURCE
-I/usr/src/secure/lib/libcrypto/../../../crypto/openssl -I/usr/src/secu
re/lib/libcrypto/../../../crypto/openssl/crypt
on 11/07/2013 23:07 Dimitry Andric said the following:
> On Jul 11, 2013, at 19:19, Andriy Gapon wrote:
>> on 11/07/2013 19:43 Andriy Gapon said the following:
>>>
>>> buildword was run as make -j8 buildworld and the it mysteriously failed
>>> like this:
>>>
>>> sh /usr/src/tools/install.sh -s -o
On Jul 11, 2013, at 19:19, Andriy Gapon wrote:
> on 11/07/2013 19:43 Andriy Gapon said the following:
>>
>> buildword was run as make -j8 buildworld and the it mysteriously failed like
>> this:
>>
>> sh /usr/src/tools/install.sh -s -o root -g wheel -m 444 liblwres.so.80
>> /usr/obj/usr/src/
on 11/07/2013 19:43 Andriy Gapon said the following:
>
> buildword was run as make -j8 buildworld and the it mysteriously failed like
> this:
>
> sh /usr/src/tools/install.sh -s -o root -g wheel -m 444 liblwres.so.80
> /usr/obj/usr/src/tmp/usr/lib
> sh /usr/src/tools/install.sh -l s liblwres
buildword was run as make -j8 buildworld and the it mysteriously failed like
this:
sh /usr/src/tools/install.sh -s -o root -g wheel -m 444 liblwres.so.80
/usr/obj/usr/src/tmp/usr/lib
sh /usr/src/tools/install.sh -l s liblwres.so.80
/usr/obj/usr/src/tmp/usr/lib/liblwres.so
1 error
*** [librar
On Tue, Nov 9, 2010 at 11:48 PM, Jeremy Chadwick
wrote:
> On Tue, Nov 09, 2010 at 06:09:08PM -0600, Bryce Edwards wrote:
>> After updating source today, I am receiving the following error when
>> running make NOCCACHE=YES -j16 buildkernel
>
> Please re-run the buildkernel without any -j or -jXX fl
On Tue, Nov 09, 2010 at 06:09:08PM -0600, Bryce Edwards wrote:
> After updating source today, I am receiving the following error when
> running make NOCCACHE=YES -j16 buildkernel
Please re-run the buildkernel without any -j or -jXX flags to see where
the actual error happened. The below doesn't s
On 11/10/2010 00:07, Bryce Edwards wrote:
> On Tue, Nov 9, 2010 at 11:04 PM, jhell wrote:
>> On 11/09/2010 19:09, Bryce Edwards wrote:
>>> After updating source today, I am receiving the following error when
>>> running make NOCCACHE=YES -j16 buildkernel
>>>
>>>
>>> ===> zlib (all)
>>> cc -O2 -pip
On Tue, Nov 9, 2010 at 11:04 PM, jhell wrote:
> On 11/09/2010 19:09, Bryce Edwards wrote:
>> After updating source today, I am receiving the following error when
>> running make NOCCACHE=YES -j16 buildkernel
>>
>>
>> ===> zlib (all)
>> cc -O2 -pipe -fno-strict-aliasing -Werror -D_KERNEL -DKLD_MODU
On 11/09/2010 19:09, Bryce Edwards wrote:
> After updating source today, I am receiving the following error when
> running make NOCCACHE=YES -j16 buildkernel
>
>
> ===> zlib (all)
> cc -O2 -pipe -fno-strict-aliasing -Werror -D_KERNEL -DKLD_MODULE
> -nostdinc -DHAVE_KERNEL_OPTION_HEADERS -includ
After updating source today, I am receiving the following error when
running make NOCCACHE=YES -j16 buildkernel
===> zlib (all)
cc -O2 -pipe -fno-strict-aliasing -Werror -D_KERNEL -DKLD_MODULE
-nostdinc -DHAVE_KERNEL_OPTION_HEADERS -include
/usr/obj/usr/src/sys/GENERIC/opt_global.h -I. -I@ -I@/
Hello,
Our recent buildworlds on both i386 and amd64, as of a couple days
ago, are failing with the below error. We use
MODULES_WITH_WORLD=true.
===> sys/modules/dtrace/dtmalloc (depend)
@ -> /usr/src/sys
machine -> /usr/src/sys/amd64/include
awk -f @/tools/vnode_if.awk @/kern/vnode_if.src -p
aw
Hello,
Our recent buildworlds on both i386 and amd64, as of a couple days
ago, are failing with the below error. We use
MODULES_WITH_WORLD=true.
===> sys/modules/dtrace/dtmalloc (depend)
@ -> /usr/src/sys
machine -> /usr/src/sys/amd64/include
awk -f @/tools/vnode_if.awk @/kern/vnode_if.src -p
When I do
make -DNO_PROFILE buildworld revision 186797 from svn
I get
==> secure/usr.bin/ssh-agent (cleandir)
rm -f ssh-agent ssh-agent.o ssh-agent.1.gz ssh-agent.1.cat.gz
rm -f .depend GPATH GRTAGS GSYMS GTAGS
===> secure/usr.bin/ssh-keygen (cleandir)
rm -f ssh-keygen ssh-keygen.o ssh-keygen.1.gz
Greetings
Installed 7 RC2 some time ago, and just tried a cvsup to 7_STABLE.
Buildworld fails with mkmagic: Printf format, after hundreds of
warnings -
magic, 6: Warning offset invalid.
I searched the archive, and see that someone else had this problem
when upgrading to 6.3, but the
On Sun, Mar 09, 2008 at 04:19:15PM -0500, Tom Judge wrote:
> Thanks for the response, it was indeed just a case of touching
> /usr/src/gnu/usr.bin/cvs/contrib/Makefile. Do you have the information
> about the relevent change sets that fix this? Then I can merge this fix to
> my local tree.
Y
On Sun, 9 Mar 2008, Tom Judge wrote:
Xin LI wrote:
Tom Judge wrote:
Hi,
We have been building RELENG_6_x source trees from read only NFS file
systems for well over a year now with out any problems. However I have
just tried to do "make buildworld" on a RELENG_7_0 source tree from
yesterda
Xin LI wrote:
Tom Judge wrote:
Hi,
We have been building RELENG_6_x source trees from read only NFS file
systems for well over a year now with out any problems. However I
have just tried to do "make buildworld" on a RELENG_7_0 source tree
from yesterday and it failed to build with the follo
Tom Judge wrote:
Hi,
We have been building RELENG_6_x source trees from read only NFS file
systems for well over a year now with out any problems. However I have
just tried to do "make buildworld" on a RELENG_7_0 source tree from
yesterday and it failed to build with the following error:
Hi,
We have been building RELENG_6_x source trees from read only NFS file
systems for well over a year now with out any problems. However I have
just tried to do "make buildworld" on a RELENG_7_0 source tree from
yesterday and it failed to build with the following error:
===> gnu/usr.bin/c
Hi,
I just csup'd the sources a few hours ago, and successfully compiled and
installed a new kernel. However, when I go to do a buildworld, this
comes up:
--
>>> stage 2.3: build tools
---
Hello,
During buildworld on RELENG_7 csup'd as of 10/22, it dies in
sys/boot/i386/boot2 with:
===> sys/boot/i386/boot2 (all)
-533 bytes available
*** Error code 1
Stop in /usr/src/sys/boot/i386/boot2.
*** Error code 1
I took a look at the cc command line:
cc -Os -fno-guess-branch-probability
On Thu, Nov 09, 2006 at 09:33:45AM -0500, Matthew Herzog wrote:
> I have never been able to "make buildworld" on sparc64 STABLE. It
> always dies in gbde.
Don't hijack threads for unrelated topics, please.
> /usr/src/sbin/gbde/gbde.c:801: warning: implicit declaration of
> function `getopt'
> /us
Hello!
>
> After running cvsup to RELENG_6_1, I started `make buildworld
> KERNCONF=BEASTIE61` as per the handbook's '21.4.1 The Canonical Way to
> Update Your System'
>
> In libexec/mail.local I get the following on stderr
> /usr/obj/usr/src/tmp/usr/bin/ld: warning: libldap-2.2.so.7, n
Hello!
I have this problem too. I use SMTP AUTH and I get error if I do buildworld.
Do you have decision of problem?
Thank you.
Victor Sherstniov
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinf
On Wed, May 10, 2006 at 12:58:49PM +0200, Spil Oss wrote:
> l.s.
>
> After running cvsup to RELENG_6_1, I started `make buildworld
> KERNCONF=BEASTIE61` as per the handbook's '21.4.1 The Canonical Way to
> Update Your System'
>
> In libexec/mail.local I get the following on stderr
> /usr/obj/usr/
Spil Oss wrote:
l.s.
After running cvsup to RELENG_6_1, I started `make buildworld
KERNCONF=BEASTIE61` as per the handbook's '21.4.1 The Canonical Way to
Update Your System'
In libexec/mail.local I get the following on stderr
/usr/obj/usr/src/tmp/usr/bin/ld: warning: libldap-2.2.so.7, needed by
l.s.
After running cvsup to RELENG_6_1, I started `make buildworld
KERNCONF=BEASTIE61` as per the handbook's '21.4.1 The Canonical Way to
Update Your System'
In libexec/mail.local I get the following on stderr
/usr/obj/usr/src/tmp/usr/bin/ld: warning: libldap-2.2.so.7, needed by
/usr/local/lib/l
On Mon, 06 Feb 2006 14:13:13 +0100 Markus Buretorp <[EMAIL PROTECTED]> wrote:
> For me, the problem was caused by some stupid envvars I had
> in my shell config. I removed these and the problem was solved.
>
> export INCLUDE_PATH=/usr/include:/usr/local/include export
> C_INCLUDE_PATH=/usr/include
Markus and freebsd-stable:
I have encountered a situation exactly the same as the one described in
this thread when attempting a source upgrade from 5.4-RELEASE-p4 to
6.0-RELEASE-p4.
I have had nothing but success on 10 other machines that were initially
running 5.4-RELEASE, 5.4-RELEASE, -p6, and
> > > One last point, either remove me from the reply to list or place the
> > > maillist
> > > back on it, thank you.
> >
> > I think you owe me an apology - but I doubt I will get it.
>
> Your correct, you won't.
I think you mean "you are" ?
It is a writer's credibility that is at stake
On Friday 09 December 2005 11:31, vizion wrote:
> > -Original Message-
> > From: Michael C. Shultz [mailto:[EMAIL PROTECTED]
> > Sent: Friday, December 09, 2005 10:32 AM
> > To: vizion
> > Cc: 'Peter Jeremy'; 'Doug Barton'
> > Su
> -Original Message-
> From: Michael C. Shultz [mailto:[EMAIL PROTECTED]
> Sent: Friday, December 09, 2005 10:32 AM
> To: vizion
> Cc: 'Peter Jeremy'; 'Doug Barton'
> Subject: Re: Upgrading 5.3 > 6.0 buildworld failure now in libmagic
>
>
secmgr wrote:
Doug Barton wrote:
+ When upgrading from one major version to another, it is
+ generally best to upgrade to the latest code in the branch
+ currently installed first, then do another upgrade to the
+ new branch.
Or as another poster said, just say latest
On Thursday 08 December 2005 08:57, [EMAIL PROTECTED] wrote:
> > From: Peter Jeremy <[EMAIL PROTECTED]>
> > Date: 2005/12/08 Thu AM 01:34:42 PST
> > To: Vizion <[EMAIL PROTECTED]>
> > CC: Doug Barton <[EMAIL PROTECTED]>, freebsd-stable@freebsd.org
>
Peter Jeremy wrote:
On Wed, 2005-Dec-07 13:34:53 -0800, Vizion wrote:
That is a judgment call - franky my experience has been that developers who
are bad at ensuring their work is well documentated are second rate rather
than top rate developers.
Software developers are notoriously p
>
> From: "Matthew D. Fuller" <[EMAIL PROTECTED]>
> Date: 2005/12/08 Thu AM 08:01:47 PST
> To: Peter Jeremy <[EMAIL PROTECTED]>
> CC: Doug Barton <[EMAIL PROTECTED]>, freebsd-stable@freebsd.org,
> Vizion <[EMAIL PROTECTED]>
> Sub
>
> From: Peter Jeremy <[EMAIL PROTECTED]>
> Date: 2005/12/08 Thu AM 01:34:42 PST
> To: Vizion <[EMAIL PROTECTED]>
> CC: Doug Barton <[EMAIL PROTECTED]>, freebsd-stable@freebsd.org
> Subject: Re: Upgrading 5.3 > 6.0 buildworld failure now in libmagic
On Thu, Dec 08, 2005 at 08:34:42PM +1100 I heard the voice of
Peter Jeremy, and lo! it spake thus:
> On Wed, 2005-Dec-07 13:34:53 -0800, Vizion wrote:
> >development is so good. It deserves better and more professional
> >attention to the role of end user documentation.
>
> Are you volunteering?
On Wed, 2005-Dec-07 13:34:53 -0800, Vizion wrote:
>Well having run many very large scale projects myself I find it difficult to
>accept either implication of this perspective.
There's a massive difference between running a large commercial project
and running a large open source project using vo
On Wednesday 07 December 2005 13:34, the author Vizion contributed to the
dialogue on-
Re: Upgrading 5.3 > 6.0 buildworld failure now in libmagic now
Stable Doc issues- thread branched from [Upgrading 5.3 > 6.0 buildworld
failure]
>On Wednesday 07 December 2005 13:01, the author Do
Doug Barton wrote:
How does this change to UPDATING in RELENG_6 look to you:
Index: UPDATING
===
RCS file: /home/ncvs/src/UPDATING,v
retrieving revision 1.416.2.7
diff -u -r1.416.2.7 UPDATING
--- UPDATING1 Nov 2005 23:44:40 -00
On Wednesday 07 December 2005 13:01, the author Doug Barton contributed to
the dialogue on-
Re: Upgrading 5.3 > 6.0 buildworld failure now in libmagic:
>Vizion wrote:
>> Well I do not want to not thank those who have made the upgrades viable.
>> The value of their
Vizion wrote:
Well I do not want to not thank those who have made the upgrades viable. The
value of their work should not be underrated.
That's a step in the right direction, thanks. :)
There is however a perennial problem that freebsd documentation has always
been seen as behind and seperat
On Tue, Dec 06, 2005 at 11:24:31PM -0500, Kenneth W Cochran wrote:
> >Certainly better documentation for the upgrade path between 5.3 and 6.0 would
> >have saved me a h*** of a lot of time.. but there it is.. live does not hand
> >out many A++s
>
> I would guess that it says 5.3 instead of 5.4 du
>From: Vizion <[EMAIL PROTECTED]>
>To: freebsd-stable@freebsd.org, [EMAIL PROTECTED]
>Date: Tue, 6 Dec 2005 19:41:30 -0800
>Cc: Doug Barton <[EMAIL PROTECTED]>, Kris Kennaway <[EMAIL PROTECTED]>
>Subject: Re: Upgrading 5.3 > 6.0 buildworld failure now in libmag
On Tuesday 06 December 2005 16:50, the author Allen contributed to the
dialogue on-
Re: Upgrading 5.3 > 6.0 buildworld failure now in libmagic:
>On Tue, December 6, 2005 19:44, Doug Barton wrote:
>> On Tue, 6 Dec 2005, secmgr wrote:
>>> Not to belabour this, but the
On Tue, December 6, 2005 19:44, Doug Barton wrote:
> On Tue, 6 Dec 2005, secmgr wrote:
>
>> Not to belabour this, but the 6.0 release notes do specificly say 5.3
>> RELEASE
>> and newer.
>
> 5.4-STABLE is newer. :)
>
>> "Source upgrades to FreeBSD 6.0-RELEASE are only supported from FreeBSD
>> 5.3
On Tue, 6 Dec 2005, secmgr wrote:
Not to belabour this, but the 6.0 release notes do specificly say 5.3 RELEASE
and newer.
5.4-STABLE is newer. :)
"Source upgrades to FreeBSD 6.0-RELEASE are only supported from FreeBSD
5.3-RELEASE or later. Users of older systems wanting to upgrade 6.0-RELEA
On Tue, Dec 06, 2005 at 05:23:42PM -0700, secmgr wrote:
> >>>Update to 5.4 before trying to update to 6.0.
> >>>
> >>>Kris
> >>>
> >>>
> >>So is there any supported direct 5.3->6.0 upgrade path, or is a stop in
> >>5.4 ville manditory now.?
> >>
> >>
> >
> >I tried to say that you have to
Kris Kennaway wrote:
On Tue, Dec 06, 2005 at 02:36:05PM -0700, secmgr wrote:
Update to 5.4 before trying to update to 6.0.
Kris
So is there any supported direct 5.3->6.0 upgrade path, or is a stop in
5.4 ville manditory now.?
I tried to say that you have to update to 5.4 bef
On Tuesday 06 December 2005 14:36, the author Doug Barton contributed to the
dialogue on-
Re: Upgrading 5.3 > 6.0 buildworld failure now in libmagic:
>On Tue, 6 Dec 2005, Vizion wrote:
>> Just an additional question if some one has time to answer.
>>
>> Should I upgr
On Tue, 6 Dec 2005, Vizion wrote:
Just an additional question if some one has time to answer.
Should I upgrade my ports from 5.4 as well prior to moving to 6?
No, that's not needed.
hth,
Doug
--
This .signature sanitized for your protection
___
On Tue, 6 Dec 2005, Vizion wrote:
Re: Upgrading 5.3 > 6.0 buildworld failure in libkrb5 but is currently:
Upgrading 5.3 > 6.0 buildworld failure now in libmagic
You should first upgrade to the latest 5-STABLE (cvs tag RELENG_5), then you
should be able to upgrade to 6-STABLE (c
On Tuesday 06 December 2005 14:15, the author Vizion contributed to the
dialogue on-
Re: Upgrading 5.3 > 6.0 buildworld failure now in libmagic:
>On Tuesday 06 December 2005 13:28, the author Kris Kennaway contributed to
>the dialogue on-
>
> Re: Upgrading 5.3 > 6.0 buildwo
On Tuesday 06 December 2005 13:28, the author Kris Kennaway contributed to
the dialogue on-
Re: Upgrading 5.3 > 6.0 buildworld failure now in libmagic:
>On Tue, Dec 06, 2005 at 01:20:44PM -0800, Vizion wrote:
>> On Tuesday 06 December 2005 11:47, the author Vizion contri
On Tuesday 06 December 2005 23:46, Kris Kennaway wrote:
> On Tue, Dec 06, 2005 at 02:36:05PM -0700, secmgr wrote:
> > >Update to 5.4 before trying to update to 6.0.
> > >
> > >Kris
> >
> > So is there any supported direct 5.3->6.0 upgrade path, or is a
> > stop in 5.4 ville manditory now.?
>
> I tr
On Tue, Dec 06, 2005 at 02:36:05PM -0700, secmgr wrote:
> >Update to 5.4 before trying to update to 6.0.
> >
> >Kris
> >
> >
> So is there any supported direct 5.3->6.0 upgrade path, or is a stop in
> 5.4 ville manditory now.?
I tried to say that you have to update to 5.4 before you can update
Kris Kennaway wrote:
On Tue, Dec 06, 2005 at 01:20:44PM -0800, Vizion wrote:
On Tuesday 06 December 2005 11:47, the author Vizion contributed to the
dialogue which was on-
Re: Upgrading 5.3 > 6.0 buildworld failure in libkrb5 but is currently:
Upgrading 5.3 > 6.0 buildworld failure
On Tue, Dec 06, 2005 at 01:20:44PM -0800, Vizion wrote:
> On Tuesday 06 December 2005 11:47, the author Vizion contributed to the
> dialogue which was on-
> Re: Upgrading 5.3 > 6.0 buildworld failure in libkrb5 but is currently:
> Upgrading 5.3 > 6.0 buildworld failure now
On Tuesday 06 December 2005 11:47, the author Vizion contributed to the
dialogue which was on-
Re: Upgrading 5.3 > 6.0 buildworld failure in libkrb5 but is currently:
Upgrading 5.3 > 6.0 buildworld failure now in libmagic
>On Tuesday 06 December 2005 04:00, the author Rusla
On Tuesday 06 December 2005 04:00, the author Ruslan Ermilov contributed to
the dialogue on-
Re: Upgrading 5.3 > 6.0 buildworld failure in libkrb5:
>On Mon, Dec 05, 2005 at 03:18:43PM -0800, Vizion wrote:
>> Hi
>>
>> I have tried repeatedly to get make buildworld fo
On Mon, Dec 05, 2005 at 03:18:43PM -0800, Vizion wrote:
> Hi
>
> I have tried repeatedly to get make buildworld for upgrading from freebsd 5.3
> to 6.0 but get repeated failure in libkrb5.
>
> FreeBSD 5.3-RELEASE #0: Fri Nov 5 04:19:18 UTC 2004
> [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENER
On Mon, Dec 05, 2005 at 03:18:43PM -0800, Vizion wrote:
> I have tried repeatedly to get make buildworld for upgrading from freebsd
> 5.3 to 6.0 but get repeated failure in libkrb5.
Maybe you should update to the latest 5-STABLE before uprading to
6-STABLE.
> I have tried with very helpful ad
Hi
I have tried repeatedly to get make buildworld for upgrading from freebsd 5.3
to 6.0 but get repeated failure in libkrb5.
FreeBSD 5.3-RELEASE #0: Fri Nov 5 04:19:18 UTC 2004
[EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC
Timecounter "i8254" frequency 1193182 Hz quality 0
CPU: AMD Athlon(
Markus Buretorp wrote:
Hello,
I'm trying to upgrade from FreeBSD 5.4-STABLE to 6.0. I've done a
cvsup to RELENG_6 and RELENG_6_0, I've ran make cleanworld, make
clean, rm -rf /usr/obj/*, etc; but nothing helps.
This is the error
cc -O2 -pipe -march=athlon-xp -DLIBC_SCCS -I/usr/src/lib/l
Peter Jeremy wrote:
On Sat, 2005-Nov-05 21:17:58 +0100, Markus Buretorp wrote:
I'm trying to upgrade from FreeBSD 5.4-STABLE to 6.0. I've done a cvsup
to RELENG_6 and RELENG_6_0, I've ran make cleanworld, make clean, rm -rf
/usr/obj/*, etc; but nothing helps.
...
/usr/src/lib/lib
On Sat, 2005-Nov-05 21:17:58 +0100, Markus Buretorp wrote:
>I'm trying to upgrade from FreeBSD 5.4-STABLE to 6.0. I've done a cvsup
>to RELENG_6 and RELENG_6_0, I've ran make cleanworld, make clean, rm -rf
>/usr/obj/*, etc; but nothing helps.
...
> /usr/src/lib/libkvm/kvm_proc.c:108: error: sto
Markus Buretorp wrote:
> Hello,
>
> I'm trying to upgrade from FreeBSD 5.4-STABLE to 6.0. I've done a cvsup
> to RELENG_6 and RELENG_6_0, I've ran make cleanworld, make clean, rm -rf
> /usr/obj/*, etc; but nothing helps.
>
> This is the error
>
I'm not entirely sure why so many users have so mu
Hello,
I'm trying to upgrade from FreeBSD 5.4-STABLE to 6.0. I've done a cvsup
to RELENG_6 and RELENG_6_0, I've ran make cleanworld, make clean, rm -rf
/usr/obj/*, etc; but nothing helps.
This is the error
cc -O2 -pipe -march=athlon-xp -DLIBC_SCCS -I/usr/src/lib/libkvm -c
/usr/src/lib
On 29-Oct-2005 Conrad J. Sabatier wrote:
> ===> usr.bin/kdump
> cc -O2 -pipe -fno-strict-aliasing -fomit-frame-pointer -ftracer
> -funit-at-a-time -march=athlon64 -I/usr/src/usr.bin/kdump/../ktrace
> -I/usr/src/usr.bin/kdump/../.. -c ioctl.c
> In file included from ioctl.c:74:
> /usr/obj/usr/src
===> usr.bin/kdump
cc -O2 -pipe -fno-strict-aliasing -fomit-frame-pointer -ftracer
-funit-at-a-time -march=athlon64 -I/usr/src/usr.bin/kdump/../ktrace
-I/usr/src/usr.bin/kdump/../.. -c ioctl.c
In file included from ioctl.c:74:
/usr/obj/usr/src/amd64/usr/include/netinet/ip_lookup.h:33: error:
`FR_
[moved over from -current]
hello all,
hoping to help test 5.4, but running into a bit of a problem with
buildworld.
* 5.3 compiles happily with the settings below.
* didn't notice anything relevant in UPDATING.
any suggestion (or castigation) would be muchly appreciated.
epi
James Housley wrote:
I have updated my source from RELENG_4_9 to RELENG_4_10 and I am
repeatedly getting a build failure on the freebsd.cf file. When I first
got it I figured it was part of the upgrade from 4.9 to 4.10, but there
was nothing in UPDATING. Now that 4.10 is installed I am still g
I have updated my source from RELENG_4_9 to RELENG_4_10 and I am
repeatedly getting a build failure on the freebsd.cf file. When I first
got it I figured it was part of the upgrade from 4.9 to 4.10, but there
was nothing in UPDATING. Now that 4.10 is installed I am still getting
the failure.
On 7 Sep 2002 at 18:11, Don Lewis wrote:
Actually, looking back over the errors, the 'tar' directory wasn't in
the object directory tree. I wonder if I should just dump the entire
source tree and start over. I could be running up against files left
over from previous bad cvsups. What d'ya th
Hello list
When running make buildworld with sources cvsupped from cvsup18.freebsd.org
at about 2300 on 6th September I get the following error:
-o boot0cfg boot0cfg.o
gzip -cn /usr/src/usr.sbin/boot0cfg/boot0cfg.8 > boot0cfg.8.gz
===> etc
===> etc/sendmail
make: don't know how to make freebs
Hello list
CVSupping sources at around 0300 UTC today, and using this cvsupfile:
*default host=cvsup.uk.freebsd.org
*default base=/usr
*default prefix=/usr
*default release=cvs
*default tag=RELENG_4
*default delete use-rel-suffix
src-all
*default tag=.
ports-all
doc-all
this gives a make
Can someone please inform me what configs or setting do I have that
leads to the following 'buildworld' error?
I have upgraded a similar box from 4.4 to 4.5 with no hitch, but this
one keeps failing at the same point. Even blown away /usr/src and
/usr/obj but to no avail.
Any help is appreciated
Good evening everybody,
I've been running into a strange (?) problem when trying to update and
rebuild system.
I was getting the newest sources, rm -rf'ing /usr/obj/* and make'ing
buildworld. Buildworld seems to run almost to the end (around 2 hours I
think) and then stops and fails wit
On Wed, Aug 08, 2001 at 12:18:24PM -0400, Jeff Palmer wrote:
> Hello,
>
> I have tried two days in a row now, to cvsup and build world on RELENG_4_3
> I have not seen any patches commited, and have not heard/read anyhting on the
>lists..
You're right that nothing's been committed which should
Hello,
I have tried two days in a row now, to
cvsup and build world on RELENG_4_3
I have not seen any patches
commited, and have not heard/read anyhting on the lists..
Below is the error message.
Thanks in advance,
Jeff Palmer
[EMAIL PROTECTED]
cd /usr/src/usr.sbin/stallion/stlstats
Kris Kennaway wrote:
>
> cvsup again; chances are you didn't get everything.
>
I cvsup'ed after I saw the first message and completely rebuilt my system
starting around 11am PDT. There were no problems in building world or
kernel.
Kent
--
Kent Stewart
Richland, WA
Cool Videos
http://www.b
On Tue, May 29, 2001 at 03:22:04AM -0700, Kris Kennaway wrote:
> > Buildworld now fails at the following-
>
> Please post your cvsupfile.
*default host=cvsup5.FreeBSD.org
*default base=/usr
*default prefix=/usr
*default release=cvs
*default tag=RELENG_4
*default delete use-rel-suffix
src
On Tue, May 29, 2001 at 05:18:40AM -0500, Matt Bedynek wrote:
> I just synced up the latest sources (src-all) via cvsup5.freebsd.org.
>
> Buildworld now fails at the following-
Please post your cvsupfile.
Kris
PGP signature
Morning.
I just synced up the latest sources (src-all) via cvsup5.freebsd.org.
Buildworld now fails at the following-
awk -f /usr/src/lib/libncurses/../../contrib/ncurses/ncurses/tinfo/MKnames.awk
/usr/src/lib/libncurses/../../contrib/ncurses/include/Caps
cc -o make_hash -O -pipe -I. -I/usr/s
Perhaps an "all clear" when you would like people to start testing what has
been committed ?
---Mike
At 04:13 PM 3/4/2001 -0800, David O'Brien wrote:
>I would suggest that only those that are interested in debugging build
>problems (and suppling patches) be active right now.
>
>--
>-
1 - 100 of 110 matches
Mail list logo
