Re: FreeBSD 11.0 i386 buildworld failure
Robert_Burmeister wrote > FreeBSD 11.0 i386 Stable > > I successfully upgraded from FreeBSD 10.3 to 11.0 Stable on 23 September > 2016. > Upon refreshing and rebuilding world to catch the 28 September 2016 > Release update, > buildworld failed using the same build options that had worked for the 22 > Sept code. Refreshed source to FreeBSD 11 Stable revision 306664 as of Oct 3rd and tried buildworld with a FreeBSD 10.3 backup kernel with the same result. Has anyone been able to bootstrap FreeBSD 11.0 i386? -- View this message in context: http://freebsd.1045724.x6.nabble.com/FreeBSD-11-0-i386-buildworld-failure-tp6133823p6134583.html Sent from the freebsd-current mailing list archive at Nabble.com. ___ 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: FreeBSD 11.0 i386 buildworld failure
Refreshed source 20160930 and make -j1 buildworld still fails: ===> lib/libdevctl (all) clang -O2 -fno-strict-aliasing -pipe -march=core2 -MD -MF.depend.devctl.o -MTdevctl.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/libdevctl/devctl.c -o devctl.o /usr/src/lib/libdevctl/devctl.c:131:6: error: use of undeclared identifier 'DEVF_CLEAR_DRIVER_DETACH' DEVF_CLEAR_DRIVER_DETACH : 0)); ^ /usr/src/lib/libdevctl/devctl.c:130:32: error: use of undeclared identifier 'DEV_CLEAR_DRIVER' return (devctl_simple_request(DEV_CLEAR_DRIVER, device, force ? ^ 2 errors generated. *** Error code 1 Stop. make[5]: stopped in /usr/src/lib/libdevctl *** Error code 1 Stop. make[4]: stopped in /usr/src/lib *** Error code 1 Stop. make[3]: stopped in /usr/src *** Error code 1 Stop. make[2]: stopped in /usr/src *** Error code 1 Stop. make[1]: stopped in /usr/src *** Error code 1 Stop. make: stopped in /usr/src BEASTIE# -- View this message in context: http://freebsd.1045724.x6.nabble.com/FreeBSD-11-0-i386-buildworld-failure-tp6133823p6134033.html Sent from the freebsd-current mailing list archive at Nabble.com. ___ 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: Base iconv (sort of) replaces libiconv in FreeBSD 10
As I use the Gnome2 desktop, I am unclear as to the recommended best practice. Base iconv and ports libiconv conflict, so one or the other should be used. FreeBSD 10 has been updated so that either base iconv or ports libiconv can be used. For me to switch between the two requires a two day recompile. I removed converters/libiconv for FreeBSD 10, as use of base iconv is now more correct. Since, glib20 has added dependancy libiconv back in, which affects many ports. (I was at first elated that iconv was finally in the base system, as updating libiconv causes much havok.) I am also working on the problem of USB drives no longer mounting from user space like they did on FreeBSD 9. An increasing number of people are noting this issue, and like descriptions of the issue were being related to iconv issues. http://www.freebsd.org/cgi/query-pr.cgi?pr=109024 I don't know whether I should continue to trouble shoot base iconv issues, or try to stick with ports' converters/libiconv until FreeBSD 11? Will use of both be somehow supported??? -- View this message in context: http://freebsd.1045724.n5.nabble.com/Base-iconv-sort-of-replaces-libiconv-in-FreeBSD-10-tp5886786p5887307.html Sent from the freebsd-current mailing list archive at Nabble.com. ___ 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
Base iconv (sort of) replaces libiconv in FreeBSD 10
While base iconv replaces libiconv in FreeBSD 10, base iconv doesn't do utf-8 - wchar_t, which is required by glib20, thus impacts thousands of ports. An entry in the FreeBSD 10 Errata stating that iconv is now in the base system, however, that it does not include all the functionality of libiconv from ports, would help make port maintainers aware of iconv issues. -- View this message in context: http://freebsd.1045724.n5.nabble.com/Base-iconv-sort-of-replaces-libiconv-in-FreeBSD-10-tp5886786.html Sent from the freebsd-current mailing list archive at Nabble.com. ___ 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: Lessons learned from source upgrade from FreeBSD i386 9.2 Stable to FreeBSD i386 10.0 Release.
Lessons learned from source upgrade from FreeBSD i386 9.2 Stable to FreeBSD i386 10.0 Release. A) Clang does not need to to be installed first. B) FreeBSD 10's change to pkg(8) (a.k.a. PKGNG) affects the portupgrade tools as well as the package tools. Even if you are not using packages, before upgrading to FreeBSD 10 install pkg(8) as described in: http://www5.us.freebsd.org/doc/handbook/pkgng-intro.html and be sure to run pkg2ng. C) FreeBSD 10 moves converters/libiconv into the base system, which directly or indirectly affects many ports. This migration has largely been taken care of for the official packages, however, if you are rebuilding from the ports tree pkg_delete libiconv must be run, or converters/libiconv must be deinstalled, before your post OS recompile of all your ports. Most of the iconv hardcodes have been addressed in the ports tree, but this is still being worked on. D) Many Gnome ports still had issues with continuing to link to libiconv.so.3, such as avahi-app and gdm. People who deleted all ports, removed /usr/local and reinstalled have reported that they do not have the problem. Apparently, some Gnome components are finicky about how they are built. A note from https://wiki.gnome.org/Projects/Jhbuild/FreeBSD Remove all .la files from the packages you just installed to prevent problems during the build. You'll have to remember to do this again each time you install more packages. I deleted the contents of /usr/local/lib and ran portupgrade -afu which rebuilt most of the problematic ports. -- View this message in context: http://freebsd.1045724.n5.nabble.com/Lessons-learned-from-source-upgrade-from-FreeBSD-i386-9-2-Stable-to-FreeBSD-i386-10-0-Release-tp5878896p5880955.html Sent from the freebsd-current mailing list archive at Nabble.com. ___ 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: Lessons learned from source upgrade from FreeBSD i386 9.2 Stable to FreeBSD i386 10.0 Release.
E) None of the USB flash drives I used with FreeBSD 9.2 will mount on FreeBSD 10.0. -- View this message in context: http://freebsd.1045724.n5.nabble.com/Lessons-learned-from-source-upgrade-from-FreeBSD-i386-9-2-Stable-to-FreeBSD-i386-10-0-Release-tp5878896p5880959.html Sent from the freebsd-current mailing list archive at Nabble.com. ___ 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: Lessons learned from source upgrade from FreeBSD i386 9.2 Stable to FreeBSD i386 10.0 Release.
Jakub Lach wrote Could you elaborate? Are those ntfs pendrives? ntfs support by ntfs.ko and mount_ntfs was removed in 10 tree. There is fuse kernel module and a port for ntfs in place of it (haven't tested but I'm told it works). Regarding fat (msdosfs) pendrives, I've just mounted one created under 8-CURRENT. They are msdosfs. Hald is seeing the stick, but the automounter isn't picking it up. I have been able to get one to mount read only with mount -t msdos /dev/da0s1 /mnt but it still doesn't like the large Lexar drives. I'm a little confused by: the FreeBSD Handbook 19.5 USB Storage Devices and halfaq haven't been updated since FreeBSD 8. Is FreeBSD 10 processing the rights differently? I got Gnome components hald avahi gdm to build, but are they functioning properly? Whether fuse is now the preferred method to mount USB file systems? I suspect that the policy configuration that worked for 9.2 is not working on 10, I am trying various devfs.conf syntax, without luck. -- View this message in context: http://freebsd.1045724.n5.nabble.com/Lessons-learned-from-source-upgrade-from-FreeBSD-i386-9-2-Stable-to-FreeBSD-i386-10-0-Release-tp5878896p5881310.html Sent from the freebsd-current mailing list archive at Nabble.com. ___ 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
