$include_dir="/home/hyper-archives/boost/include";
include("$include_dir/msg-header.inc")
?>
- Next message: Peter Dimov: "Re: bcp namespace aliasing broken, impacts package providers, shared libraries unusable since 1.69"
- Previous message: Peter Dimov: "Re: bcp namespace aliasing broken, impacts package providers, shared libraries unusable since 1.69"
- In reply to: Peter Dimov: "Re: bcp namespace aliasing broken, impacts package providers, shared libraries unusable since 1.69"
- Next in thread: Peter Dimov: "Re: bcp namespace aliasing broken, impacts package providers, shared libraries unusable since 1.69"
- Reply: Peter Dimov: "Re: bcp namespace aliasing broken, impacts package providers, shared libraries unusable since 1.69"
On 5/26/19 5:39 PM, Peter Dimov via Boost wrote:
>
> 3. Installing these libraries exposed issues with them:
>
> 3a. Log doesn't work because it has jamfiles in libs/log/config, which
> is not copied (just `build` and `src` are.)
Could you expand? I'm not sure I understand how an incomplete Boost.Log
directory tree comes to be.
- Next message: Peter Dimov: "Re: bcp namespace aliasing broken, impacts package providers, shared libraries unusable since 1.69"
- Previous message: Peter Dimov: "Re: bcp namespace aliasing broken, impacts package providers, shared libraries unusable since 1.69"
- In reply to: Peter Dimov: "Re: bcp namespace aliasing broken, impacts package providers, shared libraries unusable since 1.69"
- Next in thread: Peter Dimov: "Re: bcp namespace aliasing broken, impacts package providers, shared libraries unusable since 1.69"
- Reply: Peter Dimov: "Re: bcp namespace aliasing broken, impacts package providers, shared libraries unusable since 1.69"
$include_dir="/home/hyper-archives/boost/include";
include("$include_dir/msg-footer.inc");
?>