Actually, I've had numerous problems installing cygwin. I have two machines at home running Windows XP and also my office computer running Windows 2000 Pro.
Installing a clean system (no cygwin installed before) installed on my two home machines but hung in the postinstall scripts. I finally had to kill the script and run the remaining ones by hand. That was a few months ago, so I didn't bother to tell anyone. This time, I tried to upgrade my cygwin at the office since the one I have at home is so much better. They had 1.3.10 installed. Fortunately, I zipped the entire c:/cygwin directory before doing it. Everything was so corrupt, I finally deleted the entire cygwin tree and unzipped what I had saved. Here are some of the things I tried: 1 - I left the "setup.exe" showing "Default" and installed from sigunix.cwru.edu. It failed for some reason, I didn't bother to check the logs. 2 - I tried mirrors.kernel.org and took the trouble to try and add a few things that I installed at home and liked. It also failed in the middle for some reason, I didn't bother to check the logs. [If I only had the time to investigate all this stuff, but we're working long hours.] 3 - Finally, I renamed c:/cygwin to c:/cygwin1 and tried to perform a clean install. I used sources-redhat.mirror.redwire.net and selected "Install" instead of "Default" since that's supposed to install everything. 4 - This morning (I had left it to install overnight), I had an error popup window telling me: The dynamic link library cygintl-1.dll could not be found in the specified path (path is listed here and it includes c:\cygwin\bin) It seems that this error was generated from one of the postinstall scripts when it ran grep.exe. After clearing the error (pressing the OK button), I got about two dozen more of these errors from other calls to grep and one from a call to find in various postinstall scripts. I did a search on c:\cygwin from a Windows Explorer window and there is no file named cygintl-1.dll anywhere in the tree. I also searched under c:\WINNT, although I didn't expect it to be there. Oh, well, I tried running bash. It comes up in /cygwin/bin, as Joe indicated, and I can't run "cat" or "more" to look at the passwd file. Seems "cat" isn't in any of the bin directories, and "more" can't find cygncurses6.dll. So, what have I done wrong? What can I do to fix it? Thanks for any assistance you can provide. Chris Carlson iStor Networks, Inc. -----Original Message----- From: Brian Ford [mailto:[EMAIL PROTECTED] Sent: Friday, May 28, 2004 9:10 AM To: Joe Landman Cc: [EMAIL PROTECTED] Subject: Re: New install of 1.5.10 replacing 1.5.6: many things not working On Fri, 28 May 2004, Joe Landman wrote: > Hi folks: > > I have multiple machines with 1.5.6 installed. I wanted to upgrade to > 1.5.10 (bug fixes, speed, etc). Stuff worked (for the most part) in > 1.5.6. I was/am looking to using it for application development on windows. Are you trying to upgrade just the Cygwin package, or all Cygwin packages? > With 1.5.10 install, I get error messages about find.exe being given > bad arguments. This usually means you have a PATH problem and are getting the Windows version of find rather than the Cygwin one. > Many of the post-install scripts die with problems with grep (more in a > moment). When I open the cygbash shell, it puts me into /usr/bin by > default, Check you /etc/passwd file and make sure your user home directory is set correctly. > and the moment I cd out of there, I lose any ability to run > basic commands such as ls. Sounds like . is in your PATH, but /usr/bin isn't. > Anything that tries to use grep is rewarded with an error message about > /bin/grep not existing. Quick ls'ing around (find does not work... > sigh) does not locate a grep. > > Ok, I may be thick, but I think that there might be a problem here. > > The machines with problems: > > 1) Windows XP Home laptop. SP1 installed. 512 MB ram > > 2) Windows 2000 desktop. SP_something_or_other installed. 768 MB ram > > Both had similar working copies of 1.5.6 installed. Starting up the > cygbash shell resulted in being in the /home/landman directory (where I > thought I should be). Everything properly pathed out in the older version. > > Any thoughts? I don't have to re-install the OS... (I hope :( ). Try a Cygwin reinstall after checking out your PATH issues. Please read this: > Problem reports: http://cygwin.com/problems.html and attach cygcheck output. Maybe then someone will have a better idea. -- Brian Ford Senior Realtime Software Engineer VITAL - Visual Simulation Systems FlightSafety International the best safety device in any aircraft is a well-trained pilot... -- 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/ -- 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/
