Re: Updated: setup.exe (Release 2.872)

2015-10-12 Thread Fergus
I always install / update Cygwin from a x86/release/ directory located on my hard drive, and kept up to date. The new setup-x86.exe requires setup.ini.sig located in x86/ as well as setup.ini. Easy to manage, but is this additional requirement intentional? Fergus -- Problem reports: http://

Bad Address with /cygdrive paths

2015-10-12 Thread Barry Roberts
I've used cygwin for lots of years, and this is kind of weird to me. My operations guys set up some Windows Server 2012 R2 servers with Cygwin x86-64 2.2.1. There's a CIFS mount (from an HNAS) that I use a lot that is giving me problems. For example: $ ls /cygdrive/m/install ls: cannot access /c

Re: Cygwin/X installation: Unable to extract /etc/X11/fontpath.d/xorg-x11-fonts-75dpi:unscaled:pri=20

2015-10-12 Thread Yaakov Selkowitz
On Tue, 2015-10-06 at 20:22 -0400, Ken Brown wrote: > On 10/6/2015 7:40 PM, Michael Enright wrote: > > Good old setup_x86 fortuitously gave me the chance to see an error > > message involving one of these symlinks. I reviewed the setup log and > > read that apparently such a symlink was created as

[ANNOUNCEMENT] Updated: setup.exe (Release 2.872)

2015-10-12 Thread Yaakov Selkowitz
A new version of Setup, release 2.872, has been uploaded to https://cygwin.com/setup-x86.exe (32 bit version) https://cygwin.com/setup-x86_64.exe (64 bit version) Changes compared to 2.871: * New -i/--ini-basename option to choose a different basename for setup. * New -I/--include-sour

Re: convert does nothing - issue with cyglcms2-2 dll?

2015-10-12 Thread Ken Brown
On 10/12/2015 11:13 AM, Katriel Friedman wrote: Two apologies: - One for not reading the Reporting Problems instructions completely (and missing cygcheck.out request) - One for not seeing the helpful emails from Ken Brown and Marco Atzeri Sorry! Updates: -Attaching cygcheck.out. You've install

RE: smake compilation fails at malloc() checking

2015-10-12 Thread Aaron Schneider
> When trying to compile smake on cygwin x86 it fails at the step of checking > for malloc: > > "Checking if we may not define our own malloc()..." > > And it stalls there consuming some cpu. The developer suggests it's a cygwin > bug that was introduced recently. The steps to reproduce it are: >

Re: Life time of AST elements.

2015-10-12 Thread Frank Redeker
Am 12.10.2015 um 14:37 schrieb Frank Redeker: > Hello all, > > I'm writing a tool to analyze the call hierarchy of functions (methods) > using ClangTool. > > My idea is to collect the TranslationUnitDecls given to my own > ASTCosumer's HandleTranslationUnit method and traverse them later when > C

Life time of AST elements.

2015-10-12 Thread Frank Redeker
Hello all, I'm writing a tool to analyze the call hierarchy of functions (methods) using ClangTool. My idea is to collect the TranslationUnitDecls given to my own ASTCosumer's HandleTranslationUnit method and traverse them later when ClangTool.run() has finished. But it seems that the AST nodes

smake compilation fails at malloc() checking

2015-10-12 Thread Aaron Schneider
When trying to compile smake on cygwin x86 it fails at the step of checking for malloc: "Checking if we may not define our own malloc()..." And it stalls there consuming some cpu. The developer suggests it's a cygwin bug that was introduced recently. The steps to reproduce it are: - Download s

[ANNOUNCEMENT] Updated: binutils-2.25-4 (x86)

2015-10-12 Thread JonY
Built against master 3f8a753391fbd7807d6e4ef33a5b48b7bc43086b. This version should fix the "nm -l" slowdown problem, including incorporating all previous patches. *** CYGWIN-ANNOUNCE UNSUBSCRIBE INFO *** If you want to unsubscribe from the cygwin-announce mailing list, look at the