Date: Sun, 26 Dec 2010 00:20:33 -0500
From: Christopher Faylor <cgf-use-the-mailinglist-please AT cygwin DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: program_invocation_name
Message-ID: <20101226052033.GA443@ednor.casa.cgf.cx>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
References: <4D15177E DOT 7080508 AT redhat DOT com> <1293331193 DOT 5636 DOT 4 DOT camel AT YAAKOV04>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <1293331193.5636.4.camel@YAAKOV04>
User-Agent: Mutt/1.5.20 (2009-06-14)
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Precedence: bulk
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com

On Sat, Dec 25, 2010 at 08:39:53PM -0600, Yaakov (Cygwin/X) wrote:
>On Fri, 2010-12-24 at 14:58 -0700, Eric Blake wrote:
>> Porting of some programs originally written for glibc over to cygwin
>> would be easier if cygwin could provide the global variables char*
>> program_invocation_{short_,}name, set automatically to match argv[0] of
>> main(), and declared in <errno.h> when strict standards compliance isn't
>> requested.
>
>util-linux would benefit from this as well.
>
>> Is it worth my time to go ahead and submit a patch to add
>> this?  Or is our party line still that as long as you are using
>> non-portable means, you should just continue to use
>> readlink("/proc/self/exe") when porting to cygwin?
>
>FWIW, since we strive to be a "Linux-like environment" (per our
>website), then I think it should go in.

I'll check something in tomorrow.

I was going to check something in tonight but sourceware is doing its
weekly mysql-optimize so everything has ground to a halt.

cgf

--
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