Thanks guys, <div><br><div> I ended up finding mzc -- the install script doesn't seem to copy them over to the directory set with --prefix. I ended up running the build locally (without --prefix) and manually copying the executables in the bin directory of the unpacked tar. mzscheme and mred got copied fine, but are also built in the src/ directory, not one level up. I got everything working, just figured someone might want to check on the script.</div> <div><br></div><div>Thanks again,</div><div>-Dave<br><br><div class="gmail_quote">On Sun, Jan 31, 2010 at 10:58 AM, Norman Gray <span dir="ltr"><<a href="mailto:norman@astro.gla.ac.uk">norman@astro.gla.ac.uk</a>></span> wrote:<br> <blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"><br> Greetings.<br> <div><div></div><div class="h5"><br> On 2010 Jan 31, at 13:03, Robby Findler wrote:<br> <br> > On Sun, Jan 31, 2010 at 4:38 AM, Norman Gray <<a href="mailto:norman@astro.gla.ac.uk">norman@astro.gla.ac.uk</a>> wrote:<br> >> Note, just by the way, that --prefix=/usr/local is generally the default; that installing software somewhere else (with, say, --prefix=/my/tools/mzscheme-4.2.4) can be a good idea if you want to try things out); and that './configure --help' can tell you if there are any extra options to configure that might be of use or interest.<br> >><br> ><br> > In the case of plt, however, leaving off the --prefix argument<br> > installs into the directory where you downloaded (and the result is<br> > "mv"-able, too).<br> <br> </div></div>Ah, and I even half-remember someone remarking on this here a couple of days ago.<br> <br> I'm not doing very well this weekend....<br> <div><div></div><div class="h5"><br> All the best,<br> <br> Norman<br> <br> <br> --<br> Norman Gray : <a href="http://nxg.me.uk" target="_blank">http://nxg.me.uk</a><br> <br> <br> <br> </div></div></blockquote></div><br></div></div>