Date: Mon, 15 Mar 2004 21:07:57 +0100 From: Dimitry Andric <dimitry@andric.com> To: David Gilbert <dgilbert@dclg.ca> Cc: freebsd-hackers@freebsd.org Subject: Re: GCC include files conundrum. Message-ID: <853525693.20040315210757@andric.com> In-Reply-To: <16469.46609.293027.840180@canoe.dclg.ca> References: <16468.65270.123954.862565@canoe.dclg.ca> <20040315013817.GA68381@crodrigues.org> <16469.3340.625290.632134@canoe.dclg.ca> <20040315102516.GH15687@atrbg11.informatik.tu-muenchen.de> <16469.46609.293027.840180@canoe.dclg.ca>
next in thread | previous in thread | raw e-mail | index | archive | help
------------DFD5E0C3CF7A8 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit On 2004-03-15 at 14:56:33 David Gilbert wrote: >> In your particular case, maybe you could add a copy of >> strstream.h as a patch to the port into the build directory >> and reference it as "strstream.h" instead of <strstream.h>. >> Thus the system libstdc++ headers do not need to be polluted. > Finally a helpful idea I hadn't explored yet, thank-you. I've just sent in a PR with an analogous patch: http://www.freebsd.org/cgi/query-pr.cgi?pr=64310 Please check if this works for you. ------------DFD5E0C3CF7A8 Content-Type: application/pgp-signature -----BEGIN PGP MESSAGE----- Version: GnuPG v1.2.4 (MingW32) iD8DBQFAVg0dsF6jCi4glqMRAiKEAKDS9qsY2sXvrBz5B8AR4lWTjjLUgACglp4R d7/sng+WtmU0dPReNBouHh4= =k5t5 -----END PGP MESSAGE----- ------------DFD5E0C3CF7A8--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?853525693.20040315210757>