From owner-freebsd-emulation@FreeBSD.ORG Fri Mar 6 22:54:02 2015 Return-Path: Delivered-To: vbox@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 304FC50E; Fri, 6 Mar 2015 22:54:02 +0000 (UTC) Received: from mail-ie0-x22e.google.com (mail-ie0-x22e.google.com [IPv6:2607:f8b0:4001:c03::22e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id E2482FBF; Fri, 6 Mar 2015 22:54:01 +0000 (UTC) Received: by iecrl12 with SMTP id rl12so6777342iec.8; Fri, 06 Mar 2015 14:54:01 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=em01eux2d241OqwdO4wCKiV7ePsLJiyhZLVKPh0tjbQ=; b=p/5z+GuCUV6qLqa+1plBi9H11eGUm+AAkYi4vb3Yyq6n3ecCs55VYECNuqfu9CZcxV 7QYJpecW5PHlW+pnQ/VNw/W9Hz1Q8sXfaar9tIHDLSvYvQHRCSzgL1x7cNRTmc0FOAzr ngxVdYYpQWCCuWST9P39l9q5Au3zma6Igzln5/9KIxwkQuGnbkuhDIPgFhCdT/bhvic+ vwaw8ZGJskApkXdZ1qjOjVwZ3TEYSJ2tur8DWNuZN1lGEeMHxNUtXx7FWunB47E4BFs7 KBmXIiONWtFjFF1z5CaU5C4B6SEgjrRUkEXPiBfEvRRy2PAi2kod8cPLpIAS7PmAqOoN lq9A== X-Received: by 10.107.161.200 with SMTP id k191mr21440831ioe.51.1425682441297; Fri, 06 Mar 2015 14:54:01 -0800 (PST) Received: from [10.0.1.155] (d205-206-84-235.abhsia.telus.net. [205.206.84.235]) by mx.google.com with ESMTPSA id 38sm7765360iol.4.2015.03.06.14.53.59 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 06 Mar 2015 14:54:00 -0800 (PST) Message-ID: <54FA3006.9060504@gmail.com> Date: Fri, 06 Mar 2015 15:53:58 -0700 From: Scott Furry User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:31.0) Gecko/20100101 Thunderbird/31.5.0 MIME-Version: 1.0 To: Tijl Coosemans Subject: Re: GCC 4.8.4 wchar error blocking devel/kBuild (virtualbox-ose dependency) 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> In-Reply-To: <20150306214756.0ddfada0@kalimero.tijl.coosemans.org> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-Mailman-Approved-At: Fri, 06 Mar 2015 23:02:43 +0000 Cc: gerald@FreeBSD.org, vbox@FreeBSD.org X-BeenThere: freebsd-emulation@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Development of Emulators of other operating systems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 06 Mar 2015 22:54:02 -0000 On 06/03/2015 13:47, Tijl Coosemans wrote: > On Fri, 06 Mar 2015 13:04:32 -0700 Scott Furry 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 >>>> wrote: >>>>> On 06/03/2015 03:35, Tijl Coosemans wrote: >>>>>> On Thu, 05 Mar 2015 13:20:25 -0700 Scott Furry >>>>>> 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