X-Recipient:	archive-cygwin AT delorie DOT com
DomainKey-Signature:	a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:mime-version:in-reply-to:references:date
	:message-id:subject:from:to:content-type; q=dns; s=default; b=yG
	pATRwJr5paSU49xjc01BGMtvrcsdpLlTdNJVyoo+FXzJ9BV1Y3oPdWm9gmqyvrZ5
	HtYVnImqENtBxu8WLvjo9/qTMuVmG8LGk7FwHsKYApvAXmvFMxiX5Ri7g3fWuScI
	vPKYTVGBcxwk/lIJfY/FSjPwp2c90PA+dSLS6NbtI=
DKIM-Signature:	v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:mime-version:in-reply-to:references:date
	:message-id:subject:from:to:content-type; s=default; bh=fjz6MPvd
	s/DT3GHg8Wj8MFf1kNM=; b=hgGW2fce4x8YcqMHiB2WQOfat4ZzcwTX+vxmLEvt
	JLbFFPXO4lUT5OkD7HAT976LPM28MVXA1e79PYDFiB9Psx8fMZXbqr+fqtv3bxI3
	EWisTfesPSFppLSV3AteTB/LOdeRMaOEWnUK20wyBlAXGziQ217oMqaH4tksLXS2
	3Sg=
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.com>
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/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
Authentication-Results:	sourceware.org; auth=none
X-Virus-Found:	No
X-Spam-SWARE-Status:	No, score=-1.6 required=5.0 tests=AWL,BAYES_00,FREEMAIL_FROM,RCVD_IN_DNSWL_NONE,SPF_PASS autolearn=ham version=3.3.2
X-HELO:	mail-qg0-f51.google.com
MIME-Version:	1.0
X-Received:	by 10.224.57.142 with SMTP id c14mr47513661qah.23.1399980342466; Tue, 13 May 2014 04:25:42 -0700 (PDT)
In-Reply-To:	<CAPbWNKGufbzvGCQd4u4e3nNp5OteAWM=C7=AgE1z-UVoN6XzjA@mail.gmail.com>
References:	<CAPbWNKGufbzvGCQd4u4e3nNp5OteAWM=C7=AgE1z-UVoN6XzjA AT mail DOT gmail DOT com>
Date:	Tue, 13 May 2014 14:25:42 +0300
Message-ID:	<CAPbWNKFJMBDbyXH9S86+95L_Ak06auOn7BKnoqD9z1n7Ggtufg@mail.gmail.com>
Subject:	Re: How do start a cygwin shell session from a script ?
From:	Timothy Madden <terminatorul AT gmail DOT com>
To:	cygwin AT cygwin DOT com

It appears I found my missing shell session settings: the access
rights on the current build and source directories.

The manual build was always run within the user home directory in
cygwin, and cygwin could see the proper access right on all the files
used in the build.

But outside the user home directory, cygwin no longer sees the proper
permissions for directories and files, even though the user running
the cygwin session can very well read and write the files. But cygwin
will list the files with no permissions whatsoever, not even u+r (read
access for the file owner). If I use the Windows `icacls` command to
explicitly add the current user to the ACL on the directory with
inheritable (recursive) "full control" access right, than cygwin can
see the proper access rights too for such directories.

Can this issue maybe be fixed, so cygwin sees the same permissions, on
any files, user that Windows will grant to the current user ?

Thank you,
Timothy Madden

On Mon, May 12, 2014 at 1:12 PM, Timothy Madden <terminatorul AT gmail DOT com> wrote:
> Hello
>
> I have a CMake build script for my application, that among other
> things tries to build libvpx (open-source video codec, see
> webmproject.org).
>
> libvpx library v1.3.0 compiles fine by hand when I open a cygwin
> terminal from the Windows start menu and type in the needed
> `configure`; `make` and `make install` commands.
>
> But when I try to invoke the cygwin shell from my build script, to run
> the same 3 commands with the -lc option to sh.exe (same command line),
> something happens and the build commands no longer work like in the
> real mintty terminal. Then my build fails.
>
> I believe there is something in the cygwin shell session or
> environment that I do not know how to set right when invoking
> $(CYGWIN_DIR)/bin/sh from my CMake script.
>
> Is there a way for me to start a cygwin shell session from the build
> script, that is identical to the one that opens in the mintty terminal
> from the start menu, and run some commands there ?
>
> I checked the environment variables and umask in the mintty terminal
> and in a /bin/sh session that I launch, they are the same in both
> cases. I tried using /bin/sh, /bin/bash, /bin/dash, with both --login
> and -c options. But the automated build always fails, and the manual
> build works.
>
> Thank you,
> Timothy Madden

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

- Raw text -