Path: chuka.playstation.co.uk!tjs From: tjs@cs.monash.edu.au (Toby Sargeant) Newsgroups: scee.yaroze.programming.gnu_compiler Subject: Re: That dreaded Linux query again.... Date: 29 Sep 1998 03:30:47 GMT Organization: PlayStation Net Yaroze (SCEE) Lines: 76 Message-ID: References: <360AF965.4D35F33B@wyrddreams.demon.co.uk> <360C1CD7.133D3870@wyrddreams.demon.co.uk> NNTP-Posting-Host: longford.cs.monash.edu.au X-Newsreader: slrn (0.9.4.3 UNIX) On 29 Sep 1998 11:38:58 +1000, Toby Hutton wrote: >tjs@cs.monash.edu.au (Toby Sargeant) writes: > >> >> On 28 Sep 1998 15:05:13 +1000, Toby Hutton wrote: >> >You shouldn't have to do all the steps manually, obviously, that's >> >what gcc is for. All I can suggest is removing the cross compiler >> >you've installed, and re-do it *not as root* installing it into your >> ^^^^^^^^^^^ >> >home directory. That's what I did and I've had *no* problems. >> >> :-P that's what make -n is for. > >True, but still rootdom is a magical and powerful thing, and when >stuffing around with things for the first time, as I was, I feel safer >knowing I can rm -r ~/yaroze *afterwards* in case make -n slipped >something by me that I missed... yeah, whatever. uhuh... but that's also why the solais model of /opt is really good, where you install everything to its own directory in /opt. then if you want to get rid of it, you just nuke the directory. But yes, it is a good idea to play it safe. (gcc is very nice about where it installs things, though, so it's pretty easy to clean up any messes it leaves behind). >Toby, do you know why if I make the tools *my* psx-gcc calls psx-etc, >but James does it and psx-gcc calls just etc? Did you use the patches >on the Japanese site, or just make the x-compiler yourself? I made the cross compiler myself, the first time, stealing the specs file and the like from the psx disc, and then i did the same thing with the patches, which really only give the configure scripts an explicit psx target (as well as breaking the c preprocessor by making it accept stupid dos crlf sequences). The gdb patches were the big win. I *think* the reason that james' compiler wasn't working (I think we worked it out via email) is that if you don't explicitly specify the exec-prefix and prefix when compiling gcc, or these aren't the same as the ones you used when you compiled binutils, then the gcc configuration will find the normal as|ld etc first. What it actually looks for is /prefix/target/bin/whatever, followed by /prefix/bin/whatever, and then it probably looks in standard locations. >> the gcc install works just fine installing to wherever you want to install >> it to. in fact, it's possible to produce a gcc version that will either >> call the native compiler or the psx cross compiler depending on the flags >> that you pass it. needless to say, it's much saner to just use an exec >> prefix, but the fact is that there is that option. > >If you're a newbie then you can't be too careful. But at the same time, the point of unix is to make you think about your actions ;) >> IMHO it's much better to have a world writeable partition or directory >> that user binaries get installed into. That way people can share binaries >> that they compile (presupposing that they understand the security risks), >> and it means that you can have a relatively small partition for home >> directories. > >How many users do you have on your home machine?!? Ha, a world My home one? Only a couple. My uni one? quite a few. >writable binary directory is asking for mischief on a (real) >multi-user machine, particularly if a a newbie puts it too early in >their path, and I decide to write my own special version of passwd or >something and put it in there. Exactly. Which is why all the contrib stuff goes last in my path. And why none of the contrib directories go in the ld.so.conf. And in reality I wouldn't make it world writeable, but would rather make it writeable by a group of trusted users. Toby.