Install Cygwin On Windows Xp
Aug 26, 2018 - You will need to install several additional Cygwin components before. And including Windows XP Professional (screenshot of m8r running on.
Dennis C wrote: > > I have installed the lastest Cygwin and I get the bash shell windows > installed ok. However from my home directory, when I did pwd, I see > that the home directory has been placed in /cygdrive/c/Documents and > Settings/peter > > Now when I am installing GCC for the ARM processor, the configure > script has problem because of the spaces in the home directory > pathname. > > Is there anyway to install cygwin to any other directory other than > under Documents and Settings? Around here it is on c: cygwin. It is launched in its own window with a pif file and a startup batch file, using 4dos as the basic shell and starting bash.
-- 'I'm a war president. I make decisions here in the Oval Office in foreign policy matters with war on my mind.' 'Churchill and Bush can both be considered wartime leaders, just as Secretariat and Mr Ed were both horses.'
- James Rhodes. In comp.sys.arm Dennis C wrote: > I have installed the lastest Cygwin and I get the bash shell windows > installed ok. However from my home directory, when I did pwd, I see > that the home directory has been placed in /cygdrive/c/Documents and > Settings/peter > Is there anyway to install cygwin to any other directory other than > under Documents and Settings? It's just your home directory that is under 'My Documents', you can change that by editing /etc/passwd. See the /etc/profile script to see why your home directory was placed where it was.
'Dennis C' wrote in message news:65ee8e539.67304f85@posting.google.com. > I have installed the lastest Cygwin and I get the bash shell windows > installed ok. However from my home directory, when I did pwd, I see > that the home directory has been placed in /cygdrive/c/Documents and > Settings/peter > > Now when I am installing GCC for the ARM processor, the configure > script has problem because of the spaces in the home directory > pathname. > > Is there anyway to install cygwin to any other directory other than > under Documents and Settings?
> > Thanks It's only your 'home' directory that is at issue, not the cygwin directory (which will probably be at 'c: cygwin' unless you told it otherwise during installation. You are suffering from MS's mind-numbingly stupid directory naming scheme that, along with its partner 'Program Files', causes all sorts of irritations and complications. Fortunately, it is possible to get around (at least on W2K) - use the user manager, and go to the advanced settings. In the profile for your user, set the home folder to 'c: users dennis' or something similar. Other useful tricks (I can't remember which ones are needed, and which are generated automatically) are to set environment variables HOME to 'c: users dennis', HOMEDRIVE to 'c:', and HOMEPATH to ' users dennis'. And remember to make a directory called 'c: Progs' or similar, and install programs there instead of under 'program files' - it makes it much easier to run them from the command line.
[Note: F'up2 cut down --- should have been done by OP.] In comp.arch.embedded Dennis C wrote: > I have installed the lastest Cygwin and I get the bash shell windows > installed ok. However from my home directory, when I did pwd, I see > that the home directory has been placed in /cygdrive/c/Documents and > Settings/peter > Now when I am installing GCC for the ARM processor, the configure > script has problem because of the spaces in the home directory >Hotel giant 3 free download. pathname. > Is there anyway to install cygwin to any other directory other than > under Documents and Settings? You're mixing up the path cygwin itself is installed in with the path it places your $HOME directory in. The latter will be where XP has it unless you tell it otherwise.
But that doesn't have any bearing on where the former is (usually c: cygwin). The real problem is not the $HOME directory, anyway --- well, not unless you're unpacking and building your source packages in $HOME, which is easy to avoid. The real problem is with XP's predefined $TEMP and $TMP paths --- they're below 'Documents and Settings', too, and thus they'll contain spaces, and *that's* what breaks unwary scripts. To find the actual trouble, do env grep 'Documents and' and fix all paths this finds to get rid of spaces. Ceterum censeo, the names 'Program files' and 'Documents and Settings' were chosen by MSFT out of pure malice. I fail to see how introducing spaces into predefined system directory names could possibly have been done for any reason other than to strike a blow at all tools using command lines, which have relied on blanks as separators since days long forgotten. -- Hans-Bernhard Broeker (broeker@physik.rwth-aachen.de) Even if all the snow were burnt, ashes would remain.