5.1-CURRENT: buildworld fails
For a few past days, after doing make update, buildworld always fails when building "pam". Couldn't find it on this list! TIA ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: 5.1-CURRENT: buildworld fails
On Thu, Nov 27, 2003 at 11:59:16AM +0400, rihad wrote: > For a few past days, after doing make update, buildworld always fails > when building "pam". Couldn't find it on this list! TIA Sorry, my telepathy helmet needs a new potato, so you'll have to help me out here. Kris pgp0.pgp Description: PGP signature
Re: 5.1-CURRENT: buildworld fails
rihad wrote: For a few past days, after doing make update, buildworld always fails when building "pam". Couldn't find it on this list! TIA Have you set -02 or similar in your /etc/make.conf? My buildworld also fails if i set any optimizations. Just a guess Sebastian ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: 5.1-CURRENT: buildworld fails
Sebastian Böck wrote: rihad wrote: For a few past days, after doing make update, buildworld always fails when building "pam". Couldn't find it on this list! TIA Have you set -02 or similar in your /etc/make.conf? My buildworld also fails if i set any optimizations. Just a guess /usr/src/lib/libpam/modules/pam_echo/pam_echo.c is compiled with -Werror (treat warnings as errors). And I get: /usr/src/lib/libpam/modules/pam_echo/pam_echo.c: In function `_pam_echo': /usr/src/lib/libpam/modules/pam_echo/pam_echo.c:92: warning: dereferencing type-punned pointer will break strict-aliasing rules *** Error code 1 So the build fails. gcc version 3.3.3 [FreeBSD] 20031106 make.conf does have CPUTYPE?=p4 CFLAGS= -O2 -pipe I'll try to build it without -O2, thanks. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: 5.1-CURRENT: buildworld fails
On Thu, Nov 27, 2003 at 01:02:18PM +0400, rihad wrote: > CFLAGS= -O2 -pipe > > I'll try to build it without -O2, thanks. *sigh*, I see we need more figlet in the documentation. # CFLAGS controls the compiler settings used when compiling C code. # Note that optimization settings above -O (-O2, ...) are not recommended # or supported for compiling the world or the kernel - please revert any # nonstandard optimization settings to "-O" before submitting bug reports # to the developers. Kris pgp0.pgp Description: PGP signature
Re: 5.1-CURRENT: buildworld fails
Kris Kennaway <[EMAIL PROTECTED]> writes: > On Thu, Nov 27, 2003 at 01:02:18PM +0400, rihad wrote: > > CFLAGS= -O2 -pipe > > I'll try to build it without -O2, thanks. > *sigh*, I see we need more figlet in the documentation. < -O2 is bad, mmkay? > \ ^__^ \ (oo)\___ (__)\ )\/\ ||w | || || DES -- Dag-Erling Smørgrav - [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: 5.1-CURRENT: buildworld fails
On Sat, Nov 29, 2003 at 01:36:03AM +0100, Dag-Erling Sm?rgrav wrote: > Kris Kennaway <[EMAIL PROTECTED]> writes: > > On Thu, Nov 27, 2003 at 01:02:18PM +0400, rihad wrote: > > > CFLAGS= -O2 -pipe > > > I'll try to build it without -O2, thanks. > > *sigh*, I see we need more figlet in the documentation. > > > < -O2 is bad, mmkay? > > It shouldn't be today. I'm convenced that all of our problems with 'gcc-3.3.3 -O2' are FreeBSD code bugs. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: 5.1-CURRENT: buildworld fails
Hot Diggety! David O'Brien was rumored to have written: > > It shouldn't be today. I'm convenced that all of our problems with > 'gcc-3.3.3 -O2' are FreeBSD code bugs. I'm certainly deferring to someone with greater expertise, especially given a freebsd.org email address. :-) Just out of curiosity (and to mitigate my own personal ignorance), I'm curious how you determined them to be actual coding issues rather than compiler bugs? I've certainly seen both things in the past on other platforms, so I have an healthy amount of appreciation for both sides of the problem. -Dan ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
