how to replace llvm-3.2 with llvm-3.3?

Ryan Schmidt ryandesign at macports.org
Thu Jun 26 14:17:29 PDT 2014


On Jun 26, 2014, at 1:50 AM, René J.V. Bertin wrote:

> NB: if like me you get registry errors ("file name too long") since having upgraded to MacPorts 2.3.0, you'll have noticed as I that those sort themselves out, possibly requiring you to repeat certain commands.

This is the first I've heard of this problem. Have you filed a bug report? Are your paths (prefix, or path to the ports tree) unusually long?



More information about the macports-users mailing list