Re: Question about XP support

Am 25.05.2016 um 16:54 schrieb Corinna Vinschen: On May 25 09:56, Stephen John Smoogen wrote: On 25 May 2016 at 06:07, Corinna Vinschen wrote: On May 24 20:38, Herbert Stocker wrote: On 24.05.2016 18:44, Jim Reisert AD1C wrote: I thought that support for Windows

Re: Question about XP support

On Wed, May 25, 2016 at 10:56 AM, Corinna Vinschen wrote: > 2.6, probably. This is much more than you got back in the days when > we dropped support for 9x, NT4, W2K ;) I'll be happy with that :) -- Erik -- Problem reports: http://cygwin.com/problems.html FAQ:

Re: Question about XP support

On May 25 10:22, Erik Soderquist wrote: > On Wed, May 25, 2016 at 9:56 AM, Stephen John Smoogen wrote: > > > > On 25 May 2016 at 06:07, Corinna Vinschen wrote: > > > Uh oh, bad timing... > > > > > > The next release 2.5.2 introduces the first non-XP compatible code. > > > It's in a seldom used

Re: Question about XP support

On May 25 09:56, Stephen John Smoogen wrote: > On 25 May 2016 at 06:07, Corinna Vinschen wrote: > > On May 24 20:38, Herbert Stocker wrote: > >> On 24.05.2016 18:44, Jim Reisert AD1C wrote: > >> > I thought that support for Windows XP had been removed from Cygwin. > >>

Re: Question about XP support

On Wed, May 25, 2016 at 9:56 AM, Stephen John Smoogen wrote: > > On 25 May 2016 at 06:07, Corinna Vinschen wrote: > > Uh oh, bad timing... > > > > The next release 2.5.2 introduces the first non-XP compatible code. > > It's in a seldom used corner of the code and it doesn't require > > functions

Re: Question about XP support

On 25 May 2016 at 06:07, Corinna Vinschen wrote: > On May 24 20:38, Herbert Stocker wrote: >> On 24.05.2016 18:44, Jim Reisert AD1C wrote: >> > I thought that support for Windows XP had been removed from Cygwin. >> >> No, has not yet been removed. >> And i'm sooo happy

Re: Question about XP support

On May 24 20:38, Herbert Stocker wrote: > On 24.05.2016 18:44, Jim Reisert AD1C wrote: > > I thought that support for Windows XP had been removed from Cygwin. > > No, has not yet been removed. > And i'm sooo happy about this. Uh oh, bad timing... The next release 2.5.2 introduces the first

Re: Question about XP support

On Tue, May 24, 2016 at 10:56 AM, Erik Soderquist wrote: > There has been notice that XP support will be dropped at some point in > the future, but as far as I know, that point has not been reached. Thanks to those who replied. This will make it easier for me to fix what I broke. -- Jim

Re: Question about XP support

On 24.05.2016 18:44, Jim Reisert AD1C wrote: I thought that support for Windows XP had been removed from Cygwin. No, has not yet been removed. And i'm sooo happy about this. Cause i'm still using XP for my work. Deliberately. Why? Because it's so lightweight in a virtual machine. Give it only

Re: Question about XP support

>> On Tue, May 24, 2016 at 12:44 PM, Jim Reisert AD1C wrote: >> I thought that support for Windows XP had been removed from Cygwin. >> Yet the Cygwin home page says: >> >> https://cygwin.com/ >> >> "The Cygwin DLL currently works with all recent, commercially >> released x86 32 bit and 64

Re: Question about XP support

On Tue, May 24, 2016 at 12:44 PM, Jim Reisert AD1C wrote: > I thought that support for Windows XP had been removed from Cygwin. > Yet the Cygwin home page says: > > https://cygwin.com/ > > "The Cygwin DLL currently works with all recent, commercially > released x86 32 bit and 64 bit

Question about XP support

I thought that support for Windows XP had been removed from Cygwin. Yet the Cygwin home page says: https://cygwin.com/ "The Cygwin DLL currently works with all recent, commercially released x86 32 bit and 64 bit versions of Windows, starting with Windows XP SP3." I'm happy to be wrong

pypiwin32 question

I am trying to use ctypes and MessageBoxA in a Python script to generate a message box. That seems to be working fine most of the time. However, it seems that if I go away for a while no message box is displayed when I think it should have been. Is there some kind of timeout somewhere that will

Re: X widget question

On 22/03/2016 11:18, Jon Turney wrote: On 20/03/2016 09:57, Marco Atzeri wrote: I have finally identified where ncview was segfaulting on X86_64 The solution was to reverse the order of destruction for a chain of widgets Nice to see that you have resolved this. It's not clear from what you

Re: X widget question

On 20/03/2016 09:57, Marco Atzeri wrote: I have finally identified where ncview was segfaulting on X86_64 The solution was to reverse the order of destruction for a chain of widgets Nice to see that you have resolved this. It's not clear from what you write if you are sure there is an

X widget question

I have finally identified where ncview was segfaulting on X86_64 The solution was to reverse the order of destruction for a chain of widgets i=0; - while( (w = *(diminfo_row_widget + i++)) != NULL ) - XtDestroyWidget( w ); + while( (w = *(diminfo_row_widget +

Re: Question about tar v1.28

> Could be an accidental regression in my cygwin-specific patches betweenthe > two versions. But I don't normally use or test on text-mounts, so > I'll need confirmation that you are indeed experiencing the problem only > For what it's worth, I recently had the similar issues with Cygwin tar on

Re: Question about tar v1.28

Greetings, Douglas Coup! >> On 03/08/2016 08:43 AM, Douglas Coup wrote: >>> Hello Cygwin community. >>> >>> I'm observing some unusual behavior with tar v1.28, running as part of > >>> 32-bit Cygwin on a Windows 10 machine. > > >> I noticed this in your cygcheck output: > cygdrive prefix

Re: Question about tar v1.28

On 03/08/2016 08:43 AM, Douglas Coup wrote: > Hello Cygwin community. > > I'm observing some unusual behavior with tar v1.28, running as part of > 32-bit Cygwin on a Windows 10 machine. I noticed this in your cygcheck output: > cygdrive prefix /cygdrive system text,noacl,posix=0,auto Why

[newlib-cygwin/topic/posix_acl_funcs] faq: Update FAQ question and answer about gdb and signals

https://sourceware.org/git/gitweb.cgi?p=newlib-cygwin.git;h=9c8a6e56460cfa0b122884121561cb90a1864971 commit 9c8a6e56460cfa0b122884121561cb90a1864971 Author: Jon Turney <jon.tur...@dronecode.org.uk> Date: Thu Jan 14 17:44:18 2016 + faq: Update FAQ question and answer abo

[newlib-cygwin] faq: Update FAQ question and answer about gdb and signals

https://sourceware.org/git/gitweb.cgi?p=newlib-cygwin.git;h=9c8a6e56460cfa0b122884121561cb90a1864971 commit 9c8a6e56460cfa0b122884121561cb90a1864971 Author: Jon Turney <jon.tur...@dronecode.org.uk> Date: Thu Jan 14 17:44:18 2016 + faq: Update FAQ question and answer abo

[PATCH] Update FAQ question and answer about gdb and signals

Signed-off-by: Jon Turney --- winsup/doc/faq-programming.xml | 19 +-- 1 file changed, 13 insertions(+), 6 deletions(-) diff --git a/winsup/doc/faq-programming.xml b/winsup/doc/faq-programming.xml index af6102a..7f1ffd9 100644 ---

Re: [PATCH] Update FAQ question and answer about gdb and signals

On Jan 14 18:05, Jon Turney wrote: > Signed-off-by: Jon Turney > --- > winsup/doc/faq-programming.xml | 19 +-- > 1 file changed, 13 insertions(+), 6 deletions(-) > > diff --git a/winsup/doc/faq-programming.xml b/winsup/doc/faq-programming.xml >

Re: Question about incorrect System path from cygpath with case-sensitivity enabled

On Jan 10 22:54, Bryan Henry wrote: > Hi Corinna, > > Sorry for the delay getting back to you. I tested out the cygpath > binary from the latest snapshot and confirmed that it fixes my issue. > Thank for you making the change! You're welcome. Thanks for testing. Corinna -- Corinna Vinschen

Re: Question about incorrect System path from cygpath with case-sensitivity enabled

Hi Corinna, Sorry for the delay getting back to you. I tested out the cygpath binary from the latest snapshot and confirmed that it fixes my issue. Thank for you making the change! [~/Downloads/cygwin-inst-20160109]$ cygpath -W -u /C/Windows [~/Downloads/cygwin-inst-20160109]$ cygpath-old -W

Re: Question about incorrect System path from cygpath with case-sensitivity enabled

On Jan 2 18:33, Andrey Repin wrote: > Greetings, Bryan Henry! > > > I enabled (some time ago, not recently) case sensitivity on my Windows 8.1 > > system by setting the registry key mentioned in the FAQ here: > > https://cygwin.com/cygwin-ug-net/using-specialnames.html#pathnames-casesensitive >

Re: Question about incorrect System path from cygpath with case-sensitivity enabled

Greetings, Bryan Henry! > I enabled (some time ago, not recently) case sensitivity on my Windows 8.1 > system by setting the registry key mentioned in the FAQ here: > https://cygwin.com/cygwin-ug-net/using-specialnames.html#pathnames-casesensitive > Today, I updated Cygwin and noticed a message

Re: Question about incorrect System path from cygpath with case-sensitivity enabled

On Fri, Jan 1, 2016 at 1:21 PM, Bryan Henry wrote: > > [~]$ cygpath -S -u > /C/WINDOWS/System32 > [~]$ file `cygpath -S -u` > /C/WINDOWS/System32: cannot open `/C/WINDOWS/System32' (No such file or > directory) > [~]$ file /C/Windows/System32 > /C/Windows/System32: directory > Although I haven't

Question about incorrect System path from cygpath with case-sensitivity enabled

I enabled (some time ago, not recently) case sensitivity on my Windows 8.1 system by setting the registry key mentioned in the FAQ here: https://cygwin.com/cygwin-ug-net/using-specialnames.html#pathnames-casesensitive Today, I updated Cygwin and noticed a message about a failed postinstall

Re: texinfo package question

On 29/12/2015 05:09, lloyd.w...@yahoo.co.uk wrote: shouldn't the texinfo package be a dependency that gets pulled in for the texinfo-tex package? It doesn't seem to be (on 64-bit cygwin). thanks Lloyd Wood http://www.geomview.org/ the setup.ini has that dependency @ texinfo-tex sdesc:

texinfo package question

shouldn't the texinfo package be a dependency that gets pulled in for the texinfo-tex package? It doesn't seem to be (on 64-bit cygwin). thanks Lloyd Wood http://www.geomview.org/ -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/

another LoadLibrary question / crash (sorry)

Hi, I apologize for asking the same question that has been asked so many times - but I'm stuck. I have a DLL built in Cygwin that I'm trying to call from a program compiled in Visual Studio 2012. When I call LoadLibrary it's successful, however calls to the APIs crash the program. >From w

Re: Question about old win32 api

On Tue, Sep 22, 2015 at 10:54 AM, Yaakov Selkowitz wrote: > > Installing with Cygwin Setup. > > > This is the only supported installation method. > On Tue, Sep 22, 2015 at 10:59 AM, David Stacey wrote: > We're drifting off topic, but never mind... Thanks Yaakov, David, Achim, Vince and whoever

Re: Question about old win32 api

Michael Enright writes: > I am interested to hear if anyone has managed a group of Cygwin users > and the configuration they use, and how they went about it. I do and the only sane way is to have a local mirror with exactly the packages and versions that you are going to install and your own

Re: Question about old win32 api

On Tue, 2015-09-22 at 10:16 -0700, Michael Enright wrote: > No one was updating. New workers needed new Windows boxes with Cygwin > on them. What is the process for putting Cygwin on a new Windows box? Installing with Cygwin Setup. > Cygwin's default (or only) distribution method has a role to

Re: Question about old win32 api

On Mon, Sep 21, 2015 at 9:16 PM, Vince Rice wrote: > > The blindness was, as I’ve already pointed out, caused by blindly > updating software No one was "updating"! I have diagnosed what I did "wrong" before and I am satisfied with my conclusion. I don't yet know of a way to keep changes from

Re: Question about old win32 api

On 22/09/15 18:16, Michael Enright wrote: New workers needed new Windows boxes with Cygwin on them. What is the process for putting Cygwin on a new Windows box? It isn't "rsync Cygwin from IT". Cygwin's default (or only) distribution method has a role to play in this. Does anyone ever setup

Re: Question about old win32 api

On Sep 21, 2015, at 7:11 PM, Michael Enright wrote: > > The blindness was blindness to the fact that new users were getting a > different version than existing users in some way other than fixing > vulns. Why should you believe that in the first place? There is only one Cygwin, so why would

Re: Question about old win32 api

On Mon, Sep 21, 2015 at 1:31 PM, Marco Atzeri wrote: > > the change in nc had nothing to do with cygwin > change between 1.5 and 1.7 > > https://sourceware.org/ml/cygwin-announce/2012-05/msg00015.html > Implying a tie between the nc version to the release of 1.7.0-0 was wrong on my part. I am

Re: Question about old win32 api

On Sep 21, 2015, at 8:11 PM, Michael Enright wrote: > > On Mon, Sep 21, 2015 at 5:50 PM, Vince Rice wrote: > >> blindly > > The blindness was blindness to the fact that new users were getting a > different version than existing users in some way other than fixing > vulns.

Re: Question about old win32 api

> On Sep 21, 2015, at 7:04 PM, Michael Enright wrote: > > On Mon, Sep 21, 2015 at 1:31 PM, Marco Atzeri wrote: >> >> the change in nc had nothing to do with cygwin >> change between 1.5 and 1.7 >> >> https://sourceware.org/ml/cygwin-announce/2012-05/msg00015.html >> > >

Re: Question about old win32 api

On Mon, Sep 21, 2015 at 5:50 PM, Vince Rice wrote: >blindly The blindness was blindness to the fact that new users were getting a different version than existing users in some way other than fixing vulns. Since Cygwin isn't the sort of product that needs to make up sham reasons to upgrade as

Re: Question about old win32 api

On Mon, 2015-09-21 at 16:10 +, jacob.a.lamber...@l-3com.com wrote: > I'm attempting to compile cygwin 1.7.18. I've made some progress, but have > run into what appears to be an incompatibility between minGW's Win32 api > and this version of cygwin. Better yet, why are you trying to build

Question about old win32 api

Hi all, I'm attempting to compile cygwin 1.7.18. I've made some progress, but have run into what appears to be an incompatibility between minGW's Win32 api and this version of cygwin. The same problem is identified here: https://sourceware.org/ml/cygwin/2013-10/msg00348.html. I have run into

Re: Question about old win32 api

On 21/09/2015 22:02, jacob.a.lamber...@l-3com.com wrote: Hello anrdae...@yandex.ru! 1. https://cygwin.com/acronyms/#TOFU pretty please. Upgrading would be a pain, Who said that?... 1. Here we go. 2. While I doubt it would be technically difficult, it would be easier to keep the same

Re: Question about old win32 api

On 21/09/2015 21:55, Michael Enright wrote: On Mon, Sep 21, 2015 at 12:25 PM, Andrey Repin wrote: Upgrading would be a pain, Who said that?... PMFJI, Between Cyg 1.5 and 1.7 the command-line interface changed on the "nc" utility and, from the point of view of someone who at the time

Re: Question about old win32 api

Greetings, jacob.a.lamber...@l-3com.com! 1. https://cygwin.com/acronyms/#TOFU pretty please. > Upgrading would be a pain, Who said that?... -- With best regards, Andrey Repin Monday, September 21, 2015 22:24:28 Sorry for my terrible english... -- Problem reports:

Re: Question about old win32 api

On Mon, Sep 21, 2015 at 12:25 PM, Andrey Repin wrote: > Greetings, jacob.a.lamber...@l-3com.com! > > 1. https://cygwin.com/acronyms/#TOFU pretty please. > >> Upgrading would be a pain, > > Who said that?... > > PMFJI, Between Cyg 1.5 and 1.7 the command-line interface changed on the "nc"

RE: Question about old win32 api

Hello anrdae...@yandex.ru! > 1. https://cygwin.com/acronyms/#TOFU pretty please. > > > Upgrading would be a pain, > > Who said that?... 1. Here we go. 2. While I doubt it would be technically difficult, it would be easier to keep the same version as far as good ol' corporate policy goes.

RE: Question about old win32 api

: Re: Question about old win32 api On Mon, 2015-09-21 at 16:10 +, jacob.a.lamber...@l-3com.com wrote: > I'm attempting to compile cygwin 1.7.18. I've made some progress, but > have run into what appears to be an incompatibility between minGW's > Win32 api and this version of cygwin

Re: Question about flock - potential memory corruption?

Hi Qian, sorry for the late reply, somehow I missed this mail. On Sep 5 04:22, Qian Hong wrote: > Dear list, > > When testing Cygwin/MSYS2 on Wine, I found randomly failure of flock(): > https://bugs.wine-staging.com/show_bug.cgi?id=466#c13 > > I ran MSYS2 with Wine+Valgrind, and found

Re: Question about flock - potential memory corruption?

Hi Corinna, Thanks a lot for your time. On Tue, Sep 8, 2015 at 4:58 PM, Corinna Vinschen wrote: > I'd still be glad to stick to upstream Cygwin, but, oh well. Understand, will take care of that. > Please try the attached patch. Thanks a lot for the patch, I can

Re: Question about flock - potential memory corruption?

On Tue, Sep 8, 2015 at 11:31 PM, Corinna Vinschen wrote: > Snapshot is up. Thanks! Tested with and without valgrind, confirming fixed. $ uname -a CYGWIN_NT-5.1 2.3.0(0.290/5/3) 2015-09-08 14:46 i686 Cygwin -- Regards, Qian Hong - http://www.winehq.org -- Problem

Re: Question about flock - potential memory corruption?

On Sep 8 18:35, Qian Hong wrote: > Hi Corinna, > > Thanks a lot for your time. > > On Tue, Sep 8, 2015 at 4:58 PM, Corinna Vinschen > wrote: > > > I'd still be glad to stick to upstream Cygwin, but, oh well. > Understand, will take care of that. > > > > Please try

Re: Question about flock - potential memory corruption?

On 07/09/2015 19:45, Qian Hong wrote: > Hi, > > Attach is the simple test case I use to reproduce the valgrind warning > and random failures. > > Compile the test case in Cygwin with below command line: > $ gcc -g -O0 flock.c -o flock.exe > > Thanks! > Hi, Erm ... slight technical hitch? Your

Re: Question about flock - potential memory corruption?

Hi Sam, Thank you very much for your reply! On Tue, Sep 8, 2015 at 12:41 PM, Sam Edge <sam.e...@dwalin.fsnet.co.uk> wrote: > Erm ... slight technical hitch? Your example flock.c doesn't call > fork(), nor does it use your two macros MAX_ITER & CHILDREN. Good questi

Re: Question about flock - potential memory corruption?

Hi, I was still not able to make valgrind display Cygwin symbols, so I manually translate the address to line this time. Tested with $ uname -a CYGWIN_NT-5.1 2.2.1(0.289/5/3) 2015-08-20 11:40 i686 Cygwin ==29863== Conditional jump or move depends on uninitialised value(s) ==29863==at

Re: Question about flock - potential memory corruption?

Hi, Attach is the simple test case I use to reproduce the valgrind warning and random failures. Compile the test case in Cygwin with below command line: $ gcc -g -O0 flock.c -o flock.exe Thanks! /*** * This is a STC that

Question about flock - potential memory corruption?

Dear list, When testing Cygwin/MSYS2 on Wine, I found randomly failure of flock(): https://bugs.wine-staging.com/show_bug.cgi?id=466#c13 I ran MSYS2 with Wine+Valgrind, and found warnings like below when calling flock(): 7 ==19315== Conditional jump or move depends on uninitialised value(s)

Re: How ask a question on Tkgate for Cygwin ?

2015) +++ -Message d'origine- De : David Stacey [mailto:drsta...@tiscali.co.uk] Envoyé : dimanche 31 mai 2015 23:42 À : cygwin@cygwin.com Cc : remi2...@laposte.net Objet : Re: How ask a question on Tkgate

RE: How ask a question on Tkgate for Cygwin ?

...@laposte.net Objet : Re: How ask a question on Tkgate for Cygwin ? On 31/05/15 20:00, Rémi 2005 wrote: checking tcl/tk version... configure: error: could not find tclConfig.sh You're probably missing the 'tcl-devel' package. Whilst you're installing things, the configure script is looking for flex

Re: How ask a question on Tkgate for Cygwin ?

On 31/05/2015 11:39, Rémi 2005 wrote: checking build system type... ./config.guess: unable to guess system type This script, last modified 2003-07-02, has failed to recognize the operating system you are using. It is advised that you download the most up to date version of the config scripts

RE: How ask a question on Tkgate for Cygwin ?

a question on Tkgate for Cygwin ? On 31/05/2015 11:39, Rémi 2005 wrote: checking build system type... ./config.guess: unable to guess system type This script, last modified 2003-07-02, has failed to recognize the operating system you are using. It is advised that you download the most up to date

Re: How ask a question on Tkgate for Cygwin ?

On 31/05/15 20:00, Rémi 2005 wrote: checking tcl/tk version... configure: error: could not find tclConfig.sh You're probably missing the 'tcl-devel' package. Whilst you're installing things, the configure script is looking for flex (so install 'flex') and a Fortran compiler (so install

RE: How ask a question on Tkgate for Cygwin ?

? Thanks in advance, Cordially, Rémi, -Message d'origine- De : David Stacey [mailto:drsta...@tiscali.co.uk] Envoyé : dimanche 31 mai 2015 01:01 À : cygwin@cygwin.com Cc : remi2...@laposte.net Objet : Re: How ask a question on Tkgate for Cygwin ? On 29/05/2015 22:23, Rémi Anjou wrote: What

Re: How ask a question on Tkgate for Cygwin ?

correctly ? Thanks in advance, Cordially, Rémi, -Message d'origine- De : David Stacey [mailto:drsta...@tiscali.co.uk] Envoyé : dimanche 31 mai 2015 01:01 À : cygwin@cygwin.com Cc : remi2...@laposte.net Objet : Re: How ask a question on Tkgate for Cygwin ? On 29/05/2015 22:23, Rémi

RE: How ask a question on Tkgate for Cygwin ?

 : remi2...@laposte.net Objet : Re: How ask a question on Tkgate for Cygwin ? On 29/05/2015 22:23, Rémi Anjou wrote: What is the procedure to install Tkgate with the Cygwin version 2.871 ? tkgate isn't present as a Cygwin package, so you will have to build it from source yourself. tkgate compiles

Re: How ask a question on Tkgate for Cygwin ?

Cc : remi2...@laposte.net Objet : Re: How ask a question on Tkgate for Cygwin ? On 29/05/2015 22:23, Rémi Anjou wrote: What is the procedure to install Tkgate with the Cygwin version 2.871 ? tkgate isn't present as a Cygwin package, so you will have to build it from source yourself. tkgate

Re: How ask a question on Tkgate for Cygwin ?

+++ -Message d'origine- De : David Stacey [mailto:drsta...@tiscali.co.uk] Envoyé : dimanche 31 mai 2015 01:01 À : cygwin@cygwin.com Cc : remi2...@laposte.net Objet : Re: How ask a question on Tkgate for Cygwin ? On 29/05/2015 22:23, Rémi Anjou wrote: What is the procedure to install Tkgate

Re: How ask a question on Tkgate for Cygwin ?

On 29/05/2015 22:23, Rémi Anjou wrote: What is the procedure to install Tkgate with the Cygwin version 2.871 ? tkgate isn't present as a Cygwin package, so you will have to build it from source yourself. tkgate compiles out of the box under Cygwin. However, Fedora carries four patches [1],

How ask a question on Tkgate for Cygwin ?

Hello, What is the procedure to install Tkgate with the Cygwin version 2.871 ? Thank's in advance, -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info:

question on building qt5

-- View this message in context: http://cygwin.1069669.n5.nabble.com/question-on-building-qt5-tp118172.html Sent from the Cygwin list mailing list archive at Nabble.com. -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation

Re: File Permissions - Yet Another Question / Clarification

Greetings, Bryan Berns! He's talking about Administrators the SID (group). Interesting. Given the built-in Administrators group doesn't often [directly] play into permissions on remote systems or cross-system permission models, I'm not sure where he was going with that. Regardless, I'll

Re: File Permissions - Yet Another Question / Clarification

Replying to myself on this topic in case anyone else is interested. 2) how can I get SSH to believe the two admin groups on my files are acceptable. I'm not optimistic I'm going to get SSH to change it's behavior so I may need to recompile it to avoid the check which is obviously not

Re: File Permissions - Yet Another Question / Clarification

I'll try to reproduce the issue on a standard NTFS volume -- although I would image Cygwin is just decoding the same DACL that ICACLS is returning. The other oddity is why it's not recognizing *me* as having any permissions. In the particular case of SSH, is there any way to make SSH ignore

Re: File Permissions - Yet Another Question / Clarification

He's talking about Administrators the SID (group). Interesting. Given the built-in Administrators group doesn't often [directly] play into permissions on remote systems or cross-system permission models, I'm not sure where he was going with that. Regardless, I'll consider it water under the

Re: File Permissions - Yet Another Question / Clarification

Greetings, Bryan Berns! I'll try to reproduce the issue on a standard NTFS volume -- although I would image Cygwin is just decoding the same DACL that ICACLS is returning. The other oddity is why it's not recognizing *me* as having any permissions. getfacl may shed additional light. In

Re: File Permissions - Yet Another Question / Clarification

Bryan Berns writes: In the real world in large corporations with focus on security, Administrators is typically a tiered or least privilege arrangement. He's talking about Administrators the SID (group). In any case, I'd start with a throwaway share (or save the permissions with subinacl if I

Re: File Permissions - Yet Another Question / Clarification

Andrey, In the particular case of SSH, is there any way to make SSH ignore these permissions? Thanks, I laughed. Thanks for the less-than-helpful response. A no would have sufficed if that is indeed the case. and obviously causing us pain given the permission weirdness. Removing the

Re: File Permissions - Yet Another Question / Clarification

Greetings, Bryan Berns! Sorry for not being more clear -- yes, I had read the FAQ on SSH. I was taking the problem up a level to the more obvious weirdness demonstrated by the resultant files on a simple touch. Why would Cygwin report that 'Domain Users' --- a group not in the DACL at all

Re: File Permissions - Yet Another Question / Clarification

Andrey, Sorry for not being more clear -- yes, I had read the FAQ on SSH. I was taking the problem up a level to the more obvious weirdness demonstrated by the resultant files on a simple touch. Why would Cygwin report that 'Domain Users' --- a group not in the DACL at all --- as being able to

File Permissions - Yet Another Question / Clarification

I finally am moving my user community to Cygwin 1.7.35 at work and having some issues with ssh not thinking user's ssh keys are owned by the user. I indeed can see that their directory listings do not show their userid as having read,write, or execute to *any* of their files. In short, just

Re: File Permissions - Yet Another Question / Clarification

Greetings, Bryan Berns! I finally am moving my user community to Cygwin 1.7.35 at work and having some issues with ssh not thinking user's ssh keys are owned by the user. I indeed can see that their directory listings do not show their userid as having read,write, or execute to *any* of

Re: Question about clisp version naming

Ken Brown writes: So maybe you could dump a memory image maxima.mem and start it with a script that calls 'clisp -M maxima.mem'. I'm already doing that. :-) I just took a look at the maxima package, and it seems that you already use a script that does something like this in the absence of a

Re: Question about clisp version naming

On 3/23/2015 2:45 AM, Achim Gratz wrote: As I said, I've revoked the maxima-exec-clisp package for now, so whether you either come up with a solution for that problem or conclude that dumping of executables isn't going to be supported on Cygwin, I'm fine. OK, that's good. I'd still like to

Re: Question about clisp version naming

Ken Brown writes: OK, that's good. I'd still like to get it to work, but I'm stumped at the moment. I've tried tweaking the build in various ways, but I can't get dumping of executables and dynamic modules to work simultaneously. The earlier approach of using a lisp DLL came the closest to

Re: Question about clisp version naming

On 3/22/2015 4:50 PM, Achim Gratz wrote: Ken Brown writes: And indeed it does. I've still got a couple of things to clean up, but I expect to upload a new clisp soon that no longer uses lisp.dll. I hope that will solve the Maxima problem It doesn't… Instead of lisp.dll it now requires

Re: Question about clisp version naming

Ken Brown writes: And indeed it does. I've still got a couple of things to clean up, but I expect to upload a new clisp soon that no longer uses lisp.dll. I hope that will solve the Maxima problem It doesn't… Instead of lisp.dll it now requires lisp.exe to be in $PATH and it produces an

Re: Question about clisp version naming

On 3/22/2015 6:33 PM, Ken Brown wrote: On 3/22/2015 4:50 PM, Achim Gratz wrote: Ken Brown writes: And indeed it does. I've still got a couple of things to clean up, but I expect to upload a new clisp soon that no longer uses lisp.dll. I hope that will solve the Maxima problem It doesn't…

Re: Question about clisp version naming

On 3/17/2015 9:47 PM, Yaakov Selkowitz wrote: A .def file can be used for two purposes: 1) to specify which symbols to export in a DLL/EXE, in place of dllexport or -Wl,--export-all-symbols (EXPORTS) 2) to resolve symbols by declaring them in other DLL/EXE(s), in place of a .dll.a (IMPORTS)

Re: Question about clisp version naming

On 3/17/2015 3:20 PM, Achim Gratz wrote: Ken Brown writes: Great. Thanks for testing. There's probably no reason for me to upload a new clisp package right now (unless it would help you). But I'll give you a heads up when I'm ready to do that. I've now drilled to the bottom of what I had

Re: Question about clisp version naming

On Tue, 2015-03-17 at 17:15 -0400, Ken Brown wrote: On 3/17/2015 3:20 PM, Achim Gratz wrote: Ken Brown writes: Great. Thanks for testing. There's probably no reason for me to upload a new clisp package right now (unless it would help you). But I'll give you a heads up when I'm ready to

Re: Question about clisp version naming

On 3/17/2015 8:17 PM, Jon TURNEY wrote: On 17/03/2015 22:40, Ken Brown wrote: Yes. But that makes me wonder if I made things too complicated and could have avoided building lisp.dll. The native Windows build of clisp creates a lisp.def file, containing the symbols of lisp.exe, and it just

Re: Question about clisp version naming

On 3/17/2015 8:54 PM, Ken Brown wrote: On 3/17/2015 8:17 PM, Jon TURNEY wrote: On 17/03/2015 22:40, Ken Brown wrote: Yes. But that makes me wonder if I made things too complicated and could have avoided building lisp.dll. The native Windows build of clisp creates a lisp.def file, containing

Re: Question about clisp version naming

On Tue, 2015-03-17 at 21:09 -0400, Ken Brown wrote: On 3/17/2015 8:54 PM, Ken Brown wrote: It didn't occur to me to check the syntax of the def file, although it should have (see below). The one produced by the build (before I changed the approach) starts like this: EXPORTS IMPORTS

Re: Question about clisp version naming

On 3/17/2015 5:40 PM, Yaakov Selkowitz wrote: On Tue, 2015-03-17 at 17:15 -0400, Ken Brown wrote: On 3/17/2015 3:20 PM, Achim Gratz wrote: Ken Brown writes: Great. Thanks for testing. There's probably no reason for me to upload a new clisp package right now (unless it would help you). But

Re: Question about clisp version naming

On 17/03/2015 22:40, Ken Brown wrote: Yes. But that makes me wonder if I made things too complicated and could have avoided building lisp.dll. The native Windows build of clisp creates a lisp.def file, containing the symbols of lisp.exe, and it just adds lisp.def to the gcc command line when

Re: Question about clisp version naming

Ken Brown writes: Great. Thanks for testing. There's probably no reason for me to upload a new clisp package right now (unless it would help you). But I'll give you a heads up when I'm ready to do that. I've now drilled to the bottom of what I had assumed were build/package problems… it

Re: Question about clisp version naming

Ken Brown writes: How does the lisp.exe in clisp relate to the one that would be in maxima-exec-clisp? Achim will have to answer this one. I don't really know either. The executable dump is provided by clisp and you can name the resulting exe any which way you want. For maxima, it's

Re: Question about clisp version naming

On 3/16/2015 4:07 PM, Achim Gratz wrote: Yaakov Selkowitz writes: Is there an issue with stripping clisp executables? Yes, with the executable dumps. Is there a magic number we can use to detect these automatically? File identifies them as plain executables. CLisp knows which runtime

<    1   2   3   4   5   6   7   8   9   10   >