You have access to /usr/include! At least you can tell gcc to ignore standard include directories (-nostdinc) and specify it again before or after other include directories. Compare also -isystem, ...
The local boost headers are the first thing on my include path. I'm not sure why the /usr/include/boost files are ever used, but they are.
I wonder why there is no requirement to use either #include <boost/...> or #include "boost/..." Currently both is used which probably affects the include search path.
Maybe that's the problem. Thanks, Randy -----Original Message----- From: boost-bounces@lists.boost.org [mailto:boost-bounces@lists.boost.org] On Behalf Of Jens Seidel Sent: Monday, November 12, 2007 2:46 PM To: boost@lists.boost.org Subject: Re: [boost] [bind] segfault On Mon, Nov 12, 2007 at 01:56:14PM -0500, Ormond, Randy wrote:
I took my project's Boost out of the include path and the problem went away. I don't really understand how the RedHat /usr/include/boost got involved. Since I can't control /usr/include, I guess I'll have to be content with 1.32
You have access to /usr/include! At least you can tell gcc to ignore standard include directories (-nostdinc) and specify it again before or after other include directories. Compare also -isystem, ... I wonder why there is no requirement to use either #include <boost/...> or #include "boost/..." Currently both is used which probably affects the include search path. Should this be fixed? Jens _______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost