X-Recipient: archive-cygwin AT delorie DOT com X-Spam-Check-By: sourceware.org Date: Wed, 23 Sep 2009 14:17:35 +0200 From: Corinna Vinschen To: cygwin AT cygwin DOT com Subject: Re: Is this a known problem with getenv() ? Message-ID: <20090923121735.GA20981@calimero.vinschen.de> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <005f01ca3c4b$e5385b10$4001a8c0 AT mycomputer> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <005f01ca3c4b$e5385b10$4001a8c0@mycomputer> User-Agent: Mutt/1.5.19 (2009-02-20) Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com On Sep 23 12:46, John Emmas wrote: > I first started using cygwin almost exactly a year ago. Because of other > pressures I put it on the back burner (about 6 months ago) at which point, > it was current. However, I haven't upgraded for about 6 months. > > This morning I needed to compile an app that uses the C call, > getenv("PATH"); Let's say for the sake of argument that this was my path > (as displayed in a console window after typing "set") :- > > /usr/local/bin:/usr/bin:/bin:/usr/X11R6/bin:/a:/b:/c:/d:/e > > That's not my actual path - just an example. Cygwin's getenv() is returning > something like this:- > > /usr/local/bin:/usr/bin:/bin:/usr/X11R6/bin:/a:/b:/usr/local/bin:/usr/bin:/bin:/usr/X11R6/bin:/c:/d:/usr/local/bin:/usr/bin:/bin:/usr/X11R6/bin:/e:/usr/local/bin:/usr/bin:/bin:/usr/X11R6/bin: > > Basically, any path folder that ends in '/bin' is being inserted into the > path multiple times and I just wondered if this was a known problem? > FWIW if I use the glib equivalent (g_getenv) I get the same problem (which > probably just indicates that g_getenv is a wrapper around getenv). > > Thanks for any advice, I can't reproduce this behaviour. Maybe the cygcheck output as described here vvvv > Problem reports: http://cygwin.com/problems.html would help to figure out what's wrong on your machine. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat -- 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