On Aug 13 19:53, Corinna Vinschen wrote:
> On Aug 13 18:33, Corinna Vinschen wrote:
> > On Aug 12 20:59, Achim Gratz wrote:
> > > Corinna Vinschen writes:
> > > >> I think so, but there are likely some corner cases. But I think that
> > > >> had been proposed and shot down already, so I was trying
Hi Fenn,
On Aug 13 11:29, Fenn wrote:
> I just updated my cygwin and I am getting a segfault when I do a "ls
> -l" on my c drive at the root.
>
> I don't get this if i do a "ls -l" in my home directory.
>
> I am including details from strace and info on my install (see below
> and attached).
>
Corinna Vinschen cygwin.com> writes:
> I checked in the change we were talking about. Please give the latest
> snapshot from https://cygwin.com/snapshots/ a try.
I've had a quick look and things look good. I'll have to roll out the
snapshot to our server and revert the script changes, but it se
Marco, please see below in terms of L3 cache info. Thanks,
On Aug 14 10:56, Achim Gratz wrote:
> Corinna Vinschen cygwin.com> writes:
> > I checked in the change we were talking about. Please give the latest
> > snapshot from https://cygwin.com/snapshots/ a try.
>
> I've had a quick look and t
I hope, not to follow a red herring again, but found some interesting.
I did a fresh cygwin installation again but made an error not to copy my old
.bashrc and .bashrc-profile files.
Within .bashrc I defined an alias for ls (ls='ls --color=auto
--show-control-chars').
I noticed, that the time lag
On Aug 10 18:01, Corinna Vinschen wrote:
> On Aug 10 05:00, mku wrote:
> > Oh, sorry. I did a fresh 2.2 install to avoid side effects from my previous
> > updated one and forgot to modify the nsswitch.conf. After correcting it, the
> > result now is the same from the time aspect but loading of the
Hi.
I am trying to find out Cygwin version at run time.
I have noticed that there is `cygwin_internal (CW_GETVERSIONINFO)` API
for this. However, it seems that the `cygwin_version_info` structure
this call is supposed to fill in is not publicly available and is only
declared internally in `winsup
On 8/14/2015 9:56 AM, Václav Haisman wrote:
Hi.
I am trying to find out Cygwin version at run time.
I have noticed that there is `cygwin_internal (CW_GETVERSIONINFO)` API
for this. However, it seems that the `cygwin_version_info` structure
this call is supposed to fill in is not publicly availa
On 14 August 2015 at 16:11, Eliot Moss wrote:
> On 8/14/2015 9:56 AM, Václav Haisman wrote:
>>
>> Hi.
>>
>> I am trying to find out Cygwin version at run time.
>>
>> I have noticed that there is `cygwin_internal (CW_GETVERSIONINFO)` API
>> for this. However, it seems that the `cygwin_version_info`
On Aug 14 17:08, Václav Haisman wrote:
> On 14 August 2015 at 16:11, Eliot Moss wrote:
> > On 8/14/2015 9:56 AM, Václav Haisman wrote:
> >>
> >> Hi.
> >>
> >> I am trying to find out Cygwin version at run time.
> >>
> >> I have noticed that there is `cygwin_internal (CW_GETVERSIONINFO)` API
> >> f
On Aug 14 06:49, mku wrote:
> I hope, not to follow a red herring again, but found some interesting.
>
> I did a fresh cygwin installation again but made an error not to copy my old
> .bashrc and .bashrc-profile files.
> Within .bashrc I defined an alias for ls (ls='ls --color=auto
> --show-contro
On 2015-08-13 11:33, Yaakov Selkowitz wrote:
> On Thu, 2015-08-13 at 10:46 -0700, AC wrote:
>> On 2015-08-13 10:06, Jon TURNEY wrote:
>>> If your /etc/X11/xinit/startxwinrc mentions fbpanel, you don't have
>>> the latest version (see [1]), so maybe try updating or reinstalling
>>> the xinit packa
Corinna Vinschen writes:
> Cool, thanks for your quick feedback.
Thanks for the snapshot!
> We should just be aware that this is ultimately a kludge. I think I now
> finally understand what would have to be done to get a generic solution
> which results in correct POSIX permission evaluation for
On Aug 14 20:25, Achim Gratz wrote:
> Corinna Vinschen writes:
> > Btw., can you please also check /proc/cpuinfo?
>
> Yes, I have both AMD and Intel machines I can test this with.
>
> > As discussed, Cygwin's emulation fell short on L3 cache info. I now
> > added code to fetch L3 cache info as w
Achim,
let's hope that your update helps. In the meantime, using run version 1.3.3-1:
1) Issuing
C:\cygwin64\bin\run.exe --quote /usr/bin/bash.exe -l -c "cd; /usr/bin/startxwin"
from cmd does not start an Xwin server; no error message is produced.
2) Issuing
run.exe --quote /usr/bin/bash.exe -l
On Aug 14 17:48, Corinna Vinschen wrote:
> On Aug 14 06:49, mku wrote:
> > I hope, not to follow a red herring again, but found some interesting.
> >
> > I did a fresh cygwin installation again but made an error not to copy my old
> > .bashrc and .bashrc-profile files.
> > Within .bashrc I defined
Greetings, AC!
>>> Interesting, I'm using the global startxwinrc and my xinit package is
>>> already 1.3.4-9 yet fbpanel is still in there and there's no mention
>>> of xwin-xdg-menu in it yet I do have xwin-xdg-menu installed
>>> (20150708-1).
>>> I do not have a custom startxwinrc in my home
Jaakov Jaakov writes:
> 1) Issuing
> C:\cygwin64\bin\run.exe --quote /usr/bin/bash.exe -l -c "cd;
> /usr/bin/startxwin"
> from cmd does not start an Xwin server; no error message is produced.
You don't get a stackdump?
> 2) Issuing run.exe --quote /usr/bin/bash.exe -l -c "cd; /usr/bin/startxwin"
Andrey Repin writes:
>> Yes, it is fixed. It had been quite some time since I edited the file.
>> I'm more accustomed to package managers warning me about customized
>> files when they detect them.
>
> Cygwin's setup routine could use some love, there's no denying of that.
> However, Someone Has
19 matches
Mail list logo
