Re: Emacs is coming back - all pleased?
Eric Blake writes: According to Angelo Graziosi on 7/19/2007 8:51 AM: 1) Emacs22 depend on xemacs-emacs-common which depend from xemacs: WHY to install emacs one should install XEmacs ? That sounds like a backwards dependency. Volker, shouldn't it be that xemacs depends on xemacs-emacs-common, and that xemacs-emacs-common is standalone? If you agree, I can change the setup.hints. You're right, my fault. I don't have sourceware access today. So please change the setup hint. (also from the xemacs test version please) Ciao Volker
Re: Emacs is coming back - all pleased?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 According to Dr. Volker Zell on 7/20/2007 2:17 AM: That sounds like a backwards dependency. Volker, shouldn't it be that xemacs depends on xemacs-emacs-common, and that xemacs-emacs-common is standalone? If you agree, I can change the setup.hints. You're right, my fault. I don't have sourceware access today. So please change the setup hint. (also from the xemacs test version please) Done for both xemacs and xemacs-emacs-common. Now downloading emacs won't pull in xemacs. - -- Don't work too hard, make some time for fun as well! Eric Blake [EMAIL PROTECTED] -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (Cygwin) Comment: Public key at home.comcast.net/~ericblake/eblake.gpg Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFGoK7T84KuGfSFAYARAtPlAJ9ByDW7Kz/Jz1X1DenooNIiL5J/ewCePZLU ifS5tSSX1QYS4zJHT7hG41E= =AHJm -END PGP SIGNATURE-
Simple patch to enable stereo visuals in XWin_GL
Hi. I was wondering who maintains the experimental accelerated GLX support in Cygwin/X. I have a simple patch which enables stereo visuals (necessary to support my project, VirtualGL) on systems that support stereo. I'd like to get this patch incorporated into the Cygwin distribution of XWin_GL, if possible. Darrell -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/
[ANNOUNCEMENT] Updated: perl-5.8.8-4
The cygwin perl packages perl and perl_manpages have been updated to
revision 5.8.8-4.
This fixes the reported versiononly issue and adds documents into
/usr/share/doc/perl-5.8.8.
The versiononly issue led to incorrect dependencies on versioned scripts
(5.8.8 suffix), failing with e.g. perldoc.
perl-5.8.8 cygwin notes:
There are no changes intentionally incompatible with 5.8.7. If any
exist, they are bugs and reports are welcome. No XS module needs a
recompilation.
Additionally several modules have been added to vendor_perl.
Note: Previously installed modules in site_perl have higher precedence.
See http://www.perl.org/
ChangeLog: http://perldoc.perl.org/perl588delta.html
Old vendor patches:
* CYG01 - hints.cygwin.sh ldflags -s
* CYG03 - lib-Test-Harness-Straps $ENV{PERL5LIB} = ''
* CYG04 - major.version.cygwin.sh cygperl-5_8.dll and not
cygperl-5_8_x.dll
* CYG05 - add Win32CORE to core
Added new vendor patches:
* fixed installperl for CYG04
* CYG02 - lib-ExtUtils-Embed insensitive against leading \\s
* CYG07 - File-Spec-Cygwin-TMPDIR.patch
* Bug#38628 - allow legacy Cwd-cwd()
* Bug#40103 - File-Spec-case_tolerant.patch from 5.9.5
Detailed NEWS from README
-
5.8.8-4
- fix the reported versiononly issue
- adds documents and Changes into /usr/share/doc/perl-5.8.8
- upload new setup.hint
5.8.8-3
- Maintainer change from Gerrit Haase to Reini Urban.
- fixed installperl for the pl-CYG04major.version.cygwin.sh.patch
(skipping lib and pods).
- added #40103 - File-Spec-case_tolerant.patch from 5.9.5
- added #38628 Cwd-cwd() patch, but not the full cygwin-path.patch
posted to p5p
- added File-Spec-Cygwin-TMPDIR.patch
- added several backports for failing testsuite cases.
- Adjust the perlcygwin documentation for ntsec, cygserver and Unicode
limitations.
- included more vendor_perl packages compared to 5.8.7 (without
comment they are all new).
Rationale: Same local vendor_perl packages included as in 5.8.7,
plus some of the new CPAN packages which went to core with 5.9.5,
Bundle::CPAN, CPAN::Reporter, Module::Build, Par::Dist,
for a full CPAN bootstrap, the new libXML packages,
and some almost-core dependencies.
Win32API-File-0.1001
Pod-Simple-3.05 Test-Pod-1.26 Pod-Coverage-0.18
Test-Pod-Coverage-1.08
IO-Compress-Base-2.005
Compress-Raw-Zlib-2.005 IO-Compress-Zlib-2.005
Compress-Zlib-2.005 (updated from 1.41)
Compress-Raw-Bzip2-2.005 IO-Compress-Bzip2-2.005
Compress-Bzip2-2.09 (same)
IO-Zlib-1.05 (updated from 1.04)
IO-String-1.08 (updated from 1.07)
Archive-Tar-1.32 (updated from 1.26, but without bin)
Archive-Zip-1.20
MD5-2.03 (same)
Term-ReadLine-Perl-1.0302 (updated from 1.0203)
Term-ReadLine-Gnu-1.16 TermReadKey-2.30 (same)
XML-NamespaceSupport-1.09 XML-SAX-0.15 XML-LibXML-Common-0.13
XML-LibXML-1.63
XML-Parser-2.34 (same)
Proc-ProcessTable-0.41 (updated from 0.40)
File-Temp-0.18 YAML-0.62
Config-Tiny-2.10 File-Copy-Recursive-0.33 IPC-Run3-0.037
Probe-Perl-0.01
Tee-0.13 IO-CaptureOutput-1.03 File-pushd-0.99 File-HomeDir-0.65
Digest-SHA-5.45
Module-Signature-0.55 Devel-Symdump-2.07
URI-1.35 HTML-Tagset-3.10 HTML-Parser-3.56 libwww-perl-5.805
CPAN-1.9102
Test-Reporter-1.27 CPAN-Reporter-0.44
Net-Telnet-3.03 (same)
Module-ScanDeps-0.75 PAR-Dist-0.23
ExtUtils-CBuilder-0.19 ExtUtils-ParseXS-2.18 Regexp-Common-2.120
version-0.7203 podlators-2.0.5 Pod-Readme-0.09
Module-Build-0.2808
B-Generate-1.09 PadWalker-1.5 Alias-2.32
- removed /usr/bin/ptar and /usr/bin/ptardiff, and subsequently
Algorithm-Diff-1.1902 Text-Diff-0.35. If you want these binaries
install Archive::Tar via cpan
- PAR is not included because of /usr/bin/pp, impolite namespace
pollution. But since the PAR::Dist is included the tight version
dependency problems should have gone.
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:
[EMAIL PROTECTED]
If you need more information on unsubscribing, start reading here:
http://sources.redhat.com/lists.html#unsubscribe-simple
Please read *all* of the information on unsubscribing that is available
starting at this URL.
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports:
Re: Emacs is coming back - all pleased?
Angelo Graziosi [EMAIL PROTECTED] writes: 2) XEmacs comes with AUCTEX, so if one should use xemacs-emacs-common, WHY not adding auctex to it? Alternatively Emacs22 should have its own AUCTEX package. The compilations for Emacs and XEmacs are incompatible. In general, sharing packages between Emacs and XEmacs makes little sense, since the editors both expect .el files and .elc files to be in the same directory, and the .elc files are incompatible. So Emacs22 should have its own AUCTeX package. In my opinion as AUCTeX maintainer, so should XEmacs: the AUCTeX packaged with XEmacs is utterly outdated and quite unmaintained. The AUCTeX project provides an up-to-date XEmacs package on its download page URL:http://www.gnu.org/software/auctex/download.html. Due to policy reasons (in the name of quality assurance), the XEmacs project will not distribute this package actively maintained by upstream. Anyway: it would be infeasible to share AUCTeX between both editors (as a note aside: Debian has devised a system for sharing packages which suffers from the problem that neither Emacs/XEmacs developers nor Emacs/XEmacs itself properly understand it, and I have my doubts that the Debian people in charge of it do, either), and using the old buggy AUCTeX distributed as part of XEmacs' sumo tarball would be an extremely bad idea, anyway. -- David Kastrup -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: Emacs is coming back - all pleased?
David Kastrup wrote: Angelo Graziosi Angelo dot Graziosi@ DO_NOT writes: Sorry, but you should not cite my address explicitly! (Have you hear of spammers?) Angelo. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: alias command in Midnight Commander
Hello, Original-Nachricht Datum: Wed, 18 Jul 2007 20:16:26 +0200 Von: dIna An: cygwin@cygwin.com Betreff: alias command in Midnight Commander I'va installed mc version 4.6.1 using cygwin setup. In mc alias command doesn't work. ex: $ alias mytest='echo test' $ mytest /bin/bash: mytest: command not found When I quit mc and resent the commands on shell it works. Any idea? The subshell feature of MC is disabled by default on Cygwin - so a new shell is spawned each time you execute a command trough the command line widget in MC and your changes are immediately lost. Run MC by passing it the -U command line option and it should work as expected. -- Ist Ihr Browser Vista-kompatibel? Jetzt die neuesten Browser-Versionen downloaden: http://www.gmx.net/de/go/browser -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: Problem with ping in Windows Vista
Well, obviously it has nothing to do with Cygwin (also not with IP Helper), but it's because Windows Firewall. To solve this (with firewall on), I defined a new Inbound Rule for Windows Firewall, which accepts all inbound ICMP packets. Thanks to Dave Korn for the hint! Cheers, Arthur N. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: SOLUTION: Own Compiled Program Immediately Crashes on Startup
Jove is an Emacs like editor. As such it uses the key sequence CONTROL-X CONTROL-C (^X^C) for leaving the editor. In Cygwin however ^C still sends the interrupt signal to the editor. However the keystroke ^C should have been changed to not sending that signal. On most platforms that works - but not in Cygwin. Try adding 'tty' to the CYGWIN environment variable. Or use rxvt/xterm/etc. These are two different ways of achieving the same outcome, namely that the program will be attached to a unix-style pty instead of a Windows console. Adding tty to the CYGWIN environment variable solved the problem. The editor is running very fine now. Thanks a lot to all of you for your help. Hans -- GMX FreeMail: 1 GB Postfach, 5 E-Mail-Adressen, 10 Free SMS. Alle Infos und kostenlose Anmeldung: http://www.gmx.net/de/go/freemail -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
OpenSSH on Windows XP SP2 problems
Ok, I'm about at wits end on this one I can't seem to figure out what's going on. I've had the openssh server running on the same version of windows (Windows XP Pro SP2 fully patched) for quite some time. The first time I installed it using the instructions at http:// pigtail.net/LRP/printsrv/cygwin-sshd.html which worked beautifully. This time however, I'm having issues. After following the instructions I was first presented with issues dealing with the privilege separation feature. I've got those worked out and now have a more serious trouble that I'm not sure where to proceed from here. Now, when I try to start the sshd daemon (using debug mode) I get the following message: debug1: sshd version OpenSSH_4.6p1 debug1: read PEM private key done: type RSA debug1: private host key: #0 type 1 RSA debug1: read PEM private key done: type DSA debug1: private host key: #1 type 2 DSA debug1: rexec_argv[0]='/usr/sbin/sshd' debug1: rexec_argv[1]='-D' debug1: rexec_argv[2]='-d' debug1: Bind to port 22 on 0.0.0.0. Bind to port 22 on 0.0.0.0 failed: Bad address. Cannot bind any address. I've tried explicitly adding my IP address with the ListenAddress directive in the /etc/sshd_config file. I've tried altering the port number to a non-privileged port. I can't seem to get anything to work. I'm running the latest version of cygwin from cygwin.com. I did download another project OpenSSH for windows, which seems to be based off cygwin. It used an older version of openssh as well as the cygwin DLL, I believe, as they didn't really like having each other installed at the same time. However, the OpenSSH for windows worked as far as getting the service to load and accept connections. So I'm not sure where the root cause of the problem lies in this case. Is it a bug in this version of OpenSSH (doubtful because I've been running a similar or same version for months before I reloaded)? Is it an OS permissions problem (not sure, as I'm a UNIX geek and don't know windows internals very well)? Is it a cygwin DLL bug(I'd expect to have found more information on this, if that were the case)? Any help is greatly appreciated. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
RE: OpenSSH on Windows XP SP2 problems
On 20 July 2007 16:25, Michael Grubb wrote: Ok, I'm about at wits end on this one I can't seem to figure out what's going on. I've had the openssh server running on the same version of windows (Windows XP Pro SP2 fully patched) for quite some time. The first time I installed it using the instructions at http:// pigtail.net/LRP/printsrv/cygwin-sshd.html which worked beautifully. This time however, I'm having issues. After following the instructions I was first presented with issues dealing with the privilege separation feature. I've got those worked out and now have a more serious trouble that I'm not sure where to proceed from here. Ok, so you followed a bunch of non-standard and unsupported instructions to install sshd, then something happened which you don't tell us anything about except that it was to do with privsep, then you did some other stuff to it that you also don't tell us about it, but apparently it solved whatever it was that was the problem that you didn't tell us about, and now it doesn't work. So the answer is It could be a problem in one of the bits you didn't tell us about. Or it might not. debug1: Bind to port 22 on 0.0.0.0. Bind to port 22 on 0.0.0.0 failed: Bad address. Cannot bind any address. I've tried explicitly adding my IP address with the ListenAddress directive in the /etc/sshd_config file. I've tried altering the port number to a non-privileged port. I can't seem to get anything to work. I'm running the latest version of cygwin from cygwin.com. Have you allowed an exception for sshd in the windows firewall? I did download another project OpenSSH for windows, which seems to be based off cygwin. It used an older version of openssh as well as the cygwin DLL, I believe, as they didn't really like having each other installed at the same time. Yes, that's pretty much guaranteed fatal. Have you removed this older version? Is it in the PATH settings? More vital information you don't seem to think anybody would need... So I'm not sure where the root cause of the problem lies in this case. Owing to the lack of information and the vast number of unknowns in your description of the problem, neither is anyone else! If it isn't a firewall configuration issue, it could be any number of things; a good place to start would be by sending your cygcheck output as an attachment with your next post, as described at http://cygwin.com/problems.html. cheers, DaveK -- Can't think of a witty .sigline today -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: OpenSSH on Windows XP SP2 problems
On 07/20/2007, Michael Grubb wrote: I'm about at wits end on this one I can't seem to figure out what's going on. I've had the openssh server running on the same version of windows (Windows XP Pro SP2 fully patched) for quite some time. The first time I installed it using the instructions at http://pigtail.net/LRP/printsrv/cygwin-sshd.html which worked beautifully. This time however, I'm having issues. After following the instructions I was first presented with issues dealing with the privilege separation feature. I've got those worked out and now have a more serious trouble that I'm not sure where to proceed from here. Sorry but if you're going to use instructions for configuration from another site, then you need to address problems that you encounter using those instructions to that site/author. This list can't support content of every site out there that posts Cygwin information. If you want to configure OpenSSH, as installed via 'setup.exe', in the supported way, please read and follow the configuration instructions found in '/usr/share/doc/Cygwin/openssh.README'. If you have problems with this procedure, then this would be the list to ask for help in that case. -- Larry Hall http://www.rfk.com RFK Partners, Inc. (508) 893-9779 - RFK Office 216 Dalton Rd. (508) 893-9889 - FAX Holliston, MA 01746 _ A: Yes. Q: Are you sure? A: Because it reverses the logical flow of conversation. Q: Why is top posting annoying in email? -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: SOLUTION: Own Compiled Program Immediately Crashes on Startup
On Thu, 19 Jul 2007, Brian Dessent wrote: Hans Streibel wrote: Jove is an Emacs like editor. As such it uses the key sequence CONTROL-X CONTROL-C (^X^C) for leaving the editor. In Cygwin however ^C still sends the interrupt signal to the editor. However the keystroke ^C should have been changed to not sending that signal. On most platforms that works - but not in Cygwin. I can't tell right now what mechanism Jove is using for handling the terminal under Cygwin. There so many mechanisms: struct termio, struct termios, struct sgttyb. Jove under Cygwin follows BSD POSIX. Try adding 'tty' to the CYGWIN environment variable. Or use rxvt/xterm/etc. These are two different ways of achieving the same outcome, namely that the program will be attached to a unix-style pty instead of a Windows console. You know, I was sure this was an FAQ, and was about to reply pointing that out, but decided to check, and couldn't find any mention of the Ctrl-C problem and the CYGWIN=tty or non-console window solution, with or without emacs. Does someone want to rectify this omission by sending a patch against the FAQ sources? Igor -- http://cs.nyu.edu/~pechtcha/ |\ _,,,---,,_[EMAIL PROTECTED] | [EMAIL PROTECTED] ZZZzz /,`.-'`'-. ;-;;,_Igor Peshansky, Ph.D. (name changed!) |,4- ) )-,_. ,\ ( `'-' old name: Igor Pechtchanski '---''(_/--' `-'\_) fL a.k.a JaguaR-R-R-r-r-r-.-.-. Meow! Belief can be manipulated. Only knowledge is dangerous. -- Frank Herbert -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: OpenSSH on Windows XP SP2 problems
On Jul 20, 2007, at 10:37 AM, Dave Korn wrote: On 20 July 2007 16:25, Michael Grubb wrote: Ok, I'm about at wits end on this one I can't seem to figure out what's going on. BTW, this was an I'm frustrated and pulling my hair out please help, not an I'm angry this is broke, fix it. I've had the openssh server running on the same version of windows (Windows XP Pro SP2 fully patched) for quite some time. The first time I installed it using the instructions at http:// pigtail.net/LRP/printsrv/cygwin-sshd.html which worked beautifully. This time however, I'm having issues. After following the instructions I was first presented with issues dealing with the privilege separation feature. I've got those worked out and now have a more serious trouble that I'm not sure where to proceed from here. Ok, so you followed a bunch of non-standard and unsupported instructions to install sshd, then something happened which you don't tell us anything about except that it was to do with privsep, then you did some other stuff to it that you also don't tell us about it, but apparently it solved whatever it was that was the problem that you didn't tell us about, and now it doesn't work. So the answer is It could be a problem in one of the bits you didn't tell us about. Or it might not. To clarify the OP: I had this configuration working on a previous installation. To my knowledge they were the same versions of cygwin/openssh as what I'm running now. If they weren't the same versions, it couldn't be far off at any rate. I had to reload my OS from the ground up. I am now getting an error regarding not able to bind to any address. No, I did what /usr/share/doc/Cygwin/openssh.README says to do (but took instruction from someone who actually knows how to write configuration documentation. The contents of openssh.README is certainly informative, but contains no true instruction. At least not how to configure the server process in an easy to follow format. That file says to use the ssh-host-config script, which I did. It installed a windows service, and just as your documentation suggests it is running sshd with the -D option (or so cygrunsrv -Q sshd suggests). I'm sorry but if you want folks to follow your instructions then perhaps you should improve them to be a bit more instructive. As for elaborating on the privilege separation issue, there seemed no need. I've determined through my own troubleshooting that it isn't the culprit. Or perhaps I should say I'm no longer getting an error message. But, to deal with the privilege separation issues I've tried two approaches. First, I fixed the ownerships on /var/empty to be system.system, that halted the error messages regarding privilege separation. Then I started getting the messages I pasted in my original post, about not binding to any address. I took the additional step to disable privilege separation altogether thinking that it may be causing some behind the scenes problems. That didn't help. debug1: Bind to port 22 on 0.0.0.0. Bind to port 22 on 0.0.0.0 failed: Bad address. Cannot bind any address. I've tried explicitly adding my IP address with the ListenAddress directive in the /etc/sshd_config file. I've tried altering the port number to a non-privileged port. I can't seem to get anything to work. I'm running the latest version of cygwin from cygwin.com. Have you allowed an exception for sshd in the windows firewall? Yes, I have added both a program and a port exception, neither of which has caused any change. I did download another project OpenSSH for windows, which seems to be based off cygwin. It used an older version of openssh as well as the cygwin DLL, I believe, as they didn't really like having each other installed at the same time. Yes, that's pretty much guaranteed fatal. Have you removed this older version? Is it in the PATH settings? More vital information you don't seem to think anybody would need... Yes, I have removed the other product from the system completely. I have ensured that no other cygwin1.DLL file is present on the system (aside from c:\cygwin\bin\cygwin1.dll). I did fail to mention in the OP that I had completely removed the other product, it is no longer causing conflicts. I included that information to show that I can get other versions of ssh/cygwin to work just not this particular combination on this particular installation of the OS for some reason. Also an excerpt of one of the event log entries for the failed service start attempt: The following information is part of the event: sshd: PID 2700: `sshd' service stopped, exit status: 255. I've also attached the requested output of cygcheck -s -v -r. So I'm not sure where the root cause of the problem lies in this case. Owing to the lack of information and the vast number of unknowns in your description of the problem, neither is
RE: OpenSSH on Windows XP SP2 problems
On 20 July 2007 19:08, Michael Grubb wrote: To clarify the OP: I had this configuration working on a previous installation. To my knowledge they were the same versions of cygwin/openssh as what I'm running now. If they weren't the same versions, it couldn't be far off at any rate. I had to reload my OS from the ground up. I am now getting an error regarding not able to bind to any address. To clarify the problem: we still don't know what that configuration was. Telling us it's the same now as it was before you reinstalled the OS gives us no further information on top of the zero you've already given us. No, I did what /usr/share/doc/Cygwin/openssh.README says to do (but took instruction from someone who actually knows how to write configuration documentation. The contents of openssh.README is certainly informative, but contains no true instruction. At least not how to configure the server process in an easy to follow format. That file says to use the ssh-host-config script, which I did. Telling you to use that script *is* true instruction, and what's more, you appear to have comprehended and followed that instruction perfectly well. suggests). I'm sorry but if you want folks to follow your instructions then perhaps you should improve them to be a bit more instructive. It said to use the script, you used the script, what more are you asking for? Now you say that they need to be more instructive, but without actually explaining what problem you had with them. You're not actually trying to get help, are you? You won't tell anyone any details about what's wrong, you just want to whine about how awful we all are. Well, you go right ahead and get it all off your chest. Hope you find it satisfying. Doubt you'll find it effective, though. cheers, DaveK -- Can't think of a witty .sigline today -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
CVS path_conv build error
FYI: g++ -L/home/ford/downloads/cygb2/i686-pc-cygwin/winsup -L/home/ford/downloads/cygb2/i686-pc-cygwin/winsup/cygwin -L/home/ford/downloads/cygb2/i686-pc-cygwin/winsup/w32api/lib -isystem /home/ford/downloads/cygwin/winsup/include -isystem /home/ford/downloads/cygwin/winsup/cygwin/include -isystem /home/ford/downloads/cygwin/winsup/w32api/include -B/home/ford/downloads/cygb2/i686-pc-cygwin/newlib/ -isystem /home/ford/downloads/cygb2/i686-pc-cygwin/newlib/targ-include -isystem /home/ford/downloads/cygwin/newlib/libc/include -c -nostdinc++-g -O2 -MMD -DHAVE_DECL_GETOPT=0 -D__OUTSIDE_CYGWIN__ -DSYSCONFDIR=\/install/etc\ -Wall -Wstrict-aliasing -Wwrite-strings -fno-common -pipe -fbuiltin -fmessage-length=0 -I. -I/home/ford/downloads/cygwin/winsup/cygwin -I/home/ford/downloads/cygwin/winsup/w32api/include -I/usr/lib/gcc/i686-pc-cygwin/3.4.4/include -fno-rtti -fno-exceptions -o ./bsd_helper.o ../../../../cygwin/winsup/cygserver/bsd_helper.cc In file included from ../../../../cygwin/winsup/cygserver/bsd_helper.cc:27: /home/ford/downloads/cygwin/winsup/cygwin/security.h:338: error: `path_conv' has not been declared /home/ford/downloads/cygwin/winsup/cygwin/security.h:339: error: ISO C++ forbids declaration of `parameter' with no type /home/ford/downloads/cygwin/winsup/cygwin/security.h:340: error: `path_conv' has not been declared /home/ford/downloads/cygwin/winsup/cygwin/security.h:341: error: ISO C++ forbids declaration of `parameter' with no type /home/ford/downloads/cygwin/winsup/cygwin/security.h:343: error: `path_conv' has not been declared /home/ford/downloads/cygwin/winsup/cygwin/security.h:343: error: ISO C++ forbids declaration of `parameter' with no type /home/ford/downloads/cygwin/winsup/cygwin/security.h:344: error: `path_conv' has not been declared /home/ford/downloads/cygwin/winsup/cygwin/security.h:344: error: ISO C++ forbids declaration of `parameter' with no type /home/ford/downloads/cygwin/winsup/cygwin/security.h:347: warning: `__stdcall__' attribute only applies to function types /home/ford/downloads/cygwin/winsup/cygwin/security.h:347: error: `path_conv' was not declared in this scope /home/ford/downloads/cygwin/winsup/cygwin/security.h:347: error: expected primary-expression before ',' token /home/ford/downloads/cygwin/winsup/cygwin/security.h:347: error: expected primary-expression before int /home/ford/downloads/cygwin/winsup/cygwin/security.h:347: error: initializer expression list treated as compound expression /home/ford/downloads/cygwin/winsup/cygwin/security.h:359: error: `path_conv' has not been declared /home/ford/downloads/cygwin/winsup/cygwin/security.h:359: error: ISO C++ forbids declaration of `parameter' with no type /home/ford/downloads/cygwin/winsup/cygwin/security.h:360: error: `path_conv' has not been declared /home/ford/downloads/cygwin/winsup/cygwin/security.h:360: error: ISO C++ forbids declaration of `parameter' with no type make[3]: *** [bsd_helper.o] Error 1 -- Brian Ford Lead Realtime Software Engineer VITAL - Visual Simulation Systems FlightSafety International the best safety device in any aircraft is a well-trained crew... -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: CVS path_conv build error
Brian Ford Brian.Ford at FlightSafety.com writes:
In file included from
../../../../cygwin/winsup/cygserver/bsd_helper.cc:27:
/home/ford/downloads/cygwin/winsup/cygwin/security.h:338: error:
`path_conv' has not been declared
I worked around it like this, although including path.h would also do the
trick.
Index: security.h
===
RCS file: /cvs/src/src/winsup/cygwin/security.h,v
retrieving revision 1.88
diff -u -p -r1.88 security.h
--- security.h 20 Jul 2007 14:29:43 - 1.88
+++ security.h 20 Jul 2007 19:57:03 -
@@ -66,6 +66,8 @@ details. */
#endif /* ! SE_CREATE_TOKEN_PRIVILEGE */
+struct path_conv;
+
/* Added for debugging purposes. */
typedef struct {
BYTE Revision;
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
Updated: perl-5.8.8-4
The cygwin perl packages perl and perl_manpages have been updated to
revision 5.8.8-4.
This fixes the reported versiononly issue and adds documents into
/usr/share/doc/perl-5.8.8.
The versiononly issue led to incorrect dependencies on versioned scripts
(5.8.8 suffix), failing with e.g. perldoc.
perl-5.8.8 cygwin notes:
There are no changes intentionally incompatible with 5.8.7. If any
exist, they are bugs and reports are welcome. No XS module needs a
recompilation.
Additionally several modules have been added to vendor_perl.
Note: Previously installed modules in site_perl have higher precedence.
See http://www.perl.org/
ChangeLog: http://perldoc.perl.org/perl588delta.html
Old vendor patches:
* CYG01 - hints.cygwin.sh ldflags -s
* CYG03 - lib-Test-Harness-Straps $ENV{PERL5LIB} = ''
* CYG04 - major.version.cygwin.sh cygperl-5_8.dll and not
cygperl-5_8_x.dll
* CYG05 - add Win32CORE to core
Added new vendor patches:
* fixed installperl for CYG04
* CYG02 - lib-ExtUtils-Embed insensitive against leading \\s
* CYG07 - File-Spec-Cygwin-TMPDIR.patch
* Bug#38628 - allow legacy Cwd-cwd()
* Bug#40103 - File-Spec-case_tolerant.patch from 5.9.5
Detailed NEWS from README
-
5.8.8-4
- fix the reported versiononly issue
- adds documents and Changes into /usr/share/doc/perl-5.8.8
- upload new setup.hint
5.8.8-3
- Maintainer change from Gerrit Haase to Reini Urban.
- fixed installperl for the pl-CYG04major.version.cygwin.sh.patch
(skipping lib and pods).
- added #40103 - File-Spec-case_tolerant.patch from 5.9.5
- added #38628 Cwd-cwd() patch, but not the full cygwin-path.patch
posted to p5p
- added File-Spec-Cygwin-TMPDIR.patch
- added several backports for failing testsuite cases.
- Adjust the perlcygwin documentation for ntsec, cygserver and Unicode
limitations.
- included more vendor_perl packages compared to 5.8.7 (without
comment they are all new).
Rationale: Same local vendor_perl packages included as in 5.8.7,
plus some of the new CPAN packages which went to core with 5.9.5,
Bundle::CPAN, CPAN::Reporter, Module::Build, Par::Dist,
for a full CPAN bootstrap, the new libXML packages,
and some almost-core dependencies.
Win32API-File-0.1001
Pod-Simple-3.05 Test-Pod-1.26 Pod-Coverage-0.18
Test-Pod-Coverage-1.08
IO-Compress-Base-2.005
Compress-Raw-Zlib-2.005 IO-Compress-Zlib-2.005
Compress-Zlib-2.005 (updated from 1.41)
Compress-Raw-Bzip2-2.005 IO-Compress-Bzip2-2.005
Compress-Bzip2-2.09 (same)
IO-Zlib-1.05 (updated from 1.04)
IO-String-1.08 (updated from 1.07)
Archive-Tar-1.32 (updated from 1.26, but without bin)
Archive-Zip-1.20
MD5-2.03 (same)
Term-ReadLine-Perl-1.0302 (updated from 1.0203)
Term-ReadLine-Gnu-1.16 TermReadKey-2.30 (same)
XML-NamespaceSupport-1.09 XML-SAX-0.15 XML-LibXML-Common-0.13
XML-LibXML-1.63
XML-Parser-2.34 (same)
Proc-ProcessTable-0.41 (updated from 0.40)
File-Temp-0.18 YAML-0.62
Config-Tiny-2.10 File-Copy-Recursive-0.33 IPC-Run3-0.037
Probe-Perl-0.01
Tee-0.13 IO-CaptureOutput-1.03 File-pushd-0.99 File-HomeDir-0.65
Digest-SHA-5.45
Module-Signature-0.55 Devel-Symdump-2.07
URI-1.35 HTML-Tagset-3.10 HTML-Parser-3.56 libwww-perl-5.805
CPAN-1.9102
Test-Reporter-1.27 CPAN-Reporter-0.44
Net-Telnet-3.03 (same)
Module-ScanDeps-0.75 PAR-Dist-0.23
ExtUtils-CBuilder-0.19 ExtUtils-ParseXS-2.18 Regexp-Common-2.120
version-0.7203 podlators-2.0.5 Pod-Readme-0.09
Module-Build-0.2808
B-Generate-1.09 PadWalker-1.5 Alias-2.32
- removed /usr/bin/ptar and /usr/bin/ptardiff, and subsequently
Algorithm-Diff-1.1902 Text-Diff-0.35. If you want these binaries
install Archive::Tar via cpan
- PAR is not included because of /usr/bin/pp, impolite namespace
pollution. But since the PAR::Dist is included the tight version
dependency problems should have gone.
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:
[EMAIL PROTECTED]
If you need more information on unsubscribing, start reading here:
http://sources.redhat.com/lists.html#unsubscribe-simple
Please read *all* of the information on unsubscribing that is available
starting at this URL.
