> On 2 Jul 2020, at 20:53, Torbjörn Granlund <[email protected]> wrote: > > Hans Åberg <[email protected]> writes: > > One must run 'xcode-select install' from the Terminal. > > I came that far (except it is --install) before giving up.
Right. > But --install is not for installing a new Xcode, but for installing > command line tools. Yes, but if you have something run by a Makefile, then that would be needed, also when running in the GUI. I had a problem with that when switching Xcode version: Some things would work, others not. > What version? It does not say. If one does not indicate which one by an argument, then it is probably /Applications/Xcode, or the one set by --switch: One can set version by the --switch argument; see --help. It should be (as root) xcode-select --switch /Applications/Xcode.app/Contents/Developer > The opened > "dialogue" is not much of a dialogue as OK and Cancel was the only > options IIRC. The command takes no argument (such as an Xcode release > image) at least not as per its lackluster manual, nor in any way my > experimentation could find out. > > How to install the (in the manual) mentioned > /Applications/Xcode-beta.app remains undocumented. So here it should be xcode-select --switch /Applications/Xcode-beta.app/Contents/Developer > I may not try the Xcode betas for other reasons, they may corrupt some other > installations. > > Perhaps you also failed with your installation, overwriting the existing > Xcode? It was not I, but one on the LilyPond list that was not being able to run the lilypond program. I suggested to make a new volume with a new MacOS installation, and he found it worked, and that it was not due to MacPorts. A suggestion on the net suggested that some versions of Xcode 11 beta could cause such issues. See: https://lists.gnu.org/archive/html/lilypond-user/2020-03/msg00368.html _______________________________________________ gmp-bugs mailing list [email protected] https://gmplib.org/mailman/listinfo/gmp-bugs
