Date: Sat, 28 May 2016 14:30:10 -0700 From: Mark Millard <markmi@dsl-only.net> To: Adrian Chadd <adrian.chadd@gmail.com> Cc: Bryan Drewery <bdrewery@freebsd.org>, FreeBSD Current <freebsd-current@freebsd.org>, FreeBSD Toolchain <freebsd-toolchain@freebsd.org>, FreeBSD PowerPC ML <freebsd-ppc@freebsd.org>, Gerald Pfeifer <gerald@freebsd.org>, Warner Losh <imp@bsdimp.com>, Dimitry Andric <dim@freebsd.org> Subject: Re: svn commit: r297435 - head: still problems for stage 3 when gcc 4.2.1 is avoided (powerpc64 self-hosted build) Message-ID: <F3A1706F-47EB-471F-B08C-38AFB51CA511@dsl-only.net> In-Reply-To: <CAJ-Vmokj0hp__FgRQLVc3ZLO=7no1mUPZsYURJvNy%2B%2BtQz2i6w@mail.gmail.com> References: <5A0ACA76-6F1D-4975-9E59-2A64BB8EFC77@dsl-only.net> <56FD9757.6040709@FreeBSD.org> <9E3033D5-F416-4B78-97C2-0A0AABF5A49E@dsl-only.net> <56FDA5F9.1090601@FreeBSD.org> <481DA341-0DFC-4AF1-AD4D-56C5388FA8E3@dsl-only.net> <56FDBAA8.5060407@FreeBSD.org> <7DEF97EC-D970-4F64-AF72-8939609A1D48@dsl-only.net> <DD969902-BCA8-480B-B32F-07DCC6C3E32B@dsl-only.net> <db60bcec-a6c4-02ac-da6c-1ac70821b806@FreeBSD.org> <4953F764-FC4E-491F-A6B7-4CAF65EAAEB7@dsl-only.net> <70a54660-775d-c12c-b991-507d26ce1342@FreeBSD.org> <72F5F9FD-5854-455D-8844-C4E1887DCE9F@dsl-only.net> <C23B8A92-8855-48CE-B442-3C7BEFCEF820@dsl-only.net> <0FA52C68-43C4-489D-9EB2-2339C2B812F5@dsl-only.net> <068D322F-E46F-4FD8-8DA0-BD7D17FD2A06@dsl-only.net> <CAJ-Vmokj0hp__FgRQLVc3ZLO=7no1mUPZsYURJvNy%2B%2BtQz2i6w@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 2016-May-28, at 12:03 PM, Adrian Chadd <adrian.chadd at gmail.com> = wrote: > [snip] >=20 > hi, >=20 > please don't patch the ports compiler assumptions about things like > this. We should be targeting external toolchains on OSes (eg macosx) > where it may already generate freebsd binaries and as such we should > be calling the compiler/linker with all the flags it needs. >=20 > Having a patched compiler default for mips made things way, way harder > than it needed to be. >=20 >=20 >=20 > -adrian Are there specific technical examples of specific lessons learned from = the "patched compiler default for mips" context? Is there an intent to use /usr/src/. . . materials for = buildworld/buildkernel and the like from a non-FreeBSD context? Are = there examples? Currently I'm just providing evidence that some FreeBSD committers have = requested. I'm not a committer for FreeBSD or for upstream and will not = be making any FreeBSD system or ports changes outside my personal = context. I'm no direct risk to FreeBSD. So your note is more for the = folks having me cross check xtoolchain and related behavior than for me. Notes on my context. . . (stop reading if you do not care) Unfortunately powerpc64 and powerpc still can not be clang based overall = for buildworld/buildkernel. I will say that in my use of devel/powerpc64-xtoolchain-gcc (and so = devel/powerpc64-gcc ) to have a libc++ based FreeBSD on powerpc64 I've = always had to have some form of work around to avoid /usr/local/include = causing buildworld failures from use of the wrong files for buildworld = purposes. I have either: A) temporarily renamed files below /usr/local/include/ to avoid them = being used (or otherwise blocked /usr/local/include access) or B) used C_INCLUDE_PATH and CPLUS_INCLUDE_PATH to cause the C/C++ = compiles to look below /usr/include/ before looking below = /usr/local/include/ . (I've also experimented with extra -I's and the = like.) So far I've not used devel/powerpc64-gcc to build ports under FreeBSD. = So far I've only built ports from a self-hosted context (no cross-built = ports). So I tend to use something like lang/gcc49 to build ports. I'm = not likely to adopt a technique for building the likes of lang/gcc49 = that messes up using it to build ports. I normally self-host buildworld/buildkernel on a powerpc64 FreeBSD = context, an odd use of devel/powerpc64-gcc . But I have at times also = cross-built from an amd64 FreeBSD context and it also can have the = "wrong files for buildworld" problem for /usr/local/include/ in FreeBSD. I've never tried buildworld/buildkernel from a non-FreeBSD context and = so have never built devel/powerpc64-gcc or anything like its = configuration outside FreeBSD. =3D=3D=3D Mark Millard markmi at dsl-only.net
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?F3A1706F-47EB-471F-B08C-38AFB51CA511>