Re: [boost] [bind] segfault

From: Ormond, Randy (Randy.Ormond_at_[hidden])
Date: 2007-11-13 09:14:46

My apologies.  The explanation came to me in my sleep (which is fitting
because I must have been asleep when I made the mistake).

The recently added directories did not have our local 1.34.1 boost in
the include path.  Of course they compiled fine using the RedHat 1.32
boost but the two version collided with a segfault during execution.

Sorry for the noise.

-----Original Message-----
From: boost-bounces_at_[hidden]
[mailto:boost-bounces_at_[hidden]] On Behalf Of Jens Seidel
Sent: Monday, November 12, 2007 2:46 PM
To: boost_at_[hidden]
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