On Oct 23 17:09, Angelo Graziosi wrote: > I want to flag the following problems observed with the current snapshot > 20061023 08:34:32. > > A few days ago, it was flagged a problem with XDVI: > http://cygwin.com/ml/cygwin/2006-10/msg00591.html. > > >From the discussion of the thread (and also this > http://cygwin.com/ml/cygwin/2006-10/msg00714.html), it comes out that the > cause was the conflict between the packages ghostscript and > ghostscript-x11. > > I solved that problem with the link gs.exe --> /usr/X11R6/bin/gs.exe in > /bin (http://cygwin.com/ml/cygwin/2006-10/msg00595.html). > > Now trying the new Cygwin snapshot the trick does not work any more and
What *exactly* doesn't work anymore? Can you please provide a simple testcase which shows the problem reproducible? As for your trick, it still works for me running the X gs. $ uname -a CYGWIN_NT-5.1 cathi 1.7.0(0.160/4/2) 2006-10-23 17:00 i686 Cygwin $ cd /bin $ mv gs.exe gs.exe.orig $ ln -sf /usr/X11R6/bin/gs.exe gs.exe $ ls -l gs.exe* lrwxrwxrwx 1 corinna Users 21 Oct 23 17:25 gs.exe -> /usr/X11R6/bin/gs.exe -rwxr-x---+ 1 corinna Users 4507648 Feb 15 2006 gs.exe.orig.exe $ cd $ gs <Correctly starts the X gs binary> (Eric? Do you see what happens when renaming foo.exe to foo.exe.orig using mv(1) from coreutils-5.97-1 ? That doesn't look good to me...) Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat -- 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/
