Re: Removing old source packages
On Fri, Jun 06, 2003 at 03:52:18PM +0100, andrew brian clegg wrote: > On Fri, 6 Jun 2003, Igor Pechtchanski wrote: > > N.B.: the above will not apply as soon as the RPM package is used, since > > that package apparently uses a subdirectory in /usr/src as the RPM > > repository, so beware. > > One subdir for rpm as a whole, or one subdir for each package it manages? If you have the rpm-devel package installed, leave /usr/src/rpm alone. RPM uses this directory to build packages. -- Dario Alcocer -- Sr. Software Developer, Helix Digital Inc. [EMAIL PROTECTED] -- http://www.helixdigital.com -- 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 suspending "man bash" (intermittent)
On Wed, May 28, 2003 at 11:13:41AM -0400, Lev Bishop wrote: > Windows XP home edition > GNU bash, version 2.05b.0(9)-release (i686-pc-cygwin) > cygwin dll version 1.3.22 > cygcheck -s -v -r attached > > So I have observed a strange phenomenon, where if I execute "man bash" in > (using bash) and then suspend with ^Z, maybe one time in 4 there > is a situation where the first keypress after the suspend still somehow > gets sent to less rather than to the shell. Subsequently the shell works > fine but when I "fg man" it only wants to draw the display a line at a > time (ie it never refreshes the screen, even with ^L). Strangely, this > behaviour happens much more frequently for "man bash" from xterm and not > from the console, and even more strangely it seems much more likely to > happen with the bash man page instead of others, though I have > occasionally seen it with, eg, "man man". If you're looking to reproduce > it, for me the best way is "man bash" from an xterm then repeatedly ^Z and > "fg" until this happens (usually after 4 or 5 tries). I tried reproducing this, but I don't get the same exact results. For me, it takes 7 or 8 tries, and all I get is a missing '[1]+ Stopped' message from bash; the next keystrokes still go to bash, though. The problem seems to go away if I use 'fg' instead of 'fg man'. I was not able to It looks like some sort of race condition in the signal handling, but I couldn't tell you where (cygwin, bash, less) it is. If you have access to a Unix machine, it might be interesting to see if you can reproduce this. Who knows, it might turn out to be a bash bug. -- Dario Alcocer -- Sr. Software Developer, Helix Digital Inc. [EMAIL PROTECTED] -- http://www.helixdigital.com -- 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 suspending "man bash" (intermittent)
On Thu, May 29, 2003 at 05:04:26AM -0700, Dario Alcocer wrote: > I tried reproducing this, but I don't get the same exact results. For > me, it takes 7 or 8 tries, and all I get is a missing '[1]+ Stopped' > message from bash; the next keystrokes still go to bash, though. The > problem seems to go away if I use 'fg' instead of 'fg man'. I was not > able to s/I was not\nable to// -- Dario Alcocer -- Sr. Software Developer, Helix Digital Inc. [EMAIL PROTECTED] -- http://www.helixdigital.com -- 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/
RPM support (was Re: qmail port successfull)
On Thu, May 29, 2003 at 11:28:14AM -0400, Igor Pechtchanski wrote: > On Thu, 29 May 2003, Lapo Luchini wrote: > > This reminds me that maybe it could be cool to have an "install" option > > in "type 2 packages" that installs them directly, without bothering to > > have a "fake" local setup.ini, starting setup, let it install the > > package... this would need some command line "installed package db" > > management of some kind. Or it is already out there, only I didn't > > notice it? > > Isn't that what the RPM port eventually hopes to accomplish? ;-) Yes, at least those are /my/ plans. FWIW, I hoping to use apt-rpm. -- Dario Alcocer -- Sr. Software Developer, Helix Digital Inc. [EMAIL PROTECTED] -- http://www.helixdigital.com -- 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 suspending "man bash" (intermittent)
On Thu, May 29, 2003 at 11:02:59PM -0400, Lev Bishop wrote: > Here follow detailed results of my experimenting. > > Send the manpage to a file: > $ man bash > mb > Use less to look at it: > $ less mb > No problems suspending/restarting. > Use a pipeline in a subshell to view it (the way "man" does it): > $ (cat mb | less) > Now we have the almost the same problem as I described in my first > message - under xterm the 1st keypress sometimes goes to less instead of > to bash, subsequently foregrounding the pipeline less doesn't redraw the > screen properly, needs a newline after all commands, etc; under > console the pipeline sometimes just dies without any error message. > > More interestingly, if I don't put the pipeline in a subshell, then the > problem changes, /and ceases to be intermittent/. > $ cat mb | less > Now the problem is the same whether in xterm or console: if I ^Z then the > pipeline suspends (both processes shown by ps with an 'S', they stop > responding to keypresses) but control doesn't return to bash, and the only > way to unwedge things is to use "kill -CONT" from another window. I've duplicated this bug. In fact, I'm unable to kill the pipeline, although in my case, I didn't try CONT first, just KILL. So, it would appear that one cannot suspend pipelines that have pending input waiting. -- Dario Alcocer -- Sr. Software Developer, Helix Digital Inc. [EMAIL PROTECTED] -- http://www.helixdigital.com -- 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/
[ANNOUNCEMENT] Updated: ghostscript-7.05-2
The Ghostscript package has been updated to 7.05-2. This release now links /usr/lib/binmode.o to fix the text-mode mount bug reported by Sven Kohler. The Cygwin version of GNU Ghostscript supports both a native Win32 version and a X11 version for Cygwin XFree86. A single source package is used to build both versions. Three separate packages are used: * A base package, ghostscript-base, which contains the support files necessary for both the native and X11 versions, as well as the manual pages and documentation. * A native package, ghostscript, which contains the native version of Ghostscript (gs.exe), along with the corresponding scripts. * An X11 package, ghostscript-x11, which contains the X11 version of Ghostscript (gs.exe) and scripts. Both binary versions use the libpng and zlib shared libraries. Thanks to Pavel Tsekov for reviewing the packages. -- Dario Alcocer -- Cygwin Ghostscript Maintainer [EMAIL PROTECTED] -- http://www.helixdigital.com -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: gcc-2 ..../bin/as.exe: Permission denied
On Fri, Jan 17, 2003 at 12:43:36AM -0500, Christopher Faylor wrote: > On Fri, Jan 17, 2003 at 04:35:15PM +1100, Brendan Kosowski wrote: > >I have just installed cygwin on win98se using setup.exe. I selected gcc-2 > >as the only extra on top of the base install. I told setup that I am the > >only user and I use unix style text files. > > > >When I run "Cygwin Bash Shell" and try to compile a C program in my home > >dir (eg. "gcc-2 -o mytest.exe mytest.c ) I get the following error > >message: > > > >gcc-2: installation problem, cannot exec > >'/usr/lib/gcc-lib/i686-pc-cygwin/2.95.3-10/../../../../i686-pc-cygwin/ > >bin/as.exe': Permission denied > > > >Thanks for any help. > > Check out http://cygwin.com/bugs.html, specifically the part about sending > cygcheck output. Chris, I ran into a similar problem[1] this *just* yesterday. With the help of the Cygwin FAQ, I remembered that symlinks are expected to have the DOS/NT system attribute set. I launched command.com, changed the directory c:\cygwin\usr\i686-pc-cygwin, and ran 'attrib', and as.exe did not have the system attribute set. I then ran 'attrib +s *.exe' from command.com, and retried my compile, and it started working again. So, somehow the system attribute is getting wiped out after installation. I'll look into it some more and post anything I find. [1] - I'm using gcc-3, and Brendan is using gcc-2, but I guess the problem is independent of gcc version. -- Dario Alcocer -- Sr. Software Developer, Helix Digital Inc. [EMAIL PROTECTED] -- http://www.helixdigital.com -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: gcc-2 ..../bin/as.exe: Permission denied
On Fri, Jan 17, 2003 at 04:35:15PM +1100, Brendan Kosowski wrote: > I have just installed cygwin on win98se using setup.exe. I selected gcc-2 > as the only extra on top of the base install. I told setup that I am the > only user and I use unix style text files. > > When I run "Cygwin Bash Shell" and try to compile a C program in my home > dir (eg. "gcc-2 -o mytest.exe mytest.c ) I get the following error > message: > > gcc-2: installation problem, cannot exec > '/usr/lib/gcc-lib/i686-pc-cygwin/2.95.3-10/../../../../i686-pc-cygwin/ > bin/as.exe': Permission denied Just curious; are you running Windows stand-alone, or in an emulated environment? I ran into a very similar problem as yours yesterday using gcc-3 (also running Windows 98 SE), but running under Win4Lin. What I found in my case is that Cygwin symbolic links lose the DOS system attribute after Win4Lin shuts down. Since .../i686-pc-cygwin/bin/as.exe is supposed to a symbolic link to /usr/bin/as.exe, gcc cannot run the assembler due to the broken symbolic link. I verified that this does not happen under a stand-alone (non-Win4Lin) Win98SE installation; the system attribute persists between reboots. Check the attributes for C:\cygwin\usr\i686-pc-cygwin\bin\as.exe from a DOS command line using the 'attrib' command. If the 'S' flag isn't displayed, then reset the system attributes using the command 'attrib +s *.exe'. -- Dario Alcocer -- Sr. Software Developer, Helix Digital Inc. [EMAIL PROTECTED] -- http://www.helixdigital.com -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: Problems compiling trivial C program.
On Fri, Feb 07, 2003 at 01:33:40PM -, Christopher January wrote:
> I'm having trouble compiling this test program:
>
> void f(){}
>
> using the command line:
> gcc test.c -c -o test.o
>
> using 1.3.19 or latest Cygwin snapshot (2003-Feb-07) (same error with
> both) and gcc-3.2-3.
>
> The error I see is:
>
> 16 bit MS-DOS Subsystem
> /usr/src/cygwin-cvs/obj
> The NTVDM CPU has encountered an illegal instruction.
> CS: IP:0077 OP:f0 37 05 0e 02 Choose 'Close' to terminate the
> application.
> Close | Ignore
I've seen these errors myself in the past, all associated with
running configure and/or gcc. For some reason, NT is trying to
invoke the NT Virtual DOS Machine (NTVDM) when it runs gcc.exe.
The problem is that gcc.exe should be identified as a Win32 console
application, and therefore doesn't need NTVDM to run.
I wonder if there's some sort of memory corruption going on that
results in gcc.exe being identified as a 16-bit mode DOS program,
like maybe the NE stub in the PE file being scribbled by an errant
pointer. Maybe something in the NE stub in the actual disk file
for gcc.exe has some bits that inadvertently set of NTVDM.
Anyway, you can try the following hack that might allow you to run
the compiler (that is, as long as you don't try to run any DOS apps
under NT):
http://www.rtems.com/rtems/maillistArchives/rtems-users/2001/june/msg00182.html
There's additional information in this MSDN KnowledgeBase article:
http://support.microsoft.com/default.aspx?scid=KB;en-us;q196453
--
Dario Alcocer -- Sr. Software Developer, Helix Digital Inc.
[EMAIL PROTECTED] -- http://www.helixdigital.com
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Bug reporting: http://cygwin.com/bugs.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
Re: install native/x11 ghostscript
On Wed, 3 Dec 2003 17:41:30 +0100 (=?ISO-8859-1?Q?Westeurop=E4ische_Normalzeit?=) Ulf-Dietrich Braumann <[EMAIL PROTECTED]> wrote: > My question simply is, why setup recommends installing the > native gs even if the x11 version was already installed, or even > further, if there is some mechanism to ensure exclusive installation > of such packages. This is a *very* good question; unfortunately my knowledge of setup.exe's inner workings is very limited. Hopefully someone else (cgf, Chuck, Nicholas, ?) might be able to answer this one. -- Dario Alcocer Cygwin ghostscript maintainer -- 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: Question about ash and getopts
Peter Seebach wrote: I know this is a pseudo-FAQ, but I haven't been able to find a clear enough answer in the archives. 1. Is it not the case that POSIX provides a specification for the getopts builtin? 2. Doesn't ash, as originally written, implement getopts? I'm trying to figure out why this feature was removed, and I've never gotten an answer that made much sense. Every other POSIX-like system I can think of supports getopts in /bin/sh. Why is Cygwin different? Use the "set -- `getopt`" idiom instead: http://cygwin.com/ml/cygwin/2003-05/msg01114.html -- 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/
[ANNOUNCEMENT] Updated: ghostscript-6.51-4
--ol0V2Ee2cj Content-Type: text/plain; charset=us-ascii Content-Description: message body text Content-Transfer-Encoding: 7bit The Ghostscript package has been updated to include support for the libpng and zlib shared libraries, as suggested by Chuck Wilson. In addition, the package also now has a new setup.hint file included. This release of Ghostscript is an "X-less" version, i.e. doesn't require the cygwin-xfree libraries to run. This version does not support direct preview. In order to preview Postscript output, it's necessary to rasterize the output to a graphics format (for example, PDF or JPEG) and viewed with a suitable viewer. For build instructions, please read: /usr/doc/Cygwin/ghostscript-6.51.README The instructions have also been included at the end of this message. I want to thank Chuck Wilson for uploading the package. --ol0V2Ee2cj Content-Type: text/plain Content-Description: GS build instructions Content-Disposition: inline; filename="ghostscript-6.51.README" Content-Transfer-Encoding: 7bit Release Notes -- GNU Ghostscript for Cygwin Version 6.51, Release 4 (6.51-4) (26 February, 2002) This Cygwin version of GNU Ghostscript has been built without support for X. This release now supports the libpng and zlib shared libraries (i.e. these libraries are no longer statically linked in.) REQUIREMENTS: Due to very specific requirements Ghostscript has relating to Postscript's JPEG support, the JPEG shared library cannot be used, and must be statically linked instead. The source for the JPEG library is included in the source package, ready to build with Ghostscript. BUILDING: At a minimum, you must have all the tools needed to build Cygwin programs, i.e. make, gcc, and binutils. In addition, the zlib and libpng shared libraries must be included in your Cygwin installation. Finally, you also need to fetch the source archive, ghostscript-6.51-4-src.tar.gz, from a Cygwin mirror site. Once you have everything required for building, follow these steps: 1. Unpack ghostscript-6.51-4-src.tar.gz (the source is pre-patched to build on Cygwin): $ tar xzf ghostscript-6.51-4-src.tar.gz 2. Build from the top-level source directory: $ cd ghostscript-6.51 ; make -f src/unix-gcc.mak 3. Install the entire package: $ make -f src/unix-gcc.mak install 4. Grab the following font compressed tar files: ftp://mirror.cs.wisc.edu/pub/mirrors/ghost/gnu/fonts: gnu-gs-fonts-std-6.0.tar.gz (required) gnu-gs-fonts-other-6.0.tar.gz (optional, recommended) Unpack them into /usr/share/ghostscript/fonts (font directory contained within tar file): $ tar xzCf /usr/share/ghostscript gnu-gs-fonts-*-6.0.tar.gz 5. Once you install it, you can test it: $ gs -sDEVICE=jpeg -dBATCH -sOutputFile=tiger.jpg \ /usr/share/ghostscript/6.51/examples/tiger.ps The Cygwin patches are in CYGWIN-PATCHES, along with this file. Have fun! -- Dario Alcocer -- Sr. Software Developer, Helix Digital Inc. [EMAIL PROTECTED] -- http://www.helixdigital.com --ol0V2Ee2cj Content-Type: text/plain; charset=us-ascii Content-Description: .signature Content-Transfer-Encoding: 7bit -- Dario Alcocer -- Sr. Software Developer, Helix Digital Inc. [EMAIL PROTECTED] -- http://www.helixdigital.com --ol0V2Ee2cj-- -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
[ANNOUNCEMENT] Updated: ghostscript-6.51-3
The Ghostscript package has been updated to fix a bug reported by Greg Bond related to operation on text-mode mounts: http://sources.redhat.com/ml/cygwin/2001-12/msg00400.html This release of Ghostscript is an "X-less" version (i.e. one that doesn't require X11), and so can be used without the cygwin-xfree packages. The GNU 'standard' and 'other' Ghostscript font collections are included for convenience. Since this release is built using the unix-gcc.mak makefile, Windows GUI support is not included. This means that Postscript files must be previewed indirectly (they must be rasterized to an output file first, e.g. JPEG or PDF, and then viewed with a suitable viewer.) For build instructions, please read: /usr/doc/Cygwin/ghostscript-6.51.README The instructions have also been included at the end of this message. I want to thank Greg Bond for submitting the text-mode mount patch, and Chuck Wilson for help uploading the package. Release Notes -- GNU Ghostscript for Cygwin Version 6.51, Release 3 (6.51-3) (9 January, 2002) This Cygwin version of GNU Ghostscript has been built without support for X. This version fixes problems seen with release 2 of 6.51 (7/5/01) when running on text-mode mounts. (Thanks to Greg Bond, <[EMAIL PROTECTED]>, for submitting a patch to fix this problem.) REQUIREMENTS: Previous releases required shared libraries for zlib, libpng, and jpeg. However, due to the very specific requirements Ghostscript has regarding these libraries, these libraries are instead statically linked. As a result, Ghostscript no longer requires the use of shared libraries. The libraries are included in the source package, ready to be built with Ghostscript. BUILDING: At a minimum, you must have all the tools needed to build Cygwin programs, i.e. make, gcc, and binutils. You also need to fetch the source archive, ghostscript-6.51-src.tar.gz from a Cygwin mirror site. Once you have everything required for building, follow these steps: 1. Unpack ghostscript-6.51-src.tar.gz (the source is pre-patched to build on Cygwin): $ tar xzf ghostscript-6.51-src.tar.gz 2. Build from the top-level source directory: $ cd ghostscript-6.51 ; make -f src/unix-gcc.mak 3. Install the entire package: $ make -f src/unix-gcc.mak install 4. Grab the following font compressed tar files: ftp://mirror.cs.wisc.edu/pub/mirrors/ghost/gnu/fonts: gnu-gs-fonts-std-6.0.tar.gz (required) gnu-gs-fonts-other-6.0.tar.gz (optional, recommended) Unpack them into /usr/share/ghostscript/fonts (font directory contained within tar file): $ tar xzCf /usr/share/ghostscript gnu-gs-fonts-*-6.0.tar.gz 5. Once you install it, you can test it: $ gs -sDEVICE=jpeg -dBATCH -sOutputFile=tiger.jpg \ /usr/share/ghostscript/6.51/examples/tiger.ps The Cygwin patches are in CYGWIN-PATCHES, along with this file. Have fun! -- Dario Alcocer -- Sr. Software Developer, Helix Digital Inc. [EMAIL PROTECTED] -- http://www.helixdigital.com -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: [ANNOUNCEMENT] Updated: ghostscript-6.51-3
>>>>> "Peter" == Peter Ring <[EMAIL PROTECTED]> writes:
Peter> Please forgive a silly question.
Peter> I've rebuild the previous release (ghostscript-6.51-1) with
Peter> X support (mainly for use with xdvik in order to view dvi's
Peter> with postscript illustrations).
Peter> While this were not a major hassle (just patch
Peter> src/unix-gcc.mak a little, don't forget to set XLIBS=Xt SM
Peter> ICE Xext X11), are there any reason not to release
Peter> X-enabled binaries for ghostscript? Will gs then not run
Peter> without the X runtime libraries?
It's better to patch the X11 version of ghostscript, when that is
eventually available (see below.)
>>>>> "Chuck" == Charles Wilson <[EMAIL PROTECTED]> writes:
Chuck> Nope. If you link it against the X libraries, but then try
Chuck> to run it on a system that doesn't have those DLLs
Chuck> installed, you'll get "Couldn't find dynamic link library
Chuck> "libXFOO.dll" in {path...}" errors.
Chuck> ghostscript can't be distributed in X-linked form until the
Chuck> cygwin-xfree guys create a setup-installable set of X
Chuck> packages. (And perhaps, not even then; it's up to Dario)
Actually, it's my intention that once cygwin-xfree is supported by
setup.exe, I will create a separate package (or maybe just a separate
binary) of Ghostscript that supports X.
--
Dario Alcocer -- Sr. Software Developer, Helix Digital Inc.
[EMAIL PROTECTED] -- http://www.helixdigital.com
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Bug reporting: http://cygwin.com/bugs.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
Re: Cygwin web site?
Gene Smith wrote: Where has the cygwin web site gone? Seem to be refusing connections. http://www.cygwin.com/ Just to confirm your observation, I've not been able to get connect to www.cygwin.com since Thursday. A friend of mine tried installing last Friday and got the same result. -- D. -- 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/
