Date: Thu, 01 Feb 2018 17:55:40 +0000 From: bugzilla-noreply@freebsd.org To: pkg@FreeBSD.org Subject: [Bug 224217] [patch] Fix cross build of base/ ports Message-ID: <bug-224217-32340-qlvvVmVX5e@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-224217-32340@https.bugs.freebsd.org/bugzilla/> References: <bug-224217-32340@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D224217 Steve Wills <swills@FreeBSD.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #190229|0 |1 is obsolete| | --- Comment #11 from Steve Wills <swills@FreeBSD.org> --- Created attachment 190251 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=3D190251&action= =3Dedit Updated patch Here's an updated patch which for me allows the built compiler to generate binaries if I pass -sysroot and -isystem. The OSREL has to be in the --targ= et due to this change: https://gcc.gnu.org/viewcvs/gcc/trunk/gcc/config.gcc?r1=3D222192&r2=3D22219= 1&pathrev=3D222192 that was introduced due to this bug report: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D65535 When the --target and --host don't match, gcc's configure decides you're building a cross compiler, which we aren't doing here. So unfortunately it seems like the right thing to do is make --target and --host match and to h= ave the OSREL in both for both gcc and binutils. This change does that and after updating and rebuilding everything I seem to have a working compiler. Please test and see if this fixes the issues reported in this bug and the o= ther bugs mentioned. --=20 You are receiving this mail because: You are on the CC list for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-224217-32340-qlvvVmVX5e>