Re: Can't build -current incrementally due to libnv changes
Sorry I missed somehow header file. Done in r304912. Thanks, Mariusz On 27 August 2016 at 17:00, Andrey Chernov wrote: > Yes, 'make includes' (and 'make obj' and 'make depend') is done before > 'make all' in /usr/src/lib > ===> libnv (all) > cc -O2 -pipe -march=sandybridge -I/usr/src/lib/libnv/../../sys > -I/usr/src/lib/libnv -MD -MF.depend.cnvlist.o -MTcnvlist.o -std=gnu99 > -fstack-protector-strong -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 > -Wno-pointer-sign -Wmissing-variable-declarations -Wthread-safety > -Wno-empty-body -Wno-string-plus-int -Wno-unused-const-variable > -Qunused-arguments -c > /usr/src/lib/libnv/../../sys/contrib/libnv/cnvlist.c -o cnvlist.o > /usr/src/lib/libnv/../../sys/contrib/libnv/cnvlist.c:49:10: fatal error: > 'sys/cnv.h' file not found > #include > ^ > 1 error generated. > *** Error code 1 > ___ > freebsd-current@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org" ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Can't build -current incrementally due to libnv changes
Yes, 'make includes' (and 'make obj' and 'make depend') is done before 'make all' in /usr/src/lib ===> libnv (all) cc -O2 -pipe -march=sandybridge -I/usr/src/lib/libnv/../../sys -I/usr/src/lib/libnv -MD -MF.depend.cnvlist.o -MTcnvlist.o -std=gnu99 -fstack-protector-strong -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 -Wno-pointer-sign -Wmissing-variable-declarations -Wthread-safety -Wno-empty-body -Wno-string-plus-int -Wno-unused-const-variable -Qunused-arguments -c /usr/src/lib/libnv/../../sys/contrib/libnv/cnvlist.c -o cnvlist.o /usr/src/lib/libnv/../../sys/contrib/libnv/cnvlist.c:49:10: fatal error: 'sys/cnv.h' file not found #include ^ 1 error generated. *** Error code 1 ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: can't build CURRENT/amd64 using 9.3?
Fixed by scrubbing 9.3 and installing 10.1-RC3, which solved a couple of other issues. Respectfully, Robert Huff ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: can't build CURRENT/amd64 using 9.3?
On Fri, 2014-10-24 at 21:06 -0400, owner-freebsd-curr...@freebsd.org wrote: > roberth...@rcn.com writes: > > > I am now doing "make buildkernel" with TARGET/TARGET_ARCH on > > the command line. For installkernel, do I need to use them also, > > or will it magically know where to look? > > Kernel built. > However: > > huff@>> make installkernel > ERROR: No kernel "GENERIC" to install. > *** Error code 1 > > Stop. > bmake: stopped in /usr/src > *** [installkernel] Error code 1 > > Stop in /usr/src. > huff@>> make TARGET=amd64 TARGET_ARCH=amd64 installkernel > ERROR: Please set DESTDIR! > *** Error code 1 > It appears you almost had it right at this point, but overlooked this error which is also the instructions of how to fix this error. Note that this error kept you from destroying your i386 build host by installing some amd64 bits on it. -- Ian > Stop. > bmake: stopped in /usr/src > *** [installkernel] Error code 1 > > Stop in /usr/src. > > I believe there is a kernel in > /usr/obj/amd64.amd64/usr/src/sys/GENERIC, and world in > /usr/obj/amd64.amd64/usr/src. > > How do I make sure these get installed in the right place(s)? > > Respectfully, > > > Robert Huff > > > ___ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org" ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: can't build CURRENT/amd64 using 9.3?
Garrett Cooper writes: > The message is telling you (indirectly) that you need to run make > buildworld successfully first? Recapping: Current system: FreeBSD 9.3-RELEASE #0 r268512: Fri Jul 11 03:13:02 UTC 2014 i386 Source tree at CURRENT/r273626. No make.conf. src.conf: KERNCONF=GENERIC TARGET=amd64 TARGET_ARCH=amd64 Build uses this script: #! /bin/sh cd /usr/src if [ -f buildworld.log ] then rm buildworld.log fi chflags -R noschg /usr/obj/* rm -rf /usr/obj make cleandir date > ./buildworld.time make -j 1 TARGET=amd64 TARGET_ARCH=amd64 buildworld > ./buildworld.log 2>&1 tail -n 50 /usr/src/buildworld.log | sendmail huff Build log at "http://users.rcn.com/roberthuff/bl.gz"; So: is that or is it not a valid world build? Respectfully, Robert Huff ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: can't build CURRENT/amd64 using 9.3?
On Oct 24, 2014, at 21:02, owner-freebsd-curr...@freebsd.org wrote: > David Wolfskill writes: > >>> Kernel built. >>> However: >>> >>> huff@>> make installkernel >>> ERROR: No kernel "GENERIC" to install. >>> *** Error code 1 >>> ... >>> I believe there is a kernel in >>> /usr/obj/amd64.amd64/usr/src/sys/GENERIC, and world in >>> /usr/obj/amd64.amd64/usr/src. >>> >>> ... >> >> I believe that the cited message refers to the kernel configuration >> file, which is expected to be in sys/amd64/conf/GENERIC within the >> src hierarchy. > > Like this: > > huff@>> pwd > /usr/src > huff@>> dir sys/amd64/conf/GENERIC > -rw-rw-r-- 1 root wheel 14594 Oct 23 07:28 sys/amd64/conf/GENERIC The message is telling you (indirectly) that you need to run make buildworld successfully first… Cheers! signature.asc Description: Message signed with OpenPGP using GPGMail
Re: can't build CURRENT/amd64 using 9.3?
David Wolfskill writes: > > > I believe that the cited message refers to the kernel configuration > > > file, which is expected to be in sys/amd64/conf/GENERIC within the > > > src hierarchy. > > > >Like this: > > > > huff@>> pwd > > /usr/src > > huff@>> dir sys/amd64/conf/GENERIC > > -rw-rw-r-- 1 root wheel 14594 Oct 23 07:28 sys/amd64/conf/GENERIC > > > >? > > If the "make installkernel" is being done from /usr/src, yes. > > Contents of /etc/make.conf and/or /etc/src.conf may have bearing > on this, as well. No make.conf. src.conf= #KERNCONF="JERUSALEM" KERNCONF="GENERIC" #WITH_LIBICONV_COMPAT="yes" #TARGET=amd64 #TARGET_ARCH=amd64 Robert Huff ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: can't build CURRENT/amd64 using 9.3?
David Wolfskill writes: > >Kernel built. > >However: > > > > huff@>> make installkernel > > ERROR: No kernel "GENERIC" to install. > > *** Error code 1 > > ... > >I believe there is a kernel in > > /usr/obj/amd64.amd64/usr/src/sys/GENERIC, and world in > > /usr/obj/amd64.amd64/usr/src. > > > > ... > > I believe that the cited message refers to the kernel configuration > file, which is expected to be in sys/amd64/conf/GENERIC within the > src hierarchy. Like this: huff@>> pwd /usr/src huff@>> dir sys/amd64/conf/GENERIC -rw-rw-r-- 1 root wheel 14594 Oct 23 07:28 sys/amd64/conf/GENERIC ? Respectfully, Robert Huff ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: can't build CURRENT/amd64 using 9.3?
On Sat, Oct 25, 2014 at 12:02:48AM -0400, roberth...@rcn.com wrote: > ... > > > huff@>> make installkernel > > > ERROR: No kernel "GENERIC" to install. > > > *** Error code 1 > > > ... > > > I believe there is a kernel in > > > /usr/obj/amd64.amd64/usr/src/sys/GENERIC, and world in > > > /usr/obj/amd64.amd64/usr/src. > > > > > > ... > > > > I believe that the cited message refers to the kernel configuration > > file, which is expected to be in sys/amd64/conf/GENERIC within the > > src hierarchy. > > Like this: > > huff@>> pwd > /usr/src > huff@>> dir sys/amd64/conf/GENERIC > -rw-rw-r-- 1 root wheel 14594 Oct 23 07:28 sys/amd64/conf/GENERIC > > ? > ... If the "make installkernel" is being done from /usr/src, yes. Contents of /etc/make.conf and/or /etc/src.conf may have bearing on this, as well. I am in the habit of performing all of my builds/installs under script(1); that tends to reduce ambiguity about what happened. Peace, david -- David H. Wolfskill da...@catwhisker.org Taliban: Evil cowards with guns afraid of truth from a 14-year old girl. See http://www.catwhisker.org/~david/publickey.gpg for my public key. pgp__2beDUfr0.pgp Description: PGP signature
Re: can't build CURRENT/amd64 using 9.3?
On Fri, Oct 24, 2014 at 09:06:37PM -0400, owner-freebsd-curr...@freebsd.org wrote: > > roberth...@rcn.com writes: > > > I am now doing "make buildkernel" with TARGET/TARGET_ARCH on > > the command line. For installkernel, do I need to use them also, > > or will it magically know where to look? > > Kernel built. > However: > > huff@>> make installkernel > ERROR: No kernel "GENERIC" to install. > *** Error code 1 > ... > I believe there is a kernel in > /usr/obj/amd64.amd64/usr/src/sys/GENERIC, and world in > /usr/obj/amd64.amd64/usr/src. > > ... I believe that the cited message refers to the kernel configuration file, which is expected to be in sys/amd64/conf/GENERIC within the src hierarchy. Peace, david -- David H. Wolfskill da...@catwhisker.org Taliban: Evil cowards with guns afraid of truth from a 14-year old girl. See http://www.catwhisker.org/~david/publickey.gpg for my public key. pgpqcTVJNP9PU.pgp Description: PGP signature
Re: can't build CURRENT/amd64 using 9.3?
roberth...@rcn.com writes: > I am now doing "make buildkernel" with TARGET/TARGET_ARCH on > the command line. For installkernel, do I need to use them also, > or will it magically know where to look? Kernel built. However: huff@>> make installkernel ERROR: No kernel "GENERIC" to install. *** Error code 1 Stop. bmake: stopped in /usr/src *** [installkernel] Error code 1 Stop in /usr/src. huff@>> make TARGET=amd64 TARGET_ARCH=amd64 installkernel ERROR: Please set DESTDIR! *** Error code 1 Stop. bmake: stopped in /usr/src *** [installkernel] Error code 1 Stop in /usr/src. I believe there is a kernel in /usr/obj/amd64.amd64/usr/src/sys/GENERIC, and world in /usr/obj/amd64.amd64/usr/src. How do I make sure these get installed in the right place(s)? Respectfully, Robert Huff ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: can't build CURRENT/amd64 using 9.3?
Putting TARGET/TARGET_ARCH on the command line didn't help. Adding " -j 1 " to make - did. I am now doing "make buildkernel" with TARGET/TARGET_ARCH on the command line. For installkernel, do I need to use them also, or will it magically know where to look? Respectfully, Robert Huff ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: can't build CURRENT/amd64 using 9.3?
Ian Lepore writes: > >I have a system running > > > > FreeBSD 9.3-RELEASE #0 r268512: Fri Jul 11 03:13:02 UTC 2014 i386 > > > >I have updated the source tree to CURRENT r273542. > >If I build "make buildworld" for the GENERIC kernel and no > > make.conf or src.conf, it succeeds. > >If I use an empty make.conf and src.conf of > > > > TARGET=amd64 > > TARGET_ARCH=amd64 > > > >it dies with > > > > ld -o gcrt1.o -r crt1_s.o gcrt1_c.o > > crt1_s.o: file not recognized: File format not recognized > > *** Error code 1 > > Try putting the TARGET= and TARGET_ARCH= on the make command line rather > than in src.conf. I know the manpage says you can put them in src.conf, > but I wonder if we've broken that and you're the first person to try > since then. When I do this, I get instead: echo special chroot buildopts DIRPRFX=rescue/rescue/chroot/ >>rescue.conf echo progs chown >>rescue.conf echo special chown srcdir /usr/src/rescue/rescue/../../usr.sbin/chown >>rescue.conf echo special chown buildopts DIRPRFX=rescue/rescue/chown/ >>rescue.conf echo ln chown chgrp >>rescue.conf MAKE=/usr/obj/usr/src/make.i386/bmake MAKEOBJDIRPREFIX=/usr/obj/amd64.amd64/usr/src/rescue/rescue crunchgen -fq -m rescue.mk -c rescue.c rescue.conf crunchgen: make error: cd /usr/src/rescue/rescue/../../bin/cat && /usr/obj/usr/src/make.i386/bmake -f /tmp//crunchgen_rescueH6FUZJ -DRESCUE CRUNCH_CFLAGS=-DRESCUE DIRPRFX=rescue/rescue/cat/ loop crunchgen: make error: echo 'OBJS= 'cat.o crunchgen: make error: cd /usr/src/rescue/rescue/../../bin/chflags && /usr/obj/usr/src/make.i386/bmake -f /tmp//crunchgen_rescueH6FUZJ -DRESCUE CRUNCH_CFLAGS=-DRESCUE DIRPRFX=rescue/rescue/chflags/ loop crunchgen: make error: echo 'OBJS= 'chflags.o ... and so on for another 400+ lines before it again dies. Respectfully, Robert Huff ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: can't build CURRENT/amd64 using 9.3?
On Thu, 2014-10-23 at 21:54 -0400, owner-freebsd-curr...@freebsd.org wrote: > I have a system running > > FreeBSD 9.3-RELEASE #0 r268512: Fri Jul 11 03:13:02 UTC 2014 i386 > > I have updated the source tree to CURRENT r273542. > If I build "make buildworld" for the GENERIC kernel and no > make.conf or src.conf, it succeeds. > If I use an empty make.conf and src.conf of > > TARGET=amd64 > TARGET_ARCH=amd64 > > it dies with > > echo '#define EXTRA_MODES_FILE "i386/i386-modes.def"' >> tm.h [...] > cc -O2 -pipe -I/usr/src/lib/csu/i386-elf/../common > -I/usr/src/lib/csu/i386-elf/../../libc/include -std=gnu99 -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 -Wno-pointer-sign -Wthread-safety -Wno-empty-body > -Wno-string-plus-int -Wno-unused-const-variable -Qunused-arguments -c > /usr/src/lib/csu/i386-elf/crt1_s.S > ld -o gcrt1.o -r crt1_s.o gcrt1_c.o > crt1_s.o: file not recognized: File format not recognized > *** Error code 1 > > Stop. > bmake[3]: stopped in /usr/src/lib/csu/i386-elf > *** Error code 1 > > > Am I trying something that cannot be done? > If not: what's going on? I googled this and found answers for > Linux+gcc that don't seem to apply. > > Respectfully, > > > Robert Huff Try putting the TARGET= and TARGET_ARCH= on the make command line rather than in src.conf. I know the manpage says you can put them in src.conf, but I wonder if we've broken that and you're the first person to try since then. On an 8.4 i386 system I can get a failure (not exactly the same as the one you hit) trying to cross-build for amd64 if I put those settings in src.conf, but it works right if they're on the buildworld and installworld command lines. -- Ian ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
can't build CURRENT/amd64 using 9.3?
I have a system running FreeBSD 9.3-RELEASE #0 r268512: Fri Jul 11 03:13:02 UTC 2014 i386 I have updated the source tree to CURRENT r273542. If I build "make buildworld" for the GENERIC kernel and no make.conf or src.conf, it succeeds. If I use an empty make.conf and src.conf of TARGET=amd64 TARGET_ARCH=amd64 it dies with echo '#define EXTRA_MODES_FILE "i386/i386-modes.def"' >> tm.h (cd /usr/src/gnu/lib/csu; /usr/obj/usr/src/make.i386/bmake -f /usr/src/gnu/lib/csu/../../usr.bin/cc/cc_tools/Makefile MFILE=/usr/src/gnu/lib/csu/../../usr.bin/cc/cc_tools/Makefile GCCDIR=/usr/src/gnu/lib/csu/../../../contrib/gcc options.h) LC_ALL=C awk -f /usr/src/gnu/lib/csu/../../../contrib/gcc/opt-gather.awk /usr/src/gnu/lib/csu/../../../contrib/gcc/c.opt /usr/src/gnu/lib/csu/../../../contrib/gcc/common.opt /usr/src/gnu/lib/csu/../../../contrib/gcc/config/i386/i386.opt > optionlist LC_ALL=C awk -f /usr/src/gnu/lib/csu/../../../contrib/gcc/opt-functions.awk -f /usr/src/gnu/lib/csu/../../../contrib/gcc/opth-gen.awk < optionlist > options.h rm -f .depend CC='cc ' mkdep -f .depend -a -DCRT_BEGIN -DIN_GCC -DHAVE_LD_EH_FRAME_HDR -DDT_CONFIG -D__GLIBC__=3 -I/usr/src/gnu/lib/csu/../../../contrib/gcclibs/include -I/usr/src/gnu/lib/csu/../../../contrib/gcc/config -I/usr/src/gnu/lib/csu/../../../contrib/gcc -I. -I/usr/src/gnu/lib/csu/../../usr.bin/cc/cc_tools -std=gnu89 /usr/src/gnu/lib/csu/../../../contrib/gcc/crtstuff.c TMP=_depend$$; sed -e 's/^\([^\.]*\).o[ ]*:/\1.o \1.po \1.So:/' < .depend > $TMP; mv $TMP .depend cc -O2 -pipe -DIN_GCC -DHAVE_LD_EH_FRAME_HDR -DDT_CONFIG -D__GLIBC__=3 -fno-inline-functions -fno-exceptions -fno-zero-initialized-in-bss -fno-asynchronous-unwind-tables -fno-omit-frame-pointer -I/usr/src/gnu/lib/csu/../../../contrib/gcclibs/include -I/usr/src/gnu/lib/csu/../../../contrib/gcc/config -I/usr/src/gnu/lib/csu/../../../contrib/gcc -I. -I/usr/src/gnu/lib/csu/../../usr.bin/cc/cc_tools -std=gnu89 -Qunused-arguments -g0 -DCRT_BEGIN -c -o crtbegin.o /usr/src/gnu/lib/csu/../../../contrib/gcc/crtstuff.c cc -O2 -pipe -DIN_GCC -DHAVE_LD_EH_FRAME_HDR -DDT_CONFIG -D__GLIBC__=3 -fno-inline-functions -fno-exceptions -fno-zero-initialized-in-bss -fno-asynchronous-unwind-tables -fno-omit-frame-pointer -I/usr/src/gnu/lib/csu/../../../contrib/gcclibs/include -I/usr/src/gnu/lib/csu/../../../contrib/gcc/config -I/usr/src/gnu/lib/csu/../../../contrib/gcc -I. -I/usr/src/gnu/lib/csu/../../usr.bin/cc/cc_tools -std=gnu89 -Qunused-arguments -g0 -DCRT_END -c -o crtend.o /usr/src/gnu/lib/csu/../../../contrib/gcc/crtstuff.c cc -O2 -pipe -DIN_GCC -DHAVE_LD_EH_FRAME_HDR -DDT_CONFIG -D__GLIBC__=3 -fno-inline-functions -fno-exceptions -fno-zero-initialized-in-bss -fno-asynchronous-unwind-tables -fno-omit-frame-pointer -I/usr/src/gnu/lib/csu/../../../contrib/gcclibs/include -I/usr/src/gnu/lib/csu/../../../contrib/gcc/config -I/usr/src/gnu/lib/csu/../../../contrib/gcc -I. -I/usr/src/gnu/lib/csu/../../usr.bin/cc/cc_tools -std=gnu89 -Qunused-arguments -g0 -DCRT_BEGIN -DCRTSTUFFT_O -c -o crtbeginT.o /usr/src/gnu/lib/csu/../../../contrib/gcc/crtstuff.c cc -O2 -pipe -DIN_GCC -DHAVE_LD_EH_FRAME_HDR -DDT_CONFIG -D__GLIBC__=3 -fno-inline-functions -fno-exceptions -fno-zero-initialized-in-bss -fno-asynchronous-unwind-tables -fno-omit-frame-pointer -I/usr/src/gnu/lib/csu/../../../contrib/gcclibs/include -I/usr/src/gnu/lib/csu/../../../contrib/gcc/config -I/usr/src/gnu/lib/csu/../../../contrib/gcc -I. -I/usr/src/gnu/lib/csu/../../usr.bin/cc/cc_tools -std=gnu89 -Qunused-arguments -g0 -DCRT_BEGIN -DCRTSTUFFS_O -DSHARED -fpic -c -o crtbeginS.o /usr/src/gnu/lib/csu/../../../contrib/gcc/crtstuff.c cc -O2 -pipe -DIN_GCC -DHAVE_LD_EH_FRAME_HDR -DDT_CONFIG -D__GLIBC__=3 -fno-inline-functions -fno-exceptions -fno-zero-initialized-in-bss -fno-asynchronous-unwind-tables -fno-omit-frame-pointer -I/usr/src/gnu/lib/csu/../../../contrib/gcclibs/include -I/usr/src/gnu/lib/csu/../../../contrib/gcc/config -I/usr/src/gnu/lib/csu/../../../contrib/gcc -I. -I/usr/src/gnu/lib/csu/../../usr.bin/cc/cc_tools -std=gnu89 -Qunused-arguments -g0 -DCRT_END -DCRTSTUFFS_O -DSHARED -fpic -c -o crtendS.o /usr/src/gnu/lib/csu/../../../contrib/gcc/crtstuff.c sh /usr/src/tools/install.sh -o root -g wheel -m 444 crtbegin.o /usr/obj/usr/src/tmp/usr/lib/crtbegin.o sh /usr/src/tools/install.sh -o root -g wheel -m 444 crtend.o /usr/obj/usr/src/tmp/usr/lib/crtend.o sh /usr/src/tools/install.sh -o root -g wheel -m 444 crtbeginT.o /usr/obj/usr/src/tmp/usr/lib/crtbeginT.o sh /usr/src/tools/install.sh -o root -g wheel -m 444 crtbeginS.o /usr/obj/usr/src/tmp/usr/lib/crtbeginS.o sh /usr/src/tools/install.sh -o root -g wheel -m 444 crtendS.o /usr/obj/usr/src/tmp/usr/lib/crtendS.o echo "===> lib/csu/i386-elf (obj,depend,all,install)"; cd /usr/src/lib/csu/i386-elf && /usr/obj/usr/src/make.i386/bmake MK_TESTS=no DIRPRFX=lib/csu/i386-elf/ ob
Re: Can't build -CURRENT on 4.7
Ruslan Ermilov wrote: On Fri, Jun 06, 2003 at 11:57:00PM -0700, David O'Brien wrote: On Fri, Jun 06, 2003 at 09:46:07PM -0700, Tim Kientzle wrote: The compiler in 4.7 does not like this: -std=gnu99 As a result, buildworld of -CURRENT fails rather early. Committers are not required to support building 5-CURRENT, post 5.0-RELEASE on a 4.7 machine. So this is not grounds to remove the change. However, someone will probably patch the build system to tolerate it. Please correct me if I'm wrong, but I thought that this support will no longer be _required_ when we have a first release on the RELENG_5 (-STABLE) branch. [EMAIL PROTECTED] That was my understanding too, alas. Granted, we *must* provide an update path from the last 4.x release to the first *stable* 5.x release. But I do recall being advised that the core decided to support upgrade from *any* 4.x release to 5.0. -- Daniel C. Sobral (8-DCS) Gerencia de Operacoes Divisao de Comunicacao de Dados Coordenacao de Seguranca VIVO Centro Oeste Norte Fones: 55-61-313-7654/Cel: 55-61-9618-0904 E-mail: [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] Outros: [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] You can move the world with an idea, but you have to think of it first. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Can't build -CURRENT on 4.7
On Sat, Jun 07, 2003 at 03:34:08PM -0700, Tim Kientzle wrote:
> David O'Brien wrote:
>
> >This won't work on non-i386, due to alloca issues.
> >>+ WORLDTMP=${WORLDTMP} CSTD= \
> >may.
>
>
> Hmmm... This seems like the Right Thing in
> any case, since it is one less assumption you're
> making about the build environment.
>
> I'm still getting buildworld failures, though.
> Long after the bootstrap, using the new
> tools, I'm seeing consistent failures in
> libpthread:
>
> >building shared library libkse.so.1
> >thr_libc.So: In function `sigaction':
> >thr_libc.So(.text+0x54): multiple definition of `_sigaction'
> >thr_sigaction.So:/usr/src/current/lib/libpthread/thread/thr_sigaction.c:43: first
> >defined here
> >thr_libc.So: In function `sigprocmask':
> >thr_libc.So(.text+0x34): multiple definition of `_sigprocmask'
> >thr_sigprocmask.So:/usr/src/current/lib/libpthread/thread/thr_sigprocmask.c:46:
> >first defined here
> >*** Error code 1
> >
> >Stop in /usr/src/current/lib/libpthread.
> >*** Error code 1
>
Tim,
These have been fixed just recently (see the latest
committs to src/Makefile.inc1 and src/lib/libpthread),
and the buildworld for 5.x on 4.x now works again
(verified).
There are some uncommitted patches floating around
that allow for a buildkernel to survive as well.
I have left them for Warner's consideration.
Cheers,
--
Ruslan Ermilov Sysadmin and DBA,
[EMAIL PROTECTED] Sunbay Software Ltd,
[EMAIL PROTECTED] FreeBSD committer
pgp0.pgp
Description: PGP signature
Re: Can't build -CURRENT on 4.7
David O'Brien wrote:
This won't work on non-i386, due to alloca issues.
+ WORLDTMP=${WORLDTMP} CSTD= \
may.
Hmmm... This seems like the Right Thing in
any case, since it is one less assumption you're
making about the build environment.
I'm still getting buildworld failures, though.
Long after the bootstrap, using the new
tools, I'm seeing consistent failures in
libpthread:
building shared library libkse.so.1
thr_libc.So: In function `sigaction':
thr_libc.So(.text+0x54): multiple definition of `_sigaction'
thr_sigaction.So:/usr/src/current/lib/libpthread/thread/thr_sigaction.c:43: first
defined here
thr_libc.So: In function `sigprocmask':
thr_libc.So(.text+0x34): multiple definition of `_sigprocmask'
thr_sigprocmask.So:/usr/src/current/lib/libpthread/thread/thr_sigprocmask.c:46: first
defined here
*** Error code 1
Stop in /usr/src/current/lib/libpthread.
*** Error code 1
Tim
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Can't build -CURRENT on 4.7
In message: <[EMAIL PROTECTED]>
"David O'Brien" <[EMAIL PROTECTED]> writes:
: > + WORLDTMP=${WORLDTMP} CSTD= \
:
: may.
This seems to mostly work... I'm trying to sort out a couple of other
issues, but those may be related to other changes that I've made in my
test tree.
Warner
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Can't build -CURRENT on 4.7
On Sat, Jun 07, 2003 at 10:38:15AM -0700, Tim Kientzle wrote:
> Index: Makefile.inc1
> ===
> RCS file: /usr/src/cvs/src/Makefile.inc1,v
> retrieving revision 1.363
> diff -u -r1.363 Makefile.inc1
> --- Makefile.inc1 31 May 2003 21:29:38 - 1.363
> +++ Makefile.inc1 7 Jun 2003 04:52:43 -
> @@ -200,7 +204,7 @@
> BMAKEENV=DESTDIR= \
> INSTALL="sh ${.CURDIR}/tools/install.sh" \
> PATH=${BPATH}:${PATH} \
> - WORLDTMP=${WORLDTMP} \
> + WORLDTMP=${WORLDTMP} CSTD=c90 \
This won't work on non-i386, due to alloca issues.
> + WORLDTMP=${WORLDTMP} CSTD= \
may.
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Can't build -CURRENT on 4.7
On Sat, Jun 07, 2003 at 10:38:15AM -0700, Tim Kientzle wrote:
> Index: usr.bin/xlint/lint1/cgram.y
> ===
> RCS file: /usr/src/cvs/src/usr.bin/xlint/lint1/cgram.y,v
> retrieving revision 1.7
> diff -u -r1.7 cgram.y
> --- usr.bin/xlint/lint1/cgram.y 3 Mar 2002 15:12:19 - 1.7
> +++ usr.bin/xlint/lint1/cgram.y 7 Jun 2003 06:30:12 -
> @@ -1642,17 +1642,17 @@
> -static inline int uq_gt(uint64_t, uint64_t);
> -static inline int q_gt(int64_t, int64_t);
> +static __inline int uq_gt(uint64_t, uint64_t);
> +static __inline int q_gt(int64_t, int64_t);
>
> -static inline int
> +static __inline int
> uq_gt(uint64_t a, uint64_t b)
> {
>
> return (a > b);
> }
>
> -static inline int
> +static __inline int
Good catch! The rest of the file used __include everywhere. I've fixed
the inconsistency.
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Can't build -CURRENT on 4.7
In message: <[EMAIL PROTECTED]> "David O'Brien" <[EMAIL PROTECTED]> writes: : > First off, I'd like to say that's my understanding as well. : : That was not my understanding at all. The last time it came it, it was specifically stated that it was until the branch point. But so far the work arounds are fairly simple. I'm not going to give you more grief about it. : > Having said that, let's not get overly anal about the rules here. : > There's still a great need to have current build on 4.x machines. : > This is a long standing range war between ruslan and david over how : > much compatibility should be there. I do not want to see it play out : > in public again, but fear that it might. : : How is this a war? My elusion to "someone will probably patch the build : system to tolerate it" is that I expected that RU would add something to : -legacy or Makefile.inc1 so that the 5-CURRENT build worked 4.0. I don't : believe anyone can infer I would get in "someone"'s way in doing this. : We even have a freshly bumped __FreeBSD_version (501100) that can be used : for this. It isn't a war, yet. I'd like to keep it that way. There's some history here that makes me fear. However, I'll put those fears away and try to get a workaround that works. : > I personally don't see that the addition of -std=gnu99 is enough of a : > win in -current to justify its painful addition and the issue of : > -stable compatibility is secondary to that. It's been added 3 or 4 : > times now and every time the world has broken on some architecture. : > That alone is reason to treat the change with some skeptism as to its : > correctness. : : And the TRB hasn't even responded to my or DES's emails on the topic. : Note even a "hi, we got your message and will mull over it". Noted. I'll go and re-read the trb@ request. It came in, and then there was a flurry of commits so I thought it was OBE. I'll go look into it. : I (and another committer) had a agenda that DES's commit derailed and : I'll be damned if I'm going to let it stop me given the amount of crap : I've taken lately that has derailed every effort I've tried to make in : FreeBSD for the past 2 months. I'm not trying to give you crap here. I'm trying to point out that there are additional concerns that come into play. Warner ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Can't build -CURRENT on 4.7
On Sat, Jun 07, 2003 at 06:30:11AM -0600, M. Warner Losh wrote: > In message: <[EMAIL PROTECTED]> > Ruslan Ermilov <[EMAIL PROTECTED]> writes: > : On Fri, Jun 06, 2003 at 11:57:00PM -0700, David O'Brien wrote: > : > On Fri, Jun 06, 2003 at 09:46:07PM -0700, Tim Kientzle wrote: > : > > The compiler in 4.7 does not like this: > : > > > : > > -std=gnu99 > : > > > : > > As a result, buildworld of -CURRENT fails > : > > rather early. > : > > : > Committers are not required to support building 5-CURRENT, post > : > 5.0-RELEASE on a 4.7 machine. So this is not grounds to remove the > : > change. However, someone will probably patch the build system to > : > tolerate it. > : > > : Please correct me if I'm wrong, but I thought that this support > : will no longer be _required_ when we have a first release on the > : RELENG_5 (-STABLE) branch. [EMAIL PROTECTED] > > First off, I'd like to say that's my understanding as well. That was not my understanding at all. > Having said that, let's not get overly anal about the rules here. > There's still a great need to have current build on 4.x machines. > This is a long standing range war between ruslan and david over how > much compatibility should be there. I do not want to see it play out > in public again, but fear that it might. How is this a war? My elusion to "someone will probably patch the build system to tolerate it" is that I expected that RU would add something to -legacy or Makefile.inc1 so that the 5-CURRENT build worked 4.0. I don't believe anyone can infer I would get in "someone"'s way in doing this. We even have a freshly bumped __FreeBSD_version (501100) that can be used for this. > I personally don't see that the addition of -std=gnu99 is enough of a > win in -current to justify its painful addition and the issue of > -stable compatibility is secondary to that. It's been added 3 or 4 > times now and every time the world has broken on some architecture. > That alone is reason to treat the change with some skeptism as to its > correctness. And the TRB hasn't even responded to my or DES's emails on the topic. Note even a "hi, we got your message and will mull over it". I (and another committer) had a agenda that DES's commit derailed and I'll be damned if I'm going to let it stop me given the amount of crap I've taken lately that has derailed every effort I've tried to make in FreeBSD for the past 2 months. -- -- David ([EMAIL PROTECTED]) ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Can't build -CURRENT on 4.7
David O'Brien wrote:
On Fri, Jun 06, 2003 at 09:46:07PM -0700, Tim Kientzle wrote:
The compiler in 4.7 does not like this:
-std=gnu99
As a result, buildworld of -CURRENT fails
rather early.
Committers are not required to support building 5-CURRENT, post
5.0-RELEASE on a 4.7 machine. So this is not grounds to remove the
change. However, someone will probably patch the build system to
tolerate it.
Hmm.. I'll upgrade the machine to 4-STABLE and
see if that addresses it.
I'm also looking at at some other approaches.
For example, the attached patch changes BMAKEENV to
override CSTD in the early build phases. (This also
required changing a couple of 'inline' to '__inline'
in xlint/lint1/cgram.y.) This seems to get
it through the bootstrap, at least, although I'm still running
into build problems later on (but the cross-tools
are built by then, so I think these may be unrelated).
Tim Kientzle
Index: Makefile.inc1
===
RCS file: /usr/src/cvs/src/Makefile.inc1,v
retrieving revision 1.363
diff -u -r1.363 Makefile.inc1
--- Makefile.inc1 31 May 2003 21:29:38 - 1.363
+++ Makefile.inc1 7 Jun 2003 04:52:43 -
@@ -200,7 +204,7 @@
BMAKEENV= DESTDIR= \
INSTALL="sh ${.CURDIR}/tools/install.sh" \
PATH=${BPATH}:${PATH} \
- WORLDTMP=${WORLDTMP} \
+ WORLDTMP=${WORLDTMP} CSTD=c90 \
MAKEFLAGS="-m ${.CURDIR}/tools/build/mk ${.MAKEFLAGS}"
BMAKE= MAKEOBJDIRPREFIX=${WORLDTMP} \
${BMAKEENV} ${MAKE} -f Makefile.inc1 \
Index: usr.bin/xlint/lint1/cgram.y
===
RCS file: /usr/src/cvs/src/usr.bin/xlint/lint1/cgram.y,v
retrieving revision 1.7
diff -u -r1.7 cgram.y
--- usr.bin/xlint/lint1/cgram.y 3 Mar 2002 15:12:19 - 1.7
+++ usr.bin/xlint/lint1/cgram.y 7 Jun 2003 06:30:12 -
@@ -1642,17 +1642,17 @@
return (0);
}
-static inline int uq_gt(uint64_t, uint64_t);
-static inline int q_gt(int64_t, int64_t);
+static __inline int uq_gt(uint64_t, uint64_t);
+static __inline int q_gt(int64_t, int64_t);
-static inline int
+static __inline int
uq_gt(uint64_t a, uint64_t b)
{
return (a > b);
}
-static inline int
+static __inline int
q_gt(int64_t a, int64_t b)
{
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Can't build -CURRENT on 4.7
In message: <[EMAIL PROTECTED]> Ruslan Ermilov <[EMAIL PROTECTED]> writes: : On Fri, Jun 06, 2003 at 11:57:00PM -0700, David O'Brien wrote: : > On Fri, Jun 06, 2003 at 09:46:07PM -0700, Tim Kientzle wrote: : > > The compiler in 4.7 does not like this: : > > : > > -std=gnu99 : > > : > > As a result, buildworld of -CURRENT fails : > > rather early. : > : > Committers are not required to support building 5-CURRENT, post : > 5.0-RELEASE on a 4.7 machine. So this is not grounds to remove the : > change. However, someone will probably patch the build system to : > tolerate it. : > : Please correct me if I'm wrong, but I thought that this support : will no longer be _required_ when we have a first release on the : RELENG_5 (-STABLE) branch. [EMAIL PROTECTED] First off, I'd like to say that's my understanding as well. Having said that, let's not get overly anal about the rules here. There's still a great need to have current build on 4.x machines. This is a long standing range war between ruslan and david over how much compatibility should be there. I do not want to see it play out in public again, but fear that it might. Let's apply some common sense to this exceptional situation we find ourselves in and not resort to being overly pedantic about rules. There are a number of people who cannot run a 5.0-RELEASE system on their hardware because it was too instable to build a world. So requiring a trip through 5.0 is not an option. Therefore, we have to tolerate going from 4.x to at least 5.1 and maybe a little farther. We're just barely past 5.1 right now, so it is a little fast to be breaking this path. I personally don't see that the addition of -std=gnu99 is enough of a win in -current to justify its painful addition and the issue of -stable compatibility is secondary to that. It's been added 3 or 4 times now and every time the world has broken on some architecture. That alone is reason to treat the change with some skeptism as to its correctness. My main point, however, is that common sense needs to be applied to this situation, not blind adherence to inflexible rules. That's the sort of thing that gets us as a project into trouble. Warner ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Can't build -CURRENT on 4.7
On Fri, Jun 06, 2003 at 11:57:00PM -0700, David O'Brien wrote: > On Fri, Jun 06, 2003 at 09:46:07PM -0700, Tim Kientzle wrote: > > The compiler in 4.7 does not like this: > > > > -std=gnu99 > > > > As a result, buildworld of -CURRENT fails > > rather early. > > Committers are not required to support building 5-CURRENT, post > 5.0-RELEASE on a 4.7 machine. So this is not grounds to remove the > change. However, someone will probably patch the build system to > tolerate it. > Please correct me if I'm wrong, but I thought that this support will no longer be _required_ when we have a first release on the RELENG_5 (-STABLE) branch. [EMAIL PROTECTED] Cheers, -- Ruslan Ermilov Sysadmin and DBA, [EMAIL PROTECTED] Sunbay Software Ltd, [EMAIL PROTECTED] FreeBSD committer pgp0.pgp Description: PGP signature
Re: Can't build -CURRENT on 4.7
On Sat, Jun 07, 2003 at 01:07:24AM -0700, David O'Brien wrote: > I carefully worded the reply to specifically address build 5-CURRENT on > 4.7. Can you try src/share/mk/bsd.sys.mk rev 1.29 to see if it fixes > your problem? Have you tested it thoroughly? Didn't you back out -std=c99 in a previous revision because it also caused problems? Kris pgp0.pgp Description: PGP signature
Re: Can't build -CURRENT on 4.7
On Sat, Jun 07, 2003 at 12:08:31AM -0700, Kris Kennaway wrote: > On Fri, Jun 06, 2003 at 11:57:00PM -0700, David O'Brien wrote: > > On Fri, Jun 06, 2003 at 09:46:07PM -0700, Tim Kientzle wrote: > > > The compiler in 4.7 does not like this: > > > > > > -std=gnu99 > > > > > > As a result, buildworld of -CURRENT fails > > > rather early. > > > > Committers are not required to support building 5-CURRENT, post > > 5.0-RELEASE on a 4.7 machine. So this is not grounds to remove the > > change. However, someone will probably patch the build system to > > tolerate it. > > That's a bit of an early call given that 5.x world is currently broken > with the same error, as you know. I carefully worded the reply to specifically address build 5-CURRENT on 4.7. Can you try src/share/mk/bsd.sys.mk rev 1.29 to see if it fixes your problem? -- -- David ([EMAIL PROTECTED]) ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Can't build -CURRENT on 4.7
On Fri, Jun 06, 2003 at 11:57:00PM -0700, David O'Brien wrote: > On Fri, Jun 06, 2003 at 09:46:07PM -0700, Tim Kientzle wrote: > > The compiler in 4.7 does not like this: > > > > -std=gnu99 > > > > As a result, buildworld of -CURRENT fails > > rather early. > > Committers are not required to support building 5-CURRENT, post > 5.0-RELEASE on a 4.7 machine. So this is not grounds to remove the > change. However, someone will probably patch the build system to > tolerate it. That's a bit of an early call given that 5.x world is currently broken with the same error, as you know. Kris pgp0.pgp Description: PGP signature
Re: Can't build -CURRENT on 4.7
On Fri, Jun 06, 2003 at 09:46:07PM -0700, Tim Kientzle wrote: > The compiler in 4.7 does not like this: > > -std=gnu99 > > As a result, buildworld of -CURRENT fails > rather early. Committers are not required to support building 5-CURRENT, post 5.0-RELEASE on a 4.7 machine. So this is not grounds to remove the change. However, someone will probably patch the build system to tolerate it. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Can't build -CURRENT on 4.7
The compiler in 4.7 does not like this: -std=gnu99 As a result, buildworld of -CURRENT fails rather early. Tim Kientzle ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: cvsupit assumptions (was: Re: Re[2]: Can't build current...)
On Wed, Mar 28, 2001 at 09:15:51PM +0200, Gabriel Ambuehl wrote: > Oh and while I'm on it: where is src/crypto/rijndael in the CVS? in src/sys/crypto/rijndael :-) > CVSWEB doesn't find it, neither does it get downloaded (this time > using a complete supfile ;-)... You need the src-sys-crypto cvsup collection. Kris PGP signature
Re: cvsupit assumptions (was: Re: Re[2]: Can't build current...)
-BEGIN PGP SIGNED MESSAGE- Hello Robert, Tuesday, March 27, 2001, 8:19:42 PM, you wrote: > I've actually heard that from a couple of other people lately -- that > cvsupit still assumes that crypto should not be pulled down, and the > crypto code is now assumed in the default build. This may just be a > product of the packagized version of cvsupit shipped in the past, but it > might also be the case that cvsupit needs to be updated to take into > account changes in our cvsup policies and source layout. Actually, it doesn't even ask the user what to do with crypto if 5 CURRENT is selected (can't remember for sure what it did when one selected 4 STABLE). So even if the user selects everything that is presented to him, src-crypto and src-secure won't be in the cvsup file and thus a normal attempt to build the system will break. Guess it is time to formulate a PR on this... Oh and while I'm on it: where is src/crypto/rijndael in the CVS? CVSWEB doesn't find it, neither does it get downloaded (this time using a complete supfile ;-)... (although I managed to get the necessary files after searching with google but obviously they are not on the FreeBSD site. Those seem to be used only by the kernel as world will build without them.) Best regards, Gabriel -BEGIN PGP SIGNATURE- Version: PGP 6.0.2i iQEVAwUBOsIqW8Za2WpymlDxAQF9pwgAtVjLwwE561veqFCtW7MsZ/j/qBj5NDAx UTaqNneKx4HRBrt5xfVS0LLwYyr3HubUzvnJy7rIa24h+/7YXwQQGzVphitF3meo VaQYIB+hei6ZSCuywXpoVnYEikkMBuHRaM/BxtajTWBTeugsPQX+83L6/yVQfHSr FF1ttkTcyCnLHQLTrz+zevtmBlRaZNyBJAMgKkDGAVqQQSFIF7mniJStlEnZsq9B J1tBWHrBQjLG2Y7CkGn3WaDO5VBrCMn9fvQTQoBZUmTJ7+AGjkyWILyeMZ/iPL87 j7rcRpLyqgGlNva83pr2p3qQxeE662nbW9z/IdENdCqc4hyU8pzGzA== =cAKe -END PGP SIGNATURE- To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Can't build current...
kris> I believe Mark's intention was to keep crypt-blowfish.c optional for
kris> those who don't want to install crypto. Perhaps this is broken.
src/lib/libcrypt/Makefile says:
# Pull in the crypt-des.c source, assuming it is present.
.if exists(${.CURDIR}/../../secure/lib/libcrypt/crypt-des.c) && \
!defined(NOSECURE) && !defined(NOCRYPT)
.PATH: ${.CURDIR}/../../secure/lib/libcrypt
SRCS+= crypt-des.c crypt-blowfish.c blowfish.c
CFLAGS+=-I${.CURDIR} -DHAS_DES -DHAS_BLOWFISH
.endif
and it seems OK to me. This .if-.endif clause was there since two
libcrypt was merged into a single library (Dec/2000).
Gabriel, would you please check src/secure/lib/libcrypt/ and what's
files are sitting in this directory?
-- -
Makoto `MAR' MATSUSHITA
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: Re[2]: Can't build current...
Gabriel Ambuehl <[EMAIL PROTECTED]> wrote: > I'm using cvsup.de.FreeBSD.org which appears to be a cname > cvsup.uk.FreeBSD.org. Huh? That would be a mistake if it happened. But it isn't: j@uriah 159% nslookup cvsup.de.freebsd.org Server: uriah.heep.sax.de Address: 0.0.0.0 Non-authoritative answer: Name:ftp.ecrc.net Address: 62.208.224.162 Aliases: cvsup.de.freebsd.org j@uriah 160% nslookup cvsup.uk.freebsd.org Server: uriah.heep.sax.de Address: 0.0.0.0 Non-authoritative answer: Name:cvsup.plig.net Address: 195.40.6.42 Aliases: cvsup.uk.freebsd.org cvsup.de.freebsd.org is a cname for cvsup5.de.freebsd.org, which is a cname for ftp.ecrc.net. -- cheers, J"org .-.-. --... ...-- -.. . DL8DTL http://www.sax.de/~joerg/NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Can't build current...
On Wed, Mar 28, 2001 at 02:55:15AM +0900, Makoto MATSUSHITA wrote: > You should have src/secure/lib/libcrypt/crypt-blowfish.c. If you don't > have, it's your problem. The CVS repository has this file already: > http://www.freebsd.org/cgi/cvsweb.cgi/src/secure/lib/libcrypt/crypt-blowfish.c > > Have you update (or checkout) your src/secure, or which CVSup server you use? I believe Mark's intention was to keep crypt-blowfish.c optional for those who don't want to install crypto. Perhaps this is broken. Kris PGP signature
cvsupit assumptions (was: Re: Re[2]: Can't build current...)
On Tue, 27 Mar 2001, Gabriel Ambuehl wrote: > I'm using cvsup.de.FreeBSD.org which appears to be a cname > cvsup.uk.FreeBSD.org. But it looks like, that for some reason, > src-secure didn't get added to the cvsupfile (hmm. might be related to > the fact that cvsupit creates cvsup.intl for that purpose and I forgot > to add that one to make.conf...). Mea culpa (hope it will work now). I've actually heard that from a couple of other people lately -- that cvsupit still assumes that crypto should not be pulled down, and the crypto code is now assumed in the default build. This may just be a product of the packagized version of cvsupit shipped in the past, but it might also be the case that cvsupit needs to be updated to take into account changes in our cvsup policies and source layout. Robert N M Watson FreeBSD Core Team, TrustedBSD Project [EMAIL PROTECTED] NAI Labs, Safeport Network Services To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re[2]: Can't build current...
-BEGIN PGP SIGNED MESSAGE- Hello Makoto, Tuesday, March 27, 2001, 7:55:15 PM, you wrote: gabriel_ambuehl>> I can't seem to be able to build 5-CURRENT since several days. > You should have src/secure/lib/libcrypt/crypt-blowfish.c. If you don't > have, it's your problem. The CVS repository has this file already: > http://www.freebsd.org/cgi/cvsweb.cgi/src/secure/lib/libcrypt/crypt-blo wfish.c > Have you update (or checkout) your src/secure, or which CVSup server you use? I'm using cvsup.de.FreeBSD.org which appears to be a cname cvsup.uk.FreeBSD.org. But it looks like, that for some reason, src-secure didn't get added to the cvsupfile (hmm. might be related to the fact that cvsupit creates cvsup.intl for that purpose and I forgot to add that one to make.conf...). Mea culpa (hope it will work now). While I'm writing this: what is the general opinion about having CURRENT on production servers (I'd really love to deploy the ACLs ASAP)? I don't plan to use SMP and can wait for snapshots til the RELEASE comes... Best regards, Gabriel -BEGIN PGP SIGNATURE- Version: PGP 6.0.2i iQEVAwUBOsDJzsZa2WpymlDxAQGYMAf9E/gzHUM6H3897O9XJTRWKIyrEdW5eE6G RvRU5FK+SxLa+FucsjU9dN4Yh41VD5C+mrq6nnTppBf7Wnt2QjyRx+7q7Hs12qdC QMItugL+2iGGU6gioF0WZPeh1MrcWO6dbCn1o95QyYS/Sw9ePM+I4EA2Iiikh1EV Rf7At5/zyQfnHtab2CSn4fQCGc/onfpmYSEZd4ezj2ykD9J9BQdRZtX7IqDodCZm djhc6UYU9RFtUVzdCgXW8pYG9be9HNiUdZwnsi2GmEuSqhx05bUVJ0m1lL4t7Dwx wJNVnkzCURmxjFtjc4d6am5wjyPOXOj2nrWoO96ZfybNLoT1g6rh0A== =BB0w -END PGP SIGNATURE- To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Can't build current...
gabriel_ambuehl> I can't seem to be able to build 5-CURRENT since several days. You should have src/secure/lib/libcrypt/crypt-blowfish.c. If you don't have, it's your problem. The CVS repository has this file already: http://www.freebsd.org/cgi/cvsweb.cgi/src/secure/lib/libcrypt/crypt-blowfish.c Have you update (or checkout) your src/secure, or which CVSup server you use? -- - Makoto MATSUSHITA To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Can't build current...
-BEGIN PGP SIGNED MESSAGE- Hello, I can't seem to be able to build 5-CURRENT since several days. I just cvsupped again (tracking everything on CURRENT branch) but I always run into the following: sh /usr/src/tools/install.sh -c -o root -g wheel -m 444 libmd.a /usr/obj/usr/src/i386/usr/lib sh /usr/src/tools/install.sh -c -o root -g wheel -m 444 libmd_p.a /usr/obj/usr/src/i386/usr/lib sh /usr/src/tools/install.sh -c -s -o root -g wheel -m 444 libmd.so.2 /usr/obj/usr/src/i386/usr/lib ln -sf libmd.so.2 /usr/obj/usr/src/i386/usr/lib/libmd.so cd /usr/src/lib/libcrypt; make depend; make all; make install make: don't know how to make crypt-blowfish.c. Stop *** Error code 2 Stop in /usr/src. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. when trying to do make buildworld. Machine is a K6-2 500 running 15.3.01 5-CURRENT snapshot. Am I too stupid (haven't run into any problems on 4.X for a long time so ;-) or is this broken? Best regards, Gabriel -BEGIN PGP SIGNATURE- Version: PGP 6.0.2i iQEVAwUBOsCkO8Za2WpymlDxAQF+0gf/da0BeB8FWe+6revJQHYX9RwCFFr2/u7w AH4CO6PnK3YieMD4SHm05Ng3I1MiIcj0inZevR7jIsGAVrsnHN8i9OgCxtDANaFt cYnP+kyhSWW/qQB6wATidWxaCVMK8IdXrouAdOtyGmtaa2jVIc5tUqlgx27R9sT0 jTZl0Wu1lEmrEIKu+I2Wp9K1MUdXtiBktcDmYtj08nIe5dh160/UUh5c9ZqS41IR s+5ggR3Kcx70kitu16eRJ2IyQbwl/zl3QUOSGWKrJTJtE18tGYqjXqklC6cVFPWl TK9q5s41NwUT8U5fK+Y23p6Gzrwb5gsEvY889PAMV7VOT7MzH9fCtg== =xBW5 -END PGP SIGNATURE- To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Can't build current...
-BEGIN PGP SIGNED MESSAGE- Hello, I can't seem to be able to build 5-CURRENT since several days. I just cvsupped again (tracking everything on CURRENT branch) but I always run into the following: sh /usr/src/tools/install.sh -c -o root -g wheel -m 444 libmd.a /usr/obj/usr/src/i386/usr/lib sh /usr/src/tools/install.sh -c -o root -g wheel -m 444 libmd_p.a /usr/obj/usr/src/i386/usr/lib sh /usr/src/tools/install.sh -c -s -o root -g wheel -m 444 libmd.so.2 /usr/obj/usr/src/i386/usr/lib ln -sf libmd.so.2 /usr/obj/usr/src/i386/usr/lib/libmd.so cd /usr/src/lib/libcrypt; make depend; make all; make install make: don't know how to make crypt-blowfish.c. Stop *** Error code 2 Stop in /usr/src. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. when trying to do make buildworld. Machine is a K6-2 500 running 15.3.01 5-CURRENT snapshot. Am I too stupid (haven't run into any problems on 4.X for a long time so ;-) or is this broken? Best regards, Gabriel -BEGIN PGP SIGNATURE- Version: PGP 6.0.2i iQEVAwUBOsCglsZa2WpymlDxAQGcJggAsRBFAA/W8kaVKJSPzaPUFH00XI8vq4SV vjNjWNk65HKNyeG1ceVU7nVETBpENsLqXM0hZ04FLTBR5ii5snqfBm+JVpAvMLMa NHpnfXFImDNOsIai0LSArx86uT4jIBGer26odpnJQV0yEffdyzqdXAMMIHg2Gh2/ QJNnSjXA9Mccgkfr/W8V1DWAJaaBRfgczy3HolwhjWOpNXm6V+5ZSW3LW1tIvra/ n7N2eR7liwW/LHNbVKejbJUKc11pu9tlY59Uq9fmXFYdfV4R2R3Wrv0SvZgW9uyV YTOzBqSH9LJVjNkVMgvOjmIQ2AZgjs1N8y+ThDuAGDXLn5izlgsaUA== =AmSS -END PGP SIGNATURE- To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
