Rvm - Macports Won't Update Through Proxy

Macports/rvm/svn connection issue behind a proxy and firewall

As a workaround to get you going try:

rvm autolbs read-fail

It will not install packages automatically - it will fail in case any packages are missing and will let you know names of this packages, just install them manually with macports and it should be fine.

---

Other solution would be switching to:

rvm autolibs homebrew

to use homebrew instead of macports, or:

rvm autolibs rvm_pkg

to detect what is already installed with pkg-config and try to install rest with the old rvm pkg install ....

---

More details on autolibs: http://rvm.io/rvm/autolibs

port selfupdate: macPorts sources: command execution failed

I was behind a firewall. Tried on a different network and it worked.

MacPorts: install hangs/remains unusable

The installer hangs running package scripts because the last statement in these package scripts is exactly this "sudo port selfupdate" that you've been running manually afterwards.

Because this step did never run, your MacPorts installation lacks knowledge about the apache2 port (which is exactly why the installer runs selfupdate to give you a full-featured installation).

Unfortunately Apple's infrastructure (rsync.macports.org) seems to have connectivity problems at the moment, which is causing problems for quite a few people. You can try using one of the mirrors as outlined at https://trac.macports.org/wiki/Mirrors.

Trying to install MacPorts

They're in /opt/local/bin, so as to not overwrite stuff that came with Mac OS X or that you might have gotten from elsewhere. They won't be in your $PATH until you close that Terminal and open another (nothing can alter the environment of a running program except the program itself).

Error install hhvm with macport and fail all install with macport

I finally solved my problem with two series of actions:

1. with brew

brew tap homebrew/dupes
brew tap homebrew/versions
brew tap mcuadros/homebrew-hhvm
brew update
cd $(brew --repository)
git reset --hard FETCH_HEAD
brew update
brew install hhvm --HEAD
brew install ocaml
brew link dwarfutils ocaml
brew unlink libdwarf
brew link dwarfutils ocaml
brew link --overwrite ocaml
brew link dwarfutils ocaml
brew install hhvm --HEAD

and after...

2. with macports

   sudo port -v selfupdate
port upgrade outdated
sudo port upgrade outdated
sudo port search ImageMagick
sudo port install ImageMagick
port selfupdate
sudo port selfupdate


An important detail , MacPorts went from version 2.3.3 to version 2.3.4 in this update .

MacPort is now operational again.

Mac Ports environment variables

DON'T do that.

You should never ever ever need to set DYLD_LIBRARY_PATH outside of testing (and in very limited cases during a build). It should never be used in production code, never shipped to users, and never recommended to people who don't have a deep understanding of how dyld works. It is NOT analogous to LD_LIBRARY_PATH in ld.so. It will cause you tons of problems if you set it in your .bashrc or other init script which won't be apparent immediately. It will cause MacPorts libraries to be used instead of system libraries which will cause codesignature verification issues, binary compatibility issues, and aborts at process launch due to library version mismatch.

If you want to use the MacPorts libraries, link your project against them instead of the ones you've installed in /usr/local by setting up your header search path and library search path.

Furthermore, your use of /usr/local may have caused issues with your MacPorts install because /usr/local is part of the default search path.

macports on mac os x mountain lion

Since you just barely installed MacPorts, none of the actual ports (that you most likely had on another computer) have been installed yet.

If you run port installed, you'll notice that it returns empty.

So congratulations; 0 out of 0 ports are outdated ;-)

If you want all the same ports that you had on your other Mac(s), fire up Terminal and run port installed on those machines. That should give you a list of everything, and you can either export that list, or pick-and-choose the ones you want on your new Mountain Lion installation.

And then it will be as simple as

port install [which program]

for each of those ports that you want.

Deactivate macport

This is a bug in the demeter port. It should not install the files of the ifeffit perl module, but instead declare a dependency on p5.34-ifeffit.

Please file a ticket at https://trac.macports.org/newticket.

You can force the activation, but that will overwrite the file(s) in question with the copies from the demeter port. Uninstalling that port later will delete those files, which may then in turn break other software that relies on p5.34-ifeffit.

Installing SDL 2 with Macports; Is X11 a dependency?

Most people have moved to Homebrew as their package system, but Macports should work just fine.

Universal does not mean PowerPC necessarily. In fact almost no one needs it anymore. Universal means a fat binary, which architectures this defines is set in your Macports configuration.

SDL2 should work just fine under Quartz, no need to have X11 - as also makes deployment annoying and difficult as you need to have XQuartz installed.

Also don't be afraid to reinstall SDL2 with other options if you miss something, it shouldn't take to long.

TL;DR Just install it without any additional flags unless you discover you need something special.

---

Related Topics