Tarjei Knapstad <tarjei.knapstad@predichem.com> writes:
On Mon, 2004-11-01 at 13:33, Aleksey Gurtovoy wrote:
Tarjei Knapstad writes:
On Sun, 2004-10-31 at 18:27, Aleksey Gurtovoy wrote:
Draft zip/tarballs for the 1.32 release are available from the following locations:
http://www.meta-comm.com/engineering/boost/boost_1_32_0.tar.bz2 http://www.meta-comm.com/engineering/boost/boost_1_32_0.tar.gz http://www.meta-comm.com/engineering/boost/boost_1_32_0.zip
These are NOT the tarballs that will be released; rather, they are the first probe aiming to uncover whatever problems we are still unaware of (including problems with archives preparation)
<snip>
The first two archives does not give write permissions to the user (for the unarchived files).
That's intentional. After all, normally you shouldn't be modifying anything in the distribution. Or should you?
Maybe not for the files, but the directories definitely need +w, otherwise I can't write to them. (In other words, I can't even build now without changing the permissions of at least the directories because jam can't write to/create the build directories).
The preferred method is to set the build directory outside the boost tree with --builddir=XXXXX. You're supposed to be able to build boost from readonly media. -- Dave Abrahams Boost Consulting http://www.boost-consulting.com