Hi Kostik, Kostik Belousov wrote: > On Wed, Apr 21, 2010 at 08:57:59PM +0200, Julian H. Stacey wrote: > > Hi hack...@freebsd.org > > with amd64, but not with i386, > > /sys/amd64/conf/GENERIC COMPAT_FREEBSD7 is an undocemneted > > pre-requisite for COMPAT_IA32 > > (so those who enable COMPAT_IA32 for ports/emulators, but disable > > COMPAT_FREEBSD7 as they compile all binaries on upgrade, will trip > > up on it as I did). Currently I see: > >=20 > > cc -c -O2 -frename-registers -pipe -fno-strict-aliasing -std=3Dc99 -g -W= > all -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-proto= > types -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -ffor= > mat-extensions -nostdinc -I. -I../../.. -I../../../contrib/altq -D_KERNEL = > -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-lim= > it=3D8000 --param inline-unit-growth=3D100 --param large-function-growth=3D= > 1000 -fno-omit-frame-pointer -mcmodel=3Dkernel -mno-red-zone -mfpmath=3D3= > 87 -mno-sse -mno-sse2 -mno-sse3 -mno-mmx -mno-3dnow -msoft-float -fno-asyn= > chronous-unwind-tables -ffreestanding -fstack-protector -Werror ../../../c= > ompat/freebsd32/freebsd32_misc.c > > cc1: warnings being treated as errors > > ../../../compat/freebsd32/freebsd32_misc.c: In function 'freebsd32_semsys= > ': > > ../../../compat/freebsd32/freebsd32_misc.c:1420: warning: implicit declar= > ation of function 'freebsd7_freebsd32_semctl' > > ../../../compat/freebsd32/freebsd32_misc.c:1420: warning: nested extern d= > eclaration of 'freebsd7_freebsd32_semctl' > > ... > > ../../../compat/freebsd32/freebsd32_misc.c:1845: error: dereferencing poi= > nter to incomplete type > > *** Error code 1 > >=20 > > It could be documented in GENERIC, but better to fix it. I could > > dig through sources, but I think there's people closer to config > > who would prefer to commit their own fix, rather than me write a patch ? > > (Does that translate as "I'm lazy" ? ;-) > > You did not even provided the version of the source checkout you use.
I only posted to hackers@ which is for releases. I didnt post stable or current@ However, yes, sorry I could & should have stated 8.0-RELEASE > There were a lot of changes in this area recently. Your error cannot > happen at the specified location in recent CURRENT or RELENG_8 > (this does not mean that the problem goes away with upgrade). OK, if things have changed since I'll leave it to others, I only have sources for stable & current here, not installed binaries. Cheers, Julian -- Julian Stacey: BSD Unix Linux C Sys Eng Consultants Munich http://berklix.com Mail plain text, Not HTML quoted-printable Base64 http://www.asciiribbon.org _______________________________________________ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "freebsd-hackers-unsubscr...@freebsd.org"
