Boost logo

Boost :

From: Beman Dawes (bdawes_at_[hidden])
Date: 2008-03-17 12:20:17

Vladimir Prus wrote:
> Beman Dawes wrote:
>> Sean Hunt wrote:
>>> I get a compilation fail with the following error (or a similar-enough
>>> one, differing only in the target) on a total of 24 different targets:
>>> Jamfile</<snip>/boost-posix-2008-03-14/libs/function_types/build>.wave
>>> /<snip>/boost-posix-2008-03-14/libs/function_types/build/timestamps/cc_names
>>> /bin/sh: line 1: /<snip>/boost-posix-2008-03-14/dist/bin/wave: No such
>>> file or directory
>>> It may be the same as Dave Compton's problem, just on Linux.
>> Hum... This isn't sounding good.
>> We need someone familiar with the build system to debug this. Volunteers?
> This has nothing to do with build system. For whatever reason, Jamfile
> for the function_types library assumes there's <boost-root>/dist/bin/wave
> binary -- and there's no reason to assume that.
> I don't know how wave is used by function_types, but requiring that wave
> is built and installed seems a questionable thing -- was it ever discussed,
> and agreed upon?
> In fact, here's what Jamfile in question has:
> make $(BOOST_ROOT)/libs/function_types/build/timestamps/arity_loops
> : preprocess_arity_loops.cpp : wave
> ;
> so it's not even building anything the user would ever find in
> installed tree. I'm confused as to what's the purpose here.

Thanks for tracking this down, Volodya!

Tobias, what's going on here? Can you fix it?


Boost list run by bdawes at, gregod at, cpdaniel at, john at