Re: Bug in LT 1.5 AC_LIBTOOL_PROG_CC_C_O

[Bob Friesenhahn]

On Tue, 16 Dec 2003, Jeff Squyres wrote:
> -----
> RCS file: /cvsroot/libtool/libtool/m4/libtool.m4,v
> retrieving revision 1.20
> diff -u -r1.20 libtool.m4
> --- m4/libtool.m4       14 Nov 2003 11:12:21 -0000      1.20
> +++ m4/libtool.m4       14 Nov 2003 13:17:47 -0000
> @@ -976,13 +976,6 @@
>     mkdir out
>     printf "$lt_simple_compile_test_code" > conftest.$ac_ext
>
> -   # According to Tom Tromey, Ian Lance Taylor reported there are C compilers
> -   # that will create temporary files in the current directory regardless of
> -   # the output directory.  Thus, making CWD read-only will cause this test
> -   # to fail, enabling locking or at least warning the user not to do 
> parallel
> -   # builds.
> -   chmod -w .
> -
>     lt_compiler_flag="-o out/conftest2.$ac_objext"
>     # Insert the option either (1) after the last *FLAGS variable, or
>     # (2) before a word containing "conftest.", or (3) at the end.

It seems to me that having libtool change the access modes for the
current directory is very unfriendly behavior.  For example, if the
build is within the source tree, this would make it difficult for the
package maintainer to maintain the package.  I don't believe that
build tools should modify permissions on anything but the files that
they are responsible for.

Bob
======================================
Bob Friesenhahn
address@hidden
http://www.simplesystems.org/users/bfriesen