Building Cygwin DLL
Hi, all! When trying building Cygwin DLL with cygport under Cygwin I have error: make[3]: Entering directory `/home/alexey/cygwin-1.7.21-6/build/i686-pc-cygwin/winsup/cygwin' /home/alexey/cygwin-1.7.21-6/src/src/winsup/cygwin/gendef --cpu=i686 --output-def=cygwin.def --tlsoffsets=/home/alexey/cygwin-1.7.21-6/src/src/winsup/cygwin/tlsoffsets.h /home/alexey/cygwin-1.7.21-6/src/src/winsup/cygwin/i686.din /home/alexey/cygwin-1.7.21-6/src/src/winsup/cygwin/common.din /home/alexey/cygwin-1.7.21-6/src/src/winsup/cygwin/mkglobals_h /home/alexey/cygwin-1.7.21-6/src/src/winsup/cygwin/globals.cc > globals.h gcc -L/home/alexey/cygwin-1.7.21-6/build/i686-pc-cygwin/winsup/cygwin -isystem /home/alexey/cygwin-1.7.21-6/src/src/winsup/cygwin/include -B/home/alexey/cygwin-1.7.21-6/build/i686-pc-cygwin/newlib/ -isystem /home/alexey/cygwin-1.7.21-6/build/i686-pc-cygwin/newlib/targ-include -isystem /home/alexey/cygwin-1.7.21-6/src/src/newlib/libc/include -E - -P < /home/alexey/cygwin-1.7.21-6/src/src/winsup/cygwin/cygwin.sc.in -o cygwin.sc c++wrap -ggdb -pipe -fdebug-prefix-map=/home/alexey/cygwin-1.7.21-6/build=/usr/src/debug/cygwin-1.7.21-6 -fdebug-prefix-map=/home/alexey/cygwin-1.7.21-6/src/src=/usr/src/debug/cygwin-1.7.21-6 -O2 -g -fno-rtti -fno-exceptions -Wall -Wstrict-aliasing -Wwrite-strings -fno-common -pipe -fbuiltin -fmessage-length=0 -MMD -Werror -fmerge-constants -ftracer -c -o advapi32.o /home/alexey/cygwin-1.7.21-6/src/src/winsup/cygwin/advapi32.cc x86_64-w64-mingw32-gcc -g -ggdb -O2 -pipe -fdebug-prefix-map=/home/alexey/cygwin-1.7.21-6/build=/usr/src/debug/cygwin-1.7.21-6 -fdebug-prefix-map=/home/alexey/cygwin-1.7.21-6/src/src=/usr/src/debug/cygwin-1.7.21-6 -I. -I/home/alexey/cygwin-1.7.21-6/src/src/winsup/lsaauth -c -o cyglsa64.o /home/alexey/cygwin-1.7.21-6/src/src/winsup/lsaauth/cyglsa.c In file included from /home/alexey/cygwin-1.7.21-6/src/src/newlib/libc/include/sys/types.h:61:0, from /home/alexey/cygwin-1.7.21-6/src/src/winsup/cygwin/winsup.h:29, from /home/alexey/cygwin-1.7.21-6/src/src/winsup/cygwin/advapi32.cc:11: /home/alexey/cygwin-1.7.21-6/src/src/newlib/libc/include/sys/_types.h:72:20: fatal error: stddef.h: No such file or directory compilation terminated. /home/alexey/cygwin-1.7.21-6/src/src/winsup/cygwin/../Makefile.common:43: recipe for target `advapi32.o' failed make[3]: *** [advapi32.o] Error 1 make[3]: Leaving directory `/home/alexey/cygwin-1.7.21-6/build/i686-pc-cygwin/winsup/cygwin' Makefile:82: recipe for target `cygwin' failed make[2]: *** [cygwin] Error 1 What I'm doing wrong? Regards, Alexey. -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: An issue with Matlab for a mex file compiled with GNU CYGWIN g++
Hi Emad, On Fri, Jul 12, 2013 at 5:17 AM, Emad Gad wrote: (snip) > And that led me to conclude that the i686-w64-mingw32-g++ is the way to go (snip) > The troubles I am having now is how to build the cmake-based project with > i686-w64-mingw32-g++ compiler, through the cygwin shell? Somehow, I feel > that this may be a contradiction in terms, but let me first report my > observations. > > The main issue here is that the cmake that comes with cygwin will not accept > the compiler i686-w64-mingw32-g++. It will complain that that compiler > "cannot compile a simple file" which is a lie, because I know that it does. > I actually tested, and Matlab used successfully. So how come cmake found out > that it fails to compile? > > I found out the reason by invoking cmake with the option --debug-trycompile, > and there I saw what cmake is trying to do and how it failed. > > cmake tests the compiler by requesting it to compile a very small file, > called textCCompile.c, that it creates on the fly. However, its uses the > absolute path of this file. To be more precise, here is the literal command > that the /cygwinish/ cmake issues > > /cygdrive/c/MinGW64/mingw64/i686-w64-mingw32-g++ -o > cmTry/testCCompile.c.o -c > /home/usrername/path/to/the/file/build/CMakeFiles/CMakeTmp/testCCompile.c. > > The main problem here is that i686-w64-mingw32-g++ will not take the > absolute path of the C file /home/usrername/path/to/the/file/testCCompile.c. > Instead, it returns a "file not found" kind of error. The problem is that /cygdrive/c/MinGW64/mingw64/i686-w64-mingw32-g++ is not a Cygwin program, so it interprets /home/usrername/path/to/the/file/testCCompile.c differently from Cygwin's cmake : as a path on the current drive, starting with a directory named "home". However, Cygwin's /home is Windows' C:\cygwin\home Cygwin contains a utility called "cygpath" which can convert between POSIX paths and Windows paths: $ cygpath -w /home/usrername/path/to/the/file/testCCompile.c C:\cygwin\home\usrername\path\to\the\file\testCCompile.c Unfortunately, I don't think you can force cmake to pass all paths through it. > So I feel now that the main problem is that mingw compiler, which worked > with Matlab, the i686-w64-mingw32-g++, does not like UNIX-style absolute > paths, and will not be able to grab any file specified using this mode. > > So my question is am I in the right place? Is it normal to use a > cygwin-based cmake to compile a project with i686-w64-mingw32-g++? It may be possible to force cmake to accept the compiler you specify without checking, e.g. in the environment, like this: CXX=/cygdrive/c/MinGW64/mingw64/i686-w64-mingw32-g++ cmake --trust-the-compiler --the-compiler-is-your-friend path/to/sources But it's likely that the makefiles it generates would also use POSIX paths, and i686-w64-mingw32-g++ will not understand them unless you hack the makefiles to use cygpath to translate filenames before make passes them to i686-w64-mingw32-g++ I suspect it would be easier to use the native Windows version of cmake with the mingw compiler. Csaba -- GCS a+ e++ d- C++ ULS$ L+$ !E- W++ P+++$ w++$ tv+ b++ DI D++ 5++ The Tao of math: The numbers you can count are not the real numbers. Life is complex, with real and imaginary parts. "Ok, it boots. Which means it must be bug-free and perfect. " -- Linus Torvalds "People disagree with me. I just ignore them." -- Linus Torvalds -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: mingw/math.h not found while compiling R packages
Hi Marco,
Thanks a lot for your help. I downloaded your patched package and it
compiles without any issues.
Since the bug is in Bioconductor and not Cygwin at the end of the day,
it would probably be a good idea to file a bug report there.
If you're OK with it, I can CC you and link to your patch, just let me know.
Again, thank you!
Best,
Enrico
On 12 July 2013 04:48, marco atzeri wrote:
> Il 7/12/2013 12:02 AM, marco atzeri ha scritto:
>>
>> Il 7/11/2013 10:51 PM, Enrico Ferrero ha scritto:
>>>
>>> Hi,
>>>
>>
>> I am building biocLite, it will take some time...
>>
>
> Enrico,
> As I was thinking the package is broken.
> I don't know why they put a wrong and useless #include directive
>
> If you download the package and patch the source as
>
> ---
> --- orig/IRanges/src/common.h 2013-02-22 04:36:50.0 +0100
> +++ IRanges/src/common.h2013-07-12 00:19:05.922405200 +0200
> @@ -55,10 +55,6 @@
> #endif
> #endif
>
> -#ifdef __CYGWIN32__
> -#include
> -#endif
> -
> #ifndef NAN
> #define NAN (0.0 / 0.0)
> #endif
> -
>
> after repacking
> you can then install the local file with something like
> install.packages("/tmp/IRanges_1.16.6.tar.gz")
>
> I put the already patched file here if you are interested:
> http://matzeri.altervista.org/works/R/
>
> Regards
>
> Marco
>
>
> --
> Problem reports: http://cygwin.com/problems.html
> FAQ: http://cygwin.com/faq/
> Documentation: http://cygwin.com/docs.html
> Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
>
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: Building Cygwin DLL
On 2013-07-12 02:33, Alexey Pavlov wrote:
When trying building Cygwin DLL with cygport under Cygwin I have error:
Actually, that error is in building the LSA module:
x86_64-w64-mingw32-gcc -g -ggdb -O2 -pipe
-fdebug-prefix-map=/home/alexey/cygwin-1.7.21-6/build=/usr/src/debug/cygwin-1.7.21-6
-fdebug-prefix-map=/home/alexey/cygwin-1.7.21-6/src/src=/usr/src/debug/cygwin-1.7.21-6
-I. -I/home/alexey/cygwin-1.7.21-6/src/src/winsup/lsaauth -c -o
cyglsa64.o /home/alexey/cygwin-1.7.21-6/src/src/winsup/lsaauth/cyglsa.c
In file included from
/home/alexey/cygwin-1.7.21-6/src/src/newlib/libc/include/sys/types.h:61:0,
from
/home/alexey/cygwin-1.7.21-6/src/src/winsup/cygwin/winsup.h:29,
from
/home/alexey/cygwin-1.7.21-6/src/src/winsup/cygwin/advapi32.cc:11:
/home/alexey/cygwin-1.7.21-6/src/src/newlib/libc/include/sys/_types.h:72:20:
fatal error: stddef.h: No such file or directory
compilation terminated.
Looks like you are missing mingw64-x86_64-{headers,runtime}.
Yaakov
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: mingw/math.h not found while compiling R packages
Il 7/12/2013 10:01 AM, Enrico Ferrero ha scritto: Hi Marco, Thanks a lot for your help. I downloaded your patched package and it compiles without any issues. Since the bug is in Bioconductor and not Cygwin at the end of the day, it would probably be a good idea to file a bug report there. If you're OK with it, I can CC you and link to your patch, just let me know. Again, thank you! Best, Enrico fine for me. Ciao Marco -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
[ANNOUNCEMENT] Updated: w32api-{headers,runtime}-3.0b_svn5935-1
Version 3.0b_svn5935-1 of "w32api" has been uploaded. This version of w32api is based on mingw-w64 headers and libraries for the Cygwin toolchain and should be compatible with previous versions. Cygwin packagers, please test your applications. *** CYGWIN-ANNOUNCE UNSUBSCRIBE INFO *** If you want to unsubscribe from the cygwin-announce mailing list, look at the "List-Unsubscribe: " tag in the email header of this message. Send email to the address specified there. It will be in the format: cygwin-announce-unsubscribe-you=yourdomain.com cygwin.com If you need more information on unsubscribing, start reading here: http://sourceware.org/lists.html#unsubscribe-simple Please read *all* of the information on unsubscribing that is available starting at this URL. signature.asc Description: OpenPGP digital signature
[ANNOUNCEMENT] Updated: mingw64-*-{gcc,headers,runtime,pthreads}, New package: mingw64-*-winpthreads
This update includes: Update: mingw64-*-headers-3.0b_svn5935-1 mingw64-*-runtime-3.0b_svn5935-1 mingw64-*-gcc-4.7.3-1 mingw64-*-pthreads-20100619-5 New: mingw64-*-winpthreads-3.0b_svn5935-1 *** NOTES *** For gcc-4.7.x, struct alignment behavior has changed, -mms-bitfields is now default, for better MSVC compatibility. This may cause ABI changes in libraries that expose data structures directly to clients. Workaround include marking the struct with the gcc_struct attributes. The pthreads package is now a stub containing only runtime DLL, the POSIX threads headers and link libraries are now provided by the winpthreads package. The mingw64-*-headers package now has winpthreads as a prerequisite as well, some of the headers from the headers package are overwritten on purpose by the winpthreads package. ** The cross compiler can produce Win32 and Win64 native binaries. As a cross compiler, you may use --host=i686-w64-mingw32 or --host=x86_64-w64-mingw32 for autotools based source packages to build for Windows. *** CYGWIN-ANNOUNCE UNSUBSCRIBE INFO *** If you want to unsubscribe from the cygwin-announce mailing list, look at the "List-Unsubscribe: " tag in the email header of this message. Send email to the address specified there. It will be in the format: cygwin-announce-unsubscribe-you=yourdomain@cygwin.com If you need more information on unsubscribing, start reading here: http://sourceware.org/lists.html#unsubscribe-simple Please read *all* of the information on unsubscribing that is available starting at this URL. signature.asc Description: OpenPGP digital signature
mingw
Hejsan!
Du gillar mingw och jag vill bara visa att mingw fortfarande lever och
utvecklas ;-)
/Peter A
-Original Message-
From: cygwin-announce-ow...@cygwin.com
[mailto:cygwin-announce-ow...@cygwin.com] On Behalf Of JonY
Sent: den 12 juli 2013 12:33
To: cygwin-annou...@cygwin.com
Subject: Updated: mingw64-*-{gcc,headers,runtime,pthreads}, New package:
mingw64-*-winpthreads
This update includes:
Update:
mingw64-*-headers-3.0b_svn5935-1
mingw64-*-runtime-3.0b_svn5935-1
mingw64-*-gcc-4.7.3-1
mingw64-*-pthreads-20100619-5
New:
mingw64-*-winpthreads-3.0b_svn5935-1
*** NOTES ***
For gcc-4.7.x, struct alignment behavior has changed, -mms-bitfields is now
default, for better MSVC compatibility. This may cause ABI changes in libraries
that expose data structures directly to clients. Workaround include marking the
struct with the gcc_struct attributes.
The pthreads package is now a stub containing only runtime DLL, the POSIX
threads headers and link libraries are now provided by the winpthreads package.
The mingw64-*-headers package now has winpthreads as a prerequisite as well,
some of the headers from the headers package are overwritten on purpose by the
winpthreads package.
**
The cross compiler can produce Win32 and Win64 native binaries. As a cross
compiler, you may use --host=i686-w64-mingw32 or
--host=x86_64-w64-mingw32 for autotools based source packages to build for
Windows.
*** CYGWIN-ANNOUNCE UNSUBSCRIBE INFO ***
If you want to unsubscribe from the cygwin-announce mailing list, look at the
"List-Unsubscribe: " tag in the email header of this message. Send email to the
address specified there. It will be in the
format:
cygwin-announce-unsubscribe-you=yourdomain@cygwin.com
If you need more information on unsubscribing, start reading here:
http://sourceware.org/lists.html#unsubscribe-simple
Please read *all* of the information on unsubscribing that is available
starting at this URL.
Cygwin, git and x: directory
(please Cc: me in replies, not subscribed to the lists) Hi Cygwin and git developers, Does following scenario show signs of bugs in Cygwin and/or git? # setup git repo $ cd /tmp $ mkdir foo && cd foo $ git init # create x: directory $ mkdir x: $ ls x: # create Windows X: drive, cygwin utils can work with both unix and dos style # path names $ mkdir c:/temp/bar $ subst x: c:/temp/bar $ touch x:/file.txt $ ls x:/ file.txt # clean git tree from non-tracked files $ git clean -d -x -f Removing x:/ # observe results, git did rm -rf on the X drive instead of the local # directory named x: $ ls x: $ file x\: x:: directory $ ls x:/ ls: cannot access x:/: No such file or directory $ ls c:/temp/bar ls: cannot access c:/temp/bar: No such file or directory $ subst X:\: => C:\temp\bar In real life CMake created C: file in a build tree -- which is also a bug but a separate one -- which resulted in obviously catastrophic results. -Mikko -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
RE: libargp: argp_program_version does not work
Hello!
> int main (int argc, char **argv)
> {
> argp_program_version = version;
> argp_program_bug_address = bug_address;
>
> argp_parse (&argp, argc, argv, 0, 0, 0); }
>
> /*** End modified argp example #2 ***/
>
> If you compile the above version, you'll see that the --version option
> and bug tracker text are available.
>
> I'm sure this problem is familiar to developers and users of shared
> libraries, but I had forgotten it. I'll add a note to the Cygwin
> README file, to help all of us remember it next time.
Yes, i know this. But looks like nobody actually follows your way, because
under Linux simple redefinition perfectly works.
Of course we could fix every program, but i have an idea how to make the
original Linux code working:
1. Inside DLL we should rename this variables somehow
2. Inside libargp.a.dll we should have a constructor function (with
__attribute__((constructor))) which assigns variables inside DLL with
contents of argp_program_version and argp_program_bug_address.
3. Also inside libargp.a.dll we should have default definitions of these
variables with NULL contents.
This way code modification would not be required any more.
I'll try to implement this when have more time.
Kind regards,
Pavel Fedin
Expert Engineer
Samsung Electronics Research center Russia
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Dvd
Hi Saw your post. Do you still provide cygwin DVDs for sale? If yes where should I send the money. Thanks S Thomas
Re: libargp: argp_program_version does not work
> Hello!
>
> > int main (int argc, char **argv)
> > {
> > argp_program_version = version;
> > argp_program_bug_address = bug_address;
> >
> > argp_parse (&argp, argc, argv, 0, 0, 0); }
> >
> > /*** End modified argp example #2 ***/
> >
> > If you compile the above version, you'll see that the --version option
> > and bug tracker text are available.
> >
> > I'm sure this problem is familiar to developers and users of shared
> > libraries, but I had forgotten it. I'll add a note to the Cygwin
> > README file, to help all of us remember it next time.
>
> Yes, i know this. But looks like nobody actually follows your way, because
> under Linux simple redefinition perfectly works.
> Of course we could fix every program, but i have an idea how to make the
> original Linux code working:
> 1. Inside DLL we should rename this variables somehow
> 2. Inside libargp.a.dll we should have a constructor function (with
> __attribute__((constructor))) which assigns variables inside DLL with
> contents of argp_program_version and argp_program_bug_address.
> 3. Also inside libargp.a.dll we should have default definitions of these
> variables with NULL contents.
>
> This way code modification would not be required any more.
> I'll try to implement this when have more time.
Okay, well I agree that this sounds like a good solution. For now you have
a workaround, and I'll be glad to consider a patch if you submit one.
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: Cygwin, git and x: directory
On 07/12/2013 08:42 AM, Mikko Rapeli wrote: (please Cc: me in replies, not subscribed to the lists) Hi Cygwin and git developers, Does following scenario show signs of bugs in Cygwin and/or git? # setup git repo $ cd /tmp $ mkdir foo && cd foo $ git init # create x: directory $ mkdir x: $ ls x: I would report this on the Cygwin list, not here. Any use of dos file paths using a Cygwin tool is not recommended, officially only POSIX paths are supported. If cygwin's Cmake is generating dos style paths, that is a bug that needs reporting to the Cygwin list. Also, I'm not sure how the developers will react to mishandling a directory named x:, but the behaviour you see is a limitation of the Cygwin platform, not of git. Mark -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
basename: a faulty warning 'extra operand --test-name' in tests causes test-driver to fail
Hello,
When trying to 'make check' Open MPI from the SVN sources I observe
the following issue with 'basename' from 'coreutils' Cygwin package:
basename: extra operand `--test-name'
Try `basename --help' for more information.
--> Testing
test-driver: line 95: Aborted (core dumped)
"$@" > $log_file 2>&1
and upon investigating:
$ /usr/share/automake-1.14/test-driver --help
Usage:
test-driver --test-name=NAME --log-file=PATH --trs-file=PATH
[--expect-failure={yes|no}] [--color-tests={yes|no}]
[--enable-hard-errors={yes|no}] [--] TEST-SCRIPT
The '--test-name', '--log-file' and '--trs-file' options are mandatory.
make check-TESTS
make[1]: Entering directory
'/usr/src/64bit/release/openmpi/openmpi-1.9.0-a1/build/test/asm'
make[2]: Entering directory
'/usr/src/64bit/release/openmpi/openmpi-1.9.0-a1/build/test/asm'
basename: extra operand `--test-name'
Try `basename --help' for more information.
--> Testing
basename: extra operand `--test-name'
Try `basename --help' for more information.
--> Testing
basename: extra operand `--test-name'
Try `basename --help' for more information.
--> Testing
basename: extra operand `--test-name'
Try `basename --help' for more information.
--> Testing
...
/usr/src/64bit/release/openmpi/openmpi-1.9.0-a1/src/openmpi-1.9.0/config/test-driver:
line 95: Segmentation fault (core dumped) "$@" > $log_file
2>&1
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
SVN::Ra problems
On a 10 min old cygwin installation: $ git svn rebase Can't load '/usr/lib/perl5/vendor_perl/5.14/i686-cygwin-threads-64int/auto/SVN/_Ra/_Ra.dll' for module SVN::_Ra: No such file or directory at /usr/lib/perl5/5.14/i686-cygwin-threads-64int/DynaLoader.pm line 190. at /usr/lib/perl5/vendor_perl/5.14/i686-cygwin-threads-64int/SVN/Base.pm line 59 BEGIN failed--compilation aborted at /usr/lib/perl5/vendor_perl/5.14/i686-cygwin-threads-64int/SVN/Ra.pm line 5. Compilation failed in require at /usr/lib/git-core/git-svn line 42. Tried perlrebase but it did not help. -Mikko -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
[ANNOUNCEMENT] Updated: screen-4.1.0-20130513-2
A new version of screen, 4.1.0-20130513-2, is available in the Cygwin distribution, both 32 and 64 bits. This is a small, Cygwin-only update from the previous release. It restores a termcapinfo entry in /etc/screenrc, that lets you use the hardstatus property in screen to set the window title. The entry was accidentally left out of the previous release. screen is a terminal multiplexer and window manager that runs several separate 'screens' on a single physical character-based terminal. Each virtual terminal emulates a DEC VT100 plus several ANSI X3.64 and ISO 2022 functions. You can create multiple windows with any programs in them, kill the current window, switch between windows or copy text between them, view a list of active windows, rename windows, view scrollback history, and more. You can detach your session and even log out if you wish; your programs will keep running, and you can reattach later, maybe when logged in from a different host. Andrew E. Schulman *** To update your installation, click on the "Install Cygwin now" link on the http://cygwin.com/ web page. This downloads setup.exe to your system. Then, run setup and answer all of the questions. *** CYGWIN-ANNOUNCE UNSUBSCRIBE INFO *** If you want to unsubscribe from the cygwin-announce mailing list, look at the "List-Unsubscribe: " tag in the email header of this message. Send email to the address specified there. It will be in the format: cygwin-announce-unsubscribe-you=yourdomain.com_at_cygwin.com If you need more information on unsubscribing, start reading here: http://sourceware.org/lists.html#unsubscribe-simple Please read *all* of the information on unsubscribing that is available starting at this URL. -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: basename: a faulty warning 'extra operand --test-name' in tests causes test-driver to fail
Il 7/12/2013 5:25 PM, Vasiliy ha scritto: Hello, When trying to 'make check' Open MPI from the SVN sources I observe the following issue with 'basename' from 'coreutils' Cygwin package: basename: extra operand `--test-name' Try `basename --help' for more information. basename has no testname options. So I do not understand why it should be a basename problem... specially as it is the same on linux http://linux.die.net/man/1/basename --> Testing test-driver: line 95: Aborted (core dumped) "$@" > $log_file 2>&1 not clear to me what is aborting could you clarify ? Regards Marco -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: Troubleshooting AutoSSH
On Fri, 12 Jul 2013, Andrew Schulman wrote:
> > Trying to debug a session, .. neither AUTOSSH_DEBUG nor AUTOSSH_LOGLEVEL:
> >
> > $ env | grep AUTO
> > AUTOSSH_DEBUG=1
> > AUTOSSH_LOGLEVEL=7
> >
> > nor -vv:
> >
> > cygrunsrv -I AutoSSH -f "remote_link" -p /usr/bin/autossh -a " -vv \
> >
> > change the logging info always ("Host key verification filed"); what is
> > the correct way to increase the log level?
>
> Your command line looks wrong. Did it get cut off?
>
Yes, I only included the first half where I inserted the "-vv", which does
not work. The entire command works on other systems, so that is not the
problem.
The problem is, nothing seems to raise the debug level for autossh when
starting as a service, .. [see below].
> (1) Get the ssh command working.
>
Works fine, .. keys setup.
> (2) Get the autossh command working.
>
Bingo - looks like -v *DOES* work when starting as a user! ON startup:
$ autossh -v -M 5661:6661 -N -R 4661:127.0.0.1:2206
wtad...@nagios.winningtech.com
2013/07/12 11:10:09 autossh[5128]: checking for grace period, tries = 0
2013/07/12 11:10:09 autossh[5128]: starting ssh (count 1)
2013/07/12 11:10:09 autossh[5128]: ssh child pid is 5060
2013/07/12 11:10:09 autossh[5128]: check on child 5060
2013/07/12 11:10:09 autossh[5128]: set alarm for 600 secs
2013/07/12 11:10:09 autossh[5060]: execing /usr/bin/ssh
OpenSSH_6.2p2, OpenSSL 1.0.1e 11 Feb 2013
debug1: Reading configuration data /etc/ssh_config
debug1: Connecting to [] port 2206.
debug1: Connection established.
debug1: identity file /home//.ssh/id_rsa type 1
debug1: identity file /home//.ssh/id_rsa-cert type -1
debug1: identity file /home//.ssh/id_dsa type -1
debug1: identity file /home//.ssh/id_dsa-cert type -1
debug1: identity file /home//.ssh/id_ecdsa type -1
debug1: identity file /home//.ssh/id_ecdsa-cert type -1
debug1: Enabling compatibility mode for protocol 2.0
debug1: Local version string SSH-2.0-OpenSSH_6.2
debug1: Remote protocol version 2.0, remote software version OpenSSH_5.8
debug1: match: OpenSSH_5.8 pat OpenSSH_5*
debug1: SSH2_MSG_KEXINIT sent
debug1: SSH2_MSG_KEXINIT received
debug1: kex: server->client aes128-ctr hmac-md5 none
debug1: kex: client->server aes128-ctr hmac-md5 none
debug1: sending SSH2_MSG_KEX_ECDH_INIT
debug1: expecting SSH2_MSG_KEX_ECDH_REPLY
debug1: Server host key: ECDSA
70:5c:35:ee:86:19:23:15:32:1a:e7:d6:99:95:9a:e4
debug1: Host '[]:2206' is known and matches the ECDSA host key.
debug1: Found key in /home/n/.ssh/known_hosts:1
debug1: ssh_ecdsa_verify: signature correct
debug1: SSH2_MSG_NEWKEYS sent
debug1: expecting SSH2_MSG_NEWKEYS
debug1: SSH2_MSG_NEWKEYS received
debug1: Roaming not allowed by server
debug1: SSH2_MSG_SERVICE_REQUEST sent
debug1: SSH2_MSG_SERVICE_ACCEPT received
debug1: Authentications that can continue: publickey,keyboard-interactive
debug1: Next authentication method: publickey
debug1: Offering RSA public key: /home//.ssh/id_rsa
debug1: Server accepts key: pkalg ssh-rsa blen 279
debug1: read PEM private key done: type RSA
debug1: Authentication succeeded (publickey).
Authenticated to ([]:2206).
debug1: Local connections to LOCALHOST:5661 forwarded to remote address
127.0.0.1:6661
debug1: Local forwarding listening on ::1 port 5661.
^
It looks like the problem is that AutoSSH is binding to IPV6, *NOT*
IPv4! sshd is set to "AddressFamily inet", .. so the problem appears to be
that AutoSSH is not binding properly.
Don't see anything in the man pages or a quick search, .. how would one
force AutoSSH to bind to IPv4? IPV6 is installed on this box, but not
used.
Thanks
Lee
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
[ANNOUNCEMENT] Updated: R-2.15.3-1
Versions 2.15.3-1 of R libRmath libRmath-devel for cygwin are now available in the Cygwin distribution: CHANGES New upstream bugfix release https://mailman.stat.ethz.ch/pipermail/r-announce/2013/000560.html last of 2.x.y series DESCRIPTION R is a language and environment for statistical computing and graphics. R provides a wide variety of statistical (linear and nonlinear modelling, classical statistical tests, time-series analysis, classification, clustering, ...) and graphical techniques, and is highly extensible. The S language is often the vehicle of choice for research in statistical methodology, and R provides an Open Source route to participation in that activity. HOMEPAGE http://www.r-project.org/ Marco Atzeri If you have questions or comments, please send them to the cygwin mailing list at: cygwin (at) cygwin (dot) com . *** CYGWIN-ANNOUNCE UNSUBSCRIBE INFO *** If you want to unsubscribe from the cygwin-announce mailing list, look at the "List-Unsubscribe: " tag in the email header of this message. Send email to the address specified there. It will be in the format: cygwin-announce-unsubscribe-you=yourdomain@cygwin.com If you need more information on unsubscribing, start reading here: http://sourceware.org/lists.html#unsubscribe-simple Please read *all* of the information on unsubscribing that is available starting at this URL. -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: SVN::Ra problems
Mikko Rapeli wrote: > On a 10 min old cygwin installation: > > $ git svn rebase > Can't load > '/usr/lib/perl5/vendor_perl/5.14/i686-cygwin-threads-64int/auto/SVN/_Ra/_Ra.dll' > for module SVN::_Ra: No such file or directory at > /usr/lib/perl5/5.14/i686-cygwin-threads-64int/DynaLoader.pm line 190. > at /usr/lib/perl5/vendor_perl/5.14/i686-cygwin-threads-64int/SVN/Base.pm > line 59 > BEGIN failed--compilation aborted at > /usr/lib/perl5/vendor_perl/5.14/i686-cygwin-threads-64int/SVN/Ra.pm line 5. > Compilation failed in require at /usr/lib/git-core/git-svn line 42. SVN/_Ra/_Ra.dll is part of the subversion-perl package, as is SVN/Base.pm. You have one but not the other. Do you have /usr/lib/perl5/vendor_perl/5.14/i686-cygwin-threads-64int/auto/SVN/_Ra/_Ra.dll.new? If so, you have to reboot your computer. > Problem reports: http://cygwin.com/problems.html Otherwise, start here^^^ -- David Rothenberger daver...@acm.org -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
[ANNOUNCEMENT] New: svn_load_dirs-1.8.0-1
DESCRIPTION:
svn_load_dirs is a Perl script designed to load a number of
directories into Subversion. This is useful if you have a number of
.zip's or tar.{Z,gz,bz2}'s for a particular package and want to load
them into Subversion.
CYGWIN NOTES:
=
svn_load_dirs used to be included in the subversion-tools package,
but has been broken out into a separate package as Subversion no
longer distributes the contributed tools.
DOWNLOAD:
=
Note that downloads from sourceware.org (aka cygwin.com) aren't
allowed due to bandwidth limitations. This means that you will need
to find a mirror which has this update, please choose the one
nearest to you: http://cygwin.com/mirrors.html
QUESTIONS:
==
If you want to make a point or ask a question the Cygwin mailing list is
the appropriate place.
CYGWIN-ANNOUNCE UNSUBSCRIBE INFO:
=
To unsubscribe to the cygwin-announce mailing list, look at the
"List-Unsubscribe: " tag in the email header of this message. Send
email to the address specified there. It will be in the format:
cygwin-announce-unsubscribe-YOU=yourdomain@cygwin.com
If you need more information on unsubscribing, start reading here:
http://sourceware.org/lists.html#unsubscribe-simple
Please read *all* of the information on unsubscribing that is available
starting at this URL.
--
David Rothenberger daver...@acm.org
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: Troubleshooting AutoSSH
> debug1: Local connections to LOCALHOST:5661 forwarded to remote address > 127.0.0.1:6661 > debug1: Local forwarding listening on ::1 port 5661. > ^ > > > > It looks like the problem is that AutoSSH is binding to IPV6, *NOT* > IPv4! sshd is set to "AddressFamily inet", .. so the problem appears to be > that AutoSSH is not binding properly. > > Don't see anything in the man pages or a quick search, .. how would one > force AutoSSH to bind to IPv4? IPV6 is installed on this box, but not > used. Hi Lee. Okay, that does seem to narrow it down. You're right that autossh doesn't have any ipv4 options. It hasn't been updated in a few years, and I think it's just not ipv6-aware yet. Does it help if you include the -4 switch to ssh, to force it to use ipv4 only? It's worth a try. -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: Dvd
On Fri, Jul 12, 2013 at 10:34:31AM -0400, S Thomas wrote: >Hi >Saw your post. Do you still provide cygwin DVDs for sale? If yes where >should I send the money. >Thanks >S Thomas Not sure who you're asking. I used to provide ISO downloads but my hosting provider complained about the web traffic. So I'm not aware of anyone offering this service. cgf -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Cygwin - 64 Bit
I couldn't find a link to the Cygwin 64 Bit Setup on the Cygwin Homepage. Don't you think it's mature enough? I think it's already quite useful for the masses, even though it's "experimental" and applications are missing. Cygwin is essential for me to "rsync" data between different Machines. The 32 Bit version is extremely slow on my 64 Bit Windows 7. But with Cygwin64 I got a huge speedup. Now it's extremely fast. Especially on a second run, the OS apparently caches the filesystem structures and rsync gets even faster than on the first run. Also many other scripts work as expected. So I switched completely for my ".sh" bash file registry entry to call Cygwin64 for my automation scripts. I think you should make this wonderful 64 Bit version more public. On the homepage there is only the link to the 32 Bit version. Btw, I still have both versions installed, in case I need some apps that are not available yet for 64 bit. It's not a problem with this dual installation. -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: Troubleshooting AutoSSH
On Fri, 12 Jul 2013, Andrew Schulman wrote: > Hi Lee. Okay, that does seem to narrow it down. > > You're right that autossh doesn't have any ipv4 options. It hasn't been > updated in a few years, and I think it's just not ipv6-aware yet. > Looks like it may not be autossh - if I start sshd with a default config, it works [ssh localhost], .. if I try ssh -4 localhost, nada! It looks like *sshd* can only bind IPV6 - forcing it to bind IPV4 only prevents startup. Windows Firewall is not enabled, .. Trend Micro is installed, but I can find no evidence it is more than virus scanner. The service user (cyg_server) is a local Administrator, .. tried Administrator credentials, but the service still cannot start if I try to force IPV4. *User* level IPV4 connections (e.g. Firefox) are working, as I just did a Cygwin reinstall to verify the situation. Any thought on what might be blocking sshd from binding to the IPV4 stack? FYI, this is the first machine we have used as a Domain Member, previously we have only been running standalone; cyg_server is a local user, as is our admin user. TIA!! Lee -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: base-files-4.1-2
On Fri, Jul 05, 2013 at 02:09:44PM +0200, Corinna Vinschen wrote: > On Jul 5 07:33, Ken Brown wrote: > > base-files-4.1-2 was released as a test version in March 2012. Is > > there a plan to promote it to current? I'm not aware of any > > problems with it. > > I just tried it on 64 bit, and I see some problems. > > - /etc/postinstall/base-files-mketc.sh > > Only cosmetically: The dos file warning when creating the service > files is annoying. Setting CYGWIN=nodosfilewarning might be a good > idea. > > - /etc/profile.d/1777fix.sh > > Calls getfacl without path. Assuming tcsh is your login shell, at > the time this is run under tcsh, there's no default PATH set, so the > script doesn't find the tools: > > /etc/profile.d/1777fix.sh: line 36: getfacl: command not found > /etc/profile.d/1777fix.sh: line 36: getfacl: command not found > /etc/profile.d/1777fix.sh: line 36: getfacl: command not found > /etc/profile.d/1777fix.sh: line 36: getfacl: command not found > /etc/profile.d/1777fix.sh: line 36: getfacl: command not found > /etc/profile.d/1777fix.sh: line 46: touch: command not found > > Using the full path for all tools would fix that. > > Other than that it's ok I think. Sorry for the late response. I'll fix this and send an RFU for 4.2 during this weekend. -- Primary key fingerprint: AD8F BDC0 5A2C FD5F A179 60E7 F79B AB04 5299 EC56 signature.asc Description: Digital signature
Re: Troubleshooting AutoSSH
> On Fri, 12 Jul 2013, Andrew Schulman wrote: > > > Hi Lee. Okay, that does seem to narrow it down. > > > > You're right that autossh doesn't have any ipv4 options. It hasn't been > > updated in a few years, and I think it's just not ipv6-aware yet. > > > Looks like it may not be autossh - if I start sshd with a default config, > it works [ssh localhost], .. if I try ssh -4 localhost, nada! > > It looks like *sshd* can only bind IPV6 - forcing it to bind IPV4 only > prevents startup. OK. So does it work then to pass the -6 flag to ssh? If sshd is only accepting ipv6, then it may be autossh's port monitoring feature that's broken. It uses ssh to forward some ports of its own, and that feature might be ipv4-only. You can turn it off by passing -M0 to autossh. Does that fix the problem? If that does fix the problem, then it's not a very good solution, because you've had to disable autossh's monitoring of your connection. So it won't know if your connection has stopped passing traffic, in order to restart it. But at least we'll have a well-defined bug to report upstream. Andrew -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: Cygwin - 64 Bit
On Fri, Jul 12, 2013 at 08:48:11PM +0200, fger...@gmx.de wrote: >I couldn't find a link to the Cygwin 64 Bit Setup on the Cygwin Homepage. >Don't you think it's mature enough? We're working on making it more public. It isn't as easy as just publishing a link. cgf -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: bzr problem
Katsumi Yamaoka writes: > 0 [main] python2.7 1264 child_info_fork::abort: address space needed by > 'math.dll' (0x80) is already occupied > > But it is sometimes: > 1 [main] python2.7 5784 child_info_fork::abort: unable to remap _ARC4.dll to > same address as parent (0xBE) - try running rebaseall > > Rebaseall doesn't help. Reinstalling bzr+python doesn't, either. > How can I fix this problem? I'd venture to guess that the DLL(s) in question belong to a Python package. If so, does the rebaseall script you are using look at those libraries at all? Regards, Achim. -- +<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+ Factory and User Sound Singles for Waldorf Q+, Q and microQ: http://Synth.Stromeko.net/Downloads.html#WaldorfSounds -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: basename: a faulty warning 'extra operand --test-name' in tests causes test-driver to fail
Marco, you're right, it's the problem in their 'run_tests' file, I've
got baffled due to a lack of time. However, there's likely an issue
with Automake not recognizing '--log-file' option, but it's another
story.
> On Fri, 12 Jul 2013 18:18:06 +0200 marco atzeri wrote:
>
> basename has no testname options. So I do not understand why
> it should be a basename problem...
>
> specially as it is the same on linux
> http://linux.die.net/man/1/basename
>
> not clear to me what is aborting
> could you clarify ?
>
> Regards
> Marco
On Fri, Jul 12, 2013 at 5:25 PM, Vasiliy wrote:
> Hello,
>
> When trying to 'make check' Open MPI from the SVN sources I observe
> the following issue with 'basename' from 'coreutils' Cygwin package:
>
> basename: extra operand `--test-name'
> Try `basename --help' for more information.
> --> Testing
> test-driver: line 95: Aborted (core dumped)
> "$@" > $log_file 2>&1
>
> and upon investigating:
> $ /usr/share/automake-1.14/test-driver --help
> Usage:
> test-driver --test-name=NAME --log-file=PATH --trs-file=PATH
> [--expect-failure={yes|no}] [--color-tests={yes|no}]
> [--enable-hard-errors={yes|no}] [--] TEST-SCRIPT
> The '--test-name', '--log-file' and '--trs-file' options are mandatory.
>
> make check-TESTS
> make[1]: Entering directory
> '/usr/src/64bit/release/openmpi/openmpi-1.9.0-a1/build/test/asm'
> make[2]: Entering directory
> '/usr/src/64bit/release/openmpi/openmpi-1.9.0-a1/build/test/asm'
> basename: extra operand `--test-name'
> Try `basename --help' for more information.
> --> Testing
> basename: extra operand `--test-name'
> Try `basename --help' for more information.
> --> Testing
> basename: extra operand `--test-name'
> Try `basename --help' for more information.
> --> Testing
> basename: extra operand `--test-name'
> Try `basename --help' for more information.
> --> Testing
> ...
>
> /usr/src/64bit/release/openmpi/openmpi-1.9.0-a1/src/openmpi-1.9.0/config/test-driver:
> line 95: Segmentation fault (core dumped) "$@" > $log_file
> 2>&1
>
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: sqlite defect
These kinds of questions belong on the main mailing list. Responding there. fger...@gmx.de wrote: > I never had problems with sqlite before. > > But since 3.7.17-3 I cannot read my databases any more > "unable to open datase file". I remember there was a discussion > on the cygwin general mailing list about this problem > (backslashes in path?). Please provide more specifics about the error and how to cause it. I use SVN on a daily basis in both 32-bit and 64-bit Cygwin and have no troubles whatsoever. You should also read and follow the instructions here: http://cygwin.com/problems.html. > Is there a solution for this bug. > Or could you switch back to the working version again, > with all the dependencies, as a workaround? I will not be re-rolling SVN against a prior SQLite release. We'll have to figure out what's causing the problem in your environment. -- David Rothenberger daver...@acm.org English literature's performing flea. -- Sean O'Casey on P. G. Wodehouse -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: basename: a faulty warning 'extra operand --test-name' in tests causes test-driver to fail
On Fri, Jul 12, 2013 at 09:21:40PM +0200, Vasiliy wrote: >Marco, you're right, it's the problem in their 'run_tests' file, I've >got baffled due to a lack of time. However, there's likely an issue >with Automake not recognizing '--log-file' option, but it's another >story. automake doesn't have a --log-file option. I can't really imagine what it would do. -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
RE: Cygwin and x: directory
On 07/12/2013 08:42 AM, Mikko Rapeli wrote: > > Hi Cygwin and git developers, > > Does following scenario show signs of bugs in Cygwin and/or git? > > # setup git repo > $ cd /tmp > $ mkdir foo && cd foo > $ git init > > # create x: directory > $ mkdir x: > $ ls > x: IMHO, this makes an interesting problem (unrelated to git): Shell script prompts user for file name. User enters "x:". Script proceeds as follows: $ mkdir tmpdir $ touch tmpdir/x: $ # useful work done here $ rm -r tmpdir rm: cannot remove `tmpdir/x:': No such file or directory rm: cannot remove `tmpdir': Directory not empty $ It would seem that touch and rm are following different rules regarding how files may be named. --Ken Nellis -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: Troubleshooting AutoSSH
On Fri, 12 Jul 2013, Andrew Schulman wrote: > > It looks like *sshd* can only bind IPV6 - forcing it to bind IPV4 only > > prevents startup. > > OK. So does it work then to pass the -6 flag to ssh? > I did not try forcing -6 because that was the only way it would connect (i.e. sshd would only start with an IPV6 connection, forcing IPV4 was a non-starter). > If sshd is only accepting ipv6, then it may be autossh's port monitoring > feature that's broken. > The failure is in starting sshd, so it's something in the OpenSSH update (15 May), or something in this Windows machine. > It uses ssh to forward some ports of its own, and > that feature might be ipv4-only. You can turn it off by passing -M0 to > autossh. Does that fix the problem? > I could try, but there is no way I can test a remote connection with V6, local connections on V6 do work when using default configuration. Would there be any value in testing the previous package, openssh-6.2p1-2? Lee -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: Cygwin - 64 Bit
On 7/12/2013 3:16 PM, Christopher Faylor wrote: On Fri, Jul 12, 2013 at 08:48:11PM +0200, fger...@gmx.de wrote: I couldn't find a link to the Cygwin 64 Bit Setup on the Cygwin Homepage. Don't you think it's mature enough? We're working on making it more public. It isn't as easy as just publishing a link. So it will be ready on Thursday then? Or do you need a cat too? -- Larry _ A: Yes. > Q: Are you sure? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting annoying in email? -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: basename: a faulty warning 'extra operand --test-name' in tests causes test-driver to fail
Sorry. Please read as: "However, there's likely an issue
with Automake's 'test-driver' not recognizing '--log-file' option."
BZW, it was obvious from my first post that I've made a typo.
On Fri, 12 Jul 2013 15:26:15 -0400 Christopher Faylor wrote:
>
>> On Fri, Jul 12, 2013 at 09:21:40PM +0200, Vasiliy wrote:
>> Marco, you're right, it's the problem in their 'run_tests' file, I've
>> got baffled due to a lack of time. However, there's likely an issue
>> with Automake not recognizing '--log-file' option, but it's another
>> story.
>
> automake doesn't have a --log-file option. I can't really imagine what
> it would do.
On Fri, Jul 12, 2013 at 9:21 PM, Vasiliy wrote:
> Marco, you're right, it's the problem in their 'run_tests' file, I've
> got baffled due to a lack of time. However, there's likely an issue
> with Automake not recognizing '--log-file' option, but it's another
> story.
>
>
>> On Fri, 12 Jul 2013 18:18:06 +0200 marco atzeri wrote:
>>
>> basename has no testname options. So I do not understand why
>> it should be a basename problem...
>>
>> specially as it is the same on linux
>> http://linux.die.net/man/1/basename
>>
>> not clear to me what is aborting
>> could you clarify ?
>>
>> Regards
>> Marco
>
> On Fri, Jul 12, 2013 at 5:25 PM, Vasiliy wrote:
>> Hello,
>>
>> When trying to 'make check' Open MPI from the SVN sources I observe
>> the following issue with 'basename' from 'coreutils' Cygwin package:
>>
>> basename: extra operand `--test-name'
>> Try `basename --help' for more information.
>> --> Testing
>> test-driver: line 95: Aborted (core dumped)
>> "$@" > $log_file 2>&1
>>
>> and upon investigating:
>> $ /usr/share/automake-1.14/test-driver --help
>> Usage:
>> test-driver --test-name=NAME --log-file=PATH --trs-file=PATH
>> [--expect-failure={yes|no}] [--color-tests={yes|no}]
>> [--enable-hard-errors={yes|no}] [--] TEST-SCRIPT
>> The '--test-name', '--log-file' and '--trs-file' options are mandatory.
>>
>> make check-TESTS
>> make[1]: Entering directory
>> '/usr/src/64bit/release/openmpi/openmpi-1.9.0-a1/build/test/asm'
>> make[2]: Entering directory
>> '/usr/src/64bit/release/openmpi/openmpi-1.9.0-a1/build/test/asm'
>> basename: extra operand `--test-name'
>> Try `basename --help' for more information.
>> --> Testing
>> basename: extra operand `--test-name'
>> Try `basename --help' for more information.
>> --> Testing
>> basename: extra operand `--test-name'
>> Try `basename --help' for more information.
>> --> Testing
>> basename: extra operand `--test-name'
>> Try `basename --help' for more information.
>> --> Testing
>> ...
>>
>> /usr/src/64bit/release/openmpi/openmpi-1.9.0-a1/src/openmpi-1.9.0/config/test-driver:
>> line 95: Segmentation fault (core dumped) "$@" > $log_file
>> 2>&1
>>
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: Cygwin - 64 Bit
On Fri, Jul 12, 2013 at 04:45:37PM -0400, Larry Hall (Cygwin) wrote: >On 7/12/2013 3:16 PM, Christopher Faylor wrote: >> On Fri, Jul 12, 2013 at 08:48:11PM +0200, fger...@gmx.de wrote: >>> I couldn't find a link to the Cygwin 64 Bit Setup on the Cygwin Homepage. >>> Don't you think it's mature enough? >> >> We're working on making it more public. It isn't as easy as just >> publishing a link. > >So it will be ready on Thursday then? Or do you need a cat too? Unfortunately, my son is allergic to cats so I can't really have one or he won't visit. Of course, he rarely visits now but that's really off-topic for this mailing list. Don't make me warn myself again. This is my last warning. cgf -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
