Re: Bug in LT 1.5 AC_LIBTOOL_PROG_CC_C_O

[Gary V. Vaughan]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Bob Friesenhahn wrote:
| On Sun, 4 Jan 2004, Gary V.Vaughan wrote:
|
|>The comment shows that the intent of the chmod is to prevent compilers
|>which create tmpfile droppings in the working directory from barfing
|>during parallel builds.
|>
|>I think it is correct to test for this condition and to set
|>enable_libtool_lock if it occurs.  I do agree that
|>AC_LIBTOOL_PROG_CC_C_O is the wrong place to do that.
|
|
| But there is nothing technically wrong with compilers creating
| temporary files in the current directory!  This may even be more
| reliable for machines with small /tmp directories.
|
| I believe that libtool is incorrect to assume that locking must be
| used if the compiler places its temporary files in the current
| directory.  There may be a few compilers in the world which are not
| smart enough to create non-conflicting temporary files, but these are
| surely in the minority.  It would be wiser to assume that compilers
| work correctly, and positively identify the few that don't.  People
| with broken tools should not attempt parallel builds anyway.

Okay, that sounds reasonable.  Please apply Jeff's patch.

Cheers,
        Gary.
- --
Gary V. Vaughan      ())_.  address@hidden,gnu.org}
Research Scientist   ( '/   http://www.oranda.demon.co.uk
GNU Hacker           / )=   http://www.gnu.org/software/libtool
Technical Author   `(_~)_   http://sources.redhat.com/autobook
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQE/+oi4FRMICSmD1gYRAk3wAKClGWx1u/hKzp9yLM6lTvk4azRpcACfe3f4
Wryi2att7idNhlOptJ6mm8Q=
=xugH
-----END PGP SIGNATURE-----