Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

lout: fix to use MacPorts-selected compiler, and specify compatible compilers #662

Merged
merged 2 commits into from Sep 13, 2017
Merged

Conversation

kencu
Copy link
Contributor

@kencu kencu commented Aug 12, 2017

Description
Type(s)
  • bugfix
  • enhancement
  • security fix
Tested on

macOS 10.12
Xcode 8.3.3

Verification

Have you

  • checked your Portfile with port lint?
  • tried existing tests with sudo port test?
  • tried a full install with sudo port -vst install?
  • tested basic functionality of all binary files?

@kencu
Copy link
Contributor Author

kencu commented Aug 12, 2017

part 1 of a fix for lout failing to run on SIerra. This part fixes the build to use the MacPorts-selected compiler.

@kencu
Copy link
Contributor Author

kencu commented Aug 12, 2017

Travis built the 10.10 and 10.11 versions OK -- those clangs appear to work, but 10.12's clang does not.

@kencu
Copy link
Contributor Author

kencu commented Aug 12, 2017

here are the compiler test results on Sierra:

/usr/bin/clang FAIL
clang 3.7 not on buildbot, skip
clang 3.8 FAIL
clang 3.9 FAIL
clang 4.0 PASS
clang 5.0 PASS
gcc6 PASS

@@ -1,4 +1,5 @@
PortSystem 1.0
PortGroup compiler_blacklist_versions 1.0
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You're not using this portgroup. But you should use it, to blacklist specific versions of Xcode clang, such as compiler.blacklist-append {clang >= 802 < 900} (replace these version numbers with the actual version numbers that are affected by this bug). This should be done outside of any platform-version-specific block, assuming it would affect those versions of Xcode clang on any systems where they work.

Copy link
Contributor Author

@kencu kencu Aug 15, 2017

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can do it that way. XCode clang 703.0.31 built it OK. xcode clang 802.0.42 did not.

We don't yet know the number of the clang in the future that might work to build it again, we blacklist all clangs > 800. Once xcode 9 comes out, we can check again to see if there's an upper bound.

# see <https://github.com/macports/macports-ports/pull/662>
compiler.blacklist-append {macports-clang-3.[0-9]} clang
compiler.fallback-append {macports-clang-4.0} {macports-clang-5.0}
}
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

There is no reason to enclose plain compiler names inside curly brackets, such as on the fallback line. (I see why you're doing so on the blacklist line, though, to prevent Tcl from interpreting the square brackets.)

@kencu kencu changed the title lout: fix to use MacPorts-selected compiler lout: fix to use MacPorts-selected compiler, and specify compatible compilers Aug 26, 2017
@kencu
Copy link
Contributor Author

kencu commented Sep 4, 2017

@ryandesign -- I think everyone is leaving this to you given your requested changes (done).

@kencu kencu merged commit cb95534 into macports:master Sep 13, 2017
@kencu
Copy link
Contributor Author

kencu commented Sep 13, 2017

No revbump as Port either built correctly or not at all

@kencu kencu deleted the lout-fix branch September 20, 2017 21:25
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
3 participants