public inbox for cygwin-xfree@sourceware.org help / color / mirror / Atom feed
From: Igor Pechtchanski <pechtcha@cs.nyu.edu> To: Thomas L Roche <tlroche@us.ibm.com> Cc: cygwin@cygwin.com, cygwin-xfree@cygwin.com Subject: Re: cygwin/xfree86/emacs problems after upgrading Date: Wed, 04 Feb 2004 21:21:00 -0000 [thread overview] Message-ID: <Pine.GSO.4.56.0402041611280.8094@slinky.cs.nyu.edu> (raw) In-Reply-To: <OFD70E339D.5F6BB4DD-ON85256E2F.006C6B14-85256E2F.0074424C@us.ibm.com> On Tue, 3 Feb 2004, Thomas L Roche wrote: > [snip] > Note that I run emacs via > > emacs --debug-init & > > from bash in an xterm which I launch with > > start XWin -multiwindow -clipboard -emulate3buttons Not quite. Judging from your cygcheck output, you use startxwin.bat. More below. > [snip] > However I'm also, again only since upgrading, having problems with > unzip, e.g. > > > inflating: > /d/eclipse/builds/20040121_1953-WB213-AD-V512D-00/eclipse/plugins/com.ibm.etools.j2ee.ui/build/pluginBuild/commonbld/com/ibm/etools/ejb/ui/presentation/EJBEditorOutlineContentProvider.class > > > 735 [main] unzip 1820 cmalloc: cmalloc returned NULL > > error: zipfile probably corrupt (segmentation violation) > > which I get even unzip'ing a known-good file (i.e. one that I unzip'ed > successfully before upgrading from 1.5.5-1). Do you have a small testcase that would allow others to reproduce this? Perhaps a (small) sample .zip file? > [snip] > So it seems plausible that there is also a (base) cygwin problem, which > might be causing the emacs and unzip problems. Or that the emacs and > unzip problems are unrelated. They most likely are unrelated. > What should I try next? I'd suspect the unzip issue has to do with the path length to the file. You can try confirming it by creating a file in a deeply nested directory, putting that one file in a .zip, and then trying to unzip it into some place even deeper in the directory hierarchy. Can't help you with the emacs issue, as I don't use emacs. > [snip] > (Note that cygcheck shows > > d:\cygwin\bin > d:\cygwin\usr\X11R6\bin > > at the head of my PATH; those dirs don't exist, and they're not in my > windows path.) This (and the existence of CYGWIN_ROOT in your environment) is an artifact of using startxwin.bat. Unless you have a default directory for the Cygwin root, you can't use that file OOTB -- you'll have to edit it and replace "\cygwin" with the value of your Cygwin root (in your case, "d:\ProgramFiles\Cygwin". > CYGWIN_ROOT = `\cygwin' Hope this helps, Igor -- http://cs.nyu.edu/~pechtcha/ |\ _,,,---,,_ pechtcha@cs.nyu.edu ZZZzz /,`.-'`' -. ;-;;,_ igor@watson.ibm.com |,4- ) )-,_. ,\ ( `'-' Igor Pechtchanski, Ph.D. '---''(_/--' `-'\_) fL a.k.a JaguaR-R-R-r-r-r-.-.-. Meow! "I have since come to realize that being between your mentor and his route to the bathroom is a major career booster." -- Patrick Naughton
next prev parent reply other threads:[~2004-02-04 21:21 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2004-02-03 21:10 Thomas L Roche 2004-02-04 21:21 ` Igor Pechtchanski [this message] 2004-02-05 0:18 Harold L Hunt II 2004-02-05 0:48 ` Igor Pechtchanski 2004-02-26 17:46 ` Takuma Murakami 2004-02-26 20:53 ` Igor Pechtchanski 2004-02-27 8:41 ` Igor Pechtchanski [not found] <mailman.1828.1075842639.928.help-gnu-emacs@gnu.org> 2004-02-08 8:51 ` Jari Aalto+mail.linux
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=Pine.GSO.4.56.0402041611280.8094@slinky.cs.nyu.edu \ --to=pechtcha@cs.nyu.edu \ --cc=cygwin-xfree@cygwin.com \ --cc=cygwin@cygwin.com \ --cc=tlroche@us.ibm.com \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).