Dave Korn writes:
> On 20/04/2010 20:28, Paul Bibbings wrote:
>
>> (BTW. I'm guessing by "That'd be my fault" that you're working on gcc
>> upstream?)
>
> I certainly am; my long-term goal is a) to synchronize upstream and
> downstream so that in the end there are no cygwin-specific patches ne
On 2010-04-20 18:27, Dave Korn wrote:
On 19/04/2010 20:44, Jason Tishler wrote:
2. Yaakov recently created a libffi patch that I haven't had a chance to
test yet.
Please CC me into this discussion. I've put a lot of work into fixing
libffi in GCC, and then porting the patches to upstream
On 20/04/2010 20:28, Paul Bibbings wrote:
> (BTW. I'm guessing by "That'd be my fault" that you're working on gcc
> upstream?)
I certainly am; my long-term goal is a) to synchronize upstream and
downstream so that in the end there are no cygwin-specific patches needed and
anyone can just build
On 20/04/2010 15:06, Csaba Raduly wrote:
> On Tue, Apr 20, 2010 at 2:30 PM, Dave Korn wrote:
>> On 19/04/2010 22:16, Martin Ettl wrote:
>>> I used cppcheck
>>> [../machine/mips/strncpy.c:205]
>> Uhh, why is it telling us about the MIPS-only version of strncpy in newlib
>> that we don't even compi
On 19/04/2010 20:44, Jason Tishler wrote:
> 2. Yaakov recently created a libffi patch that I haven't had a chance to
> test yet.
Please CC me into this discussion. I've put a lot of work into fixing
libffi in GCC, and then porting the patches to upstream libffi; I'd like to
know if there's any
On 4/20/2010 6:15 PM, Tom Schutter wrote:
On Tue 2010-04-20 15:57, Jeremy Bopp wrote:
On 4/20/2010 3:52 PM, Tom Schutter wrote:
I have a machine where cron worked in 1.7.1, but now fails after an
upgrade to 1.7.5. Using strace, I have determined that lsaauth
succeeded before, but it now fails.
On Tue 2010-04-20 15:57, Jeremy Bopp wrote:
> On 4/20/2010 3:52 PM, Tom Schutter wrote:
> > I have a machine where cron worked in 1.7.1, but now fails after an
> > upgrade to 1.7.5. Using strace, I have determined that lsaauth
> > succeeded before, but it now fails.
>
> Did you remember to re-run
On 4/20/2010 9:00 AM, Matt wrote:
Hi, the info here will be vague since I haven't done too much debugging
yet, but I was wondering if anyone has been experiencing X server
crashes since around the time of the jump to Cygwin 1.7? It happens to
me maybe once a week under daily usage. /var/log/XWin
On 4/20/2010 9:38 AM, Yuval Emek wrote:
When invoking a cygwin bash shell window, I'm getting the following
message:
***message begins***
Your group is currently "mkgroup". This indicates that neither
your gid nor your pgsid (primary group associated with your SID)
is in /etc/group.
The /etc/gr
http://cygwin.com/ml/cygwin-announce/2010-04/msg00021.html
In particular,
==
NOTE NOTE NOTE NOTE NOTE NOTE NOTE NOTE NOTE NOTE NOTE NOTE NOTE NOTE
NOTE
Cygwin 1.7.1 or earlier users of LSA authentication using the cyglsa.dll
Does cyglsa attempt to deal with nested group membership? If group B
is a member of group A, and I am a member of group B, will group A
appear in the "groups" command output?
--
Tom Schutter
First American Spatial Solutions
303-440-7272 x6822
512-977-6822
--
Problem reports: http://cygwin
On 4/20/2010 3:52 PM, Tom Schutter wrote:
> I have a machine where cron worked in 1.7.1, but now fails after an
> upgrade to 1.7.5. Using strace, I have determined that lsaauth
> succeeded before, but it now fails.
Did you remember to re-run cyglsa-config as mentioned in the Cygwin DLL
release an
I have a machine where cron worked in 1.7.1, but now fails after an
upgrade to 1.7.5. Using strace, I have determined that lsaauth
succeeded before, but it now fails.
This is the strace output from the Cygwin 1.7.1 cron:
50 43500986 [main] cron 2092 cygsidlist::debug_print: -- ende sidlist ---
Dave Korn writes:
> On 17/04/2010 21:32, Paul Bibbings wrote:
>
>> The .dlls in question are:
>>
>> 21:10:29 Paul bibbi...@jijou
>> ~ $ls -l /opt/gcc-4.5.0/bin | grep dll
>> -rwxr-xr-x 1 ... 437743 Apr 15 09:08 cyggcc_s-1.dll
>> -rwxr-xr-x 1 ... 271146 Apr 15 09:08 cyggomp-1.dl
On Wed, 14 Apr 2010, Yutaka Amanai wrote:
Greetings, Yutaka,
On Cygwin, zsh forces stdin to be text-mode. By this, some commands
don't work correctly on zsh. For example, when you encode stdin with
base64 on zsh, there is a possibility that base64 produces an incorrect
result.
The text-mode "
The approach described in my earlier email [1] works with the latest
(openssh-5.5p1-1) release with a minor update.
You have to modify step 4 to include the new roaming code:
4) > gcc -Wl,--enable-auto-import,--enable-stdcall-fixup -o ssh.exe ssh.o
readconf.o clientloop.o sshtty.o sshconnect.o
On Tue, Apr 20, 2010 at 09:19:28AM +0300, Yuval Emek wrote:
>On Mon, Apr 19, 2010 at 20:48, Christopher Faylor wrote:
>> On Mon, Apr 19, 2010 at 10:48:18AM -0400, Larry Hall (Cygwin) wrote:
>>>On 4/19/2010 7:44 AM, Yuval Emek wrote:
On Mon, Apr 19, 2010 at 09:32, Christopher Faylor
?wrot
On Tue, Apr 20, 2010 at 2:30 PM, Dave Korn wrote:
> On 19/04/2010 22:16, Martin Ettl wrote:
>> I used cppcheck
>> [../machine/mips/strncpy.c:205]
>
> Uhh, why is it telling us about the MIPS-only version of strncpy in newlib
> that we don't even compile in?
>
AIUI, that's because cppcheck tries
Is it possible that this problem is somehow related to another problem
I'm experiencing, reported in
http://cygwin.com/ml/cygwin/2010-04/msg00797.html ?
On Tue, Apr 20, 2010 at 09:19, Yuval Emek wrote:
> On Mon, Apr 19, 2010 at 20:48, Christopher Faylor wrote:
>> On Mon, Apr 19, 2010 at 10:48:18A
When invoking a cygwin bash shell window, I'm getting the following message:
***message begins***
Your group is currently "mkgroup". This indicates that neither
your gid nor your pgsid (primary group associated with your SID)
is in /etc/group.
The /etc/group (and possibly /etc/passwd) files shou
Hi, the info here will be vague since I haven't done too much debugging
yet, but I was wondering if anyone has been experiencing X server
crashes since around the time of the jump to Cygwin 1.7? It happens to
me maybe once a week under daily usage. /var/log/XWin.0.log says only:
2010-04-20 08:2
On 19/04/2010 22:16, Martin Ettl wrote:
> Hello,
>
> you ever run a static code analysis tool on cygwin sources. I have done
> that! I used cppcheck
> (http://sourceforge.net/apps/mediawiki/cppcheck/index.php?title=Main_Page)
> and got the following SEVERE warning messages:
Now you know why peo
On 17/04/2010 21:32, Paul Bibbings wrote:
> The .dlls in question are:
>
> 21:10:29 Paul bibbi...@jijou
> ~ $ls -l /opt/gcc-4.5.0/bin | grep dll
> -rwxr-xr-x 1 ... 437743 Apr 15 09:08 cyggcc_s-1.dll
> -rwxr-xr-x 1 ... 271146 Apr 15 09:08 cyggomp-1.dll
> -rwxr-xr-x 1 ... 55
On Apr 15 17:01, Corinna Vinschen wrote:
> On Apr 15 10:54, Christopher Faylor wrote:
> > On Thu, Apr 15, 2010 at 10:29:24AM +0200, Corinna Vinschen wrote:
> > >On Apr 15 09:44, Rurik Christiansen wrote:
> > >> Hi,
> > >>
> > >> Is there a way to disable the stackdump ? ('ulimit -c 0' doesn't seem
On Apr 19 18:34, Charles Wilson wrote:
> On 4/19/2010 9:49 AM, Corinna Vinschen wrote:
> > any chance we can get a new tcp_wrappers package? The fact that the
> > host.allow file disables sshd access by default due to the rule order
> > in that file is a bit unnerving when trying to debug connecti
On Apr 19 18:52, risin...@nationwide.com wrote:
> 2) Once the console window is open, enter the command "stty erase ^?"
> (this is the incorrect character value (0x7f) that the backspace key is
> now sending in the console window - it should be sending ^H (0x08) like it
> has for decades in ever
Hi there,
On Tue, 19 Apr 2010 Charles Wilson wrote:
> On 4/19/2010 9:49 AM, Corinna Vinschen wrote:
> > any chance we can get a new tcp_wrappers package? ...
>
> Err... Oops.
:):):):):):):):):):):):):):)
> ... Has something broken your local DNS ...
http://groups.google.com/group/comp.protocol
27 matches
Mail list logo
