Re: make buildworld Failure on 10-STABLE and WITHOUT_OPENSSL=TRUE

[Jim Ohlstein]

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: .
 > 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: directory
 > Schedule: normal
 > Last Changed Author: marius
 > Last Changed Rev: 295289
 > Last Changed Date: 2016-02-04 19:14:24 -0500 (Thu, 04 Feb 2016)
 >
 >
 > Still present:
 >
 > 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: 295351
 > Node Kind: directory
 > Schedule: normal
 > Last Changed Author: wblock
 > Last Changed Rev: 295350
 > Last Changed Date: 2016-02-06 09:03:31 -0500 (Sat, 06 Feb 2016)
 >
 >
 > root@rubicon:/usr/src # make clean && make buildworld
 >
 >
 > [snip]
 >
 >
 >
 > cc   -O2 -pipe   -I. -DINET6 -DFTP_COMBINE_CWDS -std=iso9899:1999
 > -Qunused-arguments  -fstack-protector -Wsystem-headers -Werror -Wall
 > -Wno-format-y2k -W -Wno-unused-parameter -Wstrict-prototypes
 > -Wmissing-prototypes -Wpointer-arith -Wreturn-type -Wcast-qual
 > -Wwrite-strings -Wswitch -Wshadow -Wunused-parameter -Wcast-align
 > -Wchar-subscripts -Winline -Wnested-externs -Wredundant-decls
 > -Wold-style-definition -Wmissing-variable-declarations
-Wno-pointer-sign
 > -Wno-empty-body -Wno-string-plus-int -Wno-unused-const-variable  -c
 > /usr/src/lib/libfetch/common.c -o common.o
 > /usr/src/lib/libfetch/common.c:811:43: error: unused parameter 'URL'
 > [-Werror,-Wunused-parameter]
 > fetch_ssl(conn_t *conn, const struct url *URL, int verbose)
 >   ^


Try this patch please:
https://people.freebsd.org/~bdrewery/patches/libfetch-unused-ssl.patch




--
Regards,
Bryan Drewery


Unfortunately, I think you'll find that you'll need openssl for:
libarchive, geom_eli, tar and gssd as well.
Good luck (I tried a few years ago but failed because I really needed
geli).


Got stuck elsewhere but looks like it's totally broken. This is a 
parallel build of r 295826 but looks pretty obvious where it bails:


/usr/src/gnu/lib/libreadline/readline/../../../../contrib/libreadline/bind.c:2051:20: 
note: use '==' to turn this assignment into an equality comparison

  for (i = 0; name = names[i]; i++)
   ^
   ==
--- display.o ---
--- lib__L ---
In file included from /usr/src/lib/libldns/../../contrib/ldns/parse.c:11:
In file included from 
/usr/src/lib/libldns/../../contrib/ldns/ldns/ldns.h:98:
/usr/src/lib/libldns/../../contrib/ldns/ldns/dane.h:31:10: fatal error: 
'openssl/ssl.h' file not found

#include 
 ^
--- gnu/lib__L ---
cc   -O2 -pipe   -I/usr/src/gnu/lib/libreadline/readline/.. 
-I/usr/src/gnu/lib/libreadline/readline/../../../../contrib/libreadline 
-DHAVE_CONFIG_H -DRL_LIBRARY_VERSION='"5.2"' -std=gnu99 
-Qunused-arguments  -fstack-protector   -c 
/usr/src/gnu/lib/libreadline/readline/../../../../contrib/libreadline/display.c 
-o display.o

--- lib__L ---
1 error generated.
--- gnu/lib__L ---
--- signals.o ---
cc   -O2 -pipe   -I/usr/src/gnu/lib/libreadline/readline/.. 
-I/usr/src/gnu/lib/libreadline/readline/../../../../contrib/libreadline 
-DHAVE_CONFIG_H -DRL_LIBRARY_VERSION='"5.2"' -std=gnu99 
-Qunused-arguments  -fstack-protector   -c 
/usr/src/gnu/lib/libreadline/readline/../../../../contrib/libreadline/signals.c 
-o signals.o

--- lib__L ---
In file included from /usr/src/lib/libldns/../../contrib/ldns/rdata.c:15:
In file included from 
/usr/src/lib/libldns/../../contrib/ldns/ldns/ldns.h:98:
/usr/src/lib/libldns/../../contrib/ldns/ldns/dane.h:31:10: fatal error: 
'openssl/ssl.h' file not found

#include 
 ^
1 error generated.
In file included from /usr/src/lib/libldns/../../contrib/ldns/resolver.c:15:
In file included from 
/usr/src/lib/libldns/../../contrib/ldns/ldns/ldns.h:98:
/usr/src/lib/libldns/../../contrib/ldns/ldns/dane.h:31:10: fatal error: 
'openssl/ssl.h' file not found

#include 
 ^
1 error generated.
--- depend_subdir_libnv ---
===> lib/libnv (depend)
--- depend_subdir_libopie ---
===> lib/libopie (depend)
--- depend_subdir_libldns ---
In file included from /usr/src/lib/libldns/../../contrib/ldns/rr.c:12:
In file included from 
/usr/src/lib/libldns/../../contrib/ldns/ldns/ldns.h:98:
/usr/src/lib/libldns/../../contrib/ldns/ldns/dan

Re: make buildworld Failure on 10-STABLE and WITHOUT_OPENSSL=TRUE

[Dewayne Geraghty]

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
> > Repository Root: https://svn.freebsd.org/base
> > Repository UUID: ccf9f872-aa2e-dd11-9fc8-001c23d0bc1f
> > Revision: 295341
> > Node Kind: directory
> > Schedule: normal
> > Last Changed Author: marius
> > Last Changed Rev: 295289
> > Last Changed Date: 2016-02-04 19:14:24 -0500 (Thu, 04 Feb 2016)
> >
> >
> > Still present:
> >
> > 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: 295351
> > Node Kind: directory
> > Schedule: normal
> > Last Changed Author: wblock
> > Last Changed Rev: 295350
> > Last Changed Date: 2016-02-06 09:03:31 -0500 (Sat, 06 Feb 2016)
> >
> >
> > root@rubicon:/usr/src # make clean && make buildworld
> >
> >
> > [snip]
> >
> >
> >
> > cc   -O2 -pipe   -I. -DINET6 -DFTP_COMBINE_CWDS -std=iso9899:1999
> > -Qunused-arguments  -fstack-protector -Wsystem-headers -Werror -Wall
> > -Wno-format-y2k -W -Wno-unused-parameter -Wstrict-prototypes
> > -Wmissing-prototypes -Wpointer-arith -Wreturn-type -Wcast-qual
> > -Wwrite-strings -Wswitch -Wshadow -Wunused-parameter -Wcast-align
> > -Wchar-subscripts -Winline -Wnested-externs -Wredundant-decls
> > -Wold-style-definition -Wmissing-variable-declarations -Wno-pointer-sign
> > -Wno-empty-body -Wno-string-plus-int -Wno-unused-const-variable  -c
> > /usr/src/lib/libfetch/common.c -o common.o
> > /usr/src/lib/libfetch/common.c:811:43: error: unused parameter 'URL'
> > [-Werror,-Wunused-parameter]
> > fetch_ssl(conn_t *conn, const struct url *URL, int verbose)
> >   ^
>
>
> Try this patch please:
> https://people.freebsd.org/~bdrewery/patches/libfetch-unused-ssl.patch


>
>
> --
> Regards,
> Bryan Drewery
>
>
Unfortunately, I think you'll find that you'll need openssl for:
libarchive, geom_eli, tar and gssd as well.
Good luck (I tried a few years ago but failed because I really needed
geli).
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: make buildworld Failure on 10-STABLE and WITHOUT_OPENSSL=TRUE

[Bryan Drewery]

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: ccf9f872-aa2e-dd11-9fc8-001c23d0bc1f
> Revision: 295341
> Node Kind: directory
> Schedule: normal
> Last Changed Author: marius
> Last Changed Rev: 295289
> Last Changed Date: 2016-02-04 19:14:24 -0500 (Thu, 04 Feb 2016)
> 
> 
> Still present:
> 
> 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: 295351
> Node Kind: directory
> Schedule: normal
> Last Changed Author: wblock
> Last Changed Rev: 295350
> Last Changed Date: 2016-02-06 09:03:31 -0500 (Sat, 06 Feb 2016)
> 
> 
> root@rubicon:/usr/src # make clean && make buildworld
> 
> 
> [snip]
> 
> 
> 
> cc   -O2 -pipe   -I. -DINET6 -DFTP_COMBINE_CWDS -std=iso9899:1999
> -Qunused-arguments  -fstack-protector -Wsystem-headers -Werror -Wall
> -Wno-format-y2k -W -Wno-unused-parameter -Wstrict-prototypes
> -Wmissing-prototypes -Wpointer-arith -Wreturn-type -Wcast-qual
> -Wwrite-strings -Wswitch -Wshadow -Wunused-parameter -Wcast-align
> -Wchar-subscripts -Winline -Wnested-externs -Wredundant-decls
> -Wold-style-definition -Wmissing-variable-declarations -Wno-pointer-sign
> -Wno-empty-body -Wno-string-plus-int -Wno-unused-const-variable  -c
> /usr/src/lib/libfetch/common.c -o common.o
> /usr/src/lib/libfetch/common.c:811:43: error: unused parameter 'URL'
> [-Werror,-Wunused-parameter]
> fetch_ssl(conn_t *conn, const struct url *URL, int verbose)
>   ^


Try this patch please:
https://people.freebsd.org/~bdrewery/patches/libfetch-unused-ssl.patch


-- 
Regards,
Bryan Drewery



signature.asc
Description: OpenPGP digital signature

make buildworld Failure on 10-STABLE and WITHOUT_OPENSSL=TRUE

[Jim Ohlstein]

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: directory
Schedule: normal
Last Changed Author: marius
Last Changed Rev: 295289
Last Changed Date: 2016-02-04 19:14:24 -0500 (Thu, 04 Feb 2016)


Still present:

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: 295351
Node Kind: directory
Schedule: normal
Last Changed Author: wblock
Last Changed Rev: 295350
Last Changed Date: 2016-02-06 09:03:31 -0500 (Sat, 06 Feb 2016)


root@rubicon:/usr/src # make clean && make buildworld


[snip]



cc   -O2 -pipe   -I. -DINET6 -DFTP_COMBINE_CWDS -std=iso9899:1999 
-Qunused-arguments  -fstack-protector -Wsystem-headers -Werror -Wall 
-Wno-format-y2k -W -Wno-unused-parameter -Wstrict-prototypes 
-Wmissing-prototypes -Wpointer-arith -Wreturn-type -Wcast-qual 
-Wwrite-strings -Wswitch -Wshadow -Wunused-parameter -Wcast-align 
-Wchar-subscripts -Winline -Wnested-externs -Wredundant-decls 
-Wold-style-definition -Wmissing-variable-declarations -Wno-pointer-sign 
-Wno-empty-body -Wno-string-plus-int -Wno-unused-const-variable  -c 
/usr/src/lib/libfetch/common.c -o common.o
/usr/src/lib/libfetch/common.c:811:43: error: unused parameter 'URL' 
[-Werror,-Wunused-parameter]

fetch_ssl(conn_t *conn, const struct url *URL, int verbose)
  ^
1 error generated.
*** Error code 1

Stop.
make[5]: stopped in /usr/src/lib/libfetch
*** Error code 1

Stop.
make[4]: stopped in /usr/src/lib
*** Error code 1

Stop.
make[3]: stopped in /usr/src
*** Error code 1

Stop.
make[2]: stopped in /usr/src
*** Error code 1

Stop.
make[1]: stopped in /usr/src
*** Error code 1

Stop.
make: stopped in /usr/src



I had several options enabled in /etc/src.conf but 
"WITHOUT_OPENSSL=TRUE" is the culprit. World builds fine as long as that 
is commented.


--
Jim Ohlstein


"Never argue with a fool, onlookers may not be able to tell the 
difference." - Mark Twain

___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: Buildworld failure on stable

[Matt Smith]

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 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 place with the same error. I'm trying it again without -j4 to
>>>see what happens. But isn't looking too good. :(
>>
>>Look like hardware error.
>>RAM/CPU/MB
>
>Interestingly it *always* manages to succesfully compile clang etc and
>it has no issues compiling things from ports. It fails compiling
>something from lib like openssl or kerberos.  Doesn't buildworld build
>a bootstrap version of clang and then use that version to compile the
>rest of it? I might try downgrading my sources back to the version
>that I last succesfully compiled just to prove it one way or the other
>to myself.
>

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 try and compile r287155 with -j4 then I get the bus errors. So
I'm not convinced at all that it's hardware related at the moment.

Not saying it is. But it still could be a region of CPU cache that
never got exercised, or in the right (same) manner.
Maybe use a CPU/RAM test program, just to be sure?

--Chris


Could be something wrong with it for sure. However I installed the 
world/kernel that I had succesfully compiled with the -j1, then I 
repeatedly tried more buildworlds with -j4 again. Can't get it to go 
wrong at all now. It has 4 cores which is why I'm using j4 by the way.  
I've run buildworld since with -j4 three different times, every one has 
worked. So either there is a hardware issue which for some reason I'm no 
longer hitting, or there may have been something weird with having 
r286908 installed whilst trying to compile r287155 with j4. I really 
have no idea at this point.


It's working now though, so I think I'll just see what happens over the 
next couple of months when I try further buildworlds. If it ever happens 
again then I'll do further tests, or just buy new hardware!


Thanks for all your advice though guys.

--
Matt
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: Buildworld failure on stable

[Chris H]

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 the point it fails. However I've
> >>>deleted /usr/obj and started the buildworld again and it failed in a
> >>>different place with the same error. I'm trying it again without -j4 to
> >>>see what happens. But isn't looking too good. :(
> >>
> >>Look like hardware error.
> >>RAM/CPU/MB
> >
> >Interestingly it *always* manages to succesfully compile clang etc and 
> >it has no issues compiling things from ports. It fails compiling 
> >something from lib like openssl or kerberos.  Doesn't buildworld build 
> >a bootstrap version of clang and then use that version to compile the 
> >rest of it? I might try downgrading my sources back to the version 
> >that I last succesfully compiled just to prove it one way or the other 
> >to myself.
> >
> 
> 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 try and compile r287155 with -j4 then I get the bus errors. So 
> I'm not convinced at all that it's hardware related at the moment.
Not saying it is. But it still could be a region of CPU cache that
never got exercised, or in the right (same) manner.
Maybe use a CPU/RAM test program, just to be sure?

--Chris
> 
> -- 
> Matt
> ___
> freebsd-stable@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-stable
> To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"


___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: Buildworld failure on stable

[David Wolfskill]

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 try and compile r287155 with -j4 then I get the bus errors. So 
> I'm not convinced at all that it's hardware related at the moment.
> ...

While it is not a complete list of the updates I do to FreeBSD machines,
I believe that  has
links to a selection that is reasonably representative of those I have
been doing recently.

For my builds, I use a -j value that is twice the reported value of
`sysctl -n hw.ncpu`.  For both my laptop and my build machine, that
works out to -j16.  For my work desktop (not depicted on the page), it's
-j24.

I'm not seeing the issues you're reporting.

Peace,
david
-- 
David H. Wolfskill  da...@catwhisker.org
Those who would murder in the name of God or prophet are blasphemous cowards.

See http://www.catwhisker.org/~david/publickey.gpg for my public key.


pgpqTHoPCeBdq.pgp
Description: PGP signature

Re: Buildworld failure on stable

[Matt Smith]

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 buildworld again and it failed in a
different place with the same error. I'm trying it again without -j4 to
see what happens. But isn't looking too good. :(


Look like hardware error.
RAM/CPU/MB


Interestingly it *always* manages to succesfully compile clang etc and 
it has no issues compiling things from ports. It fails compiling 
something from lib like openssl or kerberos.  Doesn't buildworld build 
a bootstrap version of clang and then use that version to compile the 
rest of it? I might try downgrading my sources back to the version 
that I last succesfully compiled just to prove it one way or the other 
to myself.




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 try and compile r287155 with -j4 then I get the bus errors. So 
I'm not convinced at all that it's hardware related at the moment.


--
Matt
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: Buildworld failure on stable

[Matt Smith]

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 place with the same error. I'm trying it again without -j4 to
see what happens. But isn't looking too good. :(


Look like hardware error.
RAM/CPU/MB


Interestingly it *always* manages to succesfully compile clang etc and 
it has no issues compiling things from ports. It fails compiling 
something from lib like openssl or kerberos.  Doesn't buildworld build a 
bootstrap version of clang and then use that version to compile the rest 
of it? I might try downgrading my sources back to the version that I 
last succesfully compiled just to prove it one way or the other to 
myself.


--
Matt
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: Buildworld failure on stable

[Slawa Olhovchenkov]

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?
> >>
> >> --- 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/crypto
> >> -I/usr/obj/usr/src/secure/lib/libcrypto -DOPENSSL_THREADS -DDSO_
> >> DLFCN -DHAVE_DLFCN_H -DL_ENDIAN -DOPENSSL_IA32_SSE2 -DAES_ASM
> >> -DBSAES_ASM -DVPAES_ASM -DOPENSSL_BN_ASM_MONT -DOP
> >> ENSSL_BN_ASM_MONT5 -DOPENSSL_BN_ASM_GF2m -DMD5_ASM -DGHASH_ASM
> >> -DSHA1_ASM -DSHA256_ASM -DSHA512_ASM -DWHIRLPOOL_
> >> ASM -I/usr/src/secure/lib/libcrypto/../../../crypto/openssl/crypto/asn1
> >> -I/usr/src/secure/lib/libcrypto/../../..
> >> /crypto/openssl/crypto/evp
> >> -I/usr/src/secure/lib/libcrypto/../../../crypto/openssl/crypto/modes
> >> -std=gnu89 -Qunu
> >> sed-arguments  -fstack-protector -Wno-pointer-sign -Wno-empty-body
> >> -Wno-string-plus-int -Wno-unused-const-variab
> >> le -Wno-tautological-compare -Wno-unused-value -Wno-parentheses-equality
> >> -Wno-unused-function -Wno-enum-conversi
> >> on -Wno-switch -Wno-switch-enum -Wno-knr-promoted-parameter
> >> -Wno-parentheses -c /usr/src/secure/lib/libcrypto/..
> >> /../../crypto/openssl/crypto/ocsp/ocsp_ext.c -o ocsp_ext.o
> >> --- obj_dat.o ---
> >> cc: error: unable to execute command: Bus error (core dumped)
> >> cc: error: clang frontend command failed due to signal (use -v to see
> >> invocation)
> >
> >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 place with the same error. I'm trying it again without -j4 to 
> see what happens. But isn't looking too good. :(

Look like hardware error.
RAM/CPU/MB
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re[2]: Buildworld failure on stable

[wishmaster]

  

--- 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 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/crypto
>> -I/usr/obj/usr/src/secure/lib/libcrypto -DOPENSSL_THREADS -DDSO_
>> DLFCN -DHAVE_DLFCN_H -DL_ENDIAN -DOPENSSL_IA32_SSE2 -DAES_ASM
>> -DBSAES_ASM -DVPAES_ASM -DOPENSSL_BN_ASM_MONT -DOP
>> ENSSL_BN_ASM_MONT5 -DOPENSSL_BN_ASM_GF2m -DMD5_ASM -DGHASH_ASM
>> -DSHA1_ASM -DSHA256_ASM -DSHA512_ASM -DWHIRLPOOL_
>> ASM -I/usr/src/secure/lib/libcrypto/../../../crypto/openssl/crypto/asn1
>> -I/usr/src/secure/lib/libcrypto/../../..
>> /crypto/openssl/crypto/evp
>> -I/usr/src/secure/lib/libcrypto/../../../crypto/openssl/crypto/modes
>> -std=gnu89 -Qunu
>> sed-arguments  -fstack-protector -Wno-pointer-sign -Wno-empty-body
>> -Wno-string-plus-int -Wno-unused-const-variab
>> le -Wno-tautological-compare -Wno-unused-value -Wno-parentheses-equality
>> -Wno-unused-function -Wno-enum-conversi
>> on -Wno-switch -Wno-switch-enum -Wno-knr-promoted-parameter
>> -Wno-parentheses -c /usr/src/secure/lib/libcrypto/..
>> /../../crypto/openssl/crypto/ocsp/ocsp_ext.c -o ocsp_ext.o
>> --- obj_dat.o ---
>> cc: error: unable to execute command: Bus error (core dumped)
>> cc: error: clang frontend command failed due to signal (use -v to see
>> invocation)
>
>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 place with the same error. I'm trying it again without -j4 to 
see what happens. But isn't looking too good. :(

-- 
Matt 
Hi, Matt. 
May be something wrong with src.conf or make.conf? 

Cheers, 
Vitaliy 

 ___
 freebsd-stable@freebsd.org  mailing list
 https://lists.freebsd.org/mailman/listinfo/freebsd-stable 
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
 

___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: Buildworld failure on stable

[Matt Smith]

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/secure/lib/libcrypto/../../../crypto/openssl -I/usr/src/secu
re/lib/libcrypto/../../../crypto/openssl/crypto
-I/usr/obj/usr/src/secure/lib/libcrypto -DOPENSSL_THREADS -DDSO_
DLFCN -DHAVE_DLFCN_H -DL_ENDIAN -DOPENSSL_IA32_SSE2 -DAES_ASM
-DBSAES_ASM -DVPAES_ASM -DOPENSSL_BN_ASM_MONT -DOP
ENSSL_BN_ASM_MONT5 -DOPENSSL_BN_ASM_GF2m -DMD5_ASM -DGHASH_ASM
-DSHA1_ASM -DSHA256_ASM -DSHA512_ASM -DWHIRLPOOL_
ASM -I/usr/src/secure/lib/libcrypto/../../../crypto/openssl/crypto/asn1
-I/usr/src/secure/lib/libcrypto/../../..
/crypto/openssl/crypto/evp
-I/usr/src/secure/lib/libcrypto/../../../crypto/openssl/crypto/modes
-std=gnu89 -Qunu
sed-arguments  -fstack-protector -Wno-pointer-sign -Wno-empty-body
-Wno-string-plus-int -Wno-unused-const-variab
le -Wno-tautological-compare -Wno-unused-value -Wno-parentheses-equality
-Wno-unused-function -Wno-enum-conversi
on -Wno-switch -Wno-switch-enum -Wno-knr-promoted-parameter
-Wno-parentheses -c /usr/src/secure/lib/libcrypto/..
/../../crypto/openssl/crypto/ocsp/ocsp_ext.c -o ocsp_ext.o
--- obj_dat.o ---
cc: error: unable to execute command: Bus error (core dumped)
cc: error: clang frontend command failed due to signal (use -v to see
invocation)


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 place with the same error. I'm trying it again without -j4 to 
see what happens. But isn't looking too good. :(


--
Matt
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: Buildworld failure on stable

[Slawa Olhovchenkov]

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/../../../crypto/openssl -I/usr/src/secu
> re/lib/libcrypto/../../../crypto/openssl/crypto 
> -I/usr/obj/usr/src/secure/lib/libcrypto -DOPENSSL_THREADS -DDSO_
> DLFCN -DHAVE_DLFCN_H -DL_ENDIAN -DOPENSSL_IA32_SSE2 -DAES_ASM 
> -DBSAES_ASM -DVPAES_ASM -DOPENSSL_BN_ASM_MONT -DOP
> ENSSL_BN_ASM_MONT5 -DOPENSSL_BN_ASM_GF2m -DMD5_ASM -DGHASH_ASM 
> -DSHA1_ASM -DSHA256_ASM -DSHA512_ASM -DWHIRLPOOL_
> ASM -I/usr/src/secure/lib/libcrypto/../../../crypto/openssl/crypto/asn1 
> -I/usr/src/secure/lib/libcrypto/../../..
> /crypto/openssl/crypto/evp 
> -I/usr/src/secure/lib/libcrypto/../../../crypto/openssl/crypto/modes 
> -std=gnu89 -Qunu
> sed-arguments  -fstack-protector -Wno-pointer-sign -Wno-empty-body 
> -Wno-string-plus-int -Wno-unused-const-variab
> le -Wno-tautological-compare -Wno-unused-value -Wno-parentheses-equality 
> -Wno-unused-function -Wno-enum-conversi
> on -Wno-switch -Wno-switch-enum -Wno-knr-promoted-parameter 
> -Wno-parentheses -c /usr/src/secure/lib/libcrypto/..
> /../../crypto/openssl/crypto/ocsp/ocsp_ext.c -o ocsp_ext.o
> --- obj_dat.o ---
> cc: error: unable to execute command: Bus error (core dumped)
> cc: error: clang frontend command failed due to signal (use -v to see 
> invocation)

Hardware error or memory exhausted
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Buildworld failure on stable

[Matt Smith]

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/crypto 
-I/usr/obj/usr/src/secure/lib/libcrypto -DOPENSSL_THREADS -DDSO_
DLFCN -DHAVE_DLFCN_H -DL_ENDIAN -DOPENSSL_IA32_SSE2 -DAES_ASM 
-DBSAES_ASM -DVPAES_ASM -DOPENSSL_BN_ASM_MONT -DOP
ENSSL_BN_ASM_MONT5 -DOPENSSL_BN_ASM_GF2m -DMD5_ASM -DGHASH_ASM 
-DSHA1_ASM -DSHA256_ASM -DSHA512_ASM -DWHIRLPOOL_
ASM -I/usr/src/secure/lib/libcrypto/../../../crypto/openssl/crypto/asn1 
-I/usr/src/secure/lib/libcrypto/../../..
/crypto/openssl/crypto/evp 
-I/usr/src/secure/lib/libcrypto/../../../crypto/openssl/crypto/modes 
-std=gnu89 -Qunu
sed-arguments  -fstack-protector -Wno-pointer-sign -Wno-empty-body 
-Wno-string-plus-int -Wno-unused-const-variab
le -Wno-tautological-compare -Wno-unused-value -Wno-parentheses-equality 
-Wno-unused-function -Wno-enum-conversi
on -Wno-switch -Wno-switch-enum -Wno-knr-promoted-parameter 
-Wno-parentheses -c /usr/src/secure/lib/libcrypto/..

/../../crypto/openssl/crypto/ocsp/ocsp_ext.c -o ocsp_ext.o
--- obj_dat.o ---
cc: error: unable to execute command: Bus error (core dumped)
cc: error: clang frontend command failed due to signal (use -v to see 
invocation)

FreeBSD clang version 3.4.1 (tags/RELEASE_34/dot1-final 208032) 20140512
Target: x86_64-unknown-freebsd10.2
Thread model: posix
cc: note: diagnostic msg: PLEASE submit a bug report to 
https://bugs.freebsd.org/submit/ and include the crash b

acktrace, preprocessed source, and associated run script.
cc: note: diagnostic msg: Error generating preprocessed source(s).
*** [obj_dat.o] Error code 254

make[4]: stopped in /usr/src/secure/lib/libcrypto


--
Matt
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: strange stable/9 buildworld failure

[Andriy Gapon]

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 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
>>> *** [libraries] Error code 2
>>>
>>>
>>> I could not find any actual error message in the build log.
>>> /usr/obj was cleaned out before the build.
>>>
>>
>> I was able to reproduce this exact failure 3 times in a row.
>> Running buildworld without -j allowed the build to proceed further.
>> Please note that my current userland is at (quite old) r248369, also 
>> stable/9.
> 
> Hi Andriy,
> 
> Can you please post the complete build log somewhere?  Maybe there is
> something unexpected going wrong which does not show a clear error
> message?

Sorry for the noise, all, it was a pilot error indeed.

-- 
Andriy Gapon
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: strange stable/9 buildworld failure

[Dimitry Andric]

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/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
>> *** [libraries] Error code 2
>> 
>> 
>> I could not find any actual error message in the build log.
>> /usr/obj was cleaned out before the build.
>> 
> 
> I was able to reproduce this exact failure 3 times in a row.
> Running buildworld without -j allowed the build to proceed further.
> Please note that my current userland is at (quite old) r248369, also stable/9.

Hi Andriy,

Can you please post the complete build log somewhere?  Maybe there is
something unexpected going wrong which does not show a clear error
message?

-Dimitry

___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: strange stable/9 buildworld failure

[Andriy Gapon]

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.so.80
> /usr/obj/usr/src/tmp/usr/lib/liblwres.so
> 1 error
> *** [libraries] Error code 2
> 
> 
> I could not find any actual error message in the build log.
> /usr/obj was cleaned out before the build.
> 

I was able to reproduce this exact failure 3 times in a row.
Running buildworld without -j allowed the build to proceed further.
Please note that my current userland is at (quite old) r248369, also stable/9.
-- 
Andriy Gapon
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

strange stable/9 buildworld failure

[Andriy Gapon]

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
*** [libraries] Error code 2


I could not find any actual error message in the build log.
/usr/obj was cleaned out before the build.

-- 
Andriy Gapon
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: 8-STABLE buildworld failure

[Bryce Edwards]

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 flags to see where
> the actual error happened.  The below doesn't show the actual error due
> to the nature of the parallel build.
>
> I doubt this has anything to do with ccache.
>

Thanks Jeremy, I forgot to disable paralllel builds.  It is very clear
now that it is related to the following in make.conf:

PORTS_MODULES=emulators/virtualbox-ose-kmod

Looks like the path of the make environment for the port doesn't find
yasm (which is indeed installed and located in /usr/local/bin/yasm).

cd ${PORTSDIR:-/usr/ports}/emulators/virtualbox-ose-kmod;
SYSDIR=/usr/src/sys /usr/obj/usr/src/make.amd64/make -B all
===>   virtualbox-ose-kmod-3.2.10 depends on executable: yasm - not found
===>Verifying install for yasm in /usr/ports/devel/yasm
===>  Installing for yasm-1.1.0
===>   yasm-1.1.0 depends on shared library: iconv.3 - found
===>   yasm-1.1.0 depends on shared library: intl - found
===>   Generating temporary packing list
===>  Checking if devel/yasm already installed
===>   yasm-1.1.0 is already installed
  You may wish to ``make deinstall'' and install this port again
  by ``make reinstall'' to upgrade it properly.
  If you really wish to overwrite the old port of devel/yasm
  without deleting it first, set the variable "FORCE_PKG_REGISTER"
  in your environment or the "make install" command line.
*** Error code 1

Stop in /usr/ports/devel/yasm.
*** Error code 1

Stop in /usr/ports/emulators/virtualbox-ose-kmod.
*** Error code 1

Stop in /usr/ports/emulators/virtualbox-ose-kmod.
*** Error code 1

Stop in /usr/obj/usr/src/sys/GENERIC.
*** Error code 1

Stop in /usr/src.
*** Error code 1

Stop in /usr/src.


>> ===> 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@/contrib/altq
>> -finline-limit=8000 --param inline-unit-growth=100 --param
>> large-function-growth=1000 -fno-common -g -fno-omit-frame-pointer
>> -I/usr/obj/usr/src/sys/GENERIC -mcmodel=kernel -mno-red-zone
>> -mfpmath=387 -mno-sse -mno-sse2 -mno-sse3 -mno-mmx -mno-3dnow
>> -msoft-float -fno-asynchronous-unwind-tables -ffreestanding
>> -fstack-protector -std=iso9899:1999 -fstack-protector -Wall
>> -Wredundant-decls -Wnested-externs -Wstrict-prototypes
>> -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual  -Wundef
>> -Wno-pointer-sign -fformat-extensions -c
>> /usr/src/sys/modules/zlib/../../net/zlib.c
>> ld  -d -warn-common -r -d -o zlib.ko.debug zlib.o
>> :> export_syms
>> awk -f /usr/src/sys/conf/kmod_syms.awk zlib.ko.debug  export_syms |
>> xargs -J% objcopy % zlib.ko.debug
>> objcopy --only-keep-debug zlib.ko.debug zlib.ko.symbols
>> objcopy --strip-debug --add-gnu-debuglink=zlib.ko.symbols zlib.ko.debug 
>> zlib.ko
>> 1 error
>> *** Error code 2
>> 1 error
>> *** Error code 2
>
> --
> | Jeremy Chadwick                                   j...@parodius.com |
> | Parodius Networking                       http://www.parodius.com/ |
> | UNIX Systems Administrator                  Mountain View, CA, USA |
> | Making life hard for others since 1977.              PGP: 4BD6C0CB |
>
>
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: 8-STABLE buildworld failure

[Jeremy Chadwick]

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 show the actual error due
to the nature of the parallel build.

I doubt this has anything to do with ccache.

> ===> 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@/contrib/altq
> -finline-limit=8000 --param inline-unit-growth=100 --param
> large-function-growth=1000 -fno-common -g -fno-omit-frame-pointer
> -I/usr/obj/usr/src/sys/GENERIC -mcmodel=kernel -mno-red-zone
> -mfpmath=387 -mno-sse -mno-sse2 -mno-sse3 -mno-mmx -mno-3dnow
> -msoft-float -fno-asynchronous-unwind-tables -ffreestanding
> -fstack-protector -std=iso9899:1999 -fstack-protector -Wall
> -Wredundant-decls -Wnested-externs -Wstrict-prototypes
> -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual  -Wundef
> -Wno-pointer-sign -fformat-extensions -c
> /usr/src/sys/modules/zlib/../../net/zlib.c
> ld  -d -warn-common -r -d -o zlib.ko.debug zlib.o
> :> export_syms
> awk -f /usr/src/sys/conf/kmod_syms.awk zlib.ko.debug  export_syms |
> xargs -J% objcopy % zlib.ko.debug
> objcopy --only-keep-debug zlib.ko.debug zlib.ko.symbols
> objcopy --strip-debug --add-gnu-debuglink=zlib.ko.symbols zlib.ko.debug 
> zlib.ko
> 1 error
> *** Error code 2
> 1 error
> *** Error code 2

-- 
| Jeremy Chadwick   j...@parodius.com |
| Parodius Networking   http://www.parodius.com/ |
| UNIX Systems Administrator  Mountain View, CA, USA |
| Making life hard for others since 1977.  PGP: 4BD6C0CB |

___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: 8-STABLE buildworld failure

[jhell]

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 -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@/contrib/altq
>>> -finline-limit=8000 --param inline-unit-growth=100 --param
>>> large-function-growth=1000 -fno-common -g -fno-omit-frame-pointer
>>> -I/usr/obj/usr/src/sys/GENERIC -mcmodel=kernel -mno-red-zone
>>> -mfpmath=387 -mno-sse -mno-sse2 -mno-sse3 -mno-mmx -mno-3dnow
>>> -msoft-float -fno-asynchronous-unwind-tables -ffreestanding
>>> -fstack-protector -std=iso9899:1999 -fstack-protector -Wall
>>> -Wredundant-decls -Wnested-externs -Wstrict-prototypes
>>> -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual  -Wundef
>>> -Wno-pointer-sign -fformat-extensions -c
>>> /usr/src/sys/modules/zlib/../../net/zlib.c
>>> ld  -d -warn-common -r -d -o zlib.ko.debug zlib.o
>>> :> export_syms
>>> awk -f /usr/src/sys/conf/kmod_syms.awk zlib.ko.debug  export_syms |
>>> xargs -J% objcopy % zlib.ko.debug
>>> objcopy --only-keep-debug zlib.ko.debug zlib.ko.symbols
>>> objcopy --strip-debug --add-gnu-debuglink=zlib.ko.symbols zlib.ko.debug 
>>> zlib.ko
>>> 1 error
>>> *** Error code 2
>>> 1 error
>>> *** Error code 2
>>>
>>> Here's make.conf:
>>>
>>> SUP_UPDATE=yes
>>> SUPFILE=/usr/share/examples/cvsup/stable-supfile
>>> PORTSSUPFILE=/usr/share/examples/cvsup/ports-supfile
>>> SUPHOST=cvsup5.us.freebsd.org
>>>
>>> #WITHOUT_X11=yes
>>>
>>> PORTS_MODULES=emulators/virtualbox-ose-kmod
>>>
>>> # ccache
>>> .if (!empty(.CURDIR:M/usr/src*) || !empty(.CURDIR:M/usr/obj*)) &&
>>> !defined(NOCCACHE)
>>> #CC=/usr/local/libexec/ccache/world-cc
>>> #CXX=/usr/local/libexec/ccache/world-c++
>>> .endif
>>>
>>> # added by use.perl 2010-11-09 09:32:27
>>> PERL_VERSION=5.10.1
>>>
>>> And src.conf:
>>>
>>> WITHOUT_PROFILE=true# Avoid compiling profiled libraries
>>
>> This is a log from a buildkernel and not like the subject insists as a
>> buildworld. Can you please rebuild world and then try a buildkernel
>>
>> cd /usr/src
>> make -DNOCCACHE -DALWAYS_CHECK_MAKE buildworld
>> make -DNOCCACHE -DALWAYS_CHECK_MAKE buildkernel
>> make -DNOCCACHE -DALWAYS_CHECK_MAKE installkernel
>>
>> Reboot & then:
>> cd /usr/src
>> make -DNOCCACHE installworld
>> make -DNOCCACHE delete-old
>> make -DNOCCACHE delete-old-libs
>>
> 
> My apologies!  The subject is wrong and it was during the buildkernel.
>  The buildworld was done just prior just like your example and
> completed OK.  The only difference is that I did not define
> ALWAYS_CHECK_MAKE.
> 

Also quoting UPDATING:

20101022:
A workaround for a fixed ld bug has been removed in kernel code,
so make sure that your system ld is built from sources after
revision 211583 from 2010-08-21 (r210245 from 2010-07-19 if
building stable/8 kernel on head, r211584 from 2010-08-21 for
stable/7).  A symptom of incorrect ld version is
different addresses for set_pcpu section and __start_set_pcpu
symbol in kernel and/or modules.

>>
>> You may also want to adjust that example ccache make.conf example
>> sometime too as that will not always do what you expect it to do.
>>
>> --
>>
>>  jhell,v
>>


-- 

 jhell,v
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: 8-STABLE buildworld failure

[Bryce Edwards]

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_MODULE
>> -nostdinc   -DHAVE_KERNEL_OPTION_HEADERS -include
>> /usr/obj/usr/src/sys/GENERIC/opt_global.h -I. -I@ -I@/contrib/altq
>> -finline-limit=8000 --param inline-unit-growth=100 --param
>> large-function-growth=1000 -fno-common -g -fno-omit-frame-pointer
>> -I/usr/obj/usr/src/sys/GENERIC -mcmodel=kernel -mno-red-zone
>> -mfpmath=387 -mno-sse -mno-sse2 -mno-sse3 -mno-mmx -mno-3dnow
>> -msoft-float -fno-asynchronous-unwind-tables -ffreestanding
>> -fstack-protector -std=iso9899:1999 -fstack-protector -Wall
>> -Wredundant-decls -Wnested-externs -Wstrict-prototypes
>> -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual  -Wundef
>> -Wno-pointer-sign -fformat-extensions -c
>> /usr/src/sys/modules/zlib/../../net/zlib.c
>> ld  -d -warn-common -r -d -o zlib.ko.debug zlib.o
>> :> export_syms
>> awk -f /usr/src/sys/conf/kmod_syms.awk zlib.ko.debug  export_syms |
>> xargs -J% objcopy % zlib.ko.debug
>> objcopy --only-keep-debug zlib.ko.debug zlib.ko.symbols
>> objcopy --strip-debug --add-gnu-debuglink=zlib.ko.symbols zlib.ko.debug 
>> zlib.ko
>> 1 error
>> *** Error code 2
>> 1 error
>> *** Error code 2
>>
>> Here's make.conf:
>>
>> SUP_UPDATE=yes
>> SUPFILE=/usr/share/examples/cvsup/stable-supfile
>> PORTSSUPFILE=/usr/share/examples/cvsup/ports-supfile
>> SUPHOST=cvsup5.us.freebsd.org
>>
>> #WITHOUT_X11=yes
>>
>> PORTS_MODULES=emulators/virtualbox-ose-kmod
>>
>> # ccache
>> .if (!empty(.CURDIR:M/usr/src*) || !empty(.CURDIR:M/usr/obj*)) &&
>> !defined(NOCCACHE)
>> #CC=/usr/local/libexec/ccache/world-cc
>> #CXX=/usr/local/libexec/ccache/world-c++
>> .endif
>>
>> # added by use.perl 2010-11-09 09:32:27
>> PERL_VERSION=5.10.1
>>
>> And src.conf:
>>
>> WITHOUT_PROFILE=true    # Avoid compiling profiled libraries
>
> This is a log from a buildkernel and not like the subject insists as a
> buildworld. Can you please rebuild world and then try a buildkernel
>
> cd /usr/src
> make -DNOCCACHE -DALWAYS_CHECK_MAKE buildworld
> make -DNOCCACHE -DALWAYS_CHECK_MAKE buildkernel
> make -DNOCCACHE -DALWAYS_CHECK_MAKE installkernel
>
> Reboot & then:
> cd /usr/src
> make -DNOCCACHE installworld
> make -DNOCCACHE delete-old
> make -DNOCCACHE delete-old-libs
>

My apologies!  The subject is wrong and it was during the buildkernel.
 The buildworld was done just prior just like your example and
completed OK.  The only difference is that I did not define
ALWAYS_CHECK_MAKE.

>
> You may also want to adjust that example ccache make.conf example
> sometime too as that will not always do what you expect it to do.
>
> --
>
>  jhell,v
>
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: 8-STABLE buildworld failure

[jhell]

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 -include
> /usr/obj/usr/src/sys/GENERIC/opt_global.h -I. -I@ -I@/contrib/altq
> -finline-limit=8000 --param inline-unit-growth=100 --param
> large-function-growth=1000 -fno-common -g -fno-omit-frame-pointer
> -I/usr/obj/usr/src/sys/GENERIC -mcmodel=kernel -mno-red-zone
> -mfpmath=387 -mno-sse -mno-sse2 -mno-sse3 -mno-mmx -mno-3dnow
> -msoft-float -fno-asynchronous-unwind-tables -ffreestanding
> -fstack-protector -std=iso9899:1999 -fstack-protector -Wall
> -Wredundant-decls -Wnested-externs -Wstrict-prototypes
> -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual  -Wundef
> -Wno-pointer-sign -fformat-extensions -c
> /usr/src/sys/modules/zlib/../../net/zlib.c
> ld  -d -warn-common -r -d -o zlib.ko.debug zlib.o
> :> export_syms
> awk -f /usr/src/sys/conf/kmod_syms.awk zlib.ko.debug  export_syms |
> xargs -J% objcopy % zlib.ko.debug
> objcopy --only-keep-debug zlib.ko.debug zlib.ko.symbols
> objcopy --strip-debug --add-gnu-debuglink=zlib.ko.symbols zlib.ko.debug 
> zlib.ko
> 1 error
> *** Error code 2
> 1 error
> *** Error code 2
> 
> Here's make.conf:
> 
> SUP_UPDATE=yes
> SUPFILE=/usr/share/examples/cvsup/stable-supfile
> PORTSSUPFILE=/usr/share/examples/cvsup/ports-supfile
> SUPHOST=cvsup5.us.freebsd.org
> 
> #WITHOUT_X11=yes
> 
> PORTS_MODULES=emulators/virtualbox-ose-kmod
> 
> # ccache
> .if (!empty(.CURDIR:M/usr/src*) || !empty(.CURDIR:M/usr/obj*)) &&
> !defined(NOCCACHE)
> #CC=/usr/local/libexec/ccache/world-cc
> #CXX=/usr/local/libexec/ccache/world-c++
> .endif
> 
> # added by use.perl 2010-11-09 09:32:27
> PERL_VERSION=5.10.1
> 
> And src.conf:
> 
> WITHOUT_PROFILE=true# Avoid compiling profiled libraries

This is a log from a buildkernel and not like the subject insists as a
buildworld. Can you please rebuild world and then try a buildkernel

cd /usr/src
make -DNOCCACHE -DALWAYS_CHECK_MAKE buildworld
make -DNOCCACHE -DALWAYS_CHECK_MAKE buildkernel
make -DNOCCACHE -DALWAYS_CHECK_MAKE installkernel

Reboot & then:
cd /usr/src
make -DNOCCACHE installworld
make -DNOCCACHE delete-old
make -DNOCCACHE delete-old-libs


You may also want to adjust that example ccache make.conf example
sometime too as that will not always do what you expect it to do.

-- 

 jhell,v
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

8-STABLE buildworld failure

[Bryce Edwards]

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@/contrib/altq
-finline-limit=8000 --param inline-unit-growth=100 --param
large-function-growth=1000 -fno-common -g -fno-omit-frame-pointer
-I/usr/obj/usr/src/sys/GENERIC -mcmodel=kernel -mno-red-zone
-mfpmath=387 -mno-sse -mno-sse2 -mno-sse3 -mno-mmx -mno-3dnow
-msoft-float -fno-asynchronous-unwind-tables -ffreestanding
-fstack-protector -std=iso9899:1999 -fstack-protector -Wall
-Wredundant-decls -Wnested-externs -Wstrict-prototypes
-Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual  -Wundef
-Wno-pointer-sign -fformat-extensions -c
/usr/src/sys/modules/zlib/../../net/zlib.c
ld  -d -warn-common -r -d -o zlib.ko.debug zlib.o
:> export_syms
awk -f /usr/src/sys/conf/kmod_syms.awk zlib.ko.debug  export_syms |
xargs -J% objcopy % zlib.ko.debug
objcopy --only-keep-debug zlib.ko.debug zlib.ko.symbols
objcopy --strip-debug --add-gnu-debuglink=zlib.ko.symbols zlib.ko.debug zlib.ko
1 error
*** Error code 2
1 error
*** Error code 2

Here's make.conf:

SUP_UPDATE=yes
SUPFILE=/usr/share/examples/cvsup/stable-supfile
PORTSSUPFILE=/usr/share/examples/cvsup/ports-supfile
SUPHOST=cvsup5.us.freebsd.org

#WITHOUT_X11=yes

PORTS_MODULES=emulators/virtualbox-ose-kmod

# ccache
.if (!empty(.CURDIR:M/usr/src*) || !empty(.CURDIR:M/usr/obj*)) &&
!defined(NOCCACHE)
#CC=/usr/local/libexec/ccache/world-cc
#CXX=/usr/local/libexec/ccache/world-c++
.endif

# added by use.perl 2010-11-09 09:32:27
PERL_VERSION=5.10.1

And src.conf:

WITHOUT_PROFILE=true# Avoid compiling profiled libraries
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Buildworld Failure with MODULES_WITH_WORLD=true

[Mark Skurzynski]

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
awk -f @/tools/vnode_if.awk @/kern/vnode_if.src -q
awk -f @/tools/vnode_if.awk @/kern/vnode_if.src -h
rm -f .depend
mkdep -f 
.depend -a   -nostdinc -D_KERNEL -DKLD_MODULE -I/usr/src/sys/modules/dtrace/dtmalloc/../../../cddl/compat/opensolaris 
-I/usr/src/sys/modules/dtrace/dtmalloc/../../../cddl/contrib/opensolaris/uts/common -I/usr/src/sys/modules/dtrace/dtmalloc/../../.. -I. -I@ -I@/contrib/altq/usr/src/sys/modules/dtrace/dtmalloc/../../../cddl/dev/dtmalloc/dtmalloc.c===> sys/modules/dtrace/dtrace (depend)@ -> /usr/src/sysmachine -> /usr/src/sys/amd64/includeawk -f @/tools/makeobjops.awk @/kern/bus_if.m -hawk -f @/tools/makeobjops.awk @/kern/device_if.m -hawk -f @/tools/vnode_if.awk @/kern/vnode_if.src -pawk -f @/tools/vnode_if.awk @/kern/vnode_if.src -qawk -f @/tools/vnode_if.awk @/kern/vnode_if.src -h:> opt_compat.h:> opt_kstack_pages.h:> opt_nfs.hcc -c -O2 -fno-strict-aliasing -pipe -DDIS_MEM -DSMP -DDEBUG -D_KERNEL -DKLD_MODULE -std=c99 -nostdinc -I/usr/src/sys/modules/dtrace/dtrace/../../../cddl/compat/opensolaris -I/usr/src/sys/modules/dtrace/dtrace/../../../cddl/dev/dtrace -I/usr/src/sys/modules/dtrace/dtrace/../../../cddl/dev/dtrace/amd64 -I/usr/src/sys/modules/dtrace/dtrace/../../../cddl/contrib/opensol

aris/uts/common -I/usr/src/sys/modules/dtrace/dtrace/../../.. -I. -I@ 
-I@/contrib/altq -finline-limit=8000 --param inline-unit-growth=100 
--paramlarge-function-growth=1000 -fno-omit-frame-pointer -mcmodel=kernel 
-mno-red-zone -mfpmath=387 -mno-sse -mno-sse2 -mno-mmx -mno-3dnow -msoft-float 
-fno-asynchronous-unwind-tables -ffreestanding -Wall -Wredundant-decls 
-Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith 
-Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions 
-Wno-unknown-pragmas@/amd64/amd64/genassym.c@/amd64/amd64/genassym.c:39:29: 
error: opt_hwpmc_hooks.h: No suchfile or directory*** Error code 1Stop in 
/usr/src/sys/modules/dtrace/dtrace.*** Error code 1Stop in 
/usr/src/sys/modules/dtrace.*** Error code 1Stop in /usr/src/sys/modules.*** 
Error code 1Stop in /usr/src/sys.*** Error code 1Stop in /usr/src.*** Error 
code 1Stop in /usr/src.*** Error code 1Stop in /usr/src.Any ideas on how to 
resolve this?Thank you,Mark--***
*  Mark Skurzynski  *  Lomag Internet Services, 
LLC  m...@lomag.net   *  http://www.lomag.net  Edison, NJ USA   *  
908-754-0221
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Buildworld Failure with MODULES_WITH_WORLD=true

[Mark Skurzynski]

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
awk -f @/tools/vnode_if.awk @/kern/vnode_if.src -q
awk -f @/tools/vnode_if.awk @/kern/vnode_if.src -h
rm -f .depend
mkdep -f 
.depend -a   -nostdinc -D_KERNEL -DKLD_MODULE -I/usr/src/sys/modules/dtrace/dtmalloc/../../../cddl/compat/opensolaris 
-I/usr/src/sys/modules/dtrace/dtmalloc/../../../cddl/contrib/opensolaris/uts/common -I/usr/src/sys/modules/dtrace/dtmalloc/../../.. -I. -I@ -I@/contrib/altq/usr/src/sys/modules/dtrace/dtmalloc/../../../cddl/dev/dtmalloc/dtmalloc.c===> sys/modules/dtrace/dtrace (depend)@ -> /usr/src/sysmachine -> /usr/src/sys/amd64/includeawk -f @/tools/makeobjops.awk @/kern/bus_if.m -hawk -f @/tools/makeobjops.awk @/kern/device_if.m -hawk -f @/tools/vnode_if.awk @/kern/vnode_if.src -pawk -f @/tools/vnode_if.awk @/kern/vnode_if.src -qawk -f @/tools/vnode_if.awk @/kern/vnode_if.src -h:> opt_compat.h:> opt_kstack_pages.h:> opt_nfs.hcc -c -O2 -fno-strict-aliasing -pipe -DDIS_MEM -DSMP -DDEBUG -D_KERNEL -DKLD_MODULE -std=c99 -nostdinc -I/usr/src/sys/modules/dtrace/dtrace/../../../cddl/compat/opensolaris -I/usr/src/sys/modules/dtrace/dtrace/../../../cddl/dev/dtrace -I/usr/src/sys/modules/dtrace/dtrace/../../../cddl/dev/dtrace/amd64 -I/usr/src/sys/modules/dtrace/dtrace/../../../cddl/contrib/opensol

aris/uts/common -I/usr/src/sys/modules/dtrace/dtrace/../../.. -I. -I@ 
-I@/contrib/altq -finline-limit=8000 --param inline-unit-growth=100 
--paramlarge-function-growth=1000 -fno-omit-frame-pointer -mcmodel=kernel 
-mno-red-zone -mfpmath=387 -mno-sse -mno-sse2 -mno-mmx -mno-3dnow -msoft-float 
-fno-asynchronous-unwind-tables -ffreestanding -Wall -Wredundant-decls 
-Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith 
-Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions 
-Wno-unknown-pragmas@/amd64/amd64/genassym.c@/amd64/amd64/genassym.c:39:29: 
error: opt_hwpmc_hooks.h: No suchfile or directory*** Error code 1Stop in 
/usr/src/sys/modules/dtrace/dtrace.*** Error code 1Stop in 
/usr/src/sys/modules/dtrace.*** Error code 1Stop in /usr/src/sys/modules.*** 
Error code 1Stop in /usr/src/sys.*** Error code 1Stop in /usr/src.*** Error 
code 1Stop in /usr/src.*** Error code 1Stop in /usr/src.Any ideas on how to 
resolve this?Thank you,Mark--***
*  Mark Skurzynski  *  Lomag Internet Services, 
LLC  m...@lomag.net   *  http://www.lomag.net  Edison, NJ USA   *  
908-754-0221
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

buildworld failure on SSH Makefile

[Eitan Adler]

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 ssh-keygen.1.cat.gz
rm -f .depend GPATH GRTAGS GSYMS GTAGS
===> secure/usr.bin/ssh-keyscan (cleandir)
rm -f ssh-keyscan ssh-keyscan.o ssh-keyscan.1.gz ssh-keyscan.1.cat.gz
rm -f .depend GPATH GRTAGS GSYMS GTAGS
===> secure/usr.sbin (cleandir)
===> secure/usr.sbin/sshd (cleandir)
rm -f sshd sshd.o auth-rhosts.o auth-passwd.o auth-rsa.o auth-rh-rsa.o
sshpty.o

sshlogin.o servconf.o serverloop.o auth.o auth1.o auth2.o auth-options.o
session

.o auth-chall.o auth2-chall.o groupaccess.o auth-skey.o auth-bsdauth.o
auth2-hos

tbased.o auth2-kbdint.o auth2-none.o auth2-passwd.o auth2-pubkey.o
monitor_mm.o

monitor.o monitor_wrap.o kexdhs.o kexgexs.o auth-krb5.o auth2-gss.o
gss-serv.o g

ss-serv-krb5.o loginrec.o auth-pam.o auth-shadow.o auth-sia.o md5crypt.o
audit.o

 audit-bsm.o platform.o sftp-server.o sftp-common.o gss-genr.o sshd.8.gz
sshd_co

nfig.5.gz sshd.8.cat.gz sshd_config.5.cat.gz
rm -f .depend GPATH GRTAGS GSYMS GTAGS
===> share (cleandir)
"Makefile", line 1: Need an operator
make: fatal errors encountered -- cannot continue
*** Error code 1

Stop in /home/src/mysrc/local.
*** Error code 1

Stop in /home/src/mysrc/local.
*** Error code 1

Stop in /home/src/mysrc/local.


-- 
Eitan Adler
"Security is increased by designing for the way humans actually behave."
-Jakob Nielsen
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

buildworld failure

[Jeff Dowsley]

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 answer wasn't in the archive.


(Built the 7.0 STABLE kernel and installed without any problems.)

Any clues?

TIA

JeffD


_
M 0427565791

[EMAIL PROTECTED]



___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: RELENG_7_0 buildworld failure on read only source tree

[David O'Brien]

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.

You need to add
.POSIX:
to the top of /usr/src/gnu/usr.bin/cvs/contrib/Makefile.

-- 
-- David  ([EMAIL PROTECTED])
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: RELENG_7_0 buildworld failure on read only source tree

[Bjoern A. Zeeb]

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 
yesterday and it failed to build with the following error:



[error snipped]


Should it be possible to build RELENG_7_0 with a read only source tree?


This can be worked around, I think touching the Makefile would do the 
trick.  IIRC David (cc'ed) has fixed the Makefile at some point this 
January while he is updating the base cvs(1) for this exact issue, maybe we 
should MFC the changeset to RELENG_7?


Cheers,



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.


I think it was this change:

http://docs.freebsd.org/cgi/mid.cgi?200801130945.m0D9jsgf040114

--
Bjoern A. Zeeb bzeeb at Zabbadoz dot NeT
Software is harder than hardware  so better get it right the first time.
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: RELENG_7_0 buildworld failure on read only source tree

[Tom Judge]

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 following error:



[error snipped]


Should it be possible to build RELENG_7_0 with a read only source tree?


This can be worked around, I think touching the Makefile would do the 
trick.  IIRC David (cc'ed) has fixed the Makefile at some point this 
January while he is updating the base cvs(1) for this exact issue, maybe 
we should MFC the changeset to RELENG_7?


Cheers,



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.


Thanks

Tom
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: RELENG_7_0 buildworld failure on read only source tree

[Xin LI]

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:



[error snipped]


Should it be possible to build RELENG_7_0 with a read only source tree?


This can be worked around, I think touching the Makefile would do the 
trick.  IIRC David (cc'ed) has fixed the Makefile at some point this 
January while he is updating the base cvs(1) for this exact issue, maybe 
we should MFC the changeset to RELENG_7?


Cheers,
--
Xin LI <[EMAIL PROTECTED]>http://www.delphij.net/
FreeBSD - The Power to Serve!
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

RELENG_7_0 buildworld failure on read only source tree

[Tom Judge]

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/cvs/cvs (cleandir)
rm -f cvs add.o admin.o annotate.o buffer.o checkin.o checkout.o 
classify.o client.o commit.o create_adm.o cvsrc.o diff.o edit.o 
entries.o error.o expand_path.o fileattr.o filesubr.o find_names.o 
hardlink.o hash.o history.o ignore.o import.o lock.o log.o login.o 
logmsg.o main.o mkmodules.o modules.o myndbm.o no_diff.o parseinfo.o 
patch.o prepend_args.o rcs.o rcscmds.o recurse.o release.o remove.o 
repos.o root.o run.o scramble.o server.o stack.o status.o subr.o tag.o 
update.o vers_ts.o version.o watch.o wrapper.o zlib.o cvs.1.gz cvs.5.gz 
cvs.1.cat.gz cvs.5.cat.gz

rm -rf cvs-sanity
rm -f .depend GPATH GRTAGS GSYMS GTAGS
===> gnu/usr.bin/cvs/contrib (cleandir)
sed -e 's,@CSH@,/bin/csh,' -e 's,@PERL@,/usr/bin/perl,' 
/usr/src/gnu/usr.bin/cvs/contrib/../../../../contrib/cvs/contrib/Makefile.in 
> Makefile

cannot create Makefile: Read-only file system
*** Error code 2

Stop in /usr/src/gnu/usr.bin/cvs/contrib.
*** Error code 1

Stop in /usr/src/gnu/usr.bin/cvs.
*** Error code 1

Stop in /usr/src/gnu/usr.bin.
*** Error code 1

Stop in /usr/src/gnu.
*** Error code 1

Stop in /usr/src.
*** Error code 1

Stop in /usr/src.
*** Error code 1

Stop in /usr/src.


Should it be possible to build RELENG_7_0 with a read only source tree?

Thanks

Tom
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

6.2-RELEASE buildworld failure

[ota]

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
--
cd /usr/src; MAKEOBJDIRPREFIX=/usr/obj  INSTALL="sh 
/usr/src/tools/install.sh" 
PATH=/usr/obj/usr/src/tmp/legacy/usr/sbin:/usr/obj/usr/src/tmp/legacy/usr/bin:/usr/obj/usr/src/tmp/legacy/usr/games:/sbin:/bin:/usr/sbin:/usr/bin 
 WORLDTMP=/usr/obj/usr/src/tmp  MAKEFLAGS="-m /usr/src/tools/build/mk 
-m /usr/src/share/mk" make -f Makefile.inc1  TARGET=i386 
TARGET_ARCH=i386  DESTDIR=  BOOTSTRAPPING=602114 -DNO_LINT 
-DNO_CPU_CFLAGS -DNO_WARNS build-tools

===> bin/csh (obj,build-tools)
grep 'ERR_' /usr/src/bin/csh/../../contrib/tcsh/sh.err.c | grep 
'^#define' >> sh.err.h
cc -E -O2 -fno-strict-aliasing -pipe -I. -I/usr/src/bin/csh 
-I/usr/src/bin/csh/../../contrib/tcsh -D_PATH_TCSHELL='"/bin/csh"' 
-DHAVE_ICONV  -I/usr/obj/usr/src/tmp/legacy/usr/include 
/usr/src/bin/csh/../../contrib/tcsh/tc.const.c 
/usr/src/bin/csh/../../contrib/tcsh/sh.char.h /usr/src/bin/csh/config.h 
/usr/src/bin/csh/../../contrib/tcsh/config_f.h 
/usr/src/bin/csh/../../contrib/tcsh/sh.types.h sh.err.h -D_h_tc_const | 
grep 'Char STR' |  sed -e 's/Char \([a-zA-Z0-9_]*\)\(.*\)/extern Char 
\1[];/' |  sort >> tc.const.h
cc -o gethost  -L/usr/obj/usr/src/tmp/legacy/usr/lib -O2 
-fno-strict-aliasing -pipe -I. -I/usr/src/bin/csh 
-I/usr/src/bin/csh/../../contrib/tcsh -D_PATH_TCSHELL='"/bin/csh"' 
-DHAVE_ICONV  -I/usr/obj/usr/src/tmp/legacy/usr/include 
/usr/src/bin/csh/../../contrib/tcsh/gethost.c

/var/tmp//cck5eSfw.o(.text+0x25): In function `gettoken':
: undefined reference to `__sbmaskrune'
/var/tmp//cck5eSfw.o(.text+0x60): In function `gettoken':
: undefined reference to `__sbmaskrune'
*** Error code 1

Stop in /usr/src/bin/csh.
*** Error code 1

Stop in /usr/src.
*** Error code 1

Stop in /usr/src.
*** Error code 1

Stop in /usr/src.


Any ideas?


Russell Doucette
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

buildworld failure (boot2.ld too big when CFLAGS set in make.conf)

[Josh Carroll]

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  -fomit-frame-pointer
-fno-unit-at-a-time  -mno-align-long-strings  -mrtd  -mno-mmx
-mno-3dnow -mno-sse -mno-sse2 -mno-sse3  -DUFS1_AND_UFS2  -DFLAGS=0x80
 -DSIOPRT=0x3f8  -DSIOFMT=0x3  -DSIOSPD=9600
-I/usr/src/sys/boot/i386/boot2/../../common
-I/usr/src/sys/boot/i386/boot2/../btx/lib -I.  -Wall
-Waggregate-return -Wbad-function-cast -Wcast-align
-Wmissing-declarations -Wmissing-prototypes -Wnested-externs
-Wpointer-arith -Wshadow -Wstrict-prototypes -Wwrite-strings  -Winline
--param max-inline-insns-single=100 -ffreestanding
-mpreferred-stack-boundary=2  -mno-mmx -mno-3dnow -mno-sse -mno-sse2
-mno-sse3 -m32 -march=i386 -O2 -mmmx -msse -msse2 -msse3 -pipe  -S -o
boot2.s.tmp /usr/src/sys/boot/i386/boot2/boot2.c

Since CFLAGS defined in make.conf are being tacked onto the calls to
cc, and the last -O argument is the one that's effective with gcc,
it's effectively building with O2 optimizations instead of Os to
target smaller code size.

Here is my entry in make.conf:

CFLAGS+=-O2 -mmmx -msse -msse2 -msse3 -pipe

To avoid this, I wrapped setting CFLAGS with an .if so it doesn't
happen for the boot2 build:

# don't append to CFLAGS here, it breaks compilation of boot2.
.if ! ${.CURDIR:M*/boot/i386/boot2*}
CFLAGS+=-O2 -mmmx -msse -msse2 -msse3 -pipe
.endif

But is there a better way to do this? I don't think using -O2 is
overly aggressive for building world/ports, but obviously for things
that require a small code size, it's going to break. Is what I'm doing
above the best work around? Or am I missing an easier/more standard
solution? Can I prepend to a variable in make.conf instead of
appending (so that -Os comes _after_ -O2)?

Thanks,
Josh
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: sparc64 buildworld failure (NOT: LOR with today's RELENG_6)

[Kris Kennaway]

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'
> /usr/src/sbin/gbde/gbde.c:804: error: `optarg' undeclared (first use
> in this function)
> /usr/src/sbin/gbde/gbde.c:804: error: (Each undeclared identifier is
> reported only once
> /usr/src/sbin/gbde/gbde.c:804: error: for each function it appears in.)
> *** Error code 1

I guess something is wrong with your installed headers, perhaps you
spammed  with the GNU version?

Kris


pgpRKLSsODjSq.pgp
Description: PGP signature

buildworld failure in libexec.mail.local on 6.1 Release

[Victor Sherstniov]

 

 

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, needed by
> /usr/local/lib/libsasl.so, not found (try using -rpath or -rpath-link)
> /usr/obj/usr/src/tmp/usr/bin/ld: warning: liblber-2.2.so.7, needed by
> /usr/local/lib/libsasl.so, not found (try using -rpath or -rpath-link)
> /usr/local/lib/libsasl.so: undefined reference to `ldap_get_dn'
> /usr/local/lib/libsasl.so: undefined reference to `ldap_unbind'
> /usr/local/lib/libsasl.so: undefined reference to `ldap_first_entry'
> /usr/local/lib/libsasl.so: undefined reference to `ldap_simple_bind_s'
> /usr/local/lib/libsasl.so: undefined reference to `ldap_set_option'
> /usr/local/lib/libsasl.so: undefined reference to `ldap_memfree'
> /usr/local/lib/libsasl.so: undefined reference to `ldap_init'
> /usr/local/lib/libsasl.so: undefined reference to `ldap_search_ext_s'
> /usr/local/lib/libsasl.so: undefined reference to `ldap_msgfree'
> 
> >From stdout I had
> ===> libexec/mail.local (all)
> cc -O2 -pipe -funroll-loops -march=pentium3m
> -I/usr/src/libexec/mail.local/../../contrib/sendmail/include -I.
> -I/usr/local/include/sasl1 -DSASL  -c
> /usr/src/libexec/mail.local/../../contrib/sendmail/mail.local/mail.local.c
> cc -O2 -pipe -funroll-loops -march=pentium3m
> -I/usr/src/libexec/mail.local/../../contrib/sendmail/include -I.
> -I/usr/local/include/sasl1 -DSASL   -L/usr/local/lib -o mail.local
> mail.local.o /usr/obj/usr/src/libexec/mail.local/../../lib/libsm/libsm.a
> -lsasl
> *** Error code 1
 
>I guess you're trying to use a sendmail compiled with SMTP AUTH support.
>I have the same problem here.
 
>Even though libldap-2.2.so.7 and liblber-2.2.so.7 are in /usr/local/lib
>and cc has a -L/usr/local/lib flag, ld doesn't find them.
 
>Even putting the libraries in /usr/lib doesn't correct this error.
 

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/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

buildworld failure in libexec.mail.local on 6.1 Release

[Victor Sherstniov]

 

 

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/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: buildworld failure in libexec.mail.local on 6.1 Release

[Francois Tigeot]

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/src/tmp/usr/bin/ld: warning: libldap-2.2.so.7, needed by
> /usr/local/lib/libsasl.so, not found (try using -rpath or -rpath-link)
> /usr/obj/usr/src/tmp/usr/bin/ld: warning: liblber-2.2.so.7, needed by
> /usr/local/lib/libsasl.so, not found (try using -rpath or -rpath-link)
> /usr/local/lib/libsasl.so: undefined reference to `ldap_get_dn'
> /usr/local/lib/libsasl.so: undefined reference to `ldap_unbind'
> /usr/local/lib/libsasl.so: undefined reference to `ldap_first_entry'
> /usr/local/lib/libsasl.so: undefined reference to `ldap_simple_bind_s'
> /usr/local/lib/libsasl.so: undefined reference to `ldap_set_option'
> /usr/local/lib/libsasl.so: undefined reference to `ldap_memfree'
> /usr/local/lib/libsasl.so: undefined reference to `ldap_init'
> /usr/local/lib/libsasl.so: undefined reference to `ldap_search_ext_s'
> /usr/local/lib/libsasl.so: undefined reference to `ldap_msgfree'
> 
> >From stdout I had
> ===> libexec/mail.local (all)
> cc -O2 -pipe -funroll-loops -march=pentium3m
> -I/usr/src/libexec/mail.local/../../contrib/sendmail/include -I.
> -I/usr/local/include/sasl1 -DSASL  -c
> /usr/src/libexec/mail.local/../../contrib/sendmail/mail.local/mail.local.c
> cc -O2 -pipe -funroll-loops -march=pentium3m
> -I/usr/src/libexec/mail.local/../../contrib/sendmail/include -I.
> -I/usr/local/include/sasl1 -DSASL   -L/usr/local/lib -o mail.local
> mail.local.o /usr/obj/usr/src/libexec/mail.local/../../lib/libsm/libsm.a
> -lsasl
> *** Error code 1

I guess you're trying to use a sendmail compiled with SMTP AUTH support.
I have the same problem here.

Even though libldap-2.2.so.7 and liblber-2.2.so.7 are in /usr/local/lib
and cc has a -L/usr/local/lib flag, ld doesn't find them.

Even putting the libraries in /usr/lib doesn't correct this error.

-- 
Francois Tigeot
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: buildworld failure in libexec.mail.local on 6.1 Release

[Duane Whitty]

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
/usr/local/lib/libsasl.so, not found (try using -rpath or -rpath-link)
/usr/obj/usr/src/tmp/usr/bin/ld: warning: liblber-2.2.so.7, needed by
/usr/local/lib/libsasl.so, not found (try using -rpath or -rpath-link)
/usr/local/lib/libsasl.so: undefined reference to `ldap_get_dn'
/usr/local/lib/libsasl.so: undefined reference to `ldap_unbind'
/usr/local/lib/libsasl.so: undefined reference to `ldap_first_entry'
/usr/local/lib/libsasl.so: undefined reference to `ldap_simple_bind_s'
/usr/local/lib/libsasl.so: undefined reference to `ldap_set_option'
/usr/local/lib/libsasl.so: undefined reference to `ldap_memfree'
/usr/local/lib/libsasl.so: undefined reference to `ldap_init'
/usr/local/lib/libsasl.so: undefined reference to `ldap_search_ext_s'
/usr/local/lib/libsasl.so: undefined reference to `ldap_msgfree'


From stdout I had

===> libexec/mail.local (all)
cc -O2 -pipe -funroll-loops -march=pentium3m
-I/usr/src/libexec/mail.local/../../contrib/sendmail/include -I.
-I/usr/local/include/sasl1 -DSASL  -c
/usr/src/libexec/mail.local/../../contrib/sendmail/mail.local/mail.local.c 


cc -O2 -pipe -funroll-loops -march=pentium3m
-I/usr/src/libexec/mail.local/../../contrib/sendmail/include -I.
-I/usr/local/include/sasl1 -DSASL   -L/usr/local/lib -o mail.local
mail.local.o /usr/obj/usr/src/libexec/mail.local/../../lib/libsm/libsm.a
-lsasl
*** Error code 1

Stop in /usr/src/libexec/mail.local.
*** Error code 1

Stop in /usr/src/libexec.
*** Error code 1

Stop in /usr/src.
*** Error code 1

Stop in /usr/src.
*** Error code 1

Stop in /usr/src.

portversion -v on ldap shows
[EMAIL PROTECTED]:~]# portversion -v | grep ldap
openldap-client-2.2.30  =  up-to-date with port

And in /usr/local/lib I do find
lrwxr-xr-x   1 root  wheel   16 Jan 18 23:27 liblber-2.2.so ->
liblber-2.2.so.7
-rw-r--r--   1 root  wheel67109 Jan 18 23:27 liblber-2.2.so.7
-rw-r--r--   1 root  wheel73738 Jan 18 23:27 liblber.a
lrwxr-xr-x   1 root  wheel   16 Jan 18 23:27 liblber.so -> 
liblber-2.2.so.7

lrwxr-xr-x   1 root  wheel   16 Jan 18 23:27 libldap-2.2.so ->
libldap-2.2.so.7
-rw-r--r--   1 root  wheel   233395 Jan 18 23:27 libldap-2.2.so.7
-rw-r--r--   1 root  wheel   278908 Jan 18 23:27 libldap.a
lrwxr-xr-x   1 root  wheel   16 Jan 18 23:27 libldap.so -> 
libldap-2.2.so.7

lrwxr-xr-x   1 root  wheel   18 Jan 18 23:27 libldap_r-2.2.so ->
libldap_r-2.2.so.7
-rw-r--r--   1 root  wheel   254255 Jan 18 23:27 libldap_r-2.2.so.7
-rw-r--r--   1 root  wheel   310072 Jan 18 23:27 libldap_r.a
lrwxr-xr-x   1 root  wheel   18 Jan 18 23:27 libldap_r.so ->
libldap_r-2.2.so.7

[EMAIL PROTECTED]:/usr/local/lib]# uname -a
FreeBSD beastie 6.0-STABLE FreeBSD 6.0-STABLE #1: Tue Jan 17 12:53:38
CET 2006 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/BEASTIE6  i386

Probably something obvious that I'm missing?

Thanks in advance,

Spil
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"




What's in your /etc/make.conf?

Duane Whitty
--
[EMAIL PROTECTED]
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

buildworld failure in libexec.mail.local on 6.1 Release

[Spil Oss]

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/libsasl.so, not found (try using -rpath or -rpath-link)
/usr/obj/usr/src/tmp/usr/bin/ld: warning: liblber-2.2.so.7, needed by
/usr/local/lib/libsasl.so, not found (try using -rpath or -rpath-link)
/usr/local/lib/libsasl.so: undefined reference to `ldap_get_dn'
/usr/local/lib/libsasl.so: undefined reference to `ldap_unbind'
/usr/local/lib/libsasl.so: undefined reference to `ldap_first_entry'
/usr/local/lib/libsasl.so: undefined reference to `ldap_simple_bind_s'
/usr/local/lib/libsasl.so: undefined reference to `ldap_set_option'
/usr/local/lib/libsasl.so: undefined reference to `ldap_memfree'
/usr/local/lib/libsasl.so: undefined reference to `ldap_init'
/usr/local/lib/libsasl.so: undefined reference to `ldap_search_ext_s'
/usr/local/lib/libsasl.so: undefined reference to `ldap_msgfree'


From stdout I had

===> libexec/mail.local (all)
cc -O2 -pipe -funroll-loops -march=pentium3m
-I/usr/src/libexec/mail.local/../../contrib/sendmail/include -I.
-I/usr/local/include/sasl1 -DSASL  -c
/usr/src/libexec/mail.local/../../contrib/sendmail/mail.local/mail.local.c
cc -O2 -pipe -funroll-loops -march=pentium3m
-I/usr/src/libexec/mail.local/../../contrib/sendmail/include -I.
-I/usr/local/include/sasl1 -DSASL   -L/usr/local/lib -o mail.local
mail.local.o /usr/obj/usr/src/libexec/mail.local/../../lib/libsm/libsm.a
-lsasl
*** Error code 1

Stop in /usr/src/libexec/mail.local.
*** Error code 1

Stop in /usr/src/libexec.
*** Error code 1

Stop in /usr/src.
*** Error code 1

Stop in /usr/src.
*** Error code 1

Stop in /usr/src.

portversion -v on ldap shows
[EMAIL PROTECTED]:~]# portversion -v | grep ldap
openldap-client-2.2.30  =  up-to-date with port

And in /usr/local/lib I do find
lrwxr-xr-x   1 root  wheel   16 Jan 18 23:27 liblber-2.2.so ->
liblber-2.2.so.7
-rw-r--r--   1 root  wheel67109 Jan 18 23:27 liblber-2.2.so.7
-rw-r--r--   1 root  wheel73738 Jan 18 23:27 liblber.a
lrwxr-xr-x   1 root  wheel   16 Jan 18 23:27 liblber.so -> liblber-2.2.so.7
lrwxr-xr-x   1 root  wheel   16 Jan 18 23:27 libldap-2.2.so ->
libldap-2.2.so.7
-rw-r--r--   1 root  wheel   233395 Jan 18 23:27 libldap-2.2.so.7
-rw-r--r--   1 root  wheel   278908 Jan 18 23:27 libldap.a
lrwxr-xr-x   1 root  wheel   16 Jan 18 23:27 libldap.so -> libldap-2.2.so.7
lrwxr-xr-x   1 root  wheel   18 Jan 18 23:27 libldap_r-2.2.so ->
libldap_r-2.2.so.7
-rw-r--r--   1 root  wheel   254255 Jan 18 23:27 libldap_r-2.2.so.7
-rw-r--r--   1 root  wheel   310072 Jan 18 23:27 libldap_r.a
lrwxr-xr-x   1 root  wheel   18 Jan 18 23:27 libldap_r.so ->
libldap_r-2.2.so.7

[EMAIL PROTECTED]:/usr/local/lib]# uname -a
FreeBSD beastie 6.0-STABLE FreeBSD 6.0-STABLE #1: Tue Jan 17 12:53:38
CET 2006 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/BEASTIE6  i386

Probably something obvious that I'm missing?

Thanks in advance,

Spil
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: 5.4 -> 6.0 buildworld failure

[Anthony Chavez]

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:/usr/local/include:/usr/X11R6/include
> export CPLUS_INCLUDE_PATH=$C_INCLUDE_PATH export
> LIBRARY_PATH=/usr/lib:/usr/local/lib export LD_LIBRARY_PATH=. 

Thanks for the info, Markus.  I didn't have anything of the sort in my
shell config, but fortunately after I upgraded to 5.4-RELEASE-p11, I
executed a successful buildworld for 6.0-RELEASE.

Cheers!

-- 
Anthony Chavez http://anthonychavez.org/
mailto:[EMAIL PROTECTED] jabber:[EMAIL PROTECTED]


pgp3vMMxaRaGG.pgp
Description: PGP signature

Re: 5.4 -> 6.0 buildworld failure

[Anthony Chavez]

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 -p8.  Each of these machines
has a unique hardware configuration, and the one that fails to
buildworld is no exception.

I have tried an empty /etc/make.conf as well as specifically including
"CFLAGS=-O -pipe" therein.  I have also tried a default /etc/profile.
The build still fails.

I'm thinking that the best course of action might be to upgrade to
5.4-RELEASE-p11 (which builds successfully), but I'm very interested to
know what's causing this error in case my intended course of action
doesn't work.  The commit logs show no changes for this particular file
since well before this problem was reported, so the problem must have
lied somewhere else in the source tree.

Any ideas what could be causing this?  Am I on the right track?  I have
included my dmesg.boot below.

Cheers!

On Sat, 05 Nov 2005 23:49:34 +0100 Markus Buretorp <[EMAIL PROTECTED]> wrote:

> 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/libkvm/kvm_proc.c:108: error: storage size of 't_cdev'
>>>  isn't known
>>
>>Where is this error occurring during the buildworld?  (What are the
>>latest lines beginning '>>>' and '===>')
>>What non-standard bits do you have in your command line, /etc/make.conf
>>or MAKEOBJDIRPREFIX?
>
>  >>> stage 4.2: building libraries
> ...
> ===> lib/libkvm (depend,all,install)
>
> make.conf:
>
> WITHOUT_X11=yes
> CPUTYPE?=athlon-xp
> CFLAGS=-O2 -pipe
> COPTFLAGS=-O -pipe
> # added by use.perl 2005-06-24 23:01:50
> PERL_VER=5.8.7
> PERL_VERSION=5.8.7
>
> Note, I've tried without the first four lines.
>
> $ cd lib/libkvm
> /usr/src [EMAIL PROTECTED]
> $ make
> ...r/src/lib/libkvm [EMAIL PROTECTED]
> cc -O -pipe  -DLIBC_SCCS -I/usr/src/lib/libkvm  -c
> /usr/src/lib/libkvm/kvm_proc.c
> /usr/src/lib/libkvm/kvm_proc.c: In function `kvm_proclist':
> /usr/src/lib/libkvm/kvm_proc.c:108: error: storage size of 't_cdev'
> isn't known
> /usr/src/lib/libkvm/kvm_proc.c:114: error: storage size of 'pr'
> isn't known
> /usr/src/lib/libkvm/kvm_proc.c:176: error: structure has no member
> named `ki_jid'
> /usr/src/lib/libkvm/kvm_proc.c:377: error: structure has no member
> named `p_rux'
> *** Error code 1
>
> Stop in /usr/src/lib/libkvm.
>
> I found this, http://www.freebsd.org/cgi/query-pr.cgi?pr=77821 , but
> it doesn't help me much. I don't now what I've done. I've used cvsup
> and buildworld several times.

-- 
Anthony Chavez http://anthonychavez.org/
mailto:[EMAIL PROTECTED] jabber:[EMAIL PROTECTED]

--8<---cut here---start->8---
Copyright (c) 1992-2005 The FreeBSD Project.
Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
The Regents of the University of California. All rights reserved.
FreeBSD 5.4-RELEASE-p4 #1: Sun Sep 11 20:13:50 MDT 2005
[EMAIL PROTECTED]:/usr/obj/usr/src/sys/MYBOX
WARNING: debug.mpsafenet forced to 0 as ipsec requires Giant
WARNING: MPSAFE network stack disabled, expect reduced performance.
Timecounter "i8254" frequency 1193182 Hz quality 0
CPU: Intel(R) Pentium(R) 4 CPU 3.00GHz (3010.67-MHz 686-class CPU)
  Origin = "GenuineIntel"  Id = 0xf41  Stepping = 1
  
Features=0xbfebfbff
  Hyperthreading: 2 logical CPUs
real memory  = 1073414144 (1023 MB)
avail memory = 1040855040 (992 MB)
ACPI APIC Table: 
ioapic0  irqs 0-23 on motherboard
npx0:  on motherboard
npx0: INT 16 interface
acpi0:  on motherboard
acpi_bus_number: can't get _ADR
acpi_bus_number: can't get _ADR
acpi_bus_number: can't get _ADR
acpi_bus_number: can't get _ADR
acpi_bus_number: can't get _ADR
acpi_bus_number: can't get _ADR
acpi0: Power Button (fixed)
acpi_bus_number: can't get _ADR
acpi_bus_number: can't get _ADR
Timecounter "ACPI-safe" frequency 3579545 Hz quality 1000
acpi_timer0: <24-bit timer at 3.579545MHz> port 0x808-0x80b on acpi0
cpu0:  on acpi0
acpi_throttle0:  on cpu0
pcib0:  port 0xcf8-0xcff on acpi0
pci0:  on pcib0
pcib1:  at device 28.0 on pci0
pci2:  on pcib1
uhci0:  port 0xb880-0xb89f 
irq 23 at device 29.0 on pci0
usb0:  on uhci0
usb0: USB revision 1.0
uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1
uhub0: 2 ports with 2 removable, self powered
uhci1:  port 0xbc00-0xbc1f 
irq 19 at device 29.1 on pci0
usb1:  on uhci1
usb1: USB revision 1.0
uhub1: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1
uhub1: 2 ports with 2 removable, self powered

RE: Upgrading 5.3 > 6.0 buildworld failure now in libmagic

[vizion]

> > > 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 if they choose to argue ad
personam, or make patently incorrect and illogical statements and then do
not apologize afterwards. 

Your loss - not mine

Take care

david

___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: Upgrading 5.3 > 6.0 buildworld failure now in libmagic

[Michael C. Shultz]

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'
> > Subject: Re: Upgrading 5.3 > 6.0 buildworld failure now in libmagic
> >
> > On Friday 09 December 2005 09:39, vizion wrote:
> > > > Vison, you are much better at writting florid prose on how and why
> > > > FreeBSD is
> > > > such an awful OS run by a team of Techies who care nothing about end
> > > > users needs than you are at reading and comprehending simple
> > > > instructions.
> > > >
> > > >  What you write is almost believable, your writing skill is very good
> >
> > and
> >
> > > > convincing, only in this particualr case I know you are completely
> >
> > wrong
> >
> > > > and
> > > > your failure to follow the simplest advice is why your machine is now
> >
> > non
> >
> > > > operational.  Quit crying about non relevent issues and concentrate
> > > > on solving your real problem - getting that darn machine to boot up.
> > > >
> > > > One last thought, name one OS that has better documentation than
> >
> > FreeBSD
> >
> > > > please, comercial or otherwise.  Maybe there is such a beast, if so I
> >
> > am
> >
> > > > very
> > > > curious to know what it is called.
> > >
> > > Mike
> > >
> > > Rather than replying to the list I am emailing you direct and cc onl;y
> >
> > the
> >
> > > individuals to whom you cc'd your original.
> > >
> > > Frankly I never ceased to be amazed at diversionary personalized
> > > attacks that seem to be a regular occurrence on freebsd lists whenever
> > > someone makes friendly but critical observations about freebsd.  There
> > > is a touchyness there which is a big deterrent to the engagement of
> > > others
> >
> > and a
> >
> > > tendency to paternalize which, on rare occasions, is an unspeakably
> > > ugly aspect of some freebsd interactions.
> > >
> > > I do not know the root cause of such over-defensiveness I am constantly
> > > amazed when old timers do not recognize it. It is time to grow up and I
> > > hope something will happen to discourage people from arguing ad
> >
> > personam.
> >
> > > Your remarks seem to have been written with the deliberate intention of
> > > attacking the messenger rather than discussing the message. You did not
> > > even aspire to achieving accuracy.
> > >
> > > The fact the my system did upgrade successfully from 5.3 to 5.4 by
> > > following your advice does not give you the right to make false
> >
> > assumptions
> >
> > > about a failed upgrade from 5.4 to 6.0 that is due to a combination of
> > > events that have nothing whatsoever to do with the topic under
> >
> > discussion,
> >
> > > advice that has been given or even freebsd or its documentation. It
> >
> > turns
> >
> > > out that a motherboard hardware failure was the casue of the upgrade
> > > failure.. hence I have to do a total rebuild because the motherboard is
> >
> > no
> >
> > > longer available.
> >
> > And this is your excuse for attacking the FreeBSD organization?
>
> No  and I have nott attacked "the organization".  The c ritic of the way in
> which documentation is  not integrated ionto the freebsd development cycle
> was made long before there was any motherboard failure.  I do wish you
> would stick to the facts.
>
>
>
> I'm sure
>
> > everyone feels bad for you that you have to get a new motherboard.   I am
> > confused as to how better coordination between developers and technical
> > writers could have prevented it from failing though.
>
> I have not made that suggestion - only you have put forward that notion --
> come on laugh a bit - you are really being a bit wild and cranky over this
> . The motherboard failure occurred after the discussion on
> documentation not before  you really are missing the point here.
>
> > > As for the use of  perjorative terminology (florid prose) and false
> > > accusations - I am really personally very disappointed in your
> >
> > reactions.
> >
> > > What you seemed to be saying was that you were unable 

RE: Upgrading 5.3 > 6.0 buildworld failure now in libmagic

[vizion]

> -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
> 
> On Friday 09 December 2005 09:39, vizion wrote:
> > > Vison, you are much better at writting florid prose on how and why
> > > FreeBSD is
> > > such an awful OS run by a team of Techies who care nothing about end
> > > users needs than you are at reading and comprehending simple
> > > instructions.
> > >
> > >  What you write is almost believable, your writing skill is very good
> and
> > > convincing, only in this particualr case I know you are completely
> wrong
> > > and
> > > your failure to follow the simplest advice is why your machine is now
> non
> > > operational.  Quit crying about non relevent issues and concentrate on
> > > solving your real problem - getting that darn machine to boot up.
> > >
> > > One last thought, name one OS that has better documentation than
> FreeBSD
> > > please, comercial or otherwise.  Maybe there is such a beast, if so I
> am
> > > very
> > > curious to know what it is called.
> >
> > Mike
> >
> > Rather than replying to the list I am emailing you direct and cc onl;y
> the
> > individuals to whom you cc'd your original.
> >
> > Frankly I never ceased to be amazed at diversionary personalized attacks
> > that seem to be a regular occurrence on freebsd lists whenever someone
> > makes friendly but critical observations about freebsd.  There is a
> > touchyness there which is a big deterrent to the engagement of others
> and a
> > tendency to paternalize which, on rare occasions, is an unspeakably ugly
> > aspect of some freebsd interactions.
> >
> > I do not know the root cause of such over-defensiveness I am constantly
> > amazed when old timers do not recognize it. It is time to grow up and I
> > hope something will happen to discourage people from arguing ad
> personam.
> >
> > Your remarks seem to have been written with the deliberate intention of
> > attacking the messenger rather than discussing the message. You did not
> > even aspire to achieving accuracy.
> >
> > The fact the my system did upgrade successfully from 5.3 to 5.4 by
> > following your advice does not give you the right to make false
> assumptions
> > about a failed upgrade from 5.4 to 6.0 that is due to a combination of
> > events that have nothing whatsoever to do with the topic under
> discussion,
> > advice that has been given or even freebsd or its documentation. It
> turns
> > out that a motherboard hardware failure was the casue of the upgrade
> > failure.. hence I have to do a total rebuild because the motherboard is
> no
> > longer available.
> 
> 
> And this is your excuse for attacking the FreeBSD organization?  
No  and I have nott attacked "the organization".  The c ritic of the way in
which documentation is  not integrated ionto the freebsd development cycle
was made long before there was any motherboard failure.  I do wish you would
stick to the facts. 



I'm sure
> everyone feels bad for you that you have to get a new motherboard.   I am
> confused as to how better coordination between developers and technical
> writers could have prevented it from failing though.


I have not made that suggestion - only you have put forward that notion --
come on laugh a bit - you are really being a bit wild and cranky over this
. The motherboard failure occurred after the discussion on
documentation not before  you really are missing the point here.
> >
> > As for the use of  perjorative terminology (florid prose) and false
> > accusations - I am really personally very disappointed in your
> reactions.
> >
> > What you seemed to be saying was that you were unable to counter my
> > suggestions which were so unwelcome to you that you chose to attack me
> > personally.
> 
> Your suggestions were irrelevent to the problem at hand. 
My suggestions are very relevant to the documentary errors, omissions and
lack of documentary integration that waste much of the time of many end
users. 
 

My suggestions were, it is true, were off the original topic and came about
as a response to someone else who complained about freebsd documentation and
I responded to him. 

He was strongly critical because the  documentation stated that direct
upgrade from 5.3 to 6.00 was possible when, as you pointed out, it was not. 

I suggest you reread the whole thread with care and look at 

Re: Upgrading 5.3 > 6.0 buildworld failure now in libmagic

[Doug Barton]

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 RELENG_5 prior to upgrade


Based on recommendations from this thread and from kris, I changed the 
wording to be more generic, and added the same text to the UPGRADING file in 
HEAD, and RELENG_6.


Well, if it's common knowledge, lets see it documented.  We're only 
talking a few lines in the handbook or the release notes, not an entire 
chapter.


I did my bit. I'm sure that the freebsd-doc folks are eagerly anticipating 
your patches, since this is such an easy thing to add. :)




My frustration comes from the fact that this seems to be getting worse, 
not better. 


From your perspective that may be true, however from a more general 
perspective I don't agree. C'est la vie.


In addition, every time I bring this up, I'm told (usually 
by someone with a freebsd.org address) that, "oh we all know/knew about 
that"  or, "it's common knowledge".


I have been very careful to say that I agree that our documentation can 
always be improved. I've also been very careful to say that the only way 
this will happen is if someone steps up to do it. I realize that's not the 
answer you're looking for, but it's the only one we have, and all the 
elegantly phrased rants, descriptions of what we should be doing for you 
(and how we should be doing it), and other things that you (pl.) wish were 
so won't change that.


Doug


--

This .signature sanitized for your protection

___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: Upgrading 5.3 > 6.0 buildworld failure now in libmagic

[Michael C. Shultz]

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
> > Subject: Re: Upgrading 5.3 > 6.0 buildworld failure now in libmagic
> >
> > 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 volunteers.
>
> Not really I have done both and found that shared values and community
> collaboration work the same.
>
> >On a commercial
> > project, you can direct someone to do something and they have a choice of
> > either doing it or finding another job.
>
> Well that kind of development environment (rule by dictat) does not work
> very well. Developers are people who are engaged in a collaborative
> process. If you encourage them to think like prima donas then they will
> behave like prima donas rather than as part of an integrated team.
>
> >On a volunteer project, there's
> > a limit to how far you can push someone to do something they don't enjoy
> > before they just leave.
>
> Push has it limitations everywhere.. goals and communal rewards are better
> in both volunteer and commercial projects.
>
> > > The first implication is that
> > >we should be complacent about it and not seek to find a method to
> > > improve the process.
> >
> > I don't think anyone is suggesting this.  In my experience, the FreeBSD
> > project is always open to process improvements - this is especially
> > obvious in the documentation and release engineering areas.
>
>  The question is about the degree of committment to process change not
> whwther it is absent or present. The critique is there is tooo little
> comitment to process change and too much resistance to greater
> concentration on the quality of user docuimentation and the significance of
> that work in the developmenmt cycle.
>
> > >>Most of our really top
> > >>notch developers are actually very bad at documenting their work (I
> > >> don't mean bad at being timely with it, I mean that they are bad at
> > >> DOING it), and frankly their time is better spent elsewhere.
> > >
> > >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 poor at writing documentation for
> > non-technical people.  There are probably very few developers who
> > enjoy writing end-user documentation (and can write).  In my
> > experience, especially on large projects, it's rare for developers to
> > write the end-user documentation.
>
> NOTE I said"
>  F:ranky my experience has been that developers who are bad at
> ENSURING
> their work is well documentated are second rate rather than top rate
> developers. The work of the technical writer needs to influence development
> at the design stage! It does not matter whether the developer does or does
> not write the the documentation but it does matter whether the developer is
>  COMIITED to both ensuring that there is proper documentation AND that the
> documentation process is an integral part of the development process that
> influences its outcome.
>
> >They may write a rough outline but
> > it's the technical writers who actually do the documentation.
>
> The outline for  user documentation needs to be structured  BEFORE
> development begins NOT  as an afterthought. In a well structured
> development environment documentation is part of DESIGN not post design
> implementation . That is because thinking about end user at the design
> stage is necessary if the outcome of the process is going to be user
> centric.
>
> >The
> > problem is finding people with technical writing skills who are
> > interested in helping with FreeBSD.
>
> Freebsd needs to reorganize the way it develops if it is going to interest
> techn ical writers. No technical writer wants to be associated with writing
> documnets for developments that have been poorly designed for the end user.
> Clearing up someone else's mess is no fun. If you treat technical writers
> as people who come along afterwards and pick up yopur trash OF COURS

Re: Upgrading 5.3 > 6.0 buildworld failure now in libmagic

[secmgr]

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 poor at writing documentation for
non-technical people.  There are probably very few developers who
enjoy writing end-user documentation (and can write).  

My personal expectation is *not* that the FreeBSD developers tell me 
what a cdrom is.  My expectation is that they tell me what works, what 
doesn't, and warn me about whats in the middle.  Trust me, there are 
damn few "non-technical" people installing FreeBSD, and I'm pretty sure 
both of them gave up in sysinstall.  I can read (most) code and I can 
search PR's.  However, if it's 2 am and my server has puked on it's 
shoes during an upgrade due to an undocumented issue the developer knew 
about, I'm not going to recommend FreeBSD to anyone other than as a 
hobby for single men with beards.



In my
experience, especially on large projects, it's rare for developers to
write the end-user documentation.  They may write a rough outline but
it's the technical writers who actually do the documentation.  The
problem is finding people with technical writing skills who are
interested in helping with FreeBSD.

It's also worth noting that a number of FreeBSD developers are not native
English speakers.  It's probably unreasonable to expect them to write
polished English documentation.
 

Again, I'm not asking them to write chapters in the handbook and I 
understand (and assumed) they may not be native English speakers.  How 
hard is it to get a, "ata.c broke with via 666 sata chipset under heavy 
load"?  If I have a via 666 sata chipset, now I know to go looking in 
the code.  Even if don't go looking in the code, I know that I might 
want to look at a different adapter.  Don't tell me whats little more 
than a subject line of a mail message is beyond even a junior 
non-English speaking coder and a few minutes with a translation program.



Are you volunteering?


Yes, I'd like to help, not that I think my writing skills are all that 
great.  But "no" if the developers won't be forthcoming with details.


P.S. I'm not picking on the ata code or it's owners.  It was just a 
module name I knew off hand.


jim
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: Re: Upgrading 5.3 > 6.0 buildworld failure now in libmagic

[vizion]

> 
> 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]>
> 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?
> 
> It should be noted that this sort of response often comes across
> rather sneering and snarky, but (most of the time, anyway) it's really
> not meant to.  It often DOES translate pretty directly to "Yes, that
> would be nice, and it would be really great if somebody who was
> interested and capable were to grab the reins and do it."
> 
> 

Do you mean the response sounds like freebsd documentation 

See my last email for a response to that one !

ATM I am struggling on a win machine because my local server once more refused 
to upgrade to 6.0 and this time has bombed outcompletely - looks nlike a 
complete rebuild 
david

> -- 
> Matthew Fuller (MF4839)   |  [EMAIL PROTECTED]
> Systems/Network Administrator |  http://www.over-yonder.net/~fullermd/
>On the Internet, nobody can hear you scream.
> ___
> freebsd-stable@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-stable
> To unsubscribe, send any mail to "[EMAIL PROTECTED]"
> 

___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: Re: Upgrading 5.3 > 6.0 buildworld failure now in libmagic

[vizion]

> 
> 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 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 volunteers.  
Not really I have done both and found that shared values and community 
collaboration work the same. 

>On a commercial
> project, you can direct someone to do something and they have a choice of
> either doing it or finding another job.  

Well that kind of development environment (rule by dictat) does not work very 
well. Developers are people who are engaged in a collaborative process. If you 
encourage them to think like prima donas then they will behave like prima donas 
rather than as part of an integrated team.

>On a volunteer project, there's
> a limit to how far you can push someone to do something they don't enjoy
> before they just leave.

Push has it limitations everywhere.. goals and communal rewards are better in 
both volunteer and commercial projects.
> 
> > The first implication is that 
> >we should be complacent about it and not seek to find a method to improve 
> >the 
> >process.
> 
> I don't think anyone is suggesting this.  In my experience, the FreeBSD
> project is always open to process improvements - this is especially
> obvious in the documentation and release engineering areas.
> 
 The question is about the degree of committment to process change not whwther 
it is absent or present. The critique is there is tooo little comitment to 
process change and too much resistance to greater concentration on the quality 
of user docuimentation and the significance of that work in the developmenmt 
cycle.


> >>Most of our really top 
> >>notch developers are actually very bad at documenting their work (I don't
> >>mean bad at being timely with it, I mean that they are bad at DOING it), and
> >>frankly their time is better spent elsewhere. 
> >
> >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 poor at writing documentation for
> non-technical people.  There are probably very few developers who
> enjoy writing end-user documentation (and can write).  In my
> experience, especially on large projects, it's rare for developers to
> write the end-user documentation.  
NOTE I said"
 F:ranky my experience has been that developers who are bad at
ENSURING 
their work is well documentated are second rate rather than top rate developers.
The work of the technical writer needs to influence development at the design 
stage! It does not matter whether the developer does or does not write the the 
documentation but it does matter whether the developer is  COMIITED to both 
ensuring that there is proper documentation AND that the documentation process 
is an integral part of the development process that influences its outcome.

>They may write a rough outline but
> it's the technical writers who actually do the documentation.  

The outline for  user documentation needs to be structured  BEFORE development 
begins NOT  as an afterthought. In a well structured development environment 
documentation is part of DESIGN not post design implementation . That is 
because thinking about end user at the design stage is necessary if the outcome 
of the process is going to be user centric. 
>The
> problem is finding people with technical writing skills who are
> interested in helping with FreeBSD.
>
Freebsd needs to reorganize the way it develops if it is going to interest 
techn ical writers. No technical writer wants to be associated with writing 
documnets for developments that have been poorly designed for the end user. 
Clearing up someone else's mess is no fun. If you treat technical writers as 
people who come along afterwards and pick up yopur trash OF COURSE you will not 
get them involved. You need to ask WHY it is difficult to get them.  It is 
because freebsd does not produce software with a focus on end user 
satisfaction. This is a chicken and egg problem that  can only be solved by a 
fu8ndamental shift both the focus of development objectives and the development 
process.
> 
> It's also worth noting that a number of FreeBSD developers are not native
> English spe

Re: Upgrading 5.3 > 6.0 buildworld failure now in libmagic

[Matthew D. Fuller]

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?

It should be noted that this sort of response often comes across
rather sneering and snarky, but (most of the time, anyway) it's really
not meant to.  It often DOES translate pretty directly to "Yes, that
would be nice, and it would be really great if somebody who was
interested and capable were to grab the reins and do it."


-- 
Matthew Fuller (MF4839)   |  [EMAIL PROTECTED]
Systems/Network Administrator |  http://www.over-yonder.net/~fullermd/
   On the Internet, nobody can hear you scream.
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: Upgrading 5.3 > 6.0 buildworld failure now in libmagic

[Peter Jeremy]

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 volunteers.  On a commercial
project, you can direct someone to do something and they have a choice of
either doing it or finding another job.  On a volunteer project, there's
a limit to how far you can push someone to do something they don't enjoy
before they just leave.

> The first implication is that 
>we should be complacent about it and not seek to find a method to improve the 
>process.

I don't think anyone is suggesting this.  In my experience, the FreeBSD
project is always open to process improvements - this is especially
obvious in the documentation and release engineering areas.

>>Most of our really top 
>>notch developers are actually very bad at documenting their work (I don't
>>mean bad at being timely with it, I mean that they are bad at DOING it), and
>>frankly their time is better spent elsewhere. 
>
>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 poor at writing documentation for
non-technical people.  There are probably very few developers who
enjoy writing end-user documentation (and can write).  In my
experience, especially on large projects, it's rare for developers to
write the end-user documentation.  They may write a rough outline but
it's the technical writers who actually do the documentation.  The
problem is finding people with technical writing skills who are
interested in helping with FreeBSD.

It's also worth noting that a number of FreeBSD developers are not native
English speakers.  It's probably unreasonable to expect them to write
polished English documentation.

>What I have found works in development is to create team relationships that 
>cover design, development and documentation.

I agree that this is a good approach.  It's similar to the 'surgical
team' approach that Brooks recommends in "The Mythical Man-Month".  I
think that this does happen to some extent in FreeBSD but agree it
could be more widespread.  (Though it is probably harder to put it into
practice in a distributed, volunteer project than when the team share
a cubicle).

>My view would be that the freebsd project might do well to consider 
>implementing a "no release without quality documentation assurance" policy. 
...
>development is so good. It deserves better and more professional attention to 
>the role of end user documentation.

Are you volunteering?

-- 
Peter Jeremy
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Stable Doc issues- thread branched from [Upgrading 5.3 > 6.0 buildworld failure]

[Vizion]

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 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 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 seperate from the development process
>>> rather than an integral part of that process.
>>
>>You're right, however that is just "the way it is."
>
>Well having run many very large scale projects myself I  find it difficult
> to accept either implication of this perspective. The first implication is
> that we should be complacent about it and not seek to find a method to
> improve the process. The second implication is that top notch developers do
> not care about end user comfort. My experience is that most do care but
> they needa helpful environment to achieve food documentation.
>
>>Most of our really top
>>notch developers are actually very bad at documenting their work (I don't
>>mean bad at being timely with it, I mean that they are bad at DOING it),
>> and frankly their time is better spent elsewhere.
>
>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.
>
>What I have found works in development is to create team relationships that
>cover design, development and documentation. Unfortunately this does go
>against the somewhat individualistic elitist relationship that is
>unnecessarily sustained by the implications I referred to earlier (neither
> of which I buy and both of which seem to me to be condescending nonsense).
>
>My view would be that the freebsd project might do well to consider
>implementing a "no release without quality documentation assurance" policy.
>Such a policy forces design and development to integrate their work with
>whoever has been identified as responsible for user documentation (whether
>that is the designer, developer or a seprate documentation person or team.
>This encourage the preparation of user documentation as part of the project
>rather then an afterthought (that depends upon members of the "hoi poloi".
>
>>The documentation is light
>>years ahead of where it was 11 years ago when I started using FreeBSD for
>>one simple reason. Interested users stepped up and helped make it better.
>>That's the only way that things improve in an open source project.
>
>OK so some of that talent needs to be harnessed and integrated into the
>development process. In this day and age we need to believe that user
>documentation provides a paradigm for design and development not design and
>development a paradigm for documentation. The latter view characterized
>development in the early 70,s and 80's. I thought we had moved beyond that.
>
>>FWIW, I added a paragraph to the UPDATING file in both HEAD and RELENG_6
>>that describes why updating to the latest code in the installed branch is a
>>good idea before trying a major version upgrade. Hopefully that will help
>>the next person who stumbles over this same issue.
>
>Thank you so much for what you do. I trust that you will understand that
>recomendations for improvement are made BECAUSE the quality of design and
>development is so good. It deserves better and more professional attention
> to the role of end user documentation.
>
>my two pennorth
>
Just another thought - it seems that the current philosophy is
We know generally what you the users want and you will know exactly what you 
have got when we have done it!!
When we have done we will give it to you for you to sort out how you can use 
it!
Ps. If you fo not like what we have done or the way we have done it you need 
to be reminded you are lucky we have done it for you!!

Come on - it just cannot be like this for ever. 

Open source projects start like this but as they mature does not the 
concentatration need to shift towards user satisfaction rather than just a 
constant gallop towards greater technical functionality.

david

-- 
40 yrs navigating and computing in blue waters.
English Owner & Captain of British Registered 60' bluewater Ketch S/V Taurus.
 Currently in San Diego, CA. Sailing bound for Europe via Panama Canal after 
completing engineroom refit.
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: Upgrading 5.3 > 6.0 buildworld failure now in libmagic

[secmgr]

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 -   1.416.2.7
+++ UPDATING7 Dec 2005 00:42:04 -
@@ -229,7 +229,13 @@
page for more details.

Due to several updates to the build infrastructure, source
-   upgrades from versions prior to 5.3 no longer supported.
+   upgrades from versions prior to 5.4-STABLE are not likely
+   to succeed.
+
+   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 RELENG_5 prior to upgrade

This is an open source project. The only way that things improve is if 
people help make it better. It's also worth pointing out that this 
issue of upgrading to the latest version of the branch you're in has 
been "common knowledge" for, basically, always; so if the folks that 
wrote the release notes neglected to include it, it's understandable. 
(Although, as you point out, potentially frustrating for new(er) users.)


Well, if it's common knowledge, lets see it documented.  We're only 
talking a few lines in the handbook or the release notes, not an entire 
chapter.


If RE wants to change the requirements for upgrading, then how 
bleeping hard would it be to update either release notes or errata.  
It's not so much that I now need to do multiple upgrades (ok, that IS 
pretty annoying), it's that I'd never of known unless I followed this 
thread.



Ok, so, after you calm down a bit, why don't you write a message to 
[EMAIL PROTECTED] and mention this issue.



My frustration comes from the fact that this seems to be getting worse, 
not better.  In addition, every time I bring this up, I'm told (usually 
by someone with a freebsd.org address) that, "oh we all know/knew about 
that"  or, "it's common knowledge". In the case of the 
vinum/gvinum/gmirror trainwreck, I got silence, even though I strongly 
suspect multiple people knew there were problems, but just didn't want 
to talk about them.  I'd gladly help document some of this, but I'm not 
the one who knows where the skeletons are snoozing (at least till I trip 
on a femur)


So whats the big issue with letting the rest of us in on the secrets?  
I'm not looking for a book, just a line or two saying "here be dragons" 
somewhere /other /than the basement of the planing department in the 
bottom of a locked filing cabinet stuck in a disused lavatory with a 
sign on the door saying 'Beware of the Leopard' (apologies to Doug Adams).



___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: Upgrading 5.3 > 6.0 buildworld failure now in libmagic

[Vizion]

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 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 seperate from the development process rather than
>> an integral part of that process.
>
>You're right, however that is just "the way it is." 

Well having run many very large scale projects myself I  find it difficult to 
accept either implication of this perspective. The first implication is that 
we should be complacent about it and not seek to find a method to improve the 
process. The second implication is that top notch developers do not care 
about end user comfort. My experience is that most do care but they needa 
helpful environment to achieve food documentation.

>Most of our really top 
>notch developers are actually very bad at documenting their work (I don't
>mean bad at being timely with it, I mean that they are bad at DOING it), and
>frankly their time is better spent elsewhere. 

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.

What I have found works in development is to create team relationships that 
cover design, development and documentation. Unfortunately this does go 
against the somewhat individualistic elitist relationship that is 
unnecessarily sustained by the implications I referred to earlier (neither of 
which I buy and both of which seem to me to be condescending nonsense).

My view would be that the freebsd project might do well to consider 
implementing a "no release without quality documentation assurance" policy. 
Such a policy forces design and development to integrate their work with 
whoever has been identified as responsible for user documentation (whether 
that is the designer, developer or a seprate documentation person or team. 
This encourage the preparation of user documentation as part of the project 
rather then an afterthought (that depends upon members of the "hoi poloi".

>The documentation is light 
>years ahead of where it was 11 years ago when I started using FreeBSD for
>one simple reason. Interested users stepped up and helped make it better.
>That's the only way that things improve in an open source project.

OK so some of that talent needs to be harnessed and integrated into the 
development process. In this day and age we need to believe that user 
documentation provides a paradigm for design and development not design and 
development a paradigm for documentation. The latter view characterized 
development in the early 70,s and 80's. I thought we had moved beyond that.

>
>FWIW, I added a paragraph to the UPDATING file in both HEAD and RELENG_6
>that describes why updating to the latest code in the installed branch is a
>good idea before trying a major version upgrade. Hopefully that will help
>the next person who stumbles over this same issue.

Thank you so much for what you do. I trust that you will understand that 
recomendations for improvement are made BECAUSE the quality of design and 
development is so good. It deserves better and more professional attention to 
the role of end user documentation.

my two pennorth
>
>Doug

-- 
40 yrs navigating and computing in blue waters.
English Owner & Captain of British Registered 60' bluewater Ketch S/V Taurus.
 Currently in San Diego, CA. Sailing bound for Europe via Panama Canal after 
completing engineroom refit.
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: Upgrading 5.3 > 6.0 buildworld failure now in libmagic

[Doug Barton]

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 seperate from the development process rather than an 
integral part of that process.


You're right, however that is just "the way it is." Most of our really top 
notch developers are actually very bad at documenting their work (I don't 
mean bad at being timely with it, I mean that they are bad at DOING it), and 
frankly their time is better spent elsewhere. The documentation is light 
years ahead of where it was 11 years ago when I started using FreeBSD for 
one simple reason. Interested users stepped up and helped make it better. 
That's the only way that things improve in an open source project.


FWIW, I added a paragraph to the UPDATING file in both HEAD and RELENG_6 
that describes why updating to the latest code in the installed branch is a 
good idea before trying a major version upgrade. Hopefully that will help 
the next person who stumbles over this same issue.


Doug

--

This .signature sanitized for your protection

___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: Upgrading 5.3 > 6.0 buildworld failure now in libmagic

[Kris Kennaway]

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 due to oversight,
> e.g. it was written/documented/recommended before 5.4 was out.
> Maybe that's (part of) the basis for the Handbook's recommendation of
> reading the -stable list if you indeed want to track past -RELEASE.  :)

I've corrected myself already in previous replies, but to try and put
this to rest, I was mistaken when I said that 5.4 was required.
Others have already confirmed that clean 5.3 installations may be
directly upgraded to 6.0.

The problem experienced by the OP must have had another cause.  The
upgrade to 5.4 may have corrected it for him.

Kris


pgpbOFo0MhqI7.pgp
Description: PGP signature

Re: Upgrading 5.3 > 6.0 buildworld failure now in libmagic

[Kenneth W Cochran]

>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 libmagic
>
>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 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-RELEASE
>>>> will need to update to FreeBSD 5.3 or newer first, then to FreeBSD
>>>> 6.0-RELEASE."
>>>
>>> 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 -   1.416.2.7
>>> +++ UPDATING7 Dec 2005 00:42:04 -
>>> @@ -229,7 +229,13 @@
>>>  page for more details.
>>>
>>>  Due to several updates to the build infrastructure, source
>>> -   upgrades from versions prior to 5.3 no longer supported.
>>> +   upgrades from versions prior to 5.4-STABLE are not likely
>>> +   to succeed.
>>
>>Sorry to butt in but..
>>
>>Doesn't the definition of -STABLE change, for all intents and purposes, by
>>the minute?
>>
>>What next, "versions prior to 5.4-STABLE as of MMDD "?

I believe I've seen exactly this type of notation in UPDATING
over the years, in both 4.x & 5.x.

>>> +
>>> +   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.
>>
>>This is getting closer to the truth.
>>
>>Why don't you just say "update to the most recent RELENG_5 before
>>attempting."  Future proof, no room for confusion.
>
[...snip...]
>
>There is however a perennial problem that freebsd documentation has always
>been seen as behind and seperate from the development process rather than an

Maybe (hmm, even probably :) but I've found documentation,
announcements, errata, etc. (*manpages*) for FreeBSD to
be *much* better, more relevant & up to date than, umm,
"other" opensource systems.  Compared to FreeBSD, other
systems' documentation/manpages seem haphazard & in some
cases even nonexistent.

>integral part of that process. [...snip...]
>
>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 due to oversight,
e.g. it was written/documented/recommended before 5.4 was out.
Maybe that's (part of) the basis for the Handbook's recommendation of
reading the -stable list if you indeed want to track past -RELEASE.  :)

>Thank you top everyone who helped. I have now successfully upgarded to 5.4 and
>am about to begin the last leg of this journey towards 6.0.
>
>my two pennorth
>
>david
>--

Mine too I guess :)

-kc
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: Upgrading 5.3 > 6.0 buildworld failure now in libmagic

[Vizion]

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 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-RELEASE
>>> will need to update to FreeBSD 5.3 or newer first, then to FreeBSD
>>> 6.0-RELEASE."
>>
>> 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 -   1.416.2.7
>> +++ UPDATING7 Dec 2005 00:42:04 -
>> @@ -229,7 +229,13 @@
>>  page for more details.
>>
>>  Due to several updates to the build infrastructure, source
>> -   upgrades from versions prior to 5.3 no longer supported.
>> +   upgrades from versions prior to 5.4-STABLE are not likely
>> +   to succeed.
>
>Sorry to butt in but..
>
>Doesn't the definition of -STABLE change, for all intents and purposes, by
>the minute?
>
>What next, "versions prior to 5.4-STABLE as of MMDD "?
>
>> +
>> +   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.
>
>This is getting closer to the truth.
>
>Why don't you just say "update to the most recent RELENG_5 before
>attempting."  Future proof, no room for confusion.

Well I do not want to not thank those who have made the upgrades viable. The 
value of their work should not be underrated.

There is however a perennial problem that freebsd documentation has always 
been seen as behind and seperate from the development process rather than an 
integral part of that process. I do not know whether that historical habit is 
changeable. I suspect it is the only major disadvantage  from what I would 
personally describe as a somewhat  "technologically centred meritocratic 
school of governance" for the freebsd project. Some improved cohesion between 
the desire to meet the developmental needs and a desirable objective to 
provide an end user-centric operation is, to my mind desirable. On the other 
hand freebsd has prospered in the past by devotion to reliance upon 
idiosyncratic individual initiatives and that does not blend well with 
co-operatively integrated plans to similtaneously meet the twin goals I 
identify.

On the whole the result is a A for freebsd when we all want an A++


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

Thank you top everyone who helped. I have now successfully upgarded to 5.4 and 
am about to begin the last leg of this journey towards 6.0.

my two pennorth

david
-- 
40 yrs navigating and computing in blue waters.
English Owner & Captain of British Registered 60' bluewater Ketch S/V Taurus.
 Currently in San Diego, CA. Sailing bound for Europe via Panama Canal after 
completing engineroom refit.
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: Upgrading 5.3 > 6.0 buildworld failure now in libmagic

[Allen]

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-RELEASE or later. Users of older systems wanting to upgrade
>> 6.0-RELEASE
>> will need to update to FreeBSD 5.3 or newer first, then to FreeBSD
>> 6.0-RELEASE."
>
> 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 -   1.416.2.7
> +++ UPDATING7 Dec 2005 00:42:04 -
> @@ -229,7 +229,13 @@
>  page for more details.
>
>  Due to several updates to the build infrastructure, source
> -   upgrades from versions prior to 5.3 no longer supported.
> +   upgrades from versions prior to 5.4-STABLE are not likely
> +   to succeed.

Sorry to butt in but..

Doesn't the definition of -STABLE change, for all intents and purposes, by
the minute?

What next, "versions prior to 5.4-STABLE as of MMDD "?

> +
> +   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.

This is getting closer to the truth.

Why don't you just say "update to the most recent RELENG_5 before
attempting."  Future proof, no room for confusion.





___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: Upgrading 5.3 > 6.0 buildworld failure now in libmagic

[Doug Barton]

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-RELEASE 
will need to update to FreeBSD 5.3 or newer first, then to FreeBSD 
6.0-RELEASE."


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 -   1.416.2.7
+++ UPDATING7 Dec 2005 00:42:04 -
@@ -229,7 +229,13 @@
page for more details.

Due to several updates to the build infrastructure, source
-   upgrades from versions prior to 5.3 no longer supported.
+   upgrades from versions prior to 5.4-STABLE are not likely
+   to succeed.
+
+   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.


This is one of my pet peeves with FreeBSD.  You can read the Release Notes, 
the UPDATING, the ERRATA, the HARDWARE, thinking you've prepped yourself for 
the upgrade, and still be screwed.


This is an open source project. The only way that things improve is if 
people help make it better. It's also worth pointing out that this issue of 
upgrading to the latest version of the branch you're in has been "common 
knowledge" for, basically, always; so if the folks that wrote the release 
notes neglected to include it, it's understandable. (Although, as you point 
out, potentially frustrating for new(er) users.)


If RE wants to change the requirements for upgrading, then how bleeping 
hard would it be to update either release notes or errata.  It's not so 
much that I now need to do multiple upgrades (ok, that IS pretty 
annoying), it's that I'd never of known unless I followed this thread.


Ok, so, after you calm down a bit, why don't you write a message to 
[EMAIL PROTECTED] and mention this issue.


hth,

Doug

--

This .signature sanitized for your protection

___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: Upgrading 5.3 > 6.0 buildworld failure now in libmagic

[Kris Kennaway]

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 update to 5.4 before you can update to
> >6.0, i.e. updates from older versions are not supported.  It may be
> >easier to do a binary upgrade (i.e. download release media and use the
> >upgrade option).
> >
> >Kris
> > 
> >
> Not to belabour this, but the 6.0 release notes do specificly say 5.3 
> RELEASE and newer.

You're right, as others have also pointed out.

> "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-RELEASE will need to update to FreeBSD 5.3 or newer first, then to 
> FreeBSD 6.0-RELEASE."
> 
> This is one of my pet peeves with FreeBSD.  You can read the Release 
> Notes, the UPDATING, the ERRATA, the HARDWARE, thinking you've prepped 
> yourself for the upgrade, and still be screwed.  If RE wants to change 
> the requirements for upgrading, then how bleeping hard would it be to 
> update either release notes or errata.

This didn't happen here, so you don't need to be upset at RE.

Kris

pgpdXD8SIxbxN.pgp
Description: PGP signature

Re: Upgrading 5.3 > 6.0 buildworld failure now in libmagic

[secmgr]

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 before you can update to
6.0, i.e. updates from older versions are not supported.  It may be
easier to do a binary upgrade (i.e. download release media and use the
upgrade option).

Kris
 

Not to belabour this, but the 6.0 release notes do specificly say 5.3 
RELEASE and 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-RELEASE will need to update to FreeBSD 5.3 or newer first, then to 
FreeBSD 6.0-RELEASE."


This is one of my pet peeves with FreeBSD.  You can read the Release 
Notes, the UPDATING, the ERRATA, the HARDWARE, thinking you've prepped 
yourself for the upgrade, and still be screwed.  If RE wants to change 
the requirements for upgrading, then how bleeping hard would it be to 
update either release notes or errata.  It's not so much that I now need 
to do multiple upgrades (ok, that IS pretty annoying), it's that I'd 
never of known unless I followed this thread.


I've run into this while installing since 4.4, and it's gotten really 
bad since the whole 5.3 mess.  Now it's deja vu all over again.


jim
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: Upgrading 5.3 > 6.0 buildworld failure now in libmagic

[Vizion]

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 upgrade my ports from 5.4 as well prior to moving to 6?
>
>No, that's not needed.
>
Thanks again

david

-- 
40 yrs navigating and computing in blue waters.
English Owner & Captain of British Registered 60' bluewater Ketch S/V Taurus.
 Currently in San Diego, CA. Sailing bound for Europe via Panama Canal after 
completing engineroom refit.
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: Upgrading 5.3 > 6.0 buildworld failure now in libmagic

[Doug Barton]

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

___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: Upgrading 5.3 > 6.0 buildworld failure now in libmagic

[Doug Barton]

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 (cvs tag RELENG_6).


hth,

Doug

--

This .signature sanitized for your protection

___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: Upgrading 5.3 > 6.0 buildworld failure now in libmagic

[Vizion]

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 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 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 Ruslan Ermilov
>>> > contributed to the dialogue on-
>>>
>>> 
>>>
>>> >>The example of setting up ccache in /etc/make.conf is just plain
>>> >>wrong.  It shouldn't be hardcoding CC to "/usr/bin/cc", similarly
>>> >>for CXX.  Comment out the ccache stuff completely in /etc/make.conf
>>> >>(or at least the last "else" part), make sure your PATH doesn't
>>> >>include the ccache path, and try again with an empty /usr/obj.
>>> >>Please report back if it succeeded (it should).  Please send your
>>> >>complaints to the ccache port MAINTAINER as he did not respond to
>>> >>my email explaining the problem, and I'm getting really tired of
>>> >>explaining this for the Nth time.
>>> >
>>> >Thanks very much - I am building right now --after deinstalling ccache,
>>> > make cleandir x3 and an empty /usr/obj. I will post the results here
>>>
>>> Well certainly made a difference but now it fails in magic
>>
>>Update to 5.4 before trying to update to 6.0.
>
>Thank you Kris
>
>You are a mine of information as always.
>
>I do wish there was some consistency in updating about this.. I asked on
> this list whether I needed to upgrade to 5.4 before mocing to 6 and the
> advice suggested that I could go straight from 5.3 to 6 but there we are --
> guess that's life 
>
>Presumably it would be safest to delete /usr/src/* and cvsup with
> tag=RELENG_5
>
>Thanks again
>
>david

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?

I have a large ports installation on the system I am upgrading.

david

-- 
40 yrs navigating and computing in blue waters.
English Owner & Captain of British Registered 60' bluewater Ketch S/V Taurus.
 Currently in San Diego, CA. Sailing bound for Europe via Panama Canal after 
completing engineroom refit.
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: Upgrading 5.3 > 6.0 buildworld failure now in libmagic

[Vizion]

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 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 Ruslan Ermilov contributed
>> > to the dialogue on-
>>
>> 
>>
>> >>The example of setting up ccache in /etc/make.conf is just plain
>> >>wrong.  It shouldn't be hardcoding CC to "/usr/bin/cc", similarly
>> >>for CXX.  Comment out the ccache stuff completely in /etc/make.conf
>> >>(or at least the last "else" part), make sure your PATH doesn't
>> >>include the ccache path, and try again with an empty /usr/obj.
>> >>Please report back if it succeeded (it should).  Please send your
>> >>complaints to the ccache port MAINTAINER as he did not respond to
>> >>my email explaining the problem, and I'm getting really tired of
>> >>explaining this for the Nth time.
>> >
>> >Thanks very much - I am building right now --after deinstalling ccache,
>> > make cleandir x3 and an empty /usr/obj. I will post the results here
>>
>> Well certainly made a difference but now it fails in magic
>
>Update to 5.4 before trying to update to 6.0.
>
Thank you Kris

You are a mine of information as always.

I do wish there was some consistency in updating about this.. I asked on this 
list whether I needed to upgrade to 5.4 before mocing to 6 and the advice 
suggested that I could go straight from 5.3 to 6 but there we are -- guess 
that's life 

Presumably it would be safest to delete /usr/src/* and cvsup with tag=RELENG_5

Thanks again

david

-- 
40 yrs navigating and computing in blue waters.
English Owner & Captain of British Registered 60' bluewater Ketch S/V Taurus.
 Currently in San Diego, CA. Sailing bound for Europe via Panama Canal after 
completing engineroom refit.
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: Upgrading 5.3 > 6.0 buildworld failure now in libmagic

[Andy Fawcett]

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 tried to say that you have to update to 5.4 before you can update
> to 6.0, i.e. updates from older versions are not supported.  It may
> be easier to do a binary upgrade (i.e. download release media and use
> the upgrade option).

At least with a vanilla install of 5.3, I had no problem going directly 
to 6.0.

This was an extremely basic install, and I only did it because I lost my 
6.0-R cd :)

A.

-- 
Andy Fawcett | [EMAIL PROTECTED]
 | [EMAIL PROTECTED]
"In an open world without walls and fences,  | [EMAIL PROTECTED]
  we wouldn't need Windows and Gates."  -- anon  | [EMAIL PROTECTED]
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: Upgrading 5.3 > 6.0 buildworld failure now in libmagic

[Kris Kennaway]

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 to
6.0, i.e. updates from older versions are not supported.  It may be
easier to do a binary upgrade (i.e. download release media and use the
upgrade option).

Kris


pgphYPjbZzGAM.pgp
Description: PGP signature

Re: Upgrading 5.3 > 6.0 buildworld failure now in libmagic

[secmgr]

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 now in libmagic
   


On Tuesday 06 December 2005 04:00,  the author Ruslan Ermilov contributed to
the dialogue on-
 

 
   


The example of setting up ccache in /etc/make.conf is just plain
wrong.  It shouldn't be hardcoding CC to "/usr/bin/cc", similarly
for CXX.  Comment out the ccache stuff completely in /etc/make.conf
(or at least the last "else" part), make sure your PATH doesn't
include the ccache path, and try again with an empty /usr/obj.
Please report back if it succeeded (it should).  Please send your
complaints to the ccache port MAINTAINER as he did not respond to
my email explaining the problem, and I'm getting really tired of
explaining this for the Nth time.
   


Thanks very much - I am building right now --after deinstalling ccache, make
cleandir x3 and an empty /usr/obj. I will post the results here
 


Well certainly made a difference but now it fails in magic
   



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.?


jim
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: Upgrading 5.3 > 6.0 buildworld failure now in libmagic

[Kris Kennaway]

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 in libmagic
> >On Tuesday 06 December 2005 04:00,  the author Ruslan Ermilov contributed to
> >the dialogue on-
>  
> >>The example of setting up ccache in /etc/make.conf is just plain
> >>wrong.  It shouldn't be hardcoding CC to "/usr/bin/cc", similarly
> >>for CXX.  Comment out the ccache stuff completely in /etc/make.conf
> >>(or at least the last "else" part), make sure your PATH doesn't
> >>include the ccache path, and try again with an empty /usr/obj.
> >>Please report back if it succeeded (it should).  Please send your
> >>complaints to the ccache port MAINTAINER as he did not respond to
> >>my email explaining the problem, and I'm getting really tired of
> >>explaining this for the Nth time.
> >
> >Thanks very much - I am building right now --after deinstalling ccache, make
> >cleandir x3 and an empty /usr/obj. I will post the results here
> 
> 
> Well certainly made a difference but now it fails in magic

Update to 5.4 before trying to update to 6.0.

Kris


pgpf2p3434d7o.pgp
Description: PGP signature

Upgrading 5.3 > 6.0 buildworld failure now in libmagic

[Vizion]

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 Ruslan Ermilov contributed to
>the dialogue on-
 
>>The example of setting up ccache in /etc/make.conf is just plain
>>wrong.  It shouldn't be hardcoding CC to "/usr/bin/cc", similarly
>>for CXX.  Comment out the ccache stuff completely in /etc/make.conf
>>(or at least the last "else" part), make sure your PATH doesn't
>>include the ccache path, and try again with an empty /usr/obj.
>>Please report back if it succeeded (it should).  Please send your
>>complaints to the ccache port MAINTAINER as he did not respond to
>>my email explaining the problem, and I'm getting really tired of
>>explaining this for the Nth time.
>
>Thanks very much - I am building right now --after deinstalling ccache, make
>cleandir x3 and an empty /usr/obj. I will post the results here


Well certainly made a difference but now it fails in magic

building static magic library
ranlib libmagic.a
cc -fpic -DPIC -O2 -fno-strict-aliasing -pipe  
-DMAGIC='"/usr/share/misc/magic"' -DBUILTIN_ELF -DELFCORE -DHAVE_CONFIG_H 
-I/usr/src/lib/libmagic -I/usr/src/lib/libmagic/../../contrib/file  
-c /usr/src/lib/libmagic/../../contrib/file/apprentice.c -o apprentice.So
cc -fpic -DPIC -O2 -fno-strict-aliasing -pipe  
-DMAGIC='"/usr/share/misc/magic"' -DBUILTIN_ELF -DELFCORE -DHAVE_CONFIG_H 
-I/usr/src/lib/libmagic -I/usr/src/lib/libmagic/../../contrib/file  
-c /usr/src/lib/libmagic/../../contrib/file/apptype.c -o apptype.So
cc -fpic -DPIC -O2 -fno-strict-aliasing -pipe  
-DMAGIC='"/usr/share/misc/magic"' -DBUILTIN_ELF -DELFCORE -DHAVE_CONFIG_H 
-I/usr/src/lib/libmagic -I/usr/src/lib/libmagic/../../contrib/file  
-c /usr/src/lib/libmagic/../../contrib/file/ascmagic.c -o ascmagic.So
cc -fpic -DPIC -O2 -fno-strict-aliasing -pipe  
-DMAGIC='"/usr/share/misc/magic"' -DBUILTIN_ELF -DELFCORE -DHAVE_CONFIG_H 
-I/usr/src/lib/libmagic -I/usr/src/lib/libmagic/../../contrib/file  
-c /usr/src/lib/libmagic/../../contrib/file/compress.c -o compress.So
cc -fpic -DPIC -O2 -fno-strict-aliasing -pipe  
-DMAGIC='"/usr/share/misc/magic"' -DBUILTIN_ELF -DELFCORE -DHAVE_CONFIG_H 
-I/usr/src/lib/libmagic -I/usr/src/lib/libmagic/../../contrib/file  
-c /usr/src/lib/libmagic/../../contrib/file/fsmagic.c -o fsmagic.So
cc -fpic -DPIC -O2 -fno-strict-aliasing -pipe  
-DMAGIC='"/usr/share/misc/magic"' -DBUILTIN_ELF -DELFCORE -DHAVE_CONFIG_H 
-I/usr/src/lib/libmagic -I/usr/src/lib/libmagic/../../contrib/file  
-c /usr/src/lib/libmagic/../../contrib/file/funcs.c -o funcs.So
cc -fpic -DPIC -O2 -fno-strict-aliasing -pipe  
-DMAGIC='"/usr/share/misc/magic"' -DBUILTIN_ELF -DELFCORE -DHAVE_CONFIG_H 
-I/usr/src/lib/libmagic -I/usr/src/lib/libmagic/../../contrib/file  
-c /usr/src/lib/libmagic/../../contrib/file/is_tar.c -o is_tar.So
cc -fpic -DPIC -O2 -fno-strict-aliasing -pipe  
-DMAGIC='"/usr/share/misc/magic"' -DBUILTIN_ELF -DELFCORE -DHAVE_CONFIG_H 
-I/usr/src/lib/libmagic -I/usr/src/lib/libmagic/../../contrib/file  
-c /usr/src/lib/libmagic/../../contrib/file/magic.c -o magic.So
cc -fpic -DPIC -O2 -fno-strict-aliasing -pipe  
-DMAGIC='"/usr/share/misc/magic"' -DBUILTIN_ELF -DELFCORE -DHAVE_CONFIG_H 
-I/usr/src/lib/libmagic -I/usr/src/lib/libmagic/../../contrib/file  
-c /usr/src/lib/libmagic/../../contrib/file/print.c -o print.So
cc -fpic -DPIC -O2 -fno-strict-aliasing -pipe  
-DMAGIC='"/usr/share/misc/magic"' -DBUILTIN_ELF -DELFCORE -DHAVE_CONFIG_H 
-I/usr/src/lib/libmagic -I/usr/src/lib/libmagic/../../contrib/file  
-c /usr/src/lib/libmagic/../../contrib/file/readelf.c -o readelf.So
cc -fpic -DPIC -O2 -fno-strict-aliasing -pipe  
-DMAGIC='"/usr/share/misc/magic"' -DBUILTIN_ELF -DELFCORE -DHAVE_CONFIG_H 
-I/usr/src/lib/libmagic -I/usr/src/lib/libmagic/../../contrib/file  
-c /usr/src/lib/libmagic/../../contrib/file/softmagic.c -o softmagic.So
building shared library libmagic.so.2
cat /usr/src/lib/libmagic/../../contrib/file/Header 
/usr/src/lib/libmagic/../../contrib/file/Localstuff 
/usr/src/lib/libmagic/../../contrib/file/Magdir/xo65,v 
/usr/src/lib/libmagic/../../contrib/file/Magdir/virtutech,v 
/usr/src/lib/libmagic/../../contrib/file/Magdir/uuencode,v 
/usr/src/lib/libmagic/../../contrib/file/Magdir/netbsd,v 
/usr/src/lib/libmagic/../../contrib/file/Magdir/allegro 
/usr/src/lib/libmagic/../../contrib/file/Magdir/sccs 
/usr/src/lib/libmagic/../../contrib/file/Magdir/sysex 
/usr/src/lib/libmagic/../../contrib/file/Magdir/xdelta 
/usr/src/lib/libmagic/../../contrib/file/Magdir/zyxe

Re: Upgrading 5.3 > 6.0 buildworld failure in libkrb5

[Vizion]

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 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(tm)  (1593.54-MHz 686-class CPU)
>>   Origin = "AuthenticAMD"  Id = 0x6a0  Stepping = 0
>>
>> Features=0x383fbff>A,CMOV,PAT,PSE36,MMX,FXSR,SSE> AMD Features=0xc048
>> real memory  = 2080309248 (1983 MB)
>> avail memory = 2030002176 (1935 MB)
>> ACPI APIC Table: 
>>
>> I have tried with very helpful advice from freebsd-questions contributors:
>>
>> with and without ccache
>>
>> 3x make cleandir prior to build
>> additional cvsup of source tree
>>
>> but the problem still remains .
>> Hopefully someone on stable may have the answer.
>>
>> Here is my make.conf
>>
>> SENDMAIL_CF_DIR=/usr/local/share/sendmail/cf
>> # added by use.perl 2005-11-18 10:51:36
>> PERL_VER=5.8.7
>> PERL_VERSION=5.8.7
>> .if !defined(NOCCACHE)
>> .if ${.CURDIR:M/usr/src*}
>> CC=/usr/local/libexec/ccache/cc
>> CXX=/usr/local/libexec/ccache/c++
>> .else
>> CC=cc
>> CXX=c++
>> .endif
>> .else
>> CC=/usr/bin/cc
>> CXX=/usr/bin/c++
>> .endif
>
>The example of setting up ccache in /etc/make.conf is just plain
>wrong.  It shouldn't be hardcoding CC to "/usr/bin/cc", similarly
>for CXX.  Comment out the ccache stuff completely in /etc/make.conf
>(or at least the last "else" part), make sure your PATH doesn't
>include the ccache path, and try again with an empty /usr/obj.
>Please report back if it succeeded (it should).  Please send your
>complaints to the ccache port MAINTAINER as he did not respond to
>my email explaining the problem, and I'm getting really tired of
>explaining this for the Nth time.
>
Thanks very much - I am building right now --after deinstalling ccache, make 
cleandir x3 and an empty /usr/obj. I will post the results here

Thanks again for taking the time to reply

david
-- 
40 yrs navigating and computing in blue waters.
English Owner & Captain of British Registered 60' bluewater Ketch S/V Taurus.
 Currently in San Diego, CA. Sailing bound for Europe via Panama Canal after 
completing engineroom refit.
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: Upgrading 5.3 > 6.0 buildworld failure in libkrb5

[Ruslan Ermilov]

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/GENERIC
> Timecounter "i8254" frequency 1193182 Hz quality 0
> CPU: AMD Athlon(tm)  (1593.54-MHz 686-class CPU)
>   Origin = "AuthenticAMD"  Id = 0x6a0  Stepping = 0
>   
> Features=0x383fbff
>   AMD Features=0xc048
> real memory  = 2080309248 (1983 MB)
> avail memory = 2030002176 (1935 MB)
> ACPI APIC Table: 
> 
> I have tried with very helpful advice from freebsd-questions contributors:
> 
> with and without ccache
> 
> 3x make cleandir prior to build
> additional cvsup of source tree
> 
> but the problem still remains . 
> Hopefully someone on stable may have the answer.
> 
> Here is my make.conf
> 
> SENDMAIL_CF_DIR=/usr/local/share/sendmail/cf
> # added by use.perl 2005-11-18 10:51:36
> PERL_VER=5.8.7
> PERL_VERSION=5.8.7
> .if !defined(NOCCACHE)
> .if ${.CURDIR:M/usr/src*}
> CC=/usr/local/libexec/ccache/cc
> CXX=/usr/local/libexec/ccache/c++
> .else
> CC=cc
> CXX=c++
> .endif
> .else
> CC=/usr/bin/cc
> CXX=/usr/bin/c++
> .endif
> 
The example of setting up ccache in /etc/make.conf is just plain
wrong.  It shouldn't be hardcoding CC to "/usr/bin/cc", similarly
for CXX.  Comment out the ccache stuff completely in /etc/make.conf
(or at least the last "else" part), make sure your PATH doesn't
include the ccache path, and try again with an empty /usr/obj.
Please report back if it succeeded (it should).  Please send your
complaints to the ccache port MAINTAINER as he did not respond to
my email explaining the problem, and I'm getting really tired of
explaining this for the Nth time.


Cheers,
-- 
Ruslan Ermilov
[EMAIL PROTECTED]
FreeBSD committer


pgpA7r82scSj2.pgp
Description: PGP signature

Re: Upgrading 5.3 > 6.0 buildworld failure in libkrb5

[Gunther Nikl]

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 advice from freebsd-questions contributors:
> 
> with and without ccache
> 3x make cleandir prior to build
> additional cvsup of source tree

  I always build with an empty /usr/obj.

> /usr/src/kerberos5/lib/libkrb5/../../../crypto/heimdal/lib/krb5/changepw.c:170:
>  
> error: syntax error before "chpw"

  Dou you need kerberos? I disabeled it through a knob in /etc/make.conf.
  Check /usr/share/examples/etc/make.conf for details.

  Last weekend I upgraded my 5-STABLE installation to 6-STABLE and all
  went smoothly. First I built 6-STABLE from 5-STABLE, activated it and
  then I built 6-STABLE again.

  Gunther
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Upgrading 5.3 > 6.0 buildworld failure in libkrb5

[Vizion]

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(tm)  (1593.54-MHz 686-class CPU)
  Origin = "AuthenticAMD"  Id = 0x6a0  Stepping = 0
  
Features=0x383fbff
  AMD Features=0xc048
real memory  = 2080309248 (1983 MB)
avail memory = 2030002176 (1935 MB)
ACPI APIC Table: 

I have tried with very helpful advice from freebsd-questions contributors:

with and without ccache
3x make cleandir prior to build
additional cvsup of source tree

but the problem still remains . 
Hopefully someone on stable may have the answer.

Here is my make.conf

SENDMAIL_CF_DIR=/usr/local/share/sendmail/cf
# added by use.perl 2005-11-18 10:51:36
PERL_VER=5.8.7
PERL_VERSION=5.8.7
.if !defined(NOCCACHE)
.if ${.CURDIR:M/usr/src*}
CC=/usr/local/libexec/ccache/cc
CXX=/usr/local/libexec/ccache/c++
.else
CC=cc
CXX=c++
.endif
.else
CC=/usr/bin/cc
CXX=/usr/bin/c++
.endif

I show the output from pkg_info below the build result

# cd /usr/src && make NOCCACHE=1 buildworld &&  make NOCCACHE=1 buildkernel

/* NOTE: I get the same failure for the same function in linkrb5 no matter 
what I try: */

/libkrb5/../../../crypto/heimdal/lib/krb5/net_write.c 
/usr/src/kerberos5/lib/libkrb5/../../../crypto/heimdal/lib/krb5/padata.c 
/usr/src/kerberos5/lib/libkrb5/../../../crypto/heimdal/lib/krb5/principal.c 
/usr/src/kerberos5/lib/libkrb5/../../../crypto/heimdal/lib/krb5/prog_setup.c 
/usr/src/kerberos5/lib/libkrb5/../../../crypto/heimdal/lib/krb5/prompter_posix.c
 /usr/src/kerberos5/lib/libkrb5/../../../crypto/heimdal/lib/krb5/rd_cred.c 
/usr/src/kerberos5/lib/libkrb5/../../../crypto/heimdal/lib/krb5/rd_error.c 
/usr/src/kerberos5/lib/libkrb5/../../../crypto/heimdal/lib/krb5/rd_priv.c 
/usr/src/kerberos5/lib/libkrb5/../../../crypto/heimdal/lib/krb5/rd_rep.c 
/usr/src/kerberos5/lib/libkrb5/../../../crypto/heimdal/lib/krb5/rd_req.c 
/usr/src/kerberos5/lib/libkrb5/../../../crypto/heimdal/lib/krb5/rd_safe.c 
/usr/src/kerberos5/lib/libkrb5/../../../crypto/heimdal/lib/krb5/read_message.c 
/usr/src/kerberos5/lib/libkrb5/../../../crypto/heimdal/lib/krb5/recvauth.c 
/usr/src/kerberos5/lib/libkrb5/../../../crypto/heimdal/lib/krb5/replay.c 
/usr/src/kerberos5/lib/libkrb5/../../../crypto/heimdal/lib/krb5/send_to_kdc.c 
/usr/src/kerberos5/lib/libkrb5/../../../crypto/heimdal/lib/krb5/sendauth.c 
/usr/src/kerberos5/lib/libkrb5/../../../crypto/heimdal/lib/krb5/set_default_realm.c
 
/usr/src/kerberos5/lib/libkrb5/../../../crypto/heimdal/lib/krb5/sock_principal.c
 /usr/src/kerberos5/lib/libkrb5/../../../crypto/heimdal/lib/krb5/store.c 
/usr/src/kerberos5/lib/libkrb5/../../../crypto/heimdal/lib/krb5/store_emem.c 
/usr/src/kerberos5/lib/libkrb5/../../../crypto/heimdal/lib/krb5/store_fd.c 
/usr/src/kerberos5/lib/libkrb5/../../../crypto/heimdal/lib/krb5/store_mem.c 
/usr/src/kerberos5/lib/libkrb5/../../../crypto/heimdal/lib/krb5/ticket.c 
/usr/src/kerberos5/lib/libkrb5/../../../crypto/heimdal/lib/krb5/time.c 
/usr/src/kerberos5/lib/libkrb5/../../../crypto/heimdal/lib/krb5/transited.c 
/usr/src/kerberos5/lib/libkrb5/../../../crypto/heimdal/lib/krb5/verify_init.c 
/usr/src/kerberos5/lib/libkrb5/../../../crypto/heimdal/lib/krb5/verify_user.c 
/usr/src/kerberos5/lib/libkrb5/../../../crypto/heimdal/lib/krb5/version.c 
/usr/src/kerberos5/lib/libkrb5/../../../crypto/heimdal/lib/krb5/warn.c 
/usr/src/kerberos5/lib/libkrb5/../../../crypto/heimdal/lib/krb5/write_message.c
/usr/bin/cc -O2 -fno-strict-aliasing -pipe  
-I/usr/src/kerberos5/lib/libkrb5/../../../crypto/heimdal/lib/krb5 
-I/usr/src/kerberos5/lib/libkrb5/../../../crypto/heimdal/lib/asn1 
-I/usr/src/kerberos5/lib/libkrb5/../../../crypto/heimdal/lib/roken -I. 
-DHAVE_CONFIG_H -I/usr/src/kerberos5/lib/libkrb5/../../include -DINET6  
-c /usr/src/kerberos5/lib/libkrb5/../../../crypto/heimdal/lib/krb5/acl.c
/usr/bin/cc -O2 -fno-strict-aliasing -pipe  
-I/usr/src/kerberos5/lib/libkrb5/../../../crypto/heimdal/lib/krb5 
-I/usr/src/kerberos5/lib/libkrb5/../../../crypto/heimdal/lib/asn1 
-I/usr/src/kerberos5/lib/libkrb5/../../../crypto/heimdal/lib/roken -I. 
-DHAVE_CONFIG_H -I/usr/src/kerberos5/lib/libkrb5/../../include -DINET6  
-c /usr/src/kerberos5/lib/libkrb5/../../../crypto/heimdal/lib/krb5/add_et_list.c
/usr/bin/cc -O2 -fno-strict-aliasing -pipe  
-I/usr/src/kerberos5/lib/libkrb5/../../../crypto/heimdal/lib/krb5 
-I/usr/src/kerberos5/lib/libkrb5/../../../crypto/heimdal/lib/asn1 
-I/usr/src/kerberos5/lib/libkrb5/../../../crypto/heimdal/lib/roken -I. 
-DHAVE_CONFIG_H -I/usr/src/kerberos5/lib/libkrb5/../../include -DINET6  
-c 
/usr/src/kerberos5/lib/libkrb5/../../../crypto/heimdal/lib/krb5/addr_families.c
/usr/bin/cc -O2 -fno-strict-aliasing -pipe  
-I/usr/src/kerberos5/lib/libkrb5/../../../crypto/heimdal/lib/krb5 
-I/usr/src/kerberos5/lib/libkrb5/../../../crypto/heimdal/lib/asn

Re: 5.4 -> 6.0 buildworld failure

[Markus Buretorp]

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/libkvm  -c
   /usr/src/lib/libkvm/kvm_getloadavg.c
   cc -O2 -pipe -march=athlon-xp -DLIBC_SCCS -I/usr/src/lib/libkvm  -c
   /usr/src/lib/libkvm/kvm_getswapinfo.c
   cc -O2 -pipe -march=athlon-xp -DLIBC_SCCS -I/usr/src/lib/libkvm  -c
   /usr/src/lib/libkvm/kvm_proc.c
   /usr/src/lib/libkvm/kvm_proc.c: In function `kvm_proclist':
   /usr/src/lib/libkvm/kvm_proc.c:108: error: storage size of 't_cdev'
   isn't known
   /usr/src/lib/libkvm/kvm_proc.c:114: error: storage size of 'pr'
   isn't known
   /usr/src/lib/libkvm/kvm_proc.c:176: error: structure has no member
   named `ki_jid'
   /usr/src/lib/libkvm/kvm_proc.c:377: error: structure has no member
   named `p_rux'
   *** Error code 1

   Stop in /usr/src/lib/libkvm.
   *** Error code 1

   Stop in /usr/src.
   *** Error code 1

   Stop in /usr/src.
   *** Error code 1

   Stop in /usr/src.
   *** Error code 1

   Stop in /usr/src.

Some info

   FreeBSD jmb.mine.nu 5.4-STABLE FreeBSD 5.4-STABLE #0: Mon Aug 15
   21:16:37 CEST 2005   
[EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC  i386



Regards,
Markus

Ok, I solved it. I had some stupid exports (INCLUDE_PATH etc) in my 
shell config.

___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: 5.4 -> 6.0 buildworld failure

[Markus Buretorp]

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/libkvm/kvm_proc.c:108: error: storage size of 't_cdev'
 isn't known
   



I've just done a buildworld of RELENG_6 on 5.3 without problems so I
suspect it's something you've done.  It looks very much like
kvm_proc.c is being built using the wrong include files - the ones in
/usr/include/sys rather than the ones in /usr/src/sys/sys.

Where is this error occurring during the buildworld?  (What are the
latest lines beginning '>>>' and '===>')
What non-standard bits do you have in your command line, /etc/make.conf
or MAKEOBJDIRPREFIX?

 


>>> stage 4.2: building libraries
   ...
   ===> lib/libkvm (depend,all,install)

make.conf:

   WITHOUT_X11=yes
   CPUTYPE?=athlon-xp
   CFLAGS=-O2 -pipe
   COPTFLAGS=-O -pipe
   # added by use.perl 2005-06-24 23:01:50
   PERL_VER=5.8.7
   PERL_VERSION=5.8.7

Note, I've tried without the first four lines.

   $ cd lib/libkvm   
   /usr/src [EMAIL PROTECTED]
   $ make 
   ...r/src/lib/libkvm [EMAIL PROTECTED]

   cc -O -pipe  -DLIBC_SCCS -I/usr/src/lib/libkvm  -c
   /usr/src/lib/libkvm/kvm_proc.c
   /usr/src/lib/libkvm/kvm_proc.c: In function `kvm_proclist':
   /usr/src/lib/libkvm/kvm_proc.c:108: error: storage size of 't_cdev'
   isn't known
   /usr/src/lib/libkvm/kvm_proc.c:114: error: storage size of 'pr'
   isn't known
   /usr/src/lib/libkvm/kvm_proc.c:176: error: structure has no member
   named `ki_jid'
   /usr/src/lib/libkvm/kvm_proc.c:377: error: structure has no member
   named `p_rux'
   *** Error code 1

   Stop in /usr/src/lib/libkvm.



I found this, http://www.freebsd.org/cgi/query-pr.cgi?pr=77821 , but it 
doesn't help me much. I don't now what I've done. I've used cvsup and 
buildworld several times.

___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: 5.4 -> 6.0 buildworld failure

[Peter Jeremy]

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: storage size of 't_cdev'
>   isn't known

I've just done a buildworld of RELENG_6 on 5.3 without problems so I
suspect it's something you've done.  It looks very much like
kvm_proc.c is being built using the wrong include files - the ones in
/usr/include/sys rather than the ones in /usr/src/sys/sys.

Where is this error occurring during the buildworld?  (What are the
latest lines beginning '>>>' and '===>')
What non-standard bits do you have in your command line, /etc/make.conf
or MAKEOBJDIRPREFIX?

-- 
Peter Jeremy
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: 5.4 -> 6.0 buildworld failure

[Chris]

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 much troube upgrading.
The process is outlined well on the FBSD site and to surmise:

Assuming you have done your cvsup of the src tree:

# cd /usr/src/usr.sbin/mergemaster
# ./mergemaster.sh -p

Drop to Single User Mode:
As the superuser, you can execute:

# shutdown now

from a running system, which will drop it to single user mode.
Alternatively, reboot the system, and at the boot prompt,
enter the -s flag. The system will then boot single user.
At the shell prompt you should then run:

# fsck -p
# mount -u /
# mount -a -t ufs
# swapon -a

# cd /usr/obj
# chflags -R noschg *
# rm -rf *

# cd /usr/src

# make buildworld

# cd /usr/src
# make buildkernel KERNCONF=MYKERNEL
# make installkernel KERNCONF=MYKERNEL

# shutdown now

# fsck -p
# mount -u /
# mount -a -t ufs
# swapon -a

# cd /usr/src
# make installworld

# shutdown -r now

Done.

-- 
Best regards,
Chris

Nature always sides with the hidden flaw.
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

5.4 -> 6.0 buildworld failure

[Markus Buretorp]

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/libkvm/kvm_getloadavg.c
   cc -O2 -pipe -march=athlon-xp -DLIBC_SCCS -I/usr/src/lib/libkvm  -c
   /usr/src/lib/libkvm/kvm_getswapinfo.c
   cc -O2 -pipe -march=athlon-xp -DLIBC_SCCS -I/usr/src/lib/libkvm  -c
   /usr/src/lib/libkvm/kvm_proc.c
   /usr/src/lib/libkvm/kvm_proc.c: In function `kvm_proclist':
   /usr/src/lib/libkvm/kvm_proc.c:108: error: storage size of 't_cdev'
   isn't known
   /usr/src/lib/libkvm/kvm_proc.c:114: error: storage size of 'pr'
   isn't known
   /usr/src/lib/libkvm/kvm_proc.c:176: error: structure has no member
   named `ki_jid'
   /usr/src/lib/libkvm/kvm_proc.c:377: error: structure has no member
   named `p_rux'
   *** Error code 1

   Stop in /usr/src/lib/libkvm.
   *** Error code 1

   Stop in /usr/src.
   *** Error code 1

   Stop in /usr/src.
   *** Error code 1

   Stop in /usr/src.
   *** Error code 1

   Stop in /usr/src.

Some info

   FreeBSD jmb.mine.nu 5.4-STABLE FreeBSD 5.4-STABLE #0: Mon Aug 15
   21:16:37 CEST 2005
   [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC  i386



Regards,
Markus
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: RELENG_6 buildworld failure (amd64)

[Conrad J. Sabatier]

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/amd64/usr/include/netinet/ip_lookup.h:33: error:
> `FR_GROUPLEN' undeclared here (not in a function)
> /usr/obj/usr/src/amd64/usr/include/netinet/ip_lookup.h:61: error:
> syntax error before "ioctlcmd_t"
> In file included from ioctl.c:76:
> /usr/obj/usr/src/amd64/usr/include/netinet/ip_scan.h:99: error:
> syntax
> error before "ioctlcmd_t"
> *** Error code 1
> 
> Stop in /usr/src/usr.bin/kdump.
> 
> I can't find any definition of FR_GROUPLEN anywhere.  What's going on
> here?

Nevermind.  It was just some corruption in my src tree.  Sorry.

-- 
Conrad J. Sabatier <[EMAIL PROTECTED]> -- "In Unix veritas"
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

RELENG_6 buildworld failure (amd64)

[Conrad J. Sabatier]

===> 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_GROUPLEN' undeclared here (not in a function)
/usr/obj/usr/src/amd64/usr/include/netinet/ip_lookup.h:61: error:
syntax error before "ioctlcmd_t"
In file included from ioctl.c:76:
/usr/obj/usr/src/amd64/usr/include/netinet/ip_scan.h:99: error: syntax
error before "ioctlcmd_t"
*** Error code 1

Stop in /usr/src/usr.bin/kdump.

I can't find any definition of FR_GROUPLEN anywhere.  What's going on
here?

-- 
Conrad J. Sabatier <[EMAIL PROTECTED]> -- "In Unix veritas"
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

buildworld failure -- 5.4 pre-pre

[epilogue]

[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



---
the bits that i'm pulling down
---
src-base
src-bin
src-contrib
src-crypto
src-etc
src-gnu
src-include
src-libexec
src-lib
src-sbin
src-secure
src-share
src-sys
src-sys-crypto
src-tools
src-usrbin
src-usrsbin


---
make.conf settings
---
CPUTYPE?=p3   #i686
CFLAGS= -O -pipe
BDECFLAGS=  -W -Wall -ansi -pedantic -Wbad-function-cast -Wcast-align \
  -Wcast-qual -Wchar-subscripts -Winline \
  -Wmissing-prototypes -Wnested-externs -Wpointer-arith \
   -Wredundant-decls -Wshadow -Wstrict-prototypes -Wwrite-strings
COPTFLAGS= -O -pipe

NO_BLUETOOTH=  true # do not build Bluetooth related stuff
NO_FORTRAN=  true # do not build g77 and related libraries
NO_I4B=true # do not build isdn4bsd package
NO_KERBEROS=true # do not build and install Kerberos 5 (KTH
Heimdal)
NO_VINUM=   true# do not build Vinum utilities
NOATM=true# do not build ATM related programs and
libraries
NOINFO=   true# do not make or install info files
NOPROFILE= true# Avoid compiling profiled libraries


---
finally, the error
---
/usr/bin/cc -O -pipe -march=pentium3 -I/usr/src/lib/libc/include
-I/usr/src/lib/libc/../../include -I/usr/src/lib/libc/i386 -D__DB
INTERFACE_PRIVATE -I/usr/src/lib/libc/../../contrib/gdtoa -DINET6
-I/usr/obj/usr/src/lib/libc -DPOSIX_MISTAKE -I/usr/src/lib/libc/ locale
-DBROKEN_DES -DPORTMAP -DDES_BUILTIN -I/usr/src/lib/libc/rpc -DYP
-DHESIOD -Wsystem-headers -Werror -Wall -Wno-format-y2k -
Wno-uninitialized -c /usr/src/lib/libc/gen/termios.c

/usr/bin/cc -fpic -DPIC -O -pipe -march=pentium3
-I/usr/src/lib/libc/include -I/usr/src/lib/libc/../../include
-I/usr/src/lib/libc /i386 -D__DBINTERFACE_PRIVATE
-I/usr/src/lib/libc/../../contrib/gdtoa -DINET6
-I/usr/obj/usr/src/lib/libc -DPOSIX_MISTAKE -I/usr/s rc/lib/libc/locale
-DBROKEN_DES -DPORTMAP -DDES_BUILTIN -I/usr/src/lib/libc/rpc -DYP
-DHESIOD -Wsystem-headers -Werror -Wall -Wno- format-y2k
-Wno-uninitialized -c /usr/src/lib/libc/gen/termios.c -o termios.So

/usr/src/lib/libc/gen/syslog.c: In function `connectlog':

/usr/src/lib/libc/gen/syslog.c:365: error: `_PATH_LOG_PRIV' undeclared
(first use in this function)

/usr/src/lib/libc/gen/syslog.c:365: error: (Each undeclared identifier
is reported only once

/usr/src/lib/libc/gen/syslog.c:365: error: for each function it appears
in.)

*** Error code 1

/usr/src/lib/libc/gen/syslog.c: In function `connectlog':

/usr/src/lib/libc/gen/syslog.c:365: error: `_PATH_LOG_PRIV' undeclared
(first use in this function)

/usr/src/lib/libc/gen/syslog.c:365: error: (Each undeclared identifier
is reported only once

/usr/src/lib/libc/gen/syslog.c:365: error: for each function it appears
in.)

*** Error code 1
2 errors
*** Error code 2
1 error
*** Error code 2
1 error
*** Error code 2
1 error
*** Error code 2
1 error
*** Error code 2
1 error
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: Buildworld failure on RELENG_4_10 (sendmail) My fault

[James Housley]

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 getting 
the failure.

===> etc
===> etc/sendmail
make: don't know how to make freebsd.cf. Stop
*** Error code 2
1 error
*** Error code 2
1 error
*** Error code 2
1 error
*** Error code 2
1 error
There is currently no freebsd.mc or freebsd.cf in /usr/src/etc/sendmail 
on RELENG_4_10, it does exist in RELENG_4 and RELENG_4_9 and those 
inbetween.

Jim
My refuse file was based on code before the Bad Idea of putting freebsd.mc 
as an example was fixed.

Jim
--
/"\   ASCII Ribbon Campaign  .
\ / - NO HTML/RTF in e-mail  .
 X  - NO Word docs in e-mail .
/ \ -
[EMAIL PROTECTED]  http://www.FreeBSD.org The Power to Serve
[EMAIL PROTECTED]  http://www.TheHousleys.net
-
Studies show that 1 out of every 4 Americans suffer some form of
mental illness.  So look at your three best friends, if they
are okay it is YOU!


smime.p7s
Description: S/MIME Cryptographic Signature

Buildworld failure on RELENG_4_10 (sendmail)

[James Housley]

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.

===> etc
===> etc/sendmail
make: don't know how to make freebsd.cf. Stop
*** Error code 2
1 error
*** Error code 2
1 error
*** Error code 2
1 error
*** Error code 2
1 error
There is currently no freebsd.mc or freebsd.cf in /usr/src/etc/sendmail on 
RELENG_4_10, it does exist in RELENG_4 and RELENG_4_9 and those inbetween.

Jim
--
/"\   ASCII Ribbon Campaign  .
\ / - NO HTML/RTF in e-mail  .
 X  - NO Word docs in e-mail .
/ \ -
[EMAIL PROTECTED]  http://www.FreeBSD.org The Power to Serve
[EMAIL PROTECTED]  http://www.TheHousleys.net
-
Studies show that 1 out of every 4 Americans suffer some form of
mental illness.  So look at your three best friends, if they
are okay it is YOU!


smime.p7s
Description: S/MIME Cryptographic Signature

Re: Buildworld failure

[Gene Bomgardner]

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 think?



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-stable" in the body of the message

make buildworld failure

[John]

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 freebsd.mc. Stop
*** Error code 2

Stop in /usr/src/etc.
*** Error code 1

Stop in /usr/src.
*** Error code 1

Stop in /usr/src.
*** Error code 1

Stop in /usr/src.

I am running 

FreeBSD 4.6-STABLE #0: Tue Aug 20 03:05:49 BST 2002

The machine is:

CPU: AMD Athlon(tm) processor (1335.62-MHz 686-class CPU)
  Origin = "AuthenticAMD"  Id = 0x642  Stepping = 2
  Features=0x183f9ff
  AMD Features=0xc044<,AMIE,DSP,3DNow!>
real memory  = 251658240 (245760K bytes)
avail memory = 240951296 (235304K bytes)

Can anyone tell me how I can fix this please?

Thanks
-- 
John - [EMAIL PROTECTED] - http://www.reiteration.net/~jfm
For PGP public key finger [EMAIL PROTECTED] or see webpage

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-stable" in the body of the message

make buildworld failure on -STABLE

[John]

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 buildworld error:

/usr.sbin/sshd/../../lib/libssh/libssh.a -lcrypt -lcrypto -lutil -lz 
-lwrap -lpam
gzip -cn 
/home/system/src/secure/usr.sbin/sshd/../../../crypto/openssh/sshd.8 > 
sshd.8.gz
===> etc
===> etc/sendmail
make: don't know how to make freebsd.mc. Stop
*** Error code 2

Has this got anything to do with the sed problem reported recently? To me, 
it looks like something else (and apache compiled fine).

cheers
-- 
John - [EMAIL PROTECTED] - http://www.reiteration.net/~jfm
For PGP public key finger [EMAIL PROTECTED] or see webpage

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-stable" in the body of the message

4.5 buildworld failure: libfetch

[Webcraft]

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

Thank you

Feisal
http://www.webcraft99.com

---

===> libfetch
cc -O -pipe -march=pentiumpro -I. -DINET6
-I/usr/obj/usr/src/i386/usr/include -W -Wall -Wstrict-prototypes
-Wmissing-prototypes -Wpointer-arith -Wno-uninitialized -Werror
-Wreturn-type -Wcast-qual -Wwrite-strings -Wswitch -Wshadow  -c
/usr/src/lib/libfetch/fetch.c -o fetch.o
cc -O -pipe -march=pentiumpro -I. -DINET6
-I/usr/obj/usr/src/i386/usr/include -W -Wall -Wstrict-prototypes
-Wmissing-prototypes -Wpointer-arith -Wno-uninitialized -Werror
-Wreturn-type -Wcast-qual -Wwrite-strings -Wswitch -Wshadow  -c
/usr/src/lib/libfetch/common.c -o common.o
cc1: warnings being treated as errors
/usr/src/lib/libfetch/common.c: In function `_fetch_putln':
/usr/src/lib/libfetch/common.c:343: warning: cast discards qualifiers
from pointer target type
/usr/src/lib/libfetch/common.c:345: warning: cast discards qualifiers
from pointer target type
*** Error code 1

Stop in /usr/src/lib/libfetch.
*** Error code 1

Stop in /usr/src/lib.
*** Error code 1

Stop in /usr/src.
*** Error code 1

Stop in /usr/src.
*** Error code 1

Stop in /usr/src.

__
Do You Yahoo!?
Great stuff seeking new owners in Yahoo! Auctions! 
http://auctions.yahoo.com

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-stable" in the body of the message

buildworld failure: boot "-972 bytes available"; maxusers?

[Andreas Ntaflos]

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 with the following error messages:

  [snipped]
  objcopy -S -O binary boot2.out boot2.bin
  btxld -v -E 0x1000 -f bin -b
  /usr/obj/usr/src/sys/boot/i386/boot2/../btx/btx/btx -l boot2.ldr  -o bo
  ot2.ld -P 1 boot2.bin
  kernel: ver=1.01 size=740 load=9000 entry=9010 map=16M pgctl=1:1
  client: fmt=bin size=188c text=0 data=0 bss=0 entry=0
  output: fmt=bin size=21cc text=200 data=1fcc org=0 entry=0
  -972 bytes available
  *** Error code 1
  [snipped]
  
  Kinda strange error (?).
  
  Now this isn't something I've seen very often, in fact, I only had
  something like this once when I built world on my laptop. I had made some
  changes to the kernel config file, and, among others setting maxusers to
  64 (just to experiment a bit). When the build failed, I reduced maxusers
  back to 32 and it went smooth.

  But this time, I haven't made any changes to the kernel config file since
  several weeks (no maxusers, nothing), however, rebuilding world from source 
  went fine. Plus, make buildworld failed, not building the kernel.
  make'ing just kernel KERNCONF=CONFIGFILE works, so I even am not sure if 
  this is related.

  Has anyone a clue about it? 
  Recvsupping didn't seem to help (how else could it be ;))
  
  Attached you'll find the last part of the buildworld log file, maybe it
  is of interest.

Thanks and regards  
-- 
Andreas "ant" Ntaflos   
[EMAIL PROTECTED]
Vienna, AUSTRIA


uudecode < /usr/src/share/isdn/4.al.uu
uudecode < /usr/src/share/isdn/5.al.uu
uudecode < /usr/src/share/isdn/6.al.uu
uudecode < /usr/src/share/isdn/7.al.uu
uudecode < /usr/src/share/isdn/8.al.uu
uudecode < /usr/src/share/isdn/9.al.uu
uudecode < /usr/src/share/isdn/beep.al.uu
uudecode < /usr/src/share/isdn/msg.al.uu
===> share/sendmail
===> sys
===> sys/boot
===> sys/boot/ficl
cc -nostdinc -O -pipe   -mpreferred-stack-boundary=2 
-I/usr/obj/usr/src/i386/usr/include  -I/usr/src/sys/boot/ficl 
-I/usr/src/sys/boot/ficl/i386 -I/usr/src/sys/boot/ficl/../common -DFICL_TRACE -c 
/usr/src/sys/boot/ficl/dict.c -o dict.o
cc -nostdinc -O -pipe   -mpreferred-stack-boundary=2 
-I/usr/obj/usr/src/i386/usr/include  -I/usr/src/sys/boot/ficl 
-I/usr/src/sys/boot/ficl/i386 -I/usr/src/sys/boot/ficl/../common -DFICL_TRACE -c 
/usr/src/sys/boot/ficl/ficl.c -o ficl.o
/usr/src/sys/boot/ficl/dict.c: In function `dictAbortDefinition':
/usr/src/sys/boot/ficl/dict.c:52: warning: statement with no effect
/usr/src/sys/boot/ficl/dict.c:58: warning: statement with no effect
/usr/src/sys/boot/ficl/ficl.c: In function `ficlFreeVM':
/usr/src/sys/boot/ficl/ficl.c:151: warning: statement with no effect
/usr/src/sys/boot/ficl/dict.c: In function `dictAppendWord2':
/usr/src/sys/boot/ficl/dict.c:210: warning: statement with no effect
/usr/src/sys/boot/ficl/dict.c:232: warning: statement with no effect
/usr/src/sys/boot/ficl/ficl.c: In function `ficlBuild':
/usr/src/sys/boot/ficl/ficl.c:189: warning: statement with no effect
/usr/src/sys/boot/ficl/dict.c: In function `dictLookup':
/usr/src/sys/boot/ficl/dict.c:435: warning: statement with no effect
/usr/src/sys/boot/ficl/dict.c:443: warning: statement with no effect
/usr/src/sys/boot/ficl/dict.c: In function `dictLookupLoc':
/usr/src/sys/boot/ficl/dict.c:464: warning: statement with no effect
/usr/src/sys/boot/ficl/dict.c:480: warning: statement with no effect
cc -nostdinc -O -pipe   -mpreferred-stack-boundary=2 
-I/usr/obj/usr/src/i386/usr/include  -I/usr/src/sys/boot/ficl 
-I/usr/src/sys/boot/ficl/i386 -I/usr/src/sys/boot/ficl/../common -DFICL_TRACE -c 
/usr/src/sys/boot/ficl/math64.c -o math64.o
cc -nostdinc -O -pipe   -mpreferred-stack-boundary=2 
-I/usr/obj/usr/src/i386/usr/include  -I/usr/src/sys/boot/ficl 
-I/usr/src/sys/boot/ficl/i386 -I/usr/src/sys/boot/ficl/../common -DFICL_TRACE -c 
/usr/src/sys/boot/ficl/stack.c -o stack.o
cc -nostdinc -O -pipe   -mpreferred-stack-boundary=2 
-I/usr/obj/usr/src/i386/usr/include  -I/usr/src/sys/boot/ficl 
-I/usr/src/sys/boot/ficl/i386 -I/usr/src/sys/boot/ficl/../common -DFICL_TRACE -c 
/usr/src/sys/boot/ficl/vm.c -o vm.o
cc -nostdinc -O -pipe   -mpreferred-stack-boundary=2 
-I/usr/obj/usr/src/i386/usr/include  -I/usr/src/sys/boot/ficl 
-I/usr/src/sys/boot/ficl/i386 -I/usr/src/sys/boot/ficl/../common -DFICL_TRACE -c 
/usr/src/sys/boot/ficl/words.c -o words.o
/usr/src/sys/boot/ficl/words.c: In function `colon':
/usr/src/sys/boot/ficl/words.c:454: warning: implicit declaration of function 
`dictCheckThreshold'
/usr/src/sys/boot/ficl/words.c: In function `exitCoIm':
/usr/src/sys/boot/ficl/words.c:546: warning: statement with no effect
cc -nostdinc -O -pipe   -mpreferred-stack-boundary=2 
-I/usr/obj/usr/src/i386/usr/include  -I/usr/src/sys/boot/ficl 
-I/usr/s

Re: RELENG_4_3 (4.3-SECURITY buildworld failure)

[Kris Kennaway]

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 break
this..the problem is probably on your end.

Kris

 PGP signature

RELENG_4_3 (4.3-SECURITY buildworld failure)

[Jeff Palmer]

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; make 
_EXTRADEPENDecho stlstats: /usr/obj/usr/src/i386/usr/lib/libc.a 
/usr/obj/usr/src/i386/usr/lib/libncurses.a 
/usr/obj/usr/src/i386/usr/lib/libmytinfo.a >> .depend===> 
usr.sbin/wicontrolrm -f .dependmkdep -f .depend -a    
-DWICACHE -I/usr/obj/usr/src/i386/usr/include  
/usr/src/usr.sbin/wicontrol/wicontrol.c/usr/src/usr.sbin/wicontrol/wicontrol.c:680: 
unterminated character constant/usr/src/usr.sbin/wicontrol/wicontrol.c:681: 
unterminated character constant/usr/src/usr.sbin/wicontrol/wicontrol.c:688: 
unterminated character constant/usr/src/usr.sbin/wicontrol/wicontrol.c:627: 
unterminated `#if' conditionalmkdep: compile failed*** Error code 
1
 
Stop in /usr/src/usr.sbin/wicontrol.*** 
Error code 1

Re: Buildworld failure in /usr/src/lib/libc

[Kent Stewart]

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.bmwfilms.com

mailto:[EMAIL PROTECTED]
http://kstewart.urx.com/kstewart/index.html
FreeBSD News http://daily.daemonnews.org/

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-stable" in the body of the message

Re: buildworld failure

[Matt Bedynek]

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-all

-- 
Matt Bedynek
[EMAIL PROTECTED]

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-stable" in the body of the message

Re: buildworld failure

[Kris Kennaway]

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

buildworld failure

[Matt Bedynek]

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/src/lib/libncurses 
-I/usr/src/lib/libncurses/../../contrib/ncurses/ncurses 
-I/usr/src/lib/libncurses/../../contrib/ncurses/include -Wall -DFREEBSD_NATIVE 
-DNDEBUG -DHAVE_CONFIG_H -DTERMIOS -DMAIN_PROGRAM  
/usr/src/lib/libncurses/../../contrib/ncurses/ncurses/tinfo/comp_hash.c
cat namehdr boolnames boolfnames numnames numfnames strnames strfnames nameftr > 
names.c
In file included from curses.h:77,
 from 
/usr/src/lib/libncurses/../../contrib/ncurses/ncurses/curses.priv.h:234,
 from 
/usr/src/lib/libncurses/../../contrib/ncurses/ncurses/tinfo/comp_hash.c:41:
/usr/include/unctrl.h:57: syntax error before `unctrl'
/usr/include/unctrl.h:57: warning: data definition has no type or storage class
cc -o make_keys -O -pipe  -I. -I/usr/src/lib/libncurses 
-I/usr/src/lib/libncurses/../../contrib/ncurses/ncurses 
-I/usr/src/lib/libncurses/../../contrib/ncurses/include -Wall -DFREEBSD_NATIVE 
-DNDEBUG -DHAVE_CONFIG_H -DTERMIOS 
/usr/src/lib/libncurses/../../contrib/ncurses/ncurses/tinfo/make_keys.c
In file included from curses.h:77,
 from 
/usr/src/lib/libncurses/../../contrib/ncurses/ncurses/curses.priv.h:234,
 from 
/usr/src/lib/libncurses/../../contrib/ncurses/ncurses/tinfo/make_keys.c:38:
/usr/include/unctrl.h:57: syntax error before `unctrl'
/usr/include/unctrl.h:57: warning: data definition has no type or storage class
*** Error code 1
*** Error code 1
2 errors
*** Error code 2
1 error
*** Error code 2
1 error
*** Error code 2
1 error

-- 
Matt Bedynek
[EMAIL PROTECTED]

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-stable" in the body of the message

Re: buildworld failure (3-4-2001 cvsup)

[Mike Tancsa]

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.
>
>--
>-- David([EMAIL PROTECTED])
>Disclaimer: Not speaking for FreeBSD, just expressing my own opinion.
>
>To Unsubscribe: send mail to [EMAIL PROTECTED]
>with "unsubscribe freebsd-stable" in the body of the message


Mike Tancsa,  tel +1 519 651 3400
Network Administration,   [EMAIL PROTECTED]
Sentex Communications www.sentex.net
Cambridge, Ontario Canada www.sentex.net/mike


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-stable" in the body of the message