Recent config.guess still detects 64bit Cygwin as x86_64-unknown-cygwin.
This should probably be changed (upstream) to be consistent with
i686-pc-cygwin.
$ uname -srvmo
CYGWIN_NT-6.1 1.7.18(0.263/5/3) 2013-04-10 14:35 x86_64 Cygwin
$ cygcheck -f /usr/share/automake-1.13/config.guess
automake1.
Thanks all - it is done
> Greetings, Duncan Roe!
>
> >> > Thanks Dave - removing the old cygwin dlls from C:\WINDOWS fixed
> >> > gcc
> > &
>> > > alternatives.
> >> > I put them there because I like to have the odd cygwin utility
>> > > available to CMD.EXE.
>> > >
>> > > May put them back - b
Greetings, Duncan Roe!
>> > Thanks Dave - removing the old cygwin dlls from C:\WINDOWS fixed gcc
> &
>> > alternatives.
>> > I put them there because I like to have the odd cygwin utility
>> > available to CMD.EXE.
>> >
>> > May put them back - but will take more care with them in future,
>> >
Greetings, Steve Kargl!
>> >> * gfortran's example for random_see should be change to not use
>> >> system_clock for the random seed.
>> >
>> >I disagree. The example is just that a short example
>> >that demonstrates how to use random_seed. Anyone using
>> >that example in his/her code without
On 4/11/2013 10:27 PM, Larry Hall (Cygwin Developers) wrote:
On 4/11/2013 8:05 PM, Duncan Roe wrote:
Hi Casba,
On Thu, Apr 11, 2013 at 8:08 AM, Duncan Roe wrote:
Thanks Dave - removing the old cygwin dlls from C:\WINDOWS fixed gcc
&
alternatives.
I put them there because I like to have the
On 4/11/2013 8:05 PM, Duncan Roe wrote:
Hi Casba,
On Thu, Apr 11, 2013 at 8:08 AM, Duncan Roe wrote:
Thanks Dave - removing the old cygwin dlls from C:\WINDOWS fixed gcc
&
alternatives.
I put them there because I like to have the odd cygwin utility
available to CMD.EXE.
May put them back -
I am sending the test case in the attachment.
In the attachment, you will find source code for two programs - udpbugserver
and udpbugclient. "make" will build them both. They work perfectly together in
Linux, FreeBSD and Solaris. But they fail in Cygwin.
Thanks
Oleg
>
> On Thu, Apr 11, 2013
Hi Casba,
> On Thu, Apr 11, 2013 at 8:08 AM, Duncan Roe wrote:
> > Thanks Dave - removing the old cygwin dlls from C:\WINDOWS fixed gcc
&
> > alternatives.
> > I put them there because I like to have the odd cygwin utility
> > available to CMD.EXE.
> >
> > May put them back - but will take more
On Fri, Apr 12, 2013 at 01:17:07AM +0200, Angelo Graziosi wrote:
> Steve Kargl wrote
>
> > My
> > disagreemnet is predicated on the stupidity of using a 10 line
> > example subroutine without actually inspecting what it does on
> > whatever OS that one chooses to use.
>
> It is just because one h
Steve Kargl wrote
My
disagreemnet is predicated on the stupidity of using a 10 line
example subroutine without actually inspecting what it does on
whatever OS that one chooses to use.
It is just because one has tested that code that these problems came to
light... :-)
Ciao,
Angelo.
--
Pr
On 11/04/2013 7:00 PM, Steve Kargl wrote:
On Thu, Apr 11, 2013 at 11:23:42PM +0100, N.M. Maclaren wrote:
On Apr 11 2013, Steve Kargl wrote:
On Thu, Apr 11, 2013 at 10:35:54PM +0200, Tobias Burnus wrote:
* gfortran's example for random_see should be change to not use
system_clock for the random
Steve Kargl wrote:
On Thu, Apr 11, 2013 at 10:35:54PM +0200, Tobias Burnus wrote:
* gfortran's example for random_see should be change to not use
system_clock for the random seed.
I disagree. The example is just that a short example
that demonstrates how to use random_seed. Anyone using
t
On Thu, Apr 11, 2013 at 11:23:42PM +0100, N.M. Maclaren wrote:
> On Apr 11 2013, Steve Kargl wrote:
> >On Thu, Apr 11, 2013 at 10:35:54PM +0200, Tobias Burnus wrote:
> >>
> >> * gfortran's example for random_see should be change to not use
> >> system_clock for the random seed.
> >
> >I disagree.
On Apr 11 2013, Steve Kargl wrote:
On Thu, Apr 11, 2013 at 10:35:54PM +0200, Tobias Burnus wrote:
* gfortran's example for random_see should be change to not use
system_clock for the random seed.
I disagree. The example is just that a short example
that demonstrates how to use random_seed.
On Thu, Apr 11, 2013 at 10:35:54PM +0200, Tobias Burnus wrote:
>
> * gfortran's example for random_see should be change to not use
> system_clock for the random seed.
>
I disagree. The example is just that a short example
that demonstrates how to use random_seed. Anyone using
that example in
I can write a simple test server and client programs and I'll post it here,=
in a few hours. Our existing code is just too large.
Thanks
Oleg
>
> On Thu, Apr 11, 2013 at 02:19:25PM -0700, Oleg Moskalenko wrote:
> >Hi All
> >
> >I found a non-standard behavior of UDP sockets in Cygwin. Normally
On Thu, Apr 11, 2013 at 02:19:25PM -0700, Oleg Moskalenko wrote:
>Hi All
>
>I found a non-standard behavior of UDP sockets in Cygwin. Normally, people =
>do not experience it, but the communication pattern that I am going to desc=
>ribe here is often used in DTLS (actually, this is virtually the
Hi All
I found a non-standard behavior of UDP sockets in Cygwin. Normally, people = do
not experience it, but the communication pattern that I am going to desc= ribe
here is often used in DTLS (actually, this is virtually the only way t= o make
OpenSSL working with DTLS on the server side), so
Here go:
3 3 [main] ls (3892) **
283 286 [main] ls (3892) Program name: C:\cygwin\bin\ls.exe
(windows pid 3892)
130 416 [main] ls (3892) OS version: Windows NT-6.2
115 531 [main] ls (3892) ***
On 4/11/2013 4:48 PM, Angelo Graziosi wrote:
Mum wrote:
This is obviously not
how the monotonic system clock is supposed to work, so that's a bug
in Cygwin.
I fixed that in CVS.
> Mum
Oh, thanks mum... I hope it will be fixed also in the next 1.7.18.. :)
Yeah, that's pretty much the way
Tobias Burnus:
b) Newlib is broken. For clock_gettime, CLOCK_MONOTONIC is not
implemented. But both CLOCK_MONOTONIC and even _POSIX_MONOTONIC_CLOCK
(with value 200112L) are defined. However, POSIX states: "If the
Monotonic Clock option is supported, all implementations shall support
a clock_id
Mum wrote:
This is obviously not
how the monotonic system clock is supposed to work, so that's a bug
in Cygwin.
I fixed that in CVS.
> Mum
Oh, thanks mum... I hope it will be fixed also in the next 1.7.18.. :)
Ciao,
Angelo.
PS. Corinna, your "Hi kiddies" has been irresistible...
--
Pro
On Apr 11 22:35, Tobias Burnus wrote:
> Corinna Vinschen wrote:
> >On Apr 11 21:13, Tobias Burnus wrote:
> >>Where is actually the source code of the clock_gettime, which Cygwin
> >>uses? I thought that it was newlib. But looking at
> >>http://sourceware.org/cgi-bin/cvsweb.cgi/src/newlib/libc/sys/l
Corinna Vinschen wrote:
On Apr 11 21:13, Tobias Burnus wrote:
Where is actually the source code of the clock_gettime, which Cygwin
uses? I thought that it was newlib. But looking at
http://sourceware.org/cgi-bin/cvsweb.cgi/src/newlib/libc/sys/linux/clock_gettime.c?cvsroot=src
the code should ret
On 12/06/2012 13:31, Warren Young wrote:
> PACKAGE DESCRIPTION
> ===
>
> Homepage: http://sourceforge.net/projects/expat/
> License : MIT-like
>
> Expat is a C library for parsing XML, originally created and maintained
> by James Clark, but since 2001 taken over by a loose group o
On 4/10/2013 4:47 AM, Jun Iriola wrote:
Hi,
I would like to seek your help on how to execute again the cron in my
pc. I've manage to configure and run the cron last week by reading the step by
step procedure and also by running cygwin as an Administrator.
That's not what your cygcheck output
On Apr 11 15:17, Jeff Avila wrote:
> Hi there,
>
> Using a combination of Cygwin 1.7.17 and Windows Server 2012. I put a
> samba share in the Cygwin /etc/fstab. I can log in as myself, and see
> the share/cd to it (I performed the cygwin install, and am a domain
> admin on the Windows machine).
>
On Apr 11 21:13, Tobias Burnus wrote:
> Corinna Vinschen wrote:
> >Works fine for me with the current Cygwin 1.7.17, and the upcoming
> >Cygwin 1.7.18:
> > if (!clock_gettime (CLOCK_MONOTONIC, &tp))
> > printf ("tv_sec = %ld, tv_nsec = %ld\n", tp.tv_sec, tp.tv_nsec);
> ...
> > tv_sec =
On Apr 11 21:09, Angelo Graziosi wrote:
> Hi mum [1],
:)
> Corinna Vinschen wrote:
>
> >Works fine for me with the current Cygwin 1.7.17, and the upcoming
> >Cygwin 1.7.18:
> >
> > $ cat > ct.c <
> At each run, your test case almost always starts with the same value:
>
> $ gcc -o ct ct.c
> [.
Hi there,
Using a combination of Cygwin 1.7.17 and Windows Server 2012. I put a
samba share in the Cygwin /etc/fstab. I can log in as myself, and see
the share/cd to it (I performed the cygwin install, and am a domain
admin on the Windows machine).
my issue arises when other users try to ssh into
Corinna Vinschen wrote:
Works fine for me with the current Cygwin 1.7.17, and the upcoming
Cygwin 1.7.18:
if (!clock_gettime (CLOCK_MONOTONIC, &tp))
printf ("tv_sec = %ld, tv_nsec = %ld\n", tp.tv_sec, tp.tv_nsec);
...
tv_sec = 0, tv_nsec = 29920
Where is actually the source cod
Hi mum [1],
Corinna Vinschen wrote:
Works fine for me with the current Cygwin 1.7.17, and the upcoming
Cygwin 1.7.18:
$ cat > ct.c <
At each run, your test case almost always starts with the same value:
$ gcc -o ct ct.c
$ ./ct
tv_sec = 0, tv_nsec = 2793
tv_sec = 0, tv_nsec = 89104
tv_
On Thu, Apr 11, 2013 at 01:43:24PM +0100, Dave Korn wrote:
>On 11/04/2013 00:58, Dave Korn wrote:
>
>> I would like to express my gratitude to JonY for stepping into the breach
>> caused by my absence from the Cygwin community and releasing the first test
>> version of GCC 4.7 series. He did a v
Hi,
When I try to list the contents of the snapshots using the "List"
links on the right, I get an internal server error 500 for the
recent ones.
Fails:
http://cygwin.com/snapshots/winsup-src-20130409.tar
Works:
http://cygwin.com/snapshots/winsup-src-20130309.tar
Please fix / advise,
Anton Lav
On Apr 11 15:37, Tobias Burnus wrote:
> Please CC your reply to fort...@gcc.gnu.org
Please don't CC me or cgf. We're subscribed to the Cygwin list anyway.
> Dear all,
>
> using clock_gettime with CLOCK_MONOTONIC fails on Cygwin; it always
> gives 0. That breaks code compiled with GCC's gfortran
Please CC your reply to fort...@gcc.gnu.org
Dear all,
using clock_gettime with CLOCK_MONOTONIC fails on Cygwin; it always
gives 0. That breaks code compiled with GCC's gfortran which uses
system_clock in libgfortran.
libgfortran uses CLOCK_MONOTONIC if defined and otherwise it falls back
to
On 11/04/2013 00:58, Dave Korn wrote:
> I would like to express my gratitude to JonY for stepping into the breach
> caused by my absence from the Cygwin community and releasing the first test
> version of GCC 4.7 series. He did a very difficult job and did it well and
> deserves the highest of
Christopher Faylor cygwin.com> writes:
> The latest snapshot has some more signal-handling restructuring.
> I'd appreciate it if people would check it out.
Looks good so far. I've had a compile that would pretty often lock up cmake
during the config phase so that it needed to be killed from task
On Apr 11 09:49, Csaba Raduly wrote:
> Hi Duncan,
>
> On Thu, Apr 11, 2013 at 8:08 AM, Duncan Roe wrote:
> > Thanks Dave - removing the old cygwin dlls from C:\WINDOWS fixed gcc &
> > alternatives.
> > I put them there because I like to have the odd cygwin utility available
> > to CMD.EXE.
> >
> >
Hi Duncan,
On Thu, Apr 11, 2013 at 8:08 AM, Duncan Roe wrote:
> Thanks Dave - removing the old cygwin dlls from C:\WINDOWS fixed gcc &
> alternatives.
> I put them there because I like to have the odd cygwin utility available
> to CMD.EXE.
>
> May put them back - but will take more care with them
40 matches
Mail list logo
