Achim Gratz nexgo.de> writes:
> I did that (just for my account) and then the sshd service wouldn't
> start. I'll have a look at that tomorrow.
The sshd complained that it didn't like the ownership or permissions on
/var/empty. Both looked OK however, so I ended up deleting the services and
use
Hi,
I’m a student in UCLA. I want to infall OpenMPI on Cygwin64. Do you have a
tutorial webpage for that?
Thank you.
Look forward to your reply.
Best wishes,
Yue Guan
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: h
On 6/20/2014 10:32 AM, Eli Zaretskii wrote:
Date: Fri, 20 Jun 2014 15:27:14 +0100
From: Ken Brown
Why did you need to step through the Glib code? AFAIU, the file
monitor did trigger, so what I would first look at is the data it
delivers back to Emacs, not how the monitor works internally. Did
This is a followup to https://cygwin.com/ml/cygwin/2014-06/msg00324.html, from
which I extracted the following test case:
$ cat gfile-test.c
#include
#include
void
gfile_add_watch (const char *file)
{
GFile *gfile = g_file_new_for_path (file);
GFileMonitor *monitor;
GFileMonitorFlags gfl
Hi,
> The Cygwin project has too many mailing lists.
+1
> I see real value in only 3 lists:
>
> 1. User discussions
> 2. Development of Cygwin-the-project (broader than the DLL)
> 3. Talk
-1
just unify only 1 ML is simple.
the cygwin ML flow looks not so massive.
we know using well compos
On Jun 25 22:44, Denis Excoffier wrote:
> On 2014-06-25 12:15, Corinna Vinschen wrote:
> >> Stay tuned. I'm rewriting the LDAP access code to perform all critical
> >> LDAP calls in interruptible threads. The Windows LDAP calls don't
> >> provide any kind of synchronization, only timeouts. I hop
Hello,
Is DllMain() supposed to work with Cygwin and gcc?
If so, could someone share a simple, working example?
I have a relatively simple example that works with mingw, but does not work
with gcc. I could post the example if that is easier.
% uname -a
CYGWIN_NT-6.1-WOW64 CDD-NB01 1.7.30(0.27
Sergii,
kudos, I am really impressed by your usage of cygwin.
I am redirecting your question to the cygwin list
as it is more likely to find there an answer to process
limit on cygwin 64.
Regards
Marco
Original Message
Subject:[OMPI users] Fwd: openmpi linking proble
On 2014-06-25 12:15, Corinna Vinschen wrote:
>> Stay tuned. I'm rewriting the LDAP access code to perform all critical
>> LDAP calls in interruptible threads. The Windows LDAP calls don't
>> provide any kind of synchronization, only timeouts. I hoped to get away
>> with short timeouts but it see
Corinna Vinschen writes:
> Just run cygserver and every user can do it, otherwise enter the
> password for the user with `passwd -R ' as admin.
I did that (just for my account) and then the sshd service wouldn't
start. I'll have a look at that tomorrow.
Regards,
Achim.
--
+<[Q+ Matrix-12 WAVE#
On Jun 25 20:06, Achim Gratz wrote:
> Corinna Vinschen writes:
> > You read my preliminary doc, I hope? I attached it again, for
> > completeness. But, here's what happens:
>
> I guess I read it at one time, but not specifically today. :-)
>
> > If you're in a domain, and the sshd user account
Nellis, Kenneth writes:
> Now, I want to share my Cygwin $HOME directory between the two
> environments. I already keep my binaries in $HOME/bin/$(arch)
> and $HOME/lib/$(arch), so they are covered. And, of course
> /usr/bin has to continue to point to the separate Cygwin
> environments.
Mak
Corinna Vinschen writes:
> You read my preliminary doc, I hope? I attached it again, for
> completeness. But, here's what happens:
I guess I read it at one time, but not specifically today. :-)
> If you're in a domain, and the sshd user account is local, the local
> sshd account will be prefixe
-Original Message-
From: Christopher Faylor 2-bit and 64-bit in a shared environment
On Wed, Jun 25, 2014 at 01:04:24PM +, Nellis, Kenneth wrote:
>I have happily been using 32-bit Cygwin for years, developing
>shell/perl scripts and C/C++ software. Some of the users that I support
>h
On Wed, Jun 25, 2014 at 01:04:24PM +, Nellis, Kenneth wrote:
>I have happily been using 32-bit Cygwin for years, developing
>shell/perl scripts and C/C++ software. Some of the users that
>I support have upgraded to 64-bit Cygwin, and so my 32-bit C/C++
>binaries no longer work for them. That
On Jun 25 12:34, Achim Gratz wrote:
> I've just managed to set up a working sshd on a Cygwin snapshot with LDAP
> integration. The setup scripts required quite a few modifications to deal
> properly with the way local accounts and groups are now named. I've had to
> reinstate files for passwd to
I have happily been using 32-bit Cygwin for years, developing
shell/perl scripts and C/C++ software. Some of the users that
I support have upgraded to 64-bit Cygwin, and so my 32-bit C/C++
binaries no longer work for them. That has forced me to adopt
64-bit Cygwin, which I've installed on the s
New version 1.4.17-1 of
gnupg
is available in the Cygwin distribution:
CHANGES
* Avoid DoS due to garbled compressed data packets.
* Screen keyserver reponses to avoid import of unwanted keys by rogue
servers.
* Add hash algorithms to the "sig" records of the colon output.
*
I've just managed to set up a working sshd on a Cygwin snapshot with LDAP
integration. The setup scripts required quite a few modifications to deal
properly with the way local accounts and groups are now named. I've had to
reinstate files for passwd to record an "sshd" there as otherwise the
serv
On Jun 24 17:58, Corinna Vinschen wrote:
> On Jun 23 22:38, Denis Excoffier wrote:
> > On 2014-06-23 11:09, Corinna Vinschen wrote:
> > > On Jun 19 19:53, Denis Excoffier wrote:
> > >
> > > Do you really *want* to enumerate 500K users when accessing the DCs
> > > remote over a slow DSL line? Isn'
On 25/06/2014 11:21, Corinna Vinschen wrote:
On Jun 25 11:00, Marco Atzeri wrote:
On 25/06/2014 10:12, Corinna Vinschen wrote:
Hi folks,
Did you read the comments in the 2nd link I sent with my announcement?
There are more unhappy devs...
I read. Very stupid broken behavior and also very d
On Jun 25 11:00, Marco Atzeri wrote:
>
> On 25/06/2014 10:12, Corinna Vinschen wrote:
> >Hi folks,
> >
> >
> >I just uploaded windows-default-manifest-6.3-1.
> >
> >This new package contains nothing but a default application
> >compatibility manifest, which gets linked in by GCC by default, and
>
On 25/06/2014 10:12, Corinna Vinschen wrote:
Hi folks,
I just uploaded windows-default-manifest-6.3-1.
This new package contains nothing but a default application
compatibility manifest, which gets linked in by GCC by default, and
which is supposed to claim compatibility with the latest Windo
Hi folks,
I just uploaded windows-default-manifest-6.3-1.
This new package contains nothing but a default application
compatibility manifest, which gets linked in by GCC by default, and
which is supposed to claim compatibility with the latest Windows
versions available at the time.
Adding such
24 matches
Mail list logo
