Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 6 Mar 2015 21:03:51 +0100
From:      Tijl Coosemans <tijl@coosemans.org>
To:        Scott Furry <scott.wl.furry@gmail.com>
Cc:        gerald@FreeBSD.org, vbox@FreeBSD.org
Subject:   Re: GCC 4.8.4 wchar error blocking devel/kBuild (virtualbox-ose dependency)
Message-ID:  <20150306210351.2d2daf7b@kalimero.tijl.coosemans.org>
In-Reply-To: <54FA0597.3000300@gmail.com>
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>

next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, 06 Mar 2015 12:52:55 -0700 Scott Furry <scott.wl.furry@gmail.com> 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

Hmm, how about:
grep -R __wchar_t /usr/local/lib/gcc48/gcc/



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20150306210351.2d2daf7b>