Re: CLANG buildworld failure: lint: cannot exec /usr/obj/usr/src/tmp/usr/bin/cc: No such file or directory

2012-03-04 Thread Manfred Antar
At 05:25 AM 3/4/2012, O. Hartmann wrote: Buildworld of FBSD 10.o-CUR/amd64 fails with the below shown error messages since this weekend: clang -O2 -pipe -O2 -fno-strict-aliasing -pipe -pipe -O3 -fno-strict-aliasing -march=native -I/usr/src/usr.bin/xlint/xlint/../lint1 -DPREFIX=\\

Re: CLANG buildworld failure: lint: cannot exec /usr/obj/usr/src/tmp/usr/bin/cc: No such file or directory

2012-03-04 Thread Pegasus Mc Cleaft
On Sunday 04 March 2012 16:27:56 Manfred Antar wrote: At 05:25 AM 3/4/2012, O. Hartmann wrote: Buildworld of FBSD 10.o-CUR/amd64 fails with the below shown error messages since this weekend: clang -O2 -pipe -O2 -fno-strict-aliasing -pipe -pipe -O3 -fno-strict-aliasing -march=native

Re: CLANG buildworld failure: lint: cannot exec /usr/obj/usr/src/tmp/usr/bin/cc: No such file or directory

2012-03-04 Thread O. Hartmann
On 03/04/12 18:51, Pegasus Mc Cleaft wrote: On Sunday 04 March 2012 16:27:56 Manfred Antar wrote: At 05:25 AM 3/4/2012, O. Hartmann wrote: Buildworld of FBSD 10.o-CUR/amd64 fails with the below shown error messages since this weekend: clang -O2 -pipe -O2 -fno-strict-aliasing -pipe -pipe -O3

Re: CLANG buildworld failure: lint: cannot exec /usr/obj/usr/src/tmp/usr/bin/cc: No such file or directory

2012-03-04 Thread Dimitry Andric
On 2012-03-04 21:34, O. Hartmann wrote: ... Where are those new WITH_CLANG_ tags documented? In src.conf(5), where all the WITH_ and WITHOUT_ settings are documented. I should probably have sent a heads up to this list, to announce this new setting, which installs clang as /usr/bin/cc,

Re: CLANG buildworld failure: lint: cannot exec /usr/obj/usr/src/tmp/usr/bin/cc: No such file or directory

2012-03-04 Thread O. Hartmann
On 03/04/12 22:46, Dimitry Andric wrote: On 2012-03-04 21:34, O. Hartmann wrote: ... Where are those new WITH_CLANG_ tags documented? In src.conf(5), where all the WITH_ and WITHOUT_ settings are documented. I should probably have sent a heads up to this list, to announce this new

Re: CLANG buildworld failure: lint: cannot exec /usr/obj/usr/src/tmp/usr/bin/cc: No such file or directory

2012-03-04 Thread Dimitry Andric
On 2012-03-05 00:40, O. Hartmann wrote: ... All right, my /etc/src.conf looks like this now (as it does before): WITH_CLANG= YES WITH_CLANG_EXTRAS= YES # WITH_BIND_LIBS= YES WITH_BIND_SIGCHASE= YES WITH_BIND_LARGE_FILE= YES # WITH_IDEA= YES

Re: r225932 libsasl undefined references - buildworld failure

2011-10-18 Thread Anton Shterenlikht
On Tue, Oct 18, 2011 at 01:29:38AM +0900, Hajimu UMEMOTO wrote: Hi, On Mon, 17 Oct 2011 16:54:36 +0100 Anton Shterenlikht me...@bristol.ac.uk said: mexas On r225932 with mexas SENDMAIL_CFLAGS+= -I/usr/local/include -DSASL=2 mexas SENDMAIL_LDFLAGS+= -L/usr/local/lib mexas

r225932 libsasl undefined references - buildworld failure

2011-10-17 Thread Anton Shterenlikht
On r225932 with SENDMAIL_CFLAGS+= -I/usr/local/include -DSASL=2 SENDMAIL_LDFLAGS+= -L/usr/local/lib SENDMAIL_LDADD+=-lsasl2 in /etc/make.conf and with cyrus-sasl-2.1.25_1 installed, I get these errors on make buildworld: cc -O2 -pipe

Re: r225932 libsasl undefined references - buildworld failure

2011-10-17 Thread Hajimu UMEMOTO
Hi, On Mon, 17 Oct 2011 16:54:36 +0100 Anton Shterenlikht me...@bristol.ac.uk said: mexas On r225932 with mexas SENDMAIL_CFLAGS+= -I/usr/local/include -DSASL=2 mexas SENDMAIL_LDFLAGS+= -L/usr/local/lib mexas SENDMAIL_LDADD+=-lsasl2 mexas in /etc/make.conf and with

Re: buildworld failure r223619 to 225128

2011-10-16 Thread Beach Geek
On Thu, Sep 1, 2011 at 6:49 PM, Beach Geek labeachg...@gmail.com wrote: On 8/27/11, Matt Thyer matt.th...@gmail.com wrote: Have you tried moving aside your existing /usr/src and checking it out afresh? On Aug 28, 2011 12:47 AM, Beach Geek labeachg...@gmail.com wrote: On 8/25/11, Dimitry

Re: buildworld failure r223619 to 225128

2011-10-16 Thread Adrian Chadd
On 17 October 2011 00:19, Beach Geek labeachg...@gmail.com wrote: PS. A side note, we got a native driver working for the RTL8188CE wireless card, but it's still really buggy, but it's a start. Yay! I have one of those around here somewhere too.. Adrian

Re: buildworld failure r223619 to 225128

2011-09-01 Thread Beach Geek
On 8/27/11, Matt Thyer matt.th...@gmail.com wrote: Have you tried moving aside your existing /usr/src and checking it out afresh? On Aug 28, 2011 12:47 AM, Beach Geek labeachg...@gmail.com wrote: On 8/25/11, Dimitry Andric d...@freebsd.org wrote: On 2011-08-25 17:12, Beach Geek wrote: make

Re: buildworld failure r223619 to 225128

2011-08-27 Thread Beach Geek
On 8/25/11, Dimitry Andric d...@freebsd.org wrote: On 2011-08-25 17:12, Beach Geek wrote: make buildworld failed trying to upgrade from r223619 to r225128. (Note: Updating other boxes from r224774 to r225119 went flawless) On failing laptop (Toshibs Sat C655D)

buildworld failure r223619 to 225128

2011-08-25 Thread Beach Geek
make buildworld failed trying to upgrade from r223619 to r225128. (Note: Updating other boxes from r224774 to r225119 went flawless) On failing laptop (Toshibs Sat C655D) uname -v FreeBSD 9.0-CURRENT #0 r223619 Tue Jun 28 CDT 2011 ... svn info /usr/src URL: svn.freebsd.org/base/head ...

Re: buildworld failure r223619 to 225128

2011-08-25 Thread Dimitry Andric
On 2011-08-25 17:12, Beach Geek wrote: make buildworld failed trying to upgrade from r223619 to r225128. (Note: Updating other boxes from r224774 to r225119 went flawless) On failing laptop (Toshibs Sat C655D) /usr/include/c++/4.2/bits/stringfwd.h:56: internal compiler error:

Re: buildworld failure

2011-08-15 Thread Alexander Best
On Mon Aug 15 11, Robert Watson wrote: On Sun, 14 Aug 2011, Alexander Best wrote: has anybody seen this buildworld failure? Could you try the attached patch and see if it helps? I currently have it in the re@ approval queue. It does appear to fix the problem here. thanks. the patch

Buildworld failure after update r224806 to r224886

2011-08-15 Thread Ivan Klymenko
Hello, all! I have: uname -a FreeBSD nonamehost 9.0-BETA1 FreeBSD 9.0-BETA1 #0 r224806M: Sat Aug 13 15:43:38 EEST 2011 ivan@nonamehost:/usr/obj/usr/src/sys/mk9 amd64 Buildworld failure after update r224806 to r224886 In my configuration files since nothing has changed... Building

Re: Buildworld failure after update r224806 to r224886

2011-08-15 Thread Niclas Zeising
On 2011-08-15 19:38, Ivan Klymenko wrote: Hello, all! I have: uname -a FreeBSD nonamehost 9.0-BETA1 FreeBSD 9.0-BETA1 #0 r224806M: Sat Aug 13 15:43:38 EEST 2011 ivan@nonamehost:/usr/obj/usr/src/sys/mk9 amd64 Buildworld failure after update r224806 to r224886 In my configuration

Re: Buildworld failure after update r224806 to r224886

2011-08-15 Thread Ivan Klymenko
В Mon, 15 Aug 2011 20:12:35 +0200 Niclas Zeising niclas.zeis...@gmail.com пишет: ... Someone have any idea what is that? Thanks! There was a period when there was a bug in dev/std{in,err,out}, which amongst other things made it impossible to complete a buildworld. Compile a

Re: FreeBSD 9.0-BETA1/amd64 r224808: buildworld failure: === lib/clang/include (all), 1 error, *** Error code 2, 1 error, *** Error code 2, 1 error

2011-08-14 Thread Hartmann, O.
On 08/13/11 18:30, Test Rat wrote: Test Ratttse...@gmail.com writes: [...] Remaking `cat' Results of making cat: clang -O2 -pipe -O3 -Qunused-arguments -fcolor-diagnostics -march=native -g -fno-omit-frame-pointer -std=gnu99 -fstack-protector -Wsystem-headers -Wall -Wno-format-y2k -W

buildworld failure

2011-08-14 Thread Alexander Best
hi there, has anybody seen this buildworld failure? === sys/modules/portalfs (depend) @ - /usr/git-freebsd-head/sys machine - /usr/git-freebsd-head/sys/amd64/include x86 - /usr/git-freebsd-head/sys/x86/include awk -f @/tools/vnode_if.awk @/kern/vnode_if.src -p awk -f @/tools/vnode_if.awk @/kern

Re: buildworld failure

2011-08-14 Thread Kip Macy
The module makefile needs to be updated evidently. Just add it to the dependencies until rwatson gets around to fixing it. On Sun, Aug 14, 2011 at 11:50 PM, Alexander Best arun...@freebsd.org wrote: hi there, has anybody seen this buildworld failure? === sys/modules/portalfs (depend

Re: buildworld failure

2011-08-14 Thread Robert Watson
that aren't built for INVARIANTS but a GENERIC kernel that is built for INVARIANTS...) It sounds like a recipe for unfortunate things. Robert On Sun, Aug 14, 2011 at 11:50 PM, Alexander Best arun...@freebsd.org wrote: hi there, has anybody seen this buildworld failure? === sys/modules/portalfs

Avoid kernels between r224778 and r224841; bug causes buildworld failure

2011-08-14 Thread Robert Watson
Dear all: As you may have seen from current@ traffic, a bug crept in during the Capsicum merge, introduced by the infamous Last Minute Cleanup and not caught in pre-commit testing. The most noticed effect of the bug is to cause buildworld to fail due to a problem with

Re: buildworld failure

2011-08-14 Thread Robert Watson
On Sun, 14 Aug 2011, Alexander Best wrote: has anybody seen this buildworld failure? Could you try the attached patch and see if it helps? I currently have it in the re@ approval queue. It does appear to fix the problem here. Generally, I would strongly advise against using modules

FreeBSD 9.0-BETA1/amd64 r224808: buildworld failure: === lib/clang/include (all),1 error,*** Error code 2,1 error,*** Error code 2,1 error

2011-08-13 Thread Hartmann, O.
I run several boxes based on FreebSD 9.0-BETA1/amd64, compiled with clang. Since yesterday, I run on all of these machines into strange situations: buildworld won't build anymore, it fails always on all boxes at the very same position as showed by the error message below. I can build and

Re: FreeBSD 9.0-BETA1/amd64 r224808: buildworld failure: === lib/clang/include (all), 1 error, *** Error code 2, 1 error, *** Error code 2, 1 error

2011-08-13 Thread Marcelo/Porks
On Sat, Aug 13, 2011 at 05:39, Hartmann, O. ohart...@zedat.fu-berlin.de wrote: I run several boxes based on FreebSD 9.0-BETA1/amd64, compiled with clang. Since yesterday, I run on all of these machines into strange situations: buildworld won't build anymore, it fails always on all boxes at

Re: FreeBSD 9.0-BETA1/amd64 r224808: buildworld failure: === lib/clang/include (all), 1 error, *** Error code 2, 1 error, *** Error code 2, 1 error

2011-08-13 Thread Test Rat
Hartmann, O. ohart...@zedat.fu-berlin.de writes: I run several boxes based on FreebSD 9.0-BETA1/amd64, compiled with clang. Since yesterday, I run on all of these machines into strange situations: buildworld won't build anymore, it fails always on all boxes at the very same position as

Re: FreeBSD 9.0-BETA1/amd64 r224808: buildworld failure: === lib/clang/include (all), 1 error, *** Error code 2, 1 error, *** Error code 2, 1 error

2011-08-13 Thread Test Rat
Test Rat ttse...@gmail.com writes: [...] Remaking `cat' Results of making cat: clang -O2 -pipe -O3 -Qunused-arguments -fcolor-diagnostics -march=native -g -fno-omit-frame-pointer -std=gnu99 -fstack-protector -Wsystem-headers -Wall -Wno-format-y2k -W -Wno-unused-parameter

Re: Clang buildworld failure due to multiple definitions of __isnanf

2011-06-30 Thread David Schultz
On Sun, Jun 26, 2011, Eric McCorkle wrote: I've both seen reports and experienced make buildworld with clang failing in usr.bin/xlint/lint1 (really, make kernel-toolchain is what fails), because lint1 is statically linked, and there is a definition of __isnanf in both libc and libm. GCC,

Re: Clang buildworld failure due to multiple definitions of __isnanf

2011-06-28 Thread Eric McCorkle
On 6/28/11 1:42 AM, Benjamin Kaduk wrote: On Tue, 28 Jun 2011, Benjamin Kaduk wrote: On Mon, 27 Jun 2011, Eric McCorkle wrote: make.conf: CPUTYPE?=core2 .if !defined(CC) || ${CC} == cc CC=clang CFLAGS=-Qunused-arguments .endif .if !defined(CXX) || ${CXX} == c++ CXX=clang++ .endif NO_WERROR=

Re: Clang buildworld failure due to multiple definitions of __isnanf

2011-06-28 Thread Garrett Cooper
On Mon, Jun 27, 2011 at 8:59 AM, Eric McCorkle e...@shadowsun.net wrote: On 6/27/11 8:29 AM, Dimitry Andric wrote: On 2011-06-27 04:32, Eric McCorkle wrote: I've both seen reports and experienced make buildworld with clang failing in usr.bin/xlint/lint1 (really, make kernel-toolchain is what

Re: Clang buildworld failure due to multiple definitions of __isnanf

2011-06-28 Thread Garrett Cooper
On Tue, Jun 28, 2011 at 12:47 PM, Pan Tsu iny...@gmail.com wrote: Garrett Cooper yaneg...@gmail.com writes: [...] Just noticed, the CFLAGS would disable optimization, which would explain why no one else seems to see this.  Still, I think the underlying issue warrants investigation. Two

Re: Clang buildworld failure due to multiple definitions of __isnanf

2011-06-27 Thread Dimitry Andric
On 2011-06-27 04:32, Eric McCorkle wrote: I've both seen reports and experienced make buildworld with clang failing in usr.bin/xlint/lint1 (really, make kernel-toolchain is what fails), because lint1 is statically linked, and there is a definition of __isnanf in both libc and libm. GCC, on the

Re: Clang buildworld failure due to multiple definitions of __isnanf

2011-06-27 Thread Eric McCorkle
On 6/27/11 8:29 AM, Dimitry Andric wrote: On 2011-06-27 04:32, Eric McCorkle wrote: I've both seen reports and experienced make buildworld with clang failing in usr.bin/xlint/lint1 (really, make kernel-toolchain is what fails), because lint1 is statically linked, and there is a definition of

Re: Clang buildworld failure due to multiple definitions of __isnanf

2011-06-27 Thread Benjamin Kaduk
On Mon, 27 Jun 2011, Eric McCorkle wrote: make.conf: CPUTYPE?=core2 .if !defined(CC) || ${CC} == cc CC=clang CFLAGS=-Qunused-arguments .endif .if !defined(CXX) || ${CXX} == c++ CXX=clang++ .endif NO_WERROR= WERROR= NO_FSCHG= PERL_VERSION=5.12.3 Just noticed, the CFLAGS would disable

Re: Clang buildworld failure due to multiple definitions of __isnanf

2011-06-27 Thread Benjamin Kaduk
On Tue, 28 Jun 2011, Benjamin Kaduk wrote: On Mon, 27 Jun 2011, Eric McCorkle wrote: make.conf: CPUTYPE?=core2 .if !defined(CC) || ${CC} == cc CC=clang CFLAGS=-Qunused-arguments .endif .if !defined(CXX) || ${CXX} == c++ CXX=clang++ .endif NO_WERROR= WERROR= NO_FSCHG= PERL_VERSION=5.12.3 Just

Clang buildworld failure due to multiple definitions of __isnanf

2011-06-26 Thread Eric McCorkle
I've both seen reports and experienced make buildworld with clang failing in usr.bin/xlint/lint1 (really, make kernel-toolchain is what fails), because lint1 is statically linked, and there is a definition of __isnanf in both libc and libm. GCC, on the other hand, builds just fine. The file

Re: Clang buildworld failure due to multiple definitions of __isnanf

2011-06-26 Thread Steve Kargl
On Sun, Jun 26, 2011 at 10:32:02PM -0400, Eric McCorkle wrote: A better solution, I think, is to modify math.h with something like this: #ifdef __clang__ #define isnan(n) __builtin_isnan(n) ... #endif Please, no. Don't touch math.h. -- Steve

Re: Buildworld failure

2010-12-23 Thread Giorgos Keramidas
On Wed, 22 Dec 2010 19:29:39 -0500, Derek Tattersall d...@mebtel.net wrote: I blew away /usr/src and /usr/obj and re-cvsuped this morning. I attempted to buildworld, only to have the process die in the mkdep step. CC='clang' mkdep -f .depend -a

Re: Buildworld failure

2010-12-23 Thread Derek Tattersall
* Giorgos Keramidas keram...@freebsd.org [101223 06:30]: On Wed, 22 Dec 2010 19:29:39 -0500, Derek Tattersall d...@mebtel.net wrote: I blew away /usr/src and /usr/obj and re-cvsuped this morning. I attempted to buildworld, only to have the process die in the mkdep step. CC='clang' mkdep

Re: Buildworld failure

2010-12-23 Thread Giorgos Keramidas
On Thu, 23 Dec 2010 08:05:16 -0500, Derek Tattersall d...@mebtel.net wrote: NOTE: I did build a snapshot from /head at -r 216642 last afternoon and it worked fine with the default CC. So if something broke *after* that revision try bisecting from -r 216642 to the version you built, to see if

Re: Buildworld failure

2010-12-23 Thread Garrett Cooper
On Dec 23, 2010, at 5:33 AM, Giorgos Keramidas keram...@freebsd.org wrote: On Thu, 23 Dec 2010 08:05:16 -0500, Derek Tattersall d...@mebtel.net wrote: NOTE: I did build a snapshot from /head at -r 216642 last afternoon and it worked fine with the default CC. So if something broke *after* that

Buildworld failure

2010-12-22 Thread Derek Tattersall
I blew away /usr/src and /usr/obj and re-cvsuped this morning. I attempted to buildworld, only to have the process die in the mkdep step. CC='clang' mkdep -f .depend -a -I/usr/src/cddl/usr.bin/ctfmerge/../../../sys/cddl/compat/opensolaris

Buildworld failure on 5.1-REL

2003-11-29 Thread Odhiambo Washington
Hoping against hope! Still trying to fight out a problem which could possibly be a simple one compared to the others that I have seen. I have put a bzipped error text at the following URL. http://ns2.wananchi.com/~wash/FreeBSD/ Is there some clue in that file that can help me get a successful

Re: Buildworld failure on 5.1-REL

2003-11-29 Thread YONETANI Tomokazu
Hi. On Sat, Nov 29, 2003 at 11:42:36AM +0300, Odhiambo Washington wrote: Hoping against hope! Still trying to fight out a problem which could possibly be a simple one compared to the others that I have seen. I have put a bzipped error text at the following URL.

Re: Buildworld failure on 5.1-REL

2003-11-29 Thread Odhiambo Washington
* YONETANI Tomokazu [EMAIL PROTECTED] [20031129 12:17]: wrote: Hi. On Sat, Nov 29, 2003 at 11:42:36AM +0300, Odhiambo Washington wrote: Hoping against hope! Still trying to fight out a problem which could possibly be a simple one compared to the others that I have seen. I have put a

Alpha too.. (was: Re: buildworld failure on sparc64?

2003-11-13 Thread Wilko Bulte
On Wed, Nov 12, 2003 at 11:37:18PM +0100, Wilko Bulte wrote: And on Alpha as well: === lib/libpam/modules/pam_radius^M cc -O -pipe -mcpu=ev6 -mieee -I/usr/src/lib/libpam/modules/pam_radius/../../../../contrib/openpam/inc lude -I/usr/src/lib/libpam/modules/pam_radius/../../libpam -Wsystem-headers

buildworld failure on sparc64?

2003-11-12 Thread Wilko Bulte
=== lib/libpam/modules/pam_radius cc -O -pipe -I/usr/src/lib/libpam/modules/pam_radius/../../../../contrib/openpam/include -I/usr/src/lib/libpam/modules/pam_radius/../../libpam -Wsystem-headers -Werror -Wall -Wno-format-y2k -W -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wreturn-type

Buildworld Failure

2003-11-11 Thread Thomas T. Veldhouse
cc -elf -ffreestanding -Os -fno-builtin -fno-guess-branch-probability -fomi t-frame-pointer -mno-align-long-strings -mrtd -DUFS1_AND_UFS2 -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

Re: Buildworld Failure

2003-11-11 Thread Rob Evers
Thomas T. Veldhouse wrote: cc -elf -ffreestanding -Os -fno-builtin -fno-guess-branch-probability -fomi t-frame-pointer -mno-align-long-strings -mrtd -DUFS1_AND_UFS2 -I/usr/src/ sys/boot/i386/boot2/../../common -I/usr/src/sys/boot/i386/boot2/../btx/lib -I. -Wall -Waggregate-return

Re: buildworld failure: don't know how to make thr_atfork.c

2003-11-05 Thread Jeremy Messenger
On Wed, 5 Nov 2003 17:17:05 +1030, Alex Wilkinson [EMAIL PROTECTED] wrote: CVSup'd today [Wed Nov 5 17:15:14 CST 2003] and buildworld fails. $ make buildworld . snip === lib/libpthread make: don't know how to make thr_atfork.c. Stop *** Error code 2 snip It's already fixed, Daniel has

Re: buildworld failure: don't know how to make thr_atfork.c

2003-11-05 Thread villoing florian
The problem was solved. See cvs-all mailing list. thr_atfork.c was forgotten to be committed. Just run cvsup again. Florian --- Alex Wilkinson [EMAIL PROTECTED] a écrit : CVSup'd today [Wed Nov 5 17:15:14 CST 2003] and buildworld fails. $ make buildworld . === lib/libpcap yacc

buildworld failure: don't know how to make thr_atfork.c

2003-11-04 Thread Alex Wilkinson
CVSup'd today [Wed Nov 5 17:15:14 CST 2003] and buildworld fails. $ make buildworld . === lib/libpcap yacc -d -p pcapyy -o grammar.c /usr/src/lib/libpcap/../../contrib/libpcap/grammar.y ln -sf grammar.h tokdefs.h lex -t -Ppcapyy /usr/src/lib/libpcap/../../contrib/libpcap/scanner.l

10/23 cvsup buildworld failure

2003-10-24 Thread Michael L. Squires
Tinderbox /vol/vol0/users/des/tinderbox/CURRENT/amd64/amd64/src/lib/libfetch/common.c:60: error: initializer element is not constant Under 5.1-CURRENT or i386 cvsuped on 10/23 I get the same failure, with the additional error message /usr/src/lib/libfetch/common.c:58: error:

Re: 10/23 cvsup buildworld failure

2003-10-24 Thread Kris Kennaway
On Fri, Oct 24, 2003 at 10:47:22AM -0500, Michael L. Squires wrote: Tinderbox /vol/vol0/users/des/tinderbox/CURRENT/amd64/amd64/src/lib/libfetch/common.c:60: error: initializer element is not constant Under 5.1-CURRENT or i386 cvsuped on 10/23 I get the same failure, with the

Re: 10/23 cvsup buildworld failure

2003-10-24 Thread Matteo Riondato
Il Ven, 2003-10-24 alle 17:47, Michael L. Squires ha scritto: Tinderbox /vol/vol0/users/des/tinderbox/CURRENT/amd64/amd64/src/lib/libfetch/common.c:60: error: initializer element is not constant Under 5.1-CURRENT or i386 cvsuped on 10/23 I get the same failure, with the additional

Re: buildworld failure

2003-08-30 Thread Doug Barton
On Fri, 29 Aug 2003, Sheldon Hearn wrote: Okay, you philosophize while the rest of us follow the advice of the folks who have a good understanding of gcc's optimizer. :-) Not to be disagreeable, but the gcc developers seem to think that -O2 should always produce better code, and never produce

buildworld failure

2003-08-29 Thread Mike Jakubik
I have re cvsuped 2 days later (Fri Aug 29 10:19:29 EDT 2003) and I am still getting the same error, can anyone shed some light here? Thanks. === lib/libpam/modules/pam_echo cc -O2 -pipe -march=pentium4 -I/usr/src/lib/libpam/modules/pam_echo/../../.. /../contrib/openpam/include

RE: buildworld failure

2003-08-29 Thread Mike Jakubik
Subject: Re: buildworld failure On Fri, 29 Aug 2003, Mike Jakubik wrote: === lib/libpam/modules/pam_echo cc -O2 -pipe -march=pentium4 -I/usr/src/lib/libpam/modules/pam_echo/../../.. Turn off -O2 and your build will complete. -- Hi! I'm a .signature virus! Copy me into your ~/.signature

Re: buildworld failure

2003-08-29 Thread Sheldon Hearn
On (2003/08/29 11:30), Mike Jakubik wrote: Why should I have to turn off all my optimization options when building world? Because it's not working? Mind you, it's only -O2 that you're recommended to turn off; -O works fine. This shouldn't be like that. 4.x always compiled fine with -O2 and

RE: buildworld failure

2003-08-29 Thread Mike Jakubik
-Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Sheldon Hearn Sent: Friday, August 29, 2003 11:36 AM To: Mike Jakubik Cc: Current Subject: Re: buildworld failure On (2003/08/29 11:30), Mike Jakubik wrote: Why should I have to turn off all my

Re: buildworld failure

2003-08-29 Thread Sheldon Hearn
On (2003/08/29 11:41), Mike Jakubik wrote: Yes, I can see that its not working. But this is a solution to the cause, not the problem. Shouldn't this be fixed? Depends on how much work is involved in fixing it, and what the negative impact is of leaving it. Do you know what the impact is?

Re: buildworld failure

2003-08-29 Thread Robert Watson
On Fri, 29 Aug 2003, Mike Jakubik wrote: I have re cvsuped 2 days later (Fri Aug 29 10:19:29 EDT 2003) and I am still getting the same error, can anyone shed some light here? Here's the build output from my build of pam_echo a couple of days ago: cc -O -pipe -mcpu=pentiumpro

Re: buildworld failure

2003-08-29 Thread Sheldon Hearn
On (2003/08/29 11:48), Robert Watson wrote: The differences here seem to be: (1) I'm using -O, not -O2 (2) I'm optimizing -mcpu as pentiumpro, not pentium4 Isn't pentium4 a known-broken optimization at the moment? Ciao, Sheldon. ___ [EMAIL

Re: buildworld failure

2003-08-29 Thread Scott M. Likens
On Fri, 2003-08-29 at 09:04, Sheldon Hearn wrote: On (2003/08/29 11:48), Robert Watson wrote: The differences here seem to be: (1) I'm using -O, not -O2 (2) I'm optimizing -mcpu as pentiumpro, not pentium4 Isn't pentium4 a known-broken optimization at the moment? Ciao, Sheldon.

RE: buildworld failure

2003-08-29 Thread Mike Jakubik
-Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Sheldon Hearn Sent: Friday, August 29, 2003 12:05 PM To: Robert Watson Cc: Mike Jakubik; Current Subject: Re: buildworld failure On (2003/08/29 11:48), Robert Watson wrote: The differences here seem

RE: buildworld failure

2003-08-29 Thread Mike Jakubik
-Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Sheldon Hearn Sent: Friday, August 29, 2003 11:49 AM To: Mike Jakubik Cc: Current Subject: Re: buildworld failure On (2003/08/29 11:41), Mike Jakubik wrote: Yes, I can see that its not working

Re: buildworld failure

2003-08-29 Thread Daniel C. Sobral
Mike Jakubik wrote: I think the impact is more social. People will try to compile world and get failures. Specially people coming from the 4.x branch, where this sort of think never occurred. If this is the only thing preventing a clean makeworld with -O2, I think its worth taking a look at.

RE: buildworld failure

2003-08-29 Thread Robert Watson
On Fri, 29 Aug 2003, Mike Jakubik wrote: Depends on how much work is involved in fixing it, and what the negative impact is of leaving it. Do you know what the impact is? I think the impact is more social. People will try to compile world and get failures. Specially people coming

Re: buildworld failure

2003-08-29 Thread David O'Brien
On Fri, Aug 29, 2003 at 12:36:46PM -0400, Mike Jakubik wrote: I think the impact is more social. People will try to compile world and get failures. Specially people coming from the 4.x branch, where this sort of think never occurred. If this is the only thing preventing a clean makeworld

Re: buildworld failure

2003-08-29 Thread David O'Brien
On Fri, Aug 29, 2003 at 06:04:54PM +0200, Sheldon Hearn wrote: Isn't pentium4 a known-broken optimization at the moment? No, not since GCC 3.2.x. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To

Re: buildworld failure

2003-08-29 Thread Matthias Andree
Daniel C. Sobral [EMAIL PROTECTED] writes: I've been using freebsd since the 2.x days, I have always compiled world and ports with -O2, and never had any instability issues due to the optimizations. I have switched back to -O and -march=pentium4, the buildworld finished ok. Lucky you.

-current buildworld failure in libpam

2003-07-12 Thread Michael Reifenberger
Hi, buildworld stops in libpam: ... === lib/libpam/modules/pam_deny cc -O2 -pipe -I/usr/src/lib/libpam/modules/pam_deny/../../../../contrib/openpam/include -I/usr/src/lib/libpam/modules/pam_deny/../../libpam -Wsystem-headers -Werror -Wall -Wno-format-y2k -W -Wstrict-prototypes

Re: -current buildworld failure in libpam

2003-07-12 Thread Craig Rodrigues
On Sat, Jul 12, 2003 at 10:59:44AM +0200, Michael Reifenberger wrote: === lib/libpam/modules/pam_echo cc -O2 -pipe -I/usr/src/lib/libpam/modules/pam_echo/../../../../contrib/openpam/include -I/usr/src/lib/libpam/modules/pam_echo/../../libpam -Wsystem-headers -Werror -Wall -Wno-format-y2k -W

Re: -current buildworld failure in libpam

2003-07-12 Thread Michael Reifenberger
On Sat, 12 Jul 2003, Craig Rodrigues wrote: Date: Sat, 12 Jul 2003 10:02:31 -0400 From: Craig Rodrigues [EMAIL PROTECTED] To: Michael Reifenberger [EMAIL PROTECTED] Cc: FreeBSD-Current [EMAIL PROTECTED] Subject: Re: -current buildworld failure in libpam On Sat, Jul 12, 2003 at 10:59:44AM

buildworld failure - BFD - targmatch.h

2003-06-19 Thread Michael W. Oliver
Hello -CURRENT, nice to meet you. My name is Michael Oliver, and I have been running FreeBSD for a few years, and am a BIG fan. I have recently decided to run -CURRENT on my laptop (Gateway SOLO-9300cl), and on my most recent buildworld (past -CURRENT upgrades have worked), I am having trouble.

Re: buildworld failure - BFD - targmatch.h

2003-06-19 Thread Jeremy Messenger
On Thu, 19 Jun 2003 08:05:38 -0400, Michael W. Oliver [EMAIL PROTECTED] wrote: Hello -CURRENT, nice to meet you. My name is Michael Oliver, and I have been running FreeBSD for a few years, and am a BIG fan. I have recently decided to run -CURRENT on my laptop (Gateway SOLO-9300cl), and on my

Re: buildworld failure - BFD - targmatch.h

2003-06-19 Thread Michael W. Oliver
+--- On Thursday, June 19, 2003 09:38, | Jeremy Messenger proclaimed: | | On Thu, 19 Jun 2003 08:05:38 -0400, Michael W. Oliver | | [EMAIL PROTECTED] wrote: | Hello -CURRENT, nice to meet you. My name is Michael Oliver, and I | have been running FreeBSD for a few years, and am a BIG fan. I

i386 Buildworld Failure alloca cdefs.h

2003-06-14 Thread Matt
Got this on a buildworld from current sources just now, is this possibly related to the commit to sys/cdefs.h from DES ? === usr.bin/xlint/llib lint -cghapbx -Cposix /usr/src/usr.bin/xlint/llib/llib-lposix llib-lposix: In file included from /usr/obj/usr/src/i386/usr/include/sys/types.h:45,

Re: i386 Buildworld Failure alloca cdefs.h

2003-06-14 Thread Dag-Erling Smorgrav
Matt [EMAIL PROTECTED] writes: Got this on a buildworld from current sources just now, is this possibly related to the commit to sys/cdefs.h from DES ? I did not touch cdefs.h, David did. The commit message was inaccurate; while it claims that I submitted the patch, I'm only responsible for

Re: i386 Buildworld Failure alloca cdefs.h

2003-06-14 Thread Dag-Erling Smorgrav
Dag-Erling Smorgrav [EMAIL PROTECTED] writes: The #error line he added is incorrect as it breaks compliant applications which do not use the nonstandard and nonportable alloca(3). The attached patch *may* fix this. It is currently undergoing testing. DES -- Dag-Erling Smorgrav - [EMAIL

5.1-RELEASE buildworld Failure

2003-06-09 Thread Nick H.
Hello, Below is a buildworld failure on a 5.1-RELEASE box with a Generic kernel: building shared library libkse.so.1 thr_libc.So: In function `sigaction': thr_libc.So(.text+0x54): multiple definition of `_sigaction' thr_sigaction.So(.text+0x0): first defined here thr_libc.So: In function

GEOM buildworld failure

2003-06-02 Thread David Magda
Getting the following message on a buildworld: mkdep -f .depend -a -I/usr/src/lib/libgeom /usr/src/lib/libgeom/geom_getxml.c /usr/src/lib/libgeom/geom_stats.c /usr/src/lib/libgeom/geom_xml2tree.c /usr/src/lib/libgeom/geom_ctl.c /usr/src/lib/libgeom/geom_ctl.c:48:27:

Re: GEOM buildworld failure

2003-06-02 Thread Poul-Henning Kamp
This is already be fixed. In message [EMAIL PROTECTED], David Magda writes: Getting the following message on a buildworld: mkdep -f .depend -a -I/usr/src/lib/libgeom /usr/src/lib/libgeom/geom_getxml.c /usr/src/lib/libgeom/geom_stats.c /usr/src/lib/libgeom/geom_xml2tree.c

Re: buildworld failure

2003-01-30 Thread Matt
Just to let you know me bad for the report I emailed yesterday. It was just the fact I was using -j4 and so I guess it got ahead of itself. Without the - j4 the current cvsup of HEAD has built with no problems. Regards, Matt. --- Matt ([EMAIL PROTECTED]) http://www.xtaz.co.uk/ --- To

Re: make buildworld failure

2003-01-29 Thread Jeff Utter
Yeah, that fixed the above mentioned problem.. however i'm running into a build problem about an hour later, related to telnet.. maybe it was fixed overnight in cvs, i'll see if it will build now. Let me know how it goes... I may wanna try that To Unsubscribe: send mail to [EMAIL PROTECTED]

Re: make buildworld failure

2003-01-29 Thread leafy
On Wed, Jan 29, 2003 at 06:16:04AM -0500, Jeff Utter wrote: Yeah, that fixed the above mentioned problem.. however i'm running into a build problem about an hour later, related to telnet.. maybe it was fixed overnight in cvs, i'll see if it will build now. I don't think so, I cvsupped about 30

Re: make buildworld failure

2003-01-29 Thread Nick H. -- Technical Support Engineer
: Wednesday, January 29, 2003 5:48 AM Subject: Re: make buildworld failure : On Wed, Jan 29, 2003 at 06:16:04AM -0500, Jeff Utter wrote: : Yeah, that fixed the above mentioned problem.. however i'm running into a build problem about an hour later, related to telnet.. maybe it was fixed overnight in cvs

Buildworld failure

2003-01-29 Thread Matt
Apologies if this comes through again after this. I sent it from a different account this afternoon and it doesn't appear to have got through so I'm sending it again. I get a different problem to the telnet buildworld failure: === lib/liby sh /usr/src/tools/install.sh -C -o root -g wheel -m

make buildworld failure

2003-01-28 Thread Nick H. -- Technical Support Engineer
Got this today... src is fresh from cvsup2 mkdep -f pend -a-I/usr/src/lib/libpam/modules/pam_ssh/../../../../crypto/openssh -I/usr/src/lib/libpam/modules/pam_ssh/../../../../contrib/openpam/include -I /usr/src/lib/libpam/modules/pam_ssh/../../libpam

Re: make buildworld failure

2003-01-28 Thread Nick H. -- Technical Support Engineer
PROTECTED] - Original Message - From: Jeff Utter [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Tuesday, January 28, 2003 7:47 PM Subject: Re: make buildworld failure I'm having the same results here... i've been trying to figure out what the problem is for a while.. i think it's just

Re: make buildworld failure

2003-01-28 Thread Jeff Utter
i think my system is building successfully now.. i did 2 things: 1.) deleted my whole src tree, and re-downloaded it 2.) cp /usr/src/crypto/openssl/crypto/idea/idea.h /usr/src/crypto/openssh/ not sure which one fixed it, but it's been building for about 20 minutes, and i think it's past the

Re: make buildworld failure

2003-01-28 Thread Nick H. -- Technical Support Engineer
given nor endorsed by it. - Original Message - From: Jeff Utter [EMAIL PROTECTED] To: Nick H. -- Technical Support Engineer [EMAIL PROTECTED]; [EMAIL PROTECTED] Sent: Tuesday, January 28, 2003 9:32 PM Subject: Re: make buildworld failure i think my system is building successfully now.. i

buildworld failure, rtld-elf, RELENG_5_0

2003-01-23 Thread Evan Dower
I'm trying to upgrade from -stable to 5, but the build failed at rtld-elf. One error and a whole lot of warnings. I don't know where I should start as I'm new to current (even though it's technically not -current). I swear I followed the instructions in UPGRADING. Any help would be greatly

Re: buildworld failure, rtld-elf, RELENG_5_0

2003-01-23 Thread Evan Dower
recent changes to either file. Any ideas on what was going on? Thanks again, Evan Dower From: Evan Dower [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: buildworld failure, rtld-elf, RELENG_5_0 Date: Thu, 23 Jan 2003 00:17:14 -0800 I'm trying to upgrade from -stable to 5, but the build failed at rtld

Re: buildworld failure, rtld-elf, RELENG_5_0

2003-01-23 Thread Kris Kennaway
On Thu, Jan 23, 2003 at 09:15:24AM -0800, Evan Dower wrote: An update: CVSup'ing didn't fix the problem, but when I deleted the rtld.c and mv'd /etc/make.conf /etc/make.conf.hide, it stopped at /usr/src/contrib/amd/amd/srvr_nfs.c. So, I deleted that file, CVSup'd, and built again, and

buildworld failure in usr.bin/kdump

2003-01-03 Thread Michael C. Ferguson
Hi all, I just subscribed to the mailing lists today after upgrading to 5.0RC2, so I'm not sure if this has been reported or not. I'm relatively new to FreeBSD (although I'm a long time Linux user), so I'll report how I installed, just in case I missed something that might be causing

buildworld failure

2002-12-31 Thread Roderick van Domburg
Sources updated Dec 31 from anoncvs.freebsd.org on a sparc64. Didn't matter whether I used cvs update with -P or without -P. Got the following error during cleaning: === usr.sbin/fwcontrol cd: can't cd to /usr/src/usr.sbin/fwcontrol *** Error code 2 Stop in /usr/src/usr.sbin. *** Error code 1

Re: buildworld failure

2002-12-31 Thread Ceri Davies
On Tue, Dec 31, 2002 at 08:45:30PM +0100, Roderick van Domburg wrote: Sources updated Dec 31 from anoncvs.freebsd.org on a sparc64. Didn't matter whether I used cvs update with -P or without -P. Try cvs co -P. Got the following error during cleaning: === usr.sbin/fwcontrol cd: can't cd to

<    1   2   3   4   >