Re: too many environment variables on self-compiled xar archiver

2017-05-25 Thread Brian Inglis
On 2017-05-24 15:18, Hans-Bernhard Bröker wrote: > Am 24.05.2017 um 12:01 schrieb Andrey Repin: > >>> Did you notice this entry and does anyone know where this comes from? >>> !C:=C:\cygwin\bin > >> This is coming from CMD, and denotes current working directory on an >> indicated >>

Re: too many environment variables on self-compiled xar archiver

2017-05-25 Thread Andrey Repin
Greetings, Hans-Bernhard Bröker! > Am 24.05.2017 um 12:01 schrieb Andrey Repin: >>> Did you notice this entry and does anyone know where this comes from? >>> !C:=C:\cygwin\bin >> This is coming from CMD, and denotes current working directory on an >> indicated >> drive. > And for

Re: too many environment variables on self-compiled xar archiver

2017-05-24 Thread Hans-Bernhard Bröker
Am 24.05.2017 um 12:01 schrieb Andrey Repin: Did you notice this entry and does anyone know where this comes from? !C:=C:\cygwin\bin This is coming from CMD, and denotes current working directory on an indicated drive. And for (most of) all the hairy details, see

Re: too many environment variables on self-compiled xar archiver

2017-05-24 Thread Andrey Repin
Greetings, Brian Inglis! > On 2017-05-23 16:30, Michael Stellar wrote: >> I am getting the following when running my self-compiled xar 1.6.1 archiver >> gdb xar >> Starting program: /usr/local/bin/xar >> [New Thread 12044.0x1f54] >> [New Thread 12044.0xfc8] >> [New Thread 12044.0x2dcc] >> [New

Re: too many environment variables on self-compiled xar archiver

2017-05-24 Thread Michael Stellar
Tried, on 1 different machine without vs 2015 and vs 2017 installed on it, pretty much minimum env variables, getting the same result, probably it's a bug in the cygwin runtime?, does anyone or cygwin developer have other clue?. On Wed, May 24, 2017 at 2:42 PM, Michael Stellar

Re: too many environment variables on self-compiled xar archiver

2017-05-24 Thread Michael Stellar
Hello Brian, Appreciated the reply, tried to search "!C:" on registry or searching for "!C:" in all files (*.*) content on c:\cygwin or using tools like rapidee (to edit env variables), and the result is i could not found it!. Looks like it's being added by either the bash shell? itself

Re: too many environment variables on self-compiled xar archiver

2017-05-23 Thread Brian Inglis
On 2017-05-23 16:30, Michael Stellar wrote: > I am getting the following when running my self-compiled xar 1.6.1 archiver > gdb xar > Starting program: /usr/local/bin/xar > [New Thread 12044.0x1f54] > [New Thread 12044.0xfc8] > [New Thread 12044.0x2dcc] > [New Thread 12044.0x2cd8] > [New Thread

too many environment variables on self-compiled xar archiver

2017-05-23 Thread Michael Stellar
Hello, I am getting the following when running my self-compiled xar 1.6.1 archiver gdb xar Starting program: /usr/local/bin/xar [New Thread 12044.0x1f54] [New Thread 12044.0xfc8] [New Thread 12044.0x2dcc] [New Thread 12044.0x2cd8] [New Thread 12044.0x2d58] 1 [main] xar 12044