On 20.05.2019 21:49, Bob Cochran wrote:
> On 5/20/19 10:27 AM, Jose Isaias Cabrera wrote:
>> Erik Soderquist, on Monday, May 20, 2019 10:16 AM, wrote...
>>> On Sun, May 19, 2019 at 3:44 PM Bob Cochran wrote:
>>>
"Cygwin? this is probably still functional, but now can be considered a
(pre
On 19.05.2019 22:43, Bob Cochran wrote:
> And, I received the
> following feedback:
>
> "Cygwin? this is probably still functional, but now can be considered a
> (pre)historic solution."
>
> I personally have been using Cygwin for many years and have come to
> trust it for interfacing to Linux
On 09.05.2019 17:44, Bill Stewart wrote:
> On Thu, May 9, 2019 at 6:20 AM Andrey Repin wrote:
>
>> Again, there's simply no equivalent of "god user" from *NIX in Windows
>> permissions system.
>
> That's not really correct. An account that is a member of the
> Administrators local group (localize
On 09.05.2019 15:09, Andrey Repin wrote:
> Greetings, Henning!
>
>> And the group "None". I found it mentioned in ntsec. Would it be
>> possible to create a group "root" in Windows which gives it's
>> members the same power as the group Administrators? And why "None"
>> and not "Administrators"?
>
On 21.04.2019 14:45, Matt D. wrote:
>
> I had the same problem while trying to tar and untar:
>
> tar: aosp/source/system/vold/.git/shallow: Cannot create symlink to
> ‘../../../.repo/projects/system/vold.git/shallow’: No such file or directory
My current workaround for *this* particular proble
On 03.04.2019 15:16, LRN wrote:
> On 05.03.2019 17:23, LRN wrote:
>> On 05.03.2019 17:07, E. Madison Bray wrote:
>>>
>>> If they're clean, worthwhile patches then I absolutely think you
>>> should get them integrated upstream if at all possible--that&#
On 17.04.2019 20:04, Achim Gratz wrote:
> The inofficial protocol for reaching out to a package maintainer is to
> put "[Attn. Maintainer] " in the subject of your mail. Said
> maintainer may be currently unavailable or busy with other stuff, so
> please give her/him ample time to respond, i.e. at
On 17.04.2019 18:30, Brian Inglis wrote:
> On 2019-04-17 02:06, LRN wrote:
>> I've been sending emails to this list for a couple of weeks now, and no
>> one replies. Do these messages come through at all?
>
> The best way to initiate discussion may be replying to a previ
Subj. I've been sending emails to this list for a couple of weeks now, and no
one replies. Do these messages come through at all? I know for a fact that the
messages do end up in the ML archives, so they reach at least *some* places.
In case this message is being read by anyone: i'm looking either
On 03.04.2019 15:16, LRN wrote:
> On 05.03.2019 17:23, LRN wrote:
>> On 05.03.2019 17:07, E. Madison Bray wrote:
>>>
>>> If they're clean, worthwhile patches then I absolutely think you
>>> should get them integrated upstream if at all possible--that&#
On 05.03.2019 17:23, LRN wrote:
> On 05.03.2019 17:07, E. Madison Bray wrote:
>>
>> If they're clean, worthwhile patches then I absolutely think you
>> should get them integrated upstream if at all possible--that's almost
>> always preferable.
>
>
On 19.03.2019 23:42, Corinna Vinschen wrote:
> On Mar 19 22:28, LRN wrote:
>> The testcase is attached. Running it with Cygwin-i386 leads to a crash.
>
> I pushed a patch and uploaded new developer snapshots to
> https://cygwin.com/snapshots/
>
> Pleas give them a
The testcase is attached. Running it with Cygwin-i386 leads to a crash. My
guess is that the implementation is not POSIX-conformant and tries to
dereference the first argument (NULL), even though the third argument is 0.
Tested with Cygwin-3.0.4.
#include
#include
#include
int
main ()
{
wcha
ASS[0] is documented for Linux (and for POSIX) but i'm failing to find any
information on how this applies to Cygwin. I assume, since there are no "real"
signals on Cygwin, that it's not possible for a signal handler to break the
state of some function that happened to be executed when the signal h
On 19.03.2019 15:23, Andrey Repin wrote:
> It's not a secret that in earlier Windows versions members of Administrators
> group require elevated shell to create symlinks.
> Win10 is supposed to be easier, but all I've found was pointing to some
> obscure "developer mode".
Newer Windows 10 added a
On 05.03.2019 17:07, E. Madison Bray wrote:
> On Sun, Mar 3, 2019 at 11:07 AM LRN wrote:
>>
>> Looking at cygwin glib source package, i see a lot of downstream patches
>> applied to glib over the years (there are no dates, but the versions range
>> from
>> 2.34.3
Looking at cygwin glib source package, i see a lot of downstream patches
applied to glib over the years (there are no dates, but the versions range from
2.34.3 to 2.50 - that might be as early as 2012 and as late as 2017) to make it
work correctly on cygwin.
Why are these not upstream (considering
On 24.02.2019 3:29, Steven Penny wrote:
> I noticed that "python36" requires "binutils". Further, I noticed this
> dependency chain:
>
> python36 > libuuid-devel > pkg-config > libglib2.0_0
>
> "binutils" is 5,863,216 bytes and "libglib" is 3,044,044 bytes. I am of the
> opinion we should not
On 17.02.2019 14:11, Franz Fehringer wrote:
> Hi all (half off topic),
>
> I have installed (on a Windows 10 1809 system) both Cygwin and WSL (only
> the Windows component, no real Linux distribution yet).
> This scenario gives me a strange problem with antrun: With executable="bash"> i always ge
On 15.02.2019 2:41, Bill Stewart wrote:
> On Thu, Feb 14, 2019 at 4:32 PM Vince Rice wrote:
>
>> I didn't suggest everyone did. But people who want tilde expansion do,
>> because it's
>> the shell that is responsible for tilde expansion.
>> ...
>> No, it isn't "oddly" absent. As has been said rep
On 28.01.2019 17:02, LRN wrote:
> This[0] and this[1]. One header checks for atomic C/CXX extensions *and* for
> the presence of a C++ compiler, while the other only checks for extensions.
>
> The result is that the _Atomic() macro is *not* defined in cdefs.h when
> compiled wi
This[0] and this[1]. One header checks for atomic C/CXX extensions *and* for
the presence of a C++ compiler, while the other only checks for extensions.
The result is that the _Atomic() macro is *not* defined in cdefs.h when
compiled with C++, but the stdatomic.h atomic macros assume that it is, a
On 01.05.2015 16:46, John D. Hendrickson wrote:
> i've been findign allot of microsoft hacks in Unix code
I had to re-read your message a few times to make any sense of it. I'll try to
sum it up as best as i can, please verify that no meaning was lost in the
process.
Your issue is with portable
On 30.04.2015 2:43, Michael DePaulo wrote:
> On Wed, Apr 29, 2015 at 4:06 PM, Corinna Vinschen wrote:
>> On Apr 29 19:01, Rich Eizenhoefer wrote:
>>> I'm the Program Manager at Microsoft for the updated Windows 10
>>> console. I searched the Cygwin FAQ and mailing list archives for
>>> issues relat
On 11.04.2015 0:55, Frank Fesevur wrote:
> 2015-04-10 22:38 GMT+02:00 Andrew DeFaria:
>>> $ man 5 crontab
>>>
>>> See @reboot
>>>
>>> Never used it but I assume it will run after cron service is started.
>>
>> I haven't used it either, but I saw it there. Makes you wonder what would
>> happen if yo
On 04.04.2015 21:52, Andrey Repin wrote:
> Greetings, Eric Pement!
>
>> Follow-up question for Corinna or anyone who might know the answer:
>
On Apr 1 03:26, Robert Miles wrote:
>> Can I move the entire Cygwin and Cygwin64 directory trees to one
>> of the nearly empty drives, withou
On 17.03.2015 13:51, Corinna Vinschen wrote:
> On Mar 17 03:34, LRN wrote:
>> How to reproduce:
>> 1) create a shell script (say, /usr/bin/shellscript) containing this:
>>
>> #!/bin/sh
>> echo ${0##*/}
>>
>> 2) create a symlink (say, /usr/bin/asymlink)
How to reproduce:
1) create a shell script (say, /usr/bin/shellscript) containing this:
#!/bin/sh
echo ${0##*/}
2) create a symlink (say, /usr/bin/asymlink) that points to shellscript
3) create a perl script (say, /usr/bin/perlscript) containing this:
#! /usr/bin/perl -w
system '/usr/bin/asymli
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 14.05.2014 19:25, Christopher Faylor wrote:
> On Wed, May 14, 2014 at 04:10:36PM +0100, Henry S. Thompson wrote:
>> I'm trying to debug a problem with xemacs that involves the child
>> process forked when you execute M-x shell.
>>
>> None of the m
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 17.06.2013 16:50, Corinna Vinschen wrote:
> On Jun 17 08:43, Алексей Павлов wrote:
>> This simple example illustrate problem with using native symlinks.
>>
>> $ export CYGWIN=winsymlinks:nativestrict
>>
>> $ mkdir bld && mkdir source && touch source
30 matches
Mail list logo
