On 5 Jul 2018, at 04:25, Ed Maste <ema...@freebsd.org> wrote: > > On 4 July 2018 at 20:55, Eitan Adler <li...@eitanadler.com> wrote: >> On Tue, 3 Jul 2018 at 08:22, John Baldwin <j...@freebsd.org> wrote: >>> >> since GCC usually breaks >>> them. >> >> Could you explain what you mean or point to a prior conversation? >> > I'm not sure if there's a previous discussion, but the short version > is that the GCC build process includes a 'fixincludes' step which > installs modified versions of system headers in some path that GCC > uses in preference to /usr/include. Originally this was done to work > around broken system includes in proprietary operating systems that > couldn't easily be fixed upstream. In the case of FreeBSD GCC's > fixincludes actually just installs broken headers, and removing its > broken copies is the easy fix.
Those fixed includes are no longer installed in more recent gcc ports, see e.g: https://svnweb.freebsd.org/ports?view=revision&revision=444860 https://svnweb.freebsd.org/ports?view=revision&revision=444861 https://svnweb.freebsd.org/ports?view=revision&revision=445313 -Dimitry
signature.asc
Description: Message signed with OpenPGP
