Date: Fri, 06 Mar 2015 15:53:58 -0700 From: Scott Furry <scott.wl.furry@gmail.com> To: Tijl Coosemans <tijl@coosemans.org> Cc: gerald@FreeBSD.org, vbox@FreeBSD.org Subject: Re: GCC 4.8.4 wchar error blocking devel/kBuild (virtualbox-ose dependency) Message-ID: <54FA3006.9060504@gmail.com> In-Reply-To: <20150306214756.0ddfada0@kalimero.tijl.coosemans.org> References: <54F86D96.1020505@gmail.com> <54F8BA89.4000302@gmail.com> <20150306113508.05c2bcc9@kalimero.tijl.coosemans.org> <54F9FCF9.2000104@gmail.com> <20150306205149.1dc0181a@kalimero.tijl.coosemans.org> <54FA0597.3000300@gmail.com> <54FA0850.5090803@gmail.com> <20150306214756.0ddfada0@kalimero.tijl.coosemans.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 06/03/2015 13:47, Tijl Coosemans wrote: > On Fri, 06 Mar 2015 13:04:32 -0700 Scott Furry <scott.wl.furry@gmail.com> wrote: >> On 06/03/2015 12:52, Scott Furry wrote: >>> On 06/03/2015 12:51, Tijl Coosemans wrote: >>>> On Fri, 06 Mar 2015 12:16:09 -0700 Scott Furry >>>> <scott.wl.furry@gmail.com> wrote: >>>>> On 06/03/2015 03:35, Tijl Coosemans wrote: >>>>>> On Thu, 05 Mar 2015 13:20:25 -0700 Scott Furry >>>>>> <scott.wl.furry@gmail.com> wrote: >>>>>>> Originally sent to vbox@FreeBSD.org this morning: >>>>>>> On 05/03/2015 07:52, Scott Furry wrote: >>>>>>>> While attempting to build emulators/virtualbox-ose(4.3.24) from >>>>>>>> FreeBSD ports, I keep running into a error during the build of >>>>>>>> devel/kBuild(0.1.9998). >>>>>>>> Error stops the build, but it seems a strange error being unable to >>>>>>>> determine a '__wchar_t' type. >>>>>>> emulators/virtualbox-ose-kmod (4.3.24) and emulators/virtualbox-ose >>>>>>> (4.3.24) are still blocked by error given above. >>>>>>> >>>>>>> I may not be the only one affected here. A quick google search dug up >>>>>>> this thread: >>>>>>> https://gist.github.com/tangentstorm/af2c97d89e194b3356c3 >>>>>>> >>>>>>> User indicated exact same error using gcc4.8.4 build. >>>>>> Try rebuilding gcc. During installation gcc thinks it's a good >>>>>> idea to >>>>>> fix "bugs" in some system headers by copying them to an obscure >>>>>> directory >>>>>> and then using those "fixed" copies instead of the real headers. >>>>>> When these system headers are updated gcc has an outdated copy that >>>>>> can cause errors in other headers. So, to be safe, whenever you >>>>>> update >>>>>> the base system you also have to rebuild the gcc ports. >>>>> Tried your suggestion. I went to update ports. I explicitly did an >>>>> update to lang/gcc48 before ports updating. This brought gcc48 up to >>>>> version 4.8.5-20150212. However, the original error message is >>>>> persistent. It appears that kBuild is using the gcc-4.8.4 files (or is >>>>> hardcoded to use these files) from somewhere else but not the installed >>>>> version. >>>>> >>>>> Error not resolved. >>>>> >>>>> Thanks for trying. >>>> What is the output of: >>>> grep __wchar_t >>>> /usr/local/lib/gcc48/gcc/x86_64-portbld-freebsd10.0/4.8.5/include-fixed/wchar.h >>> Output: >>> grep: >>> /usr/local/lib/gcc48/gcc/x86_64-portbld-freebsd10.0/4.8.5/include-fixed/wchar.h: >>> No such file or directory >> Further to my last... >> sudo find /usr/local -name 'wchar.h' >> >> /usr/local/lib/gcc48/gcc/x86_64-portbld-freebsd10.0/4.8.4/include-fixed/wchar.h >> /usr/local/lib/gcc48/include/c++/tr1/wchar.h >> >> grep __wchar_t >> /usr/local/lib/gcc48/gcc/x86_64-portbld-freebsd10.0/4.8.4/include-fixed/wchar.h >> typedef __wchar_t wchar_t; >> >> gcc48 --version >> gcc48 (FreeBSD Ports Collection) 4.8.4 >> Copyright (C) 2013 Free Software Foundation, Inc. >> This is free software; see the source for copying conditions. There is NO >> warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. >> >> grep PORTVERSION= /usr/ports/lang/gcc48/Makefile >> PORTVERSION= 4.8.5.s20150212 > The port you need to rebuild and reinstall is lang/gcc, not lang/gcc48. Well...colour me impressed... I cd'd into /usr/ports/lang/gcc48 and did a make deinstall clean. I repeated the same for /usr/ports/lang/gcc. Then I did a make install on gcc. Did a portsnap and update of install ports. Wow...it finished without error. Really? No errors or other foolishness were reported by I do have to build log if anyone is curious. I want to say there is a conflict between gcc and gcc48. I did not explicitly call gcc48 until I did the update earlier today. Then that update appeared to be "peeled back" by to gcc but not very well. But this is just my impression. Problem solved - but there seems to be other residual issues. Thanks for your help, folks! s
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?54FA3006.9060504>