An override of "CLONE" on the bjam call seemed to do the trick:

'-sCLONE=cp -fd'

The default is CLONE=cp -pfd

Mike


On Thu, Jun 12, 2008 at 4:26 PM, mike o <mike.otj@gmail.com> wrote:
Hello All,

I am running into a FileClone failure when building boost-1.33.1 on RHEL AS 5.0 32-bit.  FileClone works fine when I build *on* the machine, but I am running into problems when building on a network filesystem.  Here is an excerpt of the bjam output w/ -d2:


    ranlib  "/mydir/.obj/boost/boost_1_33_1-build/Linux/GLIBC_2.5/32/gcc-4.1.2/bin/boost/libs/wave/build/libboost_wave.a/gcc/release/runtime-link-static/libboost_wave-gcc-s-1_33_1.a"

FileClone /mydir/boost/boost-1.33.1/Linux/GLIBC_2.5/32/gcc-4.1.2/lib/libboost_wave-gcc-s-1_33_1.a

    cp -fpd  "/mydir/.obj/boost/boost_1_33_1-build/Linux/GLIBC_2.5/32/gcc-4.1.2/bin/boost/libs/wave/build/libboost_wave.a/gcc/release/runtime-link-static/libboost_wave-gcc-s-1_33_1.a"  "/mydir/boost/boost-1.33.1/Linux/GLIBC_2.5/32/gcc-4.1.2/lib/libboost_wave-gcc-s-1_33_1.a"

cp: preserving permissions for `/mydir/boost/boost-1.33.1/Linux/GLIBC_2.5/32/gcc-4.1.2/lib/libboost_wave-gcc-s-1_33_1.a': Operation not supported
cp: preserving ACL for `/mydir/boost/boost-1.33.1/Linux/GLIBC_2.5/32/gcc-4.1.2/lib/libboost_wave-gcc-s-1_33_1.a': Operation not supported
...failed FileClone /mydir/boost/boost-1.33.1/Linux/GLIBC_2.5/32/gcc-4.1.2/lib/libboost_wave-gcc-s-1_33_1.a...
...removing /mydir/boost/boost-1.33.1/Linux/GLIBC_2.5/32/gcc-4.1.2/lib/libboost_wave-gcc-s-1_33_1.a



Is the FileClone failing simply because permissions/ACL cannot be preserved?  Even though the file is actually copied to the right place?

Is there a way to work around this?...maybe by disabling the "remove" step from FileClone, or any other way?


Thanks,
Mike