Re: upset messages
Il 11/29/2013 2:45 AM, Christopher Faylor ha scritto: /sourceware1/cygwin-staging/setup/upset: Error. Parsing failed. - duplicate packages lapack detected - x86_64/release/lapack/lapack vs. /var/ftp/pub/cygwin/x86_64/release/lapack Marco you created an additional lapack directory with duplicate files. I'd appreciate it if you would use the new upload mechanism since it will guard against this kind of thing. cgf just noticed. I tried to solve a problem and I created a different one. So to solve both I just uploaded new packages bumping to -2 I tried in the past the new method, but I had the impression was not active for me. Could you check ? Regards Marco
Re: upset messages
On Fri, Nov 29, 2013 at 11:10:16AM +0100, marco atzeri wrote: Il 11/29/2013 2:45 AM, Christopher Faylor ha scritto: /sourceware1/cygwin-staging/setup/upset: Error. Parsing failed. - duplicate packages lapack detected - x86_64/release/lapack/lapack vs. /var/ftp/pub/cygwin/x86_64/release/lapack Marco you created an additional lapack directory with duplicate files. I'd appreciate it if you would use the new upload mechanism since it will guard against this kind of thing. just noticed. I tried to solve a problem and I created a different one. So to solve both I just uploaded new packages bumping to -2 I actually fixed the problem by removing the directory. It sure looked like you had duplicated content there. I tried in the past the new method, but I had the impression was not active for me. Could you check ? AFAIK, you never sent the SSH key for upload details. I don't see anything in the archives. cgf
Re: upset messages
Il 11/29/2013 2:58 PM, Christopher Faylor ha scritto: On Fri, Nov 29, 2013 at 11:10:16AM +0100, marco atzeri wrote: I actually fixed the problem by removing the directory. It sure looked like you had duplicated content there. it was not exactly the same. there was a small difference between the two uploads, but I did it wrong I tried in the past the new method, but I had the impression was not active for me. Could you check ? AFAIK, you never sent the SSH key for upload details. I don't see anything in the archives. My fault, I assumed you already had my SSH Key cgf
two questions about new upload method
(1) Is there something I should sould be doing to tell upset which package versions are old and should be purged? I uploaded lftp, and the new version was added to the archive, but the old one (4.4.7-1) is still there. Do I need to add curr: and prev: lines to setup.hint? Or will upset figure that out and remove the old versions at some point? (2) I uploaded the unison packages for x86_64 in subdirectories of x86_64/release/unison: x86_64/release/unison/unison2.27 x86_64/release/unison/unison2.32 x86_64/release/unison/unison2.40 x86_64/release/unison/unison2.45 because that's how they're organized in x86/release. Will upset pick them up when they're organized that way? I only ask because it's been about 18 hours and they haven't appeared in any of the mirrors yet, although upset seems to be running every hour. Thanks, Andrew.
Re: two questions about new upload method
On Fri, Nov 29, 2013 at 12:27:17PM -0500, Andrew Schulman wrote: (1) Is there something I should sould be doing to tell upset which package versions are old and should be purged? There was a long thread about how to delete packages in cygwin-apps. http://cygwin.com/ml/cygwin-apps/2013-10/threads.html#00184 It also went into November. I uploaded lftp, and the new version was added to the archive, but the old one (4.4.7-1) is still there. Do I need to add curr: and prev: lines to setup.hint? Or will upset figure that out and remove the old versions at some point? (2) I uploaded the unison packages for x86_64 in subdirectories of x86_64/release/unison: x86_64/release/unison/unison2.27 x86_64/release/unison/unison2.32 x86_64/release/unison/unison2.40 x86_64/release/unison/unison2.45 because that's how they're organized in x86/release. Will upset pick them up when they're organized that way? I only ask because it's been about 18 hours and they haven't appeared in any of the mirrors yet, although upset seems to be running every hour. Guess I need to add a FAQ. Q) Why aren't my files being transferred to the release area? I've waited several days and don't see any movement. A) The package updater runs every 10 minutes so, if you don't see any movement in, e.g., 20 minutes, then your package is not going to be updated. The main reason that this could happen is if you uploaded a package that you are not actually responsible for. The updater only knows what you are responsible for based on http://cygwin.com/cygwin-pkg-maint so if you aren't listed as an owner there your packages won't be updated. I added you as the owner for unison and unison2.45. cgf
cygwin-pkg-maint update
I just noticed that gl2ps , libgl2ps1 and libgl2ps-devel are not reported as they were only recently added. But I see the same for the result of split /addition in the past like netcdf-cxx4, libnetcdf-cxx4, libnetcdf-cxx4-devel or the suitesparse expansion. So before touching anything : what is the right procedure to update cygwin-pkg-maint ? Regards Marco
SSH key for upload access
Name: Marco Atzeri Package: lapack BEGIN SSH2 PUBLIC KEY B3NzaC1yc2EDAQABAAABAQDBdNLOzObcACE50UDaWncOKGYK8Ph2j7NGdMlgRH IjzLj6ibCAJK8rSJ+9u1UY59cjUL3LbdWnJzohRMnQ+cEe2mrG1uwjQXVC5C9V0A9EFKwV 6q/Q6z3+UO4K14jH+s8tYCei/M/92c2c9zmta2w4sf6S+D1BS6MWOA5wg5GGHXAtVaiU4Z PhjOgrTDxsGY8tQBWEtUVRKaXLRHO014ObE8HddC4dgyiSk89eW8Bj0I9mfW/jtOd2pcNF G0Z/CSWjRyLftQvYHAznppse8Q9rKQYkp7jLHcNYn8oQU5vGwRZzU3axdIUCZx26YJu6AT 5h3CjsRvMjvKtvNJ2QV5Zz END SSH2 PUBLIC KEY
Re: SSH key for upload access
On Fri, Nov 29, 2013 at 10:25:39PM +0100, marco atzeri wrote: Name: Marco Atzeri Package: lapack BEGIN SSH2 PUBLIC KEY B3NzaC1yc2EDAQABAAABAQDBdNLOzObcACE50UDaWncOKGYK8Ph2j7NGdMlgRH IjzLj6ibCAJK8rSJ+9u1UY59cjUL3LbdWnJzohRMnQ+cEe2mrG1uwjQXVC5C9V0A9EFKwV 6q/Q6z3+UO4K14jH+s8tYCei/M/92c2c9zmta2w4sf6S+D1BS6MWOA5wg5GGHXAtVaiU4Z PhjOgrTDxsGY8tQBWEtUVRKaXLRHO014ObE8HddC4dgyiSk89eW8Bj0I9mfW/jtOd2pcNF G0Z/CSWjRyLftQvYHAznppse8Q9rKQYkp7jLHcNYn8oQU5vGwRZzU3axdIUCZx26YJu6AT 5h3CjsRvMjvKtvNJ2QV5Zz END SSH2 PUBLIC KEY Activated. cgf
Re: cygwin-pkg-maint update
On Fri, Nov 29, 2013 at 09:43:11PM +0100, marco atzeri wrote: I just noticed that gl2ps , libgl2ps1 and libgl2ps-devel are not reported as they were only recently added. But I see the same for the result of split /addition in the past like netcdf-cxx4, libnetcdf-cxx4, libnetcdf-cxx4-devel or the suitesparse expansion. So before touching anything : what is the right procedure to update cygwin-pkg-maint ? You can add your new packages to cygwin-pkg-maint since you have a login account on sourceware.orgi with cygwin group access. You'll need to use CVS: cvs -d :ext:sourceware.org:/cvs/cygwin co htdocs You don't add -devel or other subpackages packages like libgl2ps-devel. Just add the main package name. In case anyone noticed: unison is a special case since new version numbers are part of the package name. To answer the general question: Anyone without a cygwin group account on sourceware will have to send mail here to have one of us update cygwin-pkg-maint. Personally, I'd appreciate a patch but if you can't do that, at least use the same format as cygwin-pkg-maint in your request. cgf
Re: two questions about new upload method
On Fri, Nov 29, 2013 at 01:13:30PM -0500, Christopher Faylor wrote: I added you as the owner for unison and unison2.45. Which didn't do anything. I'm investigating why now. cgf
Re: two questions about new upload method
On Fri, Nov 29, 2013 at 10:06:50PM -0500, Christopher Faylor wrote: On Fri, Nov 29, 2013 at 01:13:30PM -0500, Christopher Faylor wrote: I added you as the owner for unison and unison2.45. Which didn't do anything. I'm investigating why now. It was because the !ready files disappeared after the previous run. I put one in unison/unison2.45 and the files were moved. cgf
src/winsup/doc ChangeLog new-features.xml
CVSROOT:/cvs/src Module name:src Changes by: cori...@sourceware.org 2013-11-29 10:14:14 Modified files: winsup/doc : ChangeLog new-features.xml Log message: * new-features.xml (ov-new1.7.26): Fix section ID and title. Add posix_spawn item. Patches: http://sourceware.org/cgi-bin/cvsweb.cgi/src/winsup/doc/ChangeLog.diff?cvsroot=srcr1=1.465r2=1.466 http://sourceware.org/cgi-bin/cvsweb.cgi/src/winsup/doc/new-features.xml.diff?cvsroot=srcr1=1.15r2=1.16
src/winsup/cygwin ChangeLog include/cygwin/std ...
CVSROOT:/cvs/src Module name:src Changes by: jtur...@sourceware.org 2013-11-29 13:05:43 Modified files: winsup/cygwin : ChangeLog winsup/cygwin/include/cygwin: stdlib.h Log message: * include/cygwin/stdlib.h(initstate, random, setstate, srandom) : Prototype if not __STRICT_ANSI__ or _XOPEN_SOURCE is defined appropriately. Patches: http://sourceware.org/cgi-bin/cvsweb.cgi/src/winsup/cygwin/ChangeLog.diff?cvsroot=srcr1=1.6266r2=1.6267 http://sourceware.org/cgi-bin/cvsweb.cgi/src/winsup/cygwin/include/cygwin/stdlib.h.diff?cvsroot=srcr1=1.15r2=1.16
src/winsup/cygwin ChangeLog include/cygwin/ver ...
CVSROOT:/cvs/src Module name:src Changes by: c...@sourceware.org 2013-11-29 13:31:54 Modified files: winsup/cygwin : ChangeLog winsup/cygwin/include/cygwin: version.h Log message: * include/cygwin/version.h (CYGWIN_VERSION_DLL_MINOR): Bump to 27. Patches: http://sourceware.org/cgi-bin/cvsweb.cgi/src/winsup/cygwin/ChangeLog.diff?cvsroot=srcr1=1.6267r2=1.6268 http://sourceware.org/cgi-bin/cvsweb.cgi/src/winsup/cygwin/include/cygwin/version.h.diff?cvsroot=srcr1=1.394r2=1.395
mosh-1.2.4-1 (x86) missing mosh executable in package !
https://sourceware.org/ml/cygwin/2013-11/msg00381.html I have tried several mirrors and i get no mosh or mosh.exe or any bash alias for mosh command. As I peek into binary package file.. I see there is only 2 files (mosh-client.exe,mosh-server.exe) , but the man page speaks of using mosh command. admin9000@Win764bitTestMachine~ $ mosh -bash: mosh: command not found admin9000@Win764bitTestMachine~ $ ls /usr/bin/mos* /usr/bin/mosh-client.exe /usr/bin/mosh-server.exe admin9000@Win764bitTestMachine~ If i use x64 cygwin. Everything works fine. admin@T64TW7Poff ~ $ mosh Usage: /usr/bin/mosh [options] [--] [user@]host [command...] admin@T64TW7Poff ~ $ ls /usr/bin/mos* /usr/bin/mosh /usr/bin/mosh-client.exe /usr/bin/mosh-server.exe -- 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, new for 64-bit: lftp 4.4.11-1
A new version of lftp, 4.4.11-1, is available in the Cygwin distribution. The is the first release of lftp for x86_64. lftp is a sophisticated file transfer program and ftp/http/bittorrent client. It supports multiple network protocols. It uses the readline library for input, so it offers tab completion and command history. It has job control and bookmarks. It can mirror sites and transfer multiple files in parallel. It keeps trying interrupted operations until it can complete them. 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://cygwin.com/lists.html#subscribe-unsubscribe 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
[ANNOUNCEMENT] Updated: Cygwin 1.7.26
Hi Cygwin friends and users, I just released Cygwin 1.7.26. This release introduces a few new features but is mainly a bugfix release. To install 32-bit Cygwin use http://cygwin.com/setup-x86.exe To install 64 bit Cygwin use http://cygwin.com/setup-x86_64.exe The 64 bit Cygwin distribution doesn't yet come with as many packages as the 32 bit version, but more packages will be available over time. If you're already running a 32 bit version of Cygwin on 64 bit Windows machines, you can continue to do so. If you're planning a new install of Cygwin on a 64 bit Windows machine, consider to use the new 64 bit Cygwin version, unless you need certain packages not yet available in the 64 bit release. What's new: --- - getaddrinfo now supports glibc-specific International Domain Name (IDN) extension flags: AI_IDN, AI_CANONIDN, AI_IDN_ALLOW_UNASSIGNED, AI_IDN_USE_STD3_ASCII_RULES. - getnameinfo now supports glibc-specific International Domain Name (IDN) extension flags: NI_IDN, NI_IDN_ALLOW_UNASSIGNED, NI_IDN_USE_STD3_ASCII_RULES. - Preliminary, experimental support of the posix_spawn family of functions. New associated header /usr/include/spawn.h. What changed: - - Slightly improve randomness of /dev/random emulation. - Allow to use advisory locking on any device. POSIX fcntl and lockf locking works with any device, BSD flock locking only with devices backed by an OS handle. Right now this excludes console windows on pre Windows 8, as well as almost all virtual files under /proc from BSD flock locking. - The header /usr/include/exceptions.h, containing implementation details for 32 bit Windows' exception handling only, has been removed. Bug fixes: -- - pthread_atparent hook should not be called in the child. Fixes: http://cygwin.com/ml/cygwin/2013-09/msg00365.html - 64 bit only: Correctly mmap'ing regions 4 Gigs. Fixes: http://cygwin.com/ml/cygwin/2013-09/msg00155.html - Fix random content of /proc/$PID/ctty if the process has no controlling tty. Set to just \n instead. - Properly set process sid rather than always using -1. Fixes: http://cygwin.com/ml/cygwin/2013-10/threads.html#00237 - Fix a potential crash after calling lseek on /dev/clipboard. - Fix a handle inheritance bug in raw disk and tape device handling which led to EBADF errors in child processes. - open(/dev, O_CREAT) accidentally created a /dev file if no /dev exists at the time. - DIR *d = opendir (foo); flock (dirfd (d), ...); worked, but did the wrong thing. - Reading from /dev/windows was broken for some time. - select'ing on /dev/windows accidentally didn't take the setting of ioctl (WINDOWS_HWND) into account. - Fix typos in cygcheck which could crash Windows 8 and 8.1 machines. Fixes: http://cygwin.com/ml/cygwin/2013-11/msg00334.html - Show OS version correctly even on Windows 8.1 and Server 2012 R2. Fixes: http://cygwin.com/ml/cygwin/2013-11/msg00343.html - dup2() could crash in some cases for a destination = 256 Fixes: http://cygwin.com/ml/cygwin/2013-09/msg00397.html - Try to workaround the following problem: unlink(2) could fail, if the file was opened casesensitive and has to be moved to the recycler due to a sharing violation. Have fun, Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat -- 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: [ANNOUNCEMENT] Updated: Cygwin 1.7.26
Corinna Vinschen wrote: I just released Cygwin 1.7.26. Just for completeness... After upgrading to this release of Cygwin, the application Terminator, installed with Cygwinports, does not work any more. Its empty window shows up with a dialog box from Cygwin/X X saying (translting): An error occurred in loading or saving the configuration for terminator.. a few settings of its configuration could not work... The Details button prints: NO DBUS running... After this, clicking OK button leaves the Terminator window containing the message: Cannot run /bin/bash... If I close this window also the X server exits.. Ciao, Angelo. -- 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: [ANNOUNCEMENT] Updated: Cygwin 1.7.26
(I forgot to say that here is on Cygwin x86) Il 29/11/2013 14.37, Angelo Graziosi ha scritto: Corinna Vinschen wrote: I just released Cygwin 1.7.26. Just for completeness... When I start Terminator from command line in xterm, beside what I described in my previous post, I see also these messages in xterm: -- $ terminator 4 [main] python2.7 1684 child_info_fork::abort: unable to remap pango.dll to same address as parent (0x91) - try running rebaseall (terminator:2632): GConf-WARNING **: Client failed to connect to the D-BUS daemon: Failed to fork() to call /usr/bin/dbus-launch: Resource temporarily unavailable 3 [main] python2.7 3804 child_info_fork::abort: unable to remap pango.dll to same address as parent (0x91) - try running rebaseall (terminator:2632): GConf-WARNING **: Client failed to connect to the D-BUS daemon: Failed to fork() to call /usr/bin/dbus-launch: Resource temporarily unavailable 3 [main] python2.7 1988 child_info_fork::abort: unable to remap pango.dll to same address as parent (0x91) - try running rebaseall (terminator:2632): GConf-WARNING **: Client failed to connect to the D-BUS daemon: Failed to fork() to call /usr/bin/dbus-launch: Resource temporarily unavailable 3 [main] python2.7 1040 child_info_fork::abort: unable to remap pango.dll to same address as parent (0x91) - try running rebaseall (terminator:2632): GConf-WARNING **: Client failed to connect to the D-BUS daemon: Failed to fork() to call /usr/bin/dbus-launch: Resource temporarily unavailable 3 [main] python2.7 3072 child_info_fork::abort: unable to remap pango.dll to same address as parent (0x91) - try running rebaseall (terminator:2632): GConf-WARNING **: Client failed to connect to the D-BUS daemon: Failed to fork() to call /usr/bin/dbus-launch: Resource temporarily unavailable Warning: python-keybinder is not installed. This means the hide_window shortcut will be unavailable Unable to bind hide_window key, another instance/window has it. 3 [main] python2.7 1404 child_info_fork::abort: unable to remap vtemodule.dll to same address as parent (0x137) - try running rebaseall --- So I tried also a manual rebaseall -p from dash (an autorebase.bat was already executed by setup-x86). But it didn't fix the issue... :-( Ciao, Angelo. After upgrading to this release of Cygwin, the application Terminator, installed with Cygwinports, does not work any more. Its empty window shows up with a dialog box from Cygwin/X X saying (translting): An error occurred in loading or saving the configuration for terminator.. a few settings of its configuration could not work... The Details button prints: NO DBUS running... After this, clicking OK button leaves the Terminator window containing the message: Cannot run /bin/bash... If I close this window also the X server exits.. Ciao, Angelo. -- 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's PHP MySQL
I am attempting to learn php programming together with interfacing it to an MySQL server from an http web-page. I ran into a fatal error. The httpd2 server logs shows the following message: PHP Fatal error: Class 'mysqli' not found The phpinfo() function has no mention of the mysqli extension. What do I need to do to get this important extension and install it in for my cygwin environment? Any help or advice would be much appreciated. -- 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: Win 7 claims setup-x86_64.exe doesn't work any more - but it does
On Fri, Nov 29, 2013 at 06:48:07AM +0100, Niklaas Baudet von Gersdorff wrote: Corinna Vinschen [2013-11-28 14:09 +0100] : On Nov 28 10:24, Robert Klemme wrote: since the last update of my cygwin 64 installer during the execution I get a Windows pop up indicating that the program does not work any more. Funny thing is: it does. I just click cancel and the installation proceeds normally. It even happens if I start the program and click cancel on the first screen. Is anybody else experiencing the same? Version is 2.831. Just tried it on a W7-64 machine and I can't reproduce this. Maybe a virus scanner is interfering? I just want to mention that I can reproduce this behaviour using the x86 setup.exe . Starting the setup.exe blaims the program does not work any more. But I can close this dialog and continue installing cygwin packages without any problems. I didn't change my system at all, just installed the new version of cygwin's setup.exe . If you tell me how, I'd debug this. http://cygwin.com/ml/cygwin/2013-11/msg00457.html -- 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
Binutils 2.23.51 compilation problem
Hello. I'm trying to compile and install binutils+GCC for my machine. I have compiled lastest binutils sources without getting any error, but installation seems to have some problems with gas documentation. The output of the installation is very large and some of the warnings are repeating (they just occur on different lines). It looks like the problem is caused by 'as.info' file, and I guess I'm using old version of some tool for '.texi' files. I don't know what to do now. Do you have any idea what can I do for running the installation successfully? Regards --- make[2]: Leaving directory '/src/binutils-2.23.51-1/build/etc' make[2]: Entering directory '/src/binutils-2.23.51-1/build/gas' Making install in doc make[3]: Entering directory '/src/binutils-2.23.51-1/build/gas/doc' make[4]: Entering directory '/src/binutils-2.23.51-1/build/gas/doc' make[4]: Nothing to be done for 'install-exec-am'. ../../../gas/doc/c-arc.texi:223: command @bullet not accepting argument in brace should not be on @table line ../../../gas/doc/c-arm.texi:393: command @bullet not accepting argument in brace should not be on @table line ../../../gas/doc/c-arm.texi:394: warning: @item missing argument ... ../../../gas/doc/c-cr16.texi:65: warning: @item missing argument ../../../gas/doc/c-tic54x.texi:113: @code expected brace ... ../../../gas/doc/c-i386.texi:979: warning: node prev `i386-Bugs' in menu `i386-Arch' and in sectioning `i386-16bit' differ ... ../../../gas/doc/c-xtensa.texi:9: warning: node `Z80-Dependent' is next for `Xtensa-Dependent' in menu but not in sectioning Makefile:397: recipe for target 'as.info' failed make[4]: *** [as.info] Error 1 make[4]: Leaving directory '/src/binutils-2.23.51-1/build/gas/doc' Makefile:592: recipe for target 'install-am' failed make[3]: *** [install-am] Error 2 make[3]: Leaving directory '/src/binutils-2.23.51-1/build/gas/doc' Makefile:2182: recipe for target 'install-recursive' failed make[2]: *** [install-recursive] Error 1 make[2]: Leaving directory '/src/binutils-2.23.51-1/build/gas' Makefile:4761: recipe for target 'install-gas' failed make[1]: *** [install-gas] Error 2 make[1]: Leaving directory '/src/binutils-2.23.51-1/build' Makefile:2141: recipe for target 'install' failed make: *** [install] Error 2 -- 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: rpm-4.11-1 (x86/x86_64)
I have made a new version of rpm available for installation. rpm is the Linux package management system used by Fedora, SuSE and others. This is just a long-delayed refresh of rpm from upstream sources. It obsoletes the rpm-doc package and adds the rpm-devel package which contains files needed for writing programs which manipulate rpm data. RPM can be found in the setup.exe Utils category. -- 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: Binutils 2.23.51 compilation problem
On Nov 29 23:40, Frew Cen wrote: Hello. I'm trying to compile and install binutils+GCC for my machine. I have compiled lastest binutils sources without getting any error, but installation seems to have some problems with gas documentation. The output of the installation is very large and some of the warnings are repeating (they just occur on different lines). It looks like the problem is caused by 'as.info' file, and I guess I'm using old version of some tool for '.texi' files. I don't know what to do now. Do you have any idea what can I do for running the installation successfully? Looks like a bug in the docs. You should report this problem to the public binutils mailing list binutils AT sourceware DOT org. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Maintainer cygwin AT cygwin DOT com Red Hat pgp1dyuywkppN.pgp Description: PGP signature
Re: Binutils 2.23.51 compilation problem
Looks like a bug in the docs. You should report this problem to the public binutils mailing list binutils AT sourceware DOT org. I'm not sure if the problem is there. I get similar message when compiling (now not installing) mingw binutils. Would some from the older versions work? Frew --- config.status: creating po/Makefile.in config.status: executing depfiles commands config.status: executing libtool commands config.status: executing default-1 commands config.status: executing bfd_stdint.h commands config.status: executing default commands make[3]: Nothing to be done for 'info'. make[3]: Leaving directory '/src/binutils-2.23.2/build/bfd/po' make[3]: Entering directory '/src/binutils-2.23.2/build/bfd' make[3]: Nothing to be done for 'info-am'. make[3]: Leaving directory '/src/binutils-2.23.2/build/bfd' Makefile:1617: recipe for target 'info-recursive' failed make[2]: *** [info-recursive] Error 1 make[2]: Leaving directory '/src/binutils-2.23.2/build/bfd' Makefile:2509: recipe for target 'all-bfd' failed make[1]: *** [all-bfd] Error 2 make[1]: Leaving directory '/src/binutils-2.23.2/build' Makefile:841: recipe for target 'all' failed make: *** [all] Error 2 -- 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
making llvm-3.1-4.cygport w/o --enable-shared?
Hi, SSIA, anyone can manage this bug? http://llvm.org/bugs/show_bug.cgi?id=13430 -- 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: mosh-1.2.4-1 (x86) missing mosh executable in package !
On 11/29/2013 02:38 AM, Egon Ojamaa wrote: https://sourceware.org/ml/cygwin/2013-11/msg00381.html I have tried several mirrors and i get no mosh or mosh.exe or any bash alias for mosh command. As I peek into binary package file.. I see there is only 2 files (mosh-client.exe,mosh-server.exe) , but the man page speaks of using mosh command. admin9000@Win764bitTestMachine~ $ mosh -bash: mosh: command not found admin9000@Win764bitTestMachine~ $ ls /usr/bin/mos* /usr/bin/mosh-client.exe /usr/bin/mosh-server.exe oops, I'll fix it ASAP admin9000@Win764bitTestMachine~ If i use x64 cygwin. Everything works fine. admin@T64TW7Poff ~ $ mosh Usage: /usr/bin/mosh [options] [--] [user@]host [command...] admin@T64TW7Poff ~ $ ls /usr/bin/mos* /usr/bin/mosh /usr/bin/mosh-client.exe /usr/bin/mosh-server.exe -- 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: chere + mintty doesn't work with mapped drives
On 29/11/2013 17:29, Charles Butterfield wrote: I've noticed that if I install a right-click shell entry via chere and use minty as the terminal that I cannot start a shell on a network share. This is true regardless of which of the following two installation commands I execute: chere -I -t mintty -s bash chere -i -2 -t mintty -s bash A related clue is that when using a mintty terminal I cannot see network shares in /cygdrive, but when using the default chere shell I can see the network shares mapped to drives (e.g. /cygdrive/y/...). Any suggestions? Can you clarify which isn't working: a) a network share mapped to a drive letter, e.g N:\my\network\location b) network share accessed via \\ e.g. \\server\path\my\network\location I think a) should always work. Are you right clicking on a directory and selecting the menu item, or right clicking a blank spot in the RH pane? The two result in different logic, with the latter having to guess it's a network path. You may be able to figure out what's going on by adding a few echos to /bin/xhere Dave. -- 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
Cygwin64 1.7.26: Problem with linking many files
I found a problem with linking many files in Cygwin64. It works fine in bash but from the Windows shell I get the below. To repeat, download the latest version of my editor from http://www.bengtl.net/files/mg3a/ Extract into a directory, go there and type make. Since it's when linking many files this seems the easiest to repeat. There is no problem in Cygwin32, either from bash or the Windows shell. I have tried reinstalling the latest Cygwin, and rebooted. These are the errors when compiling with make from the Windows shell: gcc -pipe -O2 -DDIRED -DPREFIXREGION -c basic.c gcc -pipe -O2 -DDIRED -DPREFIXREGION -c dir.c gcc -pipe -O2 -DDIRED -DPREFIXREGION -c dired.c gcc -pipe -O2 -DDIRED -DPREFIXREGION -c file.c gcc -pipe -O2 -DDIRED -DPREFIXREGION -c line.c gcc -pipe -O2 -DDIRED -DPREFIXREGION -c match.c gcc -pipe -O2 -DDIRED -DPREFIXREGION -c paragraph.c gcc -pipe -O2 -DDIRED -DPREFIXREGION -c random.c gcc -pipe -O2 -DDIRED -DPREFIXREGION -c region.c gcc -pipe -O2 -DDIRED -DPREFIXREGION -c search.c gcc -pipe -O2 -DDIRED -DPREFIXREGION -c ucs.c gcc -pipe -O2 -DDIRED -DPREFIXREGION -c util.c gcc -pipe -O2 -DDIRED -DPREFIXREGION -c variables.c gcc -pipe -O2 -DDIRED -DPREFIXREGION -c version.c gcc -pipe -O2 -DDIRED -DPREFIXREGION -c width.c gcc -pipe -O2 -DDIRED -DPREFIXREGION -c window.c gcc -pipe -O2 -DDIRED -DPREFIXREGION -c word.c gcc -pipe -O2 -DDIRED -DPREFIXREGION -c langmode_c.c gcc -pipe -O2 -DDIRED -DPREFIXREGION -c ucsnames.c gcc -pipe -O2 -DDIRED -DPREFIXREGION -c buffer.c gcc -pipe -O2 -DDIRED -DPREFIXREGION -c display.c gcc -pipe -O2 -DDIRED -DPREFIXREGION -c echo.c gcc -pipe -O2 -DDIRED -DPREFIXREGION -c extend.c gcc -pipe -O2 -DDIRED -DPREFIXREGION -c help.c gcc -pipe -O2 -DDIRED -DPREFIXREGION -c kbd.c gcc -pipe -O2 -DDIRED -DPREFIXREGION -c keymap.c gcc -pipe -O2 -DDIRED -DPREFIXREGION -c macro.c gcc -pipe -O2 -DDIRED -DPREFIXREGION -c main.c gcc -pipe -O2 -DDIRED -DPREFIXREGION -c modes.c gcc -pipe -O2 -DDIRED -DPREFIXREGION -c cinfo.c gcc -pipe -O2 -DDIRED -DPREFIXREGION -c spawn.c gcc -pipe -O2 -DDIRED -DPREFIXREGION -c ttyio.c gcc -pipe -O2 -DDIRED -DPREFIXREGION -c tty.c gcc -pipe -O2 -DDIRED -DPREFIXREGION -c ttykbd.c gcc -pipe -O2 -DDIRED -DPREFIXREGION -c fileio.c gcc -pipe -O2 -DDIRED -DPREFIXREGION -o mg basic.o dir.o dired.o file.o line.o match.o paragraph.o random.o region.o search.o ucs.o util.o variables.o version.o width.o window.o word.o langmode_c.o ucsnames.o buffer.o display.o echo.o extend.o help.o kbd.o keymap.o macro.o main.o modes.o cinfo.o spawn.o ttyio.o tty.o ttykbd.o fileio.o -lcurses /usr/lib/gcc/x86_64-pc-cygwin/4.8.2/../../../../x86_64-pc-cygwin/bin/ld: cannot find macro.o: Too many open files /usr/lib/gcc/x86_64-pc-cygwin/4.8.2/../../../../x86_64-pc-cygwin/bin/ld: cannot find main.o: Too many open files /usr/lib/gcc/x86_64-pc-cygwin/4.8.2/../../../../x86_64-pc-cygwin/bin/ld: cannot find modes.o: Too many open files /usr/lib/gcc/x86_64-pc-cygwin/4.8.2/../../../../x86_64-pc-cygwin/bin/ld: cannot find cinfo.o: Too many open files /usr/lib/gcc/x86_64-pc-cygwin/4.8.2/../../../../x86_64-pc-cygwin/bin/ld: cannot find spawn.o: Too many open files /usr/lib/gcc/x86_64-pc-cygwin/4.8.2/../../../../x86_64-pc-cygwin/bin/ld: cannot find ttyio.o: Too many open files /usr/lib/gcc/x86_64-pc-cygwin/4.8.2/../../../../x86_64-pc-cygwin/bin/ld: cannot find tty.o: Too many open files /usr/lib/gcc/x86_64-pc-cygwin/4.8.2/../../../../x86_64-pc-cygwin/bin/ld: cannot find ttykbd.o: Too many open files /usr/lib/gcc/x86_64-pc-cygwin/4.8.2/../../../../x86_64-pc-cygwin/bin/ld: cannot find fileio.o: Too many open files /usr/lib/gcc/x86_64-pc-cygwin/4.8.2/../../../../x86_64-pc-cygwin/bin/ld: cannot find -lcurses /usr/lib/gcc/x86_64-pc-cygwin/4.8.2/../../../../x86_64-pc-cygwin/bin/ld: cannot find -lgcc_s /usr/lib/gcc/x86_64-pc-cygwin/4.8.2/../../../../x86_64-pc-cygwin/bin/ld: cannot find -lgcc /usr/lib/gcc/x86_64-pc-cygwin/4.8.2/../../../../x86_64-pc-cygwin/bin/ld: cannot find -lcygwin /usr/lib/gcc/x86_64-pc-cygwin/4.8.2/../../../../x86_64-pc-cygwin/bin/ld: cannot find -ladvapi32 /usr/lib/gcc/x86_64-pc-cygwin/4.8.2/../../../../x86_64-pc-cygwin/bin/ld: cannot find -lshell32 /usr/lib/gcc/x86_64-pc-cygwin/4.8.2/../../../../x86_64-pc-cygwin/bin/ld: cannot find -luser32 /usr/lib/gcc/x86_64-pc-cygwin/4.8.2/../../../../x86_64-pc-cygwin/bin/ld: cannot find -lkernel32 /usr/lib/gcc/x86_64-pc-cygwin/4.8.2/../../../../x86_64-pc-cygwin/bin/ld: cannot find -lgcc_s /usr/lib/gcc/x86_64-pc-cygwin/4.8.2/../../../../x86_64-pc-cygwin/bin/ld: cannot find -lgcc /usr/lib/gcc/x86_64-pc-cygwin/4.8.2/../../../../x86_64-pc-cygwin/bin/ld: cannot find /usr/lib/gcc/x86_64-pc-cygwin/4.8.2/crtend.o: Too many open files collect2: error: ld returned 1 exit status Makefile:68: recipe for target 'mg' failed make: *** [mg] Error 1 make.out Description: Binary data cygcheck.out Description: Binary data -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation:
Re: bug in 'cs' value of Xterm termcap (was: Updated: screen 4.1.0-20130513-1)
Am 27.11.2013 23:14, schrieb matthew patton: For whatever reason I set my newly installed environment to use 'xterm' mode and ran across this bug. The archives led me to http://www.cygwin.com/ml/cygwin/2013-07/msg00029.html and specifically # Set the hardstatus prop on gui terms to set the titlebar/icon title termcapinfo xterm*|rxvt*|kterm*|Eterm*|cygwin hs:ts=\E]0;:fs=\007:ds=\E]0;\007 and wanted to mention that with both the -1 and -2 releases, even with the 'termcapinfo' override in the above post the hardstatus and caption lines end up 1 line off the bottom IFF $TERM=xterm be it in an honest to goodness X11 xterm or the windows terminal. This causes everything to fail to properly scroll. Once a single screen worth of output is sent, everything just gets put on the last line. This obviously is not a good thing. However if $TERM is any of 'cygwin', 'xterm-vt220', 'xterm-256color', 'vt100', or 'vt220' it works just fine since the offending 'cs' stanza is never set like below. termcap xterm|fptwist hs@:cs=\E[%i%d;%dr:im=\E[4h:ei=\E[4l terminfo xterm|fptwist hs@:cs=\E[%i%p1%d;%p2%dr:im=\E[4h:ei=\E[4l In my ~/.screenrc it was sufficient to use termcapinfo xterm* cs to restore correct behavior. Unfortunately I haven't a clue what the various escape sequences mean. The ts/fs/ds entries are a trick to mimick the window title as a pseudo hard status line. cs is the scrolling region. Not understanding your report completely (what is the -1 and -2 releases?), it could be that some application (maybe screen itself?) uses cs in the wrong way which produces exactly the described effect. I noticed myself recently that this can happen if cs is assumed to be just \E[%i%d;%dr without the %p1,%p2 items, which is kind of weird. Anyway, does it happen in a fresh terminal, then screen, then ls, or did you run any other applications before the bug occurs? -- Thomas -- 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: chere + mintty doesn't work with mapped drives
Dave wrote: Can you clarify which isn't working: a) a network share mapped to a drive letter, e.g N:\my\network\location This is my situation. I have my Y: drive mapped to a Linux Samba server. See more details below b) network share accessed via \\ e.g. \\server\path\my\network\location Not doing this. I think a) should always work. Sadly that is not my experience. Are you right clicking on a directory and selecting the menu item, or right clicking a blank spot in the RH pane? The two result in different logic, with the latter having to guess it's a network path. I am right clicking on a directory name in either (tried both) the LH or RH pane of an explore.exe window. In both cases what happens Is that a new window is launched (good) with an initial title of the form /bin/xhere /bin/bash.exe Y:\apps. After a brief pause, I see Starting /bin/bash.exe, than another brief pause and the window title changes to /cygdrive/c/WINDOWS/system32 and I get a Bash command prompt. The PWD is just what the title indicates (i.e. .../system32) You may be able to figure out what's going on by adding a few echos to /bin/xhere That a good tip. I didn't realize it was a script. I'll try that. Regards -- Charlie P.S. I'm also having trouble figuring out how to post replies to what I see on the web archive. I did NOT get any email reply to my prior post, it just showed up on the web archive (that was good). I carefully checked my spam quarantine areas several times to be sure. Actually my first post on this topic was my second attempt to post. I had to add myself to the white-list which I didn't notice at first since the white-list suggestion was stuck in MY stupid stupid Outlook spam filter (Thanks so much Outlook). In any event, I have cobbled together something that resembles a reply to an email that I have really scraped off the web archive. That seems awfully complicated. Surely I'm missing something. But I just cannot see the Reply button on the archive. Is this like when my wife says, its right there and points to it and yep, its really right there? :-( -- 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
what package is needed to compile .help files ?
Hi, what package is needed to compile .help files ? Many thanks in advance, Aaron -- 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
cpp gives various results depending on the path used
Hi, I looks like cpp gives various results depending on the path used. $ cpp --version cpp (GCC) 4.8.2 $ /lib/cpp dummy.c q; echo $? cpp: error: spawn: No such file or directory 1 $ /bin/cpp dummy.c q; echo $? cpp: error: spawn: No such file or directory 1 $ /usr/bin/cpp dummy.c q; echo $? 0 I get these results with both versions (x32 x64). I have restored the previous version (4.7.3) and it works fine. dummy.c only contains a #define. I hit this problem while trying to recompile bup after I done a CygWin's update. bup uses /lib/cpp. Regards, P.Rouleau -- Bjarne Stroustrup: “C makes it easy to shoot yourself in the foot; C++ makes it harder, but when you do it blows your whole leg off.” -- 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
[PATCH] 'rebase' uninitialised variable (was: Cygwin64: Rebase problems)
On 02/11/2013 11:06, David Stacey wrote: I'm trying to reinstall 64-bit Cygwin, using a snapshot taken on 2013-10-24. The post-install step goes into an infinite loop whilst running 'texlive-collection-basic.sh': perl is attempting to load some modules (IO.dll, MD5.dll, Fcnt.dll, Cwd.dll), which fail with rebase errors. The script waits five seconds before trying (and failing) again; this repeats ad infinitum. I am pleased to report that I have tracked down the cause of my rebase woes to an uninitialised variable in the 'rebase' package. A simple patch (attached) fixes the problem. Jason Tishler: As rebase maintainer, if you agree with my diagnosis then please could you make new versions of 'rebase' containing the fix for both architectures. Thank you. Dave. --- origsrc/rebase/rebase.c 2013-03-19 17:33:54.0 + +++ src/rebase/rebase.c 2013-11-29 18:32:08.760089000 + @@ -861,6 +861,7 @@ collect_image_info (const char *pathname img_info_list[img_info_size].slot_size = roundup2 (img_info_list[img_info_size].size, ALLOCATION_SLOT); img_info_list[img_info_size].flag.needs_rebasing = 1; + img_info_list[img_info_size].flag.cannot_rebase = 0; /* This back and forth from POSIX to Win32 is a way to get a full path more thoroughly. For instance, the difference between /bin and /usr/bin will be eliminated. */ -- 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
Updated, new for 64-bit: lftp 4.4.11-1
A new version of lftp, 4.4.11-1, is available in the Cygwin distribution. The is the first release of lftp for x86_64. lftp is a sophisticated file transfer program and ftp/http/bittorrent client. It supports multiple network protocols. It uses the readline library for input, so it offers tab completion and command history. It has job control and bookmarks. It can mirror sites and transfer multiple files in parallel. It keeps trying interrupted operations until it can complete them. 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://cygwin.com/lists.html#subscribe-unsubscribe Please read *all* of the information on unsubscribing that is available starting at this URL.
Updated: Cygwin 1.7.26
Hi Cygwin friends and users, I just released Cygwin 1.7.26. This release introduces a few new features but is mainly a bugfix release. To install 32-bit Cygwin use http://cygwin.com/setup-x86.exe To install 64 bit Cygwin use http://cygwin.com/setup-x86_64.exe The 64 bit Cygwin distribution doesn't yet come with as many packages as the 32 bit version, but more packages will be available over time. If you're already running a 32 bit version of Cygwin on 64 bit Windows machines, you can continue to do so. If you're planning a new install of Cygwin on a 64 bit Windows machine, consider to use the new 64 bit Cygwin version, unless you need certain packages not yet available in the 64 bit release. What's new: --- - getaddrinfo now supports glibc-specific International Domain Name (IDN) extension flags: AI_IDN, AI_CANONIDN, AI_IDN_ALLOW_UNASSIGNED, AI_IDN_USE_STD3_ASCII_RULES. - getnameinfo now supports glibc-specific International Domain Name (IDN) extension flags: NI_IDN, NI_IDN_ALLOW_UNASSIGNED, NI_IDN_USE_STD3_ASCII_RULES. - Preliminary, experimental support of the posix_spawn family of functions. New associated header /usr/include/spawn.h. What changed: - - Slightly improve randomness of /dev/random emulation. - Allow to use advisory locking on any device. POSIX fcntl and lockf locking works with any device, BSD flock locking only with devices backed by an OS handle. Right now this excludes console windows on pre Windows 8, as well as almost all virtual files under /proc from BSD flock locking. - The header /usr/include/exceptions.h, containing implementation details for 32 bit Windows' exception handling only, has been removed. Bug fixes: -- - pthread_atparent hook should not be called in the child. Fixes: http://cygwin.com/ml/cygwin/2013-09/msg00365.html - 64 bit only: Correctly mmap'ing regions 4 Gigs. Fixes: http://cygwin.com/ml/cygwin/2013-09/msg00155.html - Fix random content of /proc/$PID/ctty if the process has no controlling tty. Set to just \n instead. - Properly set process sid rather than always using -1. Fixes: http://cygwin.com/ml/cygwin/2013-10/threads.html#00237 - Fix a potential crash after calling lseek on /dev/clipboard. - Fix a handle inheritance bug in raw disk and tape device handling which led to EBADF errors in child processes. - open(/dev, O_CREAT) accidentally created a /dev file if no /dev exists at the time. - DIR *d = opendir (foo); flock (dirfd (d), ...); worked, but did the wrong thing. - Reading from /dev/windows was broken for some time. - select'ing on /dev/windows accidentally didn't take the setting of ioctl (WINDOWS_HWND) into account. - Fix typos in cygcheck which could crash Windows 8 and 8.1 machines. Fixes: http://cygwin.com/ml/cygwin/2013-11/msg00334.html - Show OS version correctly even on Windows 8.1 and Server 2012 R2. Fixes: http://cygwin.com/ml/cygwin/2013-11/msg00343.html - dup2() could crash in some cases for a destination = 256 Fixes: http://cygwin.com/ml/cygwin/2013-09/msg00397.html - Try to workaround the following problem: unlink(2) could fail, if the file was opened casesensitive and has to be moved to the recycler due to a sharing violation. Have fun, Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat
