Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Date: Wed, 7 Apr 2004 15:57:59 +0200
From: "Gerrit P. Haase" <freeweb AT nyckelpiga DOT de>
Reply-To: "Gerrit P. Haase" <freeweb AT nyckelpiga DOT de>
Organization: Esse keine toten Tiere
Message-ID: <69167940155.20040407155759@familiehaase.de>
To: "Edward S. Peschko" <esp5 AT pge DOT com>
CC: Cygwin List <cygwin AT cygwin DOT com>
Subject: Re: errors coming from building from scratch
In-Reply-To: <20040406191728.GC13267@mdssdev05.comp.pge.com>
References: <20040406020236 DOT GA11062 AT mdssdev05 DOT comp DOT pge DOT com> <4968407554 DOT 20040406121907 AT familiehaase DOT de> <20040406184304 DOT GA13267 AT mdssdev05 DOT comp DOT pge DOT com> <6 DOT 0 DOT 1 DOT 1 DOT 0 DOT 20040406145027 DOT 037c0400 AT 127 DOT 0 DOT 0 DOT 1> <20040406191728 DOT GC13267 AT mdssdev05 DOT comp DOT pge DOT com>
MIME-Version: 1.0
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7bit

Hi Edward,

>> Perhaps I'm missing something obvious but it seems to me that the real
>> question is why automake is installing things with the incorrect 
>> permissions for you.  Is there a reason you're not focused on this issue?

> Well, as a quick workaround I am focused on this issue (I install my own hacked
> version of automake) but there are two reasons why I think 777 perms is a bad policy
> to follow:

>     1) I think its going to be a hard issue to sell automake on the necessity
>        of making cygwin behave totally different from any other environment,
>        and make a kludge to have arguments to install for cygwin be 777
>        by default.

Why?  Different platforms always need their own special way to get
things running. BTW, the default setting for executables should be 755
as it is on Linux too, in the Windows world, also shared libs need this
permission.


>     2) down-the-stream packages don't necessarily use automake - they've
>        already got generated Makefile.in or configure scripts which have 644
>        hardcoded. Asking users to get a new version of automake and regenning
>        things using automake is too much to ask IMO.

I'm not sure if automake includes code for managing DLL installation at
all, this is usually done via libtool.


>     3) imo - philosophically its just wrong to require execute permissions
>        for the libraries. the program links with the libraries to use the
>        libraries functionality, it doesn't 'execute the library'.

It is this way on Windows, shared libraries must be executable.


> Its not a question of whether or not I can hack around stuff, I can and will,
> its a question of how clean people want the building process to be, and how
> useful the tools are. As well as how close they mimic other unixes.

The tools should just work.  If they do things wrong, then the tools
need to be fixed.


Gerrit
-- 
=^..^=                                     http://nyckelpiga.de/donate.html


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/