Simon, quoted below, is correct about the /usr/local/lib infinite-reference being a problem. In case it's of any use to other OSX users, my guess is that macPorts caused that error. I infer that based on the time at which the symlink was created, which was at the time when I was trying to install MacPorts. (That install failed. I cannot pin down the time too well because it took several hours of compilation to fail.)
I am putting a link to a posting I made on this issue below, in case its thread expands to provide good hints for other R/Leopard users. (Simon's suggestion about moving "lib 1" to "lib" worked for me.) http://www.nabble.com/problem-installing-2.6.1-on-OSX-Leopard-%28after-failed-MacPorts-install%29-tf4933141.html#a14119813 Simon Urbanek wrote: > > > > No. The failure is due to a strange symlink in /usr/local/lib that > points to itself. I suspect that this has something to do with an > upgrade from Tiger to Leopard or Xcode 3 installation and that Apple > actually creates that infinite symlink. Given that there is "/usr/loca/ > lib 1" lingering around, I'd bet that > > sudo rm /usr/local/lib > sudo mv '/usr/local/lib 1' /usr/local/lib > > will fix the problem. > > -- View this message in context: http://www.nabble.com/R-install-problem-on-MacOS-10.5.1-%28PR-10476%29-tf4897418.html#a14170397 Sent from the R devel mailing list archive at Nabble.com. ______________________________________________ R-devel@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-devel