HARMS OF INSTALLING MACPORTS INSTALL

HARMS OF INSTALLING MACPORTS INSTALL

I recommend that if you're about to do any such manual compilation, you first change your PATH in that terminal so it only references at most one of MacPorts and Fink. To do this we will install OSXFUSE and a GUI tool called MacFusion that will make. Most dependencies for scientific / unix software I have are through macports (also up to date as of ). Usually that works ok, sometimes it doesn't, sometimes it mysteriously breaks later on.

Does your friend compile other Unixy software manually, outside of Fink and MacPorts? It's possible that those programs will end up dynamically linking against a combination of Fink and MacPorts libraries. Oh, one more little thing that can cause trouble. Then you could put a symlink to /sw/bin/qemu in there, to ensure it will take priority over the MacPorts version.

Unfortunately llvmgcc-4.2 compiler ship with XCode is not suitable to compile Ruby (it works but some features are buggy). In these cases, I find it helpful to make a directory in $HOME/bin, and put it at the front of your PATH. When installation is complete, tools are finally available but is not enough. Eg: If the MacPorts version of qemu has a bug, and you need to make sure you only run the Fink version. The only time it's important is if you want to run some program from one distribution and not the other. Most of the time, even the PATH concerns don't matter much. As others have mentioned, homebrew is quite a bit less careful about this. They're both pretty careful not to interfere with the other. Installation and use of MacPorts, Programmer All, we have been working hard to make a technical sharing website that all programmers love. Fink will (by default) install in /sw, and MacPorts in /opt/local, though it's possible to change those. There's no problem at all installing both Fink and MacPorts at the same time, I have them both installed right now. Best answer: Hi, I'm one of the project leads for Fink.

Harms of installing macports