Ugh, top-posting... Reformatted. On Sat, 13 Jan 2007, Thomas Antony wrote:
> On 1/13/07, Dave Korn <[EMAIL PROTECTED]> wrote: <http://cygwin.com/acronyms/#PCYMTNQREAIYR>. Thanks. > > [snip] > > It would be helpful if you could run "cygcheck -c >a.txt" before doing so, > > "cygcheck -c >b.txt" afterwards, and then show us the output of "grep > > 'gcc\|mingw\|w32api' a.txt b.txt". It would be good if we verify whether > > cygcheck spots these busted links and identifies them as a problem > > ... > Nop. > > [EMAIL PROTECTED] ~ > $ grep 'gcc\|mingw\|w32api' a.txt b.txt > a.txt:gcc 3.4.4-3 OK > a.txt:gcc-core 3.4.4-3 OK > a.txt:gcc-g++ 3.4.4-3 OK > a.txt:gcc-mingw 20040810-1 OK > a.txt:gcc-mingw-core 20050522-1 OK > a.txt:gcc-mingw-g++ 20050522-1 OK > a.txt:mingw-runtime 3.11-1 OK > a.txt:w32api 3.8-1 OK > b.txt:gcc 3.4.4-3 OK > b.txt:gcc-core 3.4.4-3 OK > b.txt:gcc-g++ 3.4.4-3 OK > b.txt:gcc-mingw 20040810-1 OK > b.txt:gcc-mingw-core 20050522-1 OK > b.txt:gcc-mingw-g++ 20050522-1 OK > b.txt:mingw-runtime 3.11-1 OK > b.txt:w32api 3.8-1 OK > > I guess I am gonna have to reinstall the whole thing. Since cygcheck uses the listings of the installed files from the package distribution tarball, it's not going to catch missing files/symlinks that are supposed to be created during the postinstall phase. In fact, since gcc-mingw is distributed as a tarball that is extracted in a postinstall script, it's not possible to check whether it's incomplete using cygcheck. 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! Freedom is just another word for "nothing left to lose"... -- Janis Joplin -- 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/
