From owner-freebsd-toolchain@freebsd.org Thu Jun 29 10:10:59 2017 Return-Path: Delivered-To: freebsd-toolchain@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 16C8DD98D60; Thu, 29 Jun 2017 10:10:59 +0000 (UTC) (envelope-from gerald@pfeifer.com) Received: from ainaz.pair.com (ainaz.pair.com [209.68.2.66]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id E2A0C7E4FB; Thu, 29 Jun 2017 10:10:58 +0000 (UTC) (envelope-from gerald@pfeifer.com) Received: from ainaz.pair.com (localhost [127.0.0.1]) by ainaz.pair.com (Postfix) with ESMTP id A7BCB3F4D9; Thu, 29 Jun 2017 06:10:56 -0400 (EDT) Received: from [192.168.1.102] (unknown [202.188.138.130]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ainaz.pair.com (Postfix) with ESMTPSA id D30993F4D5; Thu, 29 Jun 2017 06:10:37 -0400 (EDT) Date: Thu, 29 Jun 2017 18:10:16 +0800 User-Agent: K-9 Mail for Android In-Reply-To: References: <6FD738D6-F163-4BC5-8E6E-A9B9F35595CD@dsl-only.net> <82A991B0-FD8B-457F-8483-D61AE5E6D6F6@pfeifer.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Subject: Re: lang/gcc* package builds vs. release/11.0.1/ and the future release/11.1.0 because of vm_ooffset_t and vm_pindex_t changes and how the lang/gcc* work To: Mark Millard CC: papowell@astart.com, FreeBSD-STABLE Mailing List , FreeBSD Toolchain , FreeBSD Ports , Pedro Giffuni From: Gerald Pfeifer Message-ID: X-BeenThere: freebsd-toolchain@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Maintenance of FreeBSD's integrated toolchain List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 29 Jun 2017 10:10:59 -0000 Am 28=2E Juni 2017 22:38:52 GMT+08:00 schrieb Mark Millard : >A primary test is building lang/gcc5-devel under release/11=2E0=2E1 >and then using it under stable/11 or some draft of release/11=2E1=2E0 =2E Thank you, Mark=2E Let me know how it went=2E In the meantime I'll prepare= the change for gcc5 itself=2E >It looks like the the lang/gcc5-devel build still creates and >uses the headers that go in include-fixed/ but that they are >removed from $(STAGEDIR}${TARGLIB} 's tree before installation >or packaging=2E > >So, if I understand right, lang/gcc5-devel itself still does use >the adjusted headers to produce its own materials but when >lang/gcc5-devel is used later it does not=2E Definitely >something to be testing since it is a mix overall=2E I am not worried about that since that should not cause any binary incompa= tibilities (ABI)=2E The problem we encountered was about source code and AP= I in a wide sense of that term=2E >Is some form of exp-like run needed that tries to force use >of a release/11=2E0=2E1 built lang/gcc5-devel (-r444563) to build >other things under, say, stable/11 or some draft of >release/11=2E1=2E0 ? Is this odd combination even possible >currently? I am not aware of it, and while originally I was thinking to request an -e= xp run (after the GCC version update which is dragging due to broken ports)= , time is not on our side and the change should be low risk=2E > [altermative approach] But I guess that did not work out=2E Not with my current level of connectivity and my notebook a dead brick on = top of that=2E And my preference is to still build, but stow away (unless e= xplicitly requested to keep)=2E >Eventually most of the lang/gcc* 's will need whatever >technique is used=2E Yes, agreed=2E Version 5 is most important since it's the default; then 6;= 4=2Ex is for retro computing fans ;-), so 7 will then be next=2E Gerald