llvm-3.4: error: invalid version number in '-mmacosx-version-min='

[watsodw]

Error is: clang: error: invalid version number in '-mmacosx-version-min=';

Running Mountain Lion 10.8.5, Xcode 5.0.2;

Is this version of llvm and clang only for Mavericks?

[ryandesign (Ryan Carsten Schmidt)]

Replying to david.w.watson@…:

Is this version of llvm and clang only for Mavericks?

No; apparently there is a bug.

Are you running MacPorts 2.2.1 as indicated, or trunk?

[watsodw]

I'm running 2.2.1, not trunk.

[jeremyhu (Jeremy Huddleston Sequoia)]

I can't reproduce this. There are no other reports. The buildbots are all happy. You're going to need to provide more information. There's something interesting about your configuration that is triggering this. Can you please provide additional information?

[ryandesign (Ryan Carsten Schmidt)]

Ah yes. The log shows:

:info:configure checking for sed... /opt/macports/bin/sed

What is this? I assume this is GNU sed, but MacPorts gsed port deliberately installs the binary as gsed, not sed; did you manually create a sed symlink to gsed? If so, that's a problem, and would explain the first error shown in the log:

:info:build sed: invalid option -- E

-E is an option that only works with BSD sed (which is what OS X ships with; GNU sed would require the -r option instead).

[ryandesign (Ryan Carsten Schmidt)]

Makefile.rules runs this code on Darwin:

  # Strip a number like 10.4.7 to 10.4
  DARWIN_VERSION := $(shell echo $(DARWIN_VERSION)| sed -E 's/(10.[0-9]+).*/\1/')
  # Get "4" out of 10.4 for later pieces in the makefile.
  DARWIN_MAJVERS := $(shell echo $(DARWIN_VERSION)| sed -E 's/10.([0-9]+).*/\1/')

By using the -E flag, this code assumes that sed is BSD sed; this is a reasonable assumption on Darwin, and making sed be (or be a symlink to) gsed will break this. So if sed is (or is a symlink to) gsed on your system, please remove that. If you want to be able to run gsed by typing sed, the way we intend for you to be able to do that is for you to add /opt/macports/libexec/gnubin to your shell $PATH variable; this won't adversely affect port builds.