[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: HP-UX make causes autoconf timestamp issues
From: |
Eric Blake |
Subject: |
Re: HP-UX make causes autoconf timestamp issues |
Date: |
Mon, 24 Jan 2011 14:10:53 -0700 |
User-agent: |
Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.13) Gecko/20101209 Fedora/3.1.7-0.35.b3pre.fc14 Lightning/1.0b3pre Mnenhy/0.8.3 Thunderbird/3.1.7 |
On 01/24/2011 02:00 PM, Ralf Wildenhues wrote:
>> That is, is it only an autoconf bug,
>> where if you fix the autoconf bug, then all other victims will be fixed?
>
> No. If you are building from a read-only tree, or, more generally, any
> source tree that has been generated elsewhere and that is not supposed
> to see updates, and the tree has rules that update shipped files, then
> there are potentially problems with HP-UX make.
All the more reason to document the issue in INSTALL. If I'm
understanding you correctly, disabling autom4te.cache only disables
autoconf's contribution to the rebuild rules (others may remain, for
things like gperf- or yacc-generated files), but we might as well start
somewhere by documenting what we can.
> How about:
>
> The non-Posix time stamp semantics of HP-UX make can cause spurious
> rebuilds of generated files in the source tree.
>
> and then continue with this:
>
>>> + It is recommended to turn off autom4te caching on these systems if GNU
>>> + make cannot be used (see info Autoconf 'Customizing autom4te').
Yes, that wording does sound a bit better.
--
Eric Blake address@hidden +1-801-349-2682
Libvirt virtualization library http://libvirt.org
signature.asc
Description: OpenPGP digital signature