Date: Wed, 4 Jul 2018 22:25:21 -0400 From: Ed Maste <emaste@freebsd.org> To: Eitan Adler <lists@eitanadler.com> Cc: John Baldwin <jhb@freebsd.org>, src-committers <src-committers@freebsd.org>, svn-src-all@freebsd.org, svn-src-head@freebsd.org Subject: Re: svn commit: r335888 - in head: contrib/blacklist/bin lib/libpjdlog sbin/hastd Message-ID: <CAPyFy2B5ox2qtuwZhmAjEBy6Bw7zn1up06DQt%2B7DfgC0ebjp0Q@mail.gmail.com> In-Reply-To: <CAF6rxg=xx%2BO1AQ-TCX3rhpNMa%2B5xMJpzuXoGG5tu5J=ptU8Lag@mail.gmail.com> References: <201807031353.w63DrsAa079940@repo.freebsd.org> <980f862d-02d0-a1ce-cf4c-1d39021013fb@FreeBSD.org> <20180703150203.GA34086@bsdpad.com> <a85b3bc0-d170-84e1-4c83-a1e4d657cd13@FreeBSD.org> <CAF6rxg=xx%2BO1AQ-TCX3rhpNMa%2B5xMJpzuXoGG5tu5J=ptU8Lag@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 4 July 2018 at 20:55, Eitan Adler <lists@eitanadler.com> wrote: > On Tue, 3 Jul 2018 at 08:22, John Baldwin <jhb@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.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAPyFy2B5ox2qtuwZhmAjEBy6Bw7zn1up06DQt%2B7DfgC0ebjp0Q>