Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT sources DOT redhat DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT sources DOT redhat DOT com>
List-Help: <mailto:cygwin-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT sources DOT redhat DOT com
Delivered-To: mailing list cygwin AT sources DOT redhat DOT com
Message-ID: <3B7B2B5F.4070703@ece.gatech.edu>
Date: Wed, 15 Aug 2001 22:09:35 -0400
From: Charles Wilson <cwilson AT ece DOT gatech DOT edu>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.2) Gecko/20010713
X-Accept-Language: en-us
MIME-Version: 1.0
To: tromey AT redhat DOT com
CC: Robert Collins <robert DOT collins AT itdomain DOT com DOT au>, cygwin AT Cygwin DOT Com,
        Bernard Dautrevaux <Dautrevaux AT microprocess DOT com>,
        "'Tim Van Holder'" <tim DOT van DOT holder AT pandora DOT be>, automake AT gnu DOT org
Subject: Re: Automake 1.4l released
References: <3B7974C6 DOT 83934084 AT yahoo DOT com> <3B797B22 DOT C06C71D9 AT yahoo DOT com> <87bslip7hj DOT fsf AT creche DOT redhat DOT com> <20010814195923 DOT A28367 AT redhat DOT com> <87wv46uoac DOT fsf AT creche DOT redhat DOT com> <997839007 DOT 16944 DOT 3 DOT camel AT robertlinux> <3B79DED8 DOT 3040807 AT ece DOT gatech DOT edu> <87snes4u2y DOT fsf AT creche DOT redhat DOT com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit

Tom Tromey wrote:

>>>>>>"Charles" == Charles Wilson <cwilson AT ece DOT gatech DOT edu> writes:
>>>>>>
> 
> Charles> Nope.  It actually seems to be due to a change in automake.
> Charles> Apparently, make distcheck did not previously 'chmod -R a-w'.
> 
> I looked a bit but due to massive reorganization it is a pain to find
> out when this went in.
> 
> 
> We rely on `cp -p' in a few places, all in `dist'.  The problem is
> most obvious in `distcheck' because it makes the tree read-only when
> it is unpacked.  But suppose you use something like CVSREAD and check
> out a tree.  Then a file like configure could very well be read-only,
> leading to the same problem for a simple `dist'.
> 
> I think we could add a check for whether "cp -p works in ." to
> AM_INIT_AUTOMAKE and then use the result everywhere.  For this to work
> we'd also need to add code to `missing' to handle this case, I think
> (code I'm not entirely sure how to write -- ideally it would restore
> the original file's permissions once it was done with the copy).
> 
> I think our goal should be to support this feature everywhere.  But if
> there aren't maintainers who need this in 1.5, I would prefer to file
> a PR and leave it until a later release.  If you are such a
> maintainer, please speak up.  Charles, are you?


No, I am not.  None of my (very small) original source contributions are 
autotool'ed <hangs head in shame>.  My interest is in making it easier 
to get a working, autotool/libtool system for building DLL's on cygwin 
"transparently" -- e.g. just like so's on unix.  Then, I can more easily 
port stuff to cygwin; I'm not *really* that concerned about originating 
software on cygwin (although that may be important to other people).

Since robert collin's hacked version of libtool which meets this goal 
requires:

auto-import changes in binutils
   --> completed (a few pending problems, but mostly there)
up-to-date autoconf
   --> 2.52 package for cygwin was released a few weeks ago
automake-1.4i or later
   --> so I've been tracking recent automake development. Hopefully, 
when automake-1.5 is released (and verified to work acceptably on 
cygwin), an official cygwin package will be released soon thereafter.

Therefore I've been meddling (read: I've been a major PITA :-) in the 

developers' mailing lists for those projects recently.


--Chuck



--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/