> No, that looks like I'd expect it to. You need to look at the process
> map when you have fork problems, since the problem seems to be
> intermittent.
How so? Something like
for i in `seq 1000`; do
cat /proc/self/maps > procselfmaps_`date +%s.%N`.txt;
done &
before running the problematic c
Tony Kelman wrote:
You've got two different cygwin1.dll somewhere on your PATH.
For more information, I have one cygwin64 installation on C:, one
cygwin32 installation on E:, and they're never both on my path at
the same time. I'm not sure where that orphan registry entry that was
showing up in
Tony Kelman writes:
>> Something occupies the heap area for Cygwin, based on the low address.
>> What does /proc/self/maps tell you?
>
> $ cat /proc/self/maps
[…]
>
> Hopefully you know what you're looking at there. Anything meaningful in that?
No, that looks like I'd expect it to. You need to lo
Wayne Porter wrote:
This is how it is currently set up. I can log in to the server via ssh
or use the current method, which is to map the network share using my
account credentials that they have set up for me. This works just fine
in Windows and for the most part in Cygwin. I can read/write from
>> Still a problem in 14936. Folks, this could be very bad. Anyone at all
>> testing the insider builds, or are we going to be blindsided when an
>> update goes out to everyone that breaks cygwin?
>
> How about you start with a sane PATH that doesn#t contain all the
> Windows stuff? Set a system v
On Sun, Oct 02, 2016 at 04:43:42PM -0700, Linda Walsh wrote:
> Wayne Porter wrote:
> > > Essentially you have a bunch of users on different machines that aren't
> > > sharing their files under any common (or shared) security authority
> > > (like a single domain). Until you persuade the owners o
On Sun, Oct 02, 2016 at 04:35:21PM -0700, Linda Walsh wrote:
> Wayne Porter wrote:
> > The server that the W: drive is mapped on is not using domain accounts. As
> > far as I know,
> > all Linux servers we have are running local accounts. Is there something I
> > can set in
> > my local /etc/pass
Wayne Porter wrote:
Essentially you have a bunch of users on different machines that aren't
sharing their files under any common (or shared) security authority
(like a single domain). Until you persuade the owners of those linux machines
to move the linux machines under a common security
Wayne Porter wrote:
The server that the W: drive is mapped on is not using domain accounts. As far
as I know,
all Linux servers we have are running local accounts. Is there something I can
set in
my local /etc/passwd to convince Cygwin to map it to my user account?
---
Let me phrase th
Thorsten,
That's a great pointer. I've just investigated using the `flex`
package as an example.
Untarring flex-2.6.1-1.tar.xz, usr/bin/flex++ is extracted as a Cygwin
symlink to usr/bin/flex.exe.
If I create a native symlink to flex.exe, tar it all up to a new tar
archive, then extract it somewhe
CYGWIN CHANGES:
===
Fix compatibility with svn 1.9 as described
https://cygwin.com/ml/cygwin/2016-09/msg00205.html
Thanks to David Stacey for the information.
DESCRIPTION:
svn_load_dirs is a Perl script designed to load a number of
directories into Subversion. This is
Greetings, Gene Pavlovsky!
> I'm installing Cygwin 64-bit on a fresh Win 7 x64 installation.
> Before running setup.exe I've set the system env var CYGWIN=winsymlinks:native
> After that I ran setup-x86_64.exe and installed cygwin64.
> The symlinks to .exe files in bin, created by setup, are not n
Versions 6.1.1-1 of
onig (source only)
libonig4 (API bump)
liboning-devel
have been uploaded.
DESCRIPTION
Oniguruma is a regular expressions library.
The characteristics of this library is that different character encoding
for every regular expression object c
On 10/1/2016 10:58 AM, Brian Inglis wrote:
On 2016-10-01 07:30, Ken Brown wrote:
I'm having an issue building icu, which boils down to the following
test case:
$ cat foo.cc
#include
locale_t foo;
$ g++ -c --std=c++0x foo.cc
foo.cc:2:1: error: ‘locale_t’ does not name a type
locale_t foo;
^
If
Tony Kelman writes:
>> Could you paste a complete sample of the error message so we can
>> determine where in the Cygwin code it's coming from?
>
> Still a problem in 14936. Folks, this could be very bad. Anyone at all
> testing the insider builds, or are we going to be blindsided when an
> update
Matthijs Nescio writes:
> I am using Windows 7. During the setup, the install has hung after it
> was finished, running some postinstall script for quite some time.
It seems you aborted setup or your log files are truncated. Unless you
let it finish the postinstall phase, you can't expect Cygwin
* Gene Pavlovsky (Sat, 1 Oct 2016 18:52:47 +0300)
>
> I'm installing Cygwin 64-bit on a fresh Win 7 x64 installation.
> Before running setup.exe I've set the system env var CYGWIN=winsymlinks:native
> After that I ran setup-x86_64.exe and installed cygwin64.
> The symlinks to .exe files in bin, cr
Am 31.08.2016 um 15:58 schrieb Corinna Vinschen:
Hi folks,
I uploaded a new Cygwin release 2.6.0-1.
...
Somehow the way to setup the default locale has changed; raising
problems as described in
https://cygwin.com/ml/cygwin/2016-10/msg0.html .
This affects also bash (without -l). It is "h
> You've got two different cygwin1.dll somewhere on your PATH.
For more information, I have one cygwin64 installation on C:, one
cygwin32 installation on E:, and they're never both on my path at
the same time. I'm not sure where that orphan registry entry that was
showing up in cygcheck.out came f
> You've got two different cygwin1.dll somewhere on your PATH. As your builds
> proceed, they likely start out using the correct cygwin1.dll but sometimes
> load
> the wrong cygwin1.dll along the way. The error message tells you how to solve
> the problem. But I usually use this method:
>
Tony Kelman wrote:
Could you paste a complete sample of the error message so we can
determine where in the Cygwin code it's coming from?
Still a problem in 14936. Folks, this could be very bad. Anyone at all
testing the insider builds, or are we going to be blindsided when an
update goes out to
21 matches
Mail list logo
