Ruby fails to build using the usual

sudo port install/upgrade ruby

when using MacPorts trunk (but not 1.7.1) because port runs setgid and miniruby that is built and used in the build
sees that as a security problem and will not run as requested.

Is this a problem or is there a way to get around this? Are there other ports that don't like running setgid?

See https://trac.macports.org/ticket/19131
_______________________________________________
macports-dev mailing list
[email protected]
http://lists.macosforge.org/mailman/listinfo.cgi/macports-dev

Reply via email to