Opened 3 years ago

Last modified 3 years ago

#21708 new enhancement

Detect XCode version

Reported by: mkoeppe Owned by:
Priority: major Milestone: sage-7.5
Component: build: configure Keywords:
Cc: vbraun, embray, jdemeyer, tscrim, aschilling Merged in:
Authors: Reviewers:
Report Upstream: N/A Work issues:
Branch: Commit:
Dependencies: Stopgaps:

Change History (5)

comment:1 in reply to: ↑ description Changed 3 years ago by jdemeyer

Replying to mkoeppe:

We should detect the XCode version in configure and refuse to build until the user has updated XCode to latest.

I don't like these kind of checks. They are often annoying are rarely helpful. (I remember that MPIR at some point had very strict compiler checks. Often, those checks would fail and MPIR would refuse to build. But if the check was bypassed, MPIR built just fine)

Besides, are we sure that "Outdated XCode versions frequently cause build trouble"? I know that badly/partially installed XCode versions frequently cause build trouble. If you want to add a check, I would focus on that first.

comment:2 Changed 3 years ago by mkoeppe

I actually don't like such tests either, but I think it's better than having users find out after hours of building sage when building one of the later packages breaks.

I don't know much about the project's infrastructure for testing (buildbots?). So I don't know if we ever test automatically on different Mac OS versions, different XCode versions etc.

Travis CI has some infrastructure for that: https://docs.travis-ci.com/user/osx-ci-environment/ Perhaps we can use it?

comment:4 follow-up: Changed 3 years ago by vbraun

  • I agree that its super annoying
  • Since the Xcode version is loosely tied to the OS version we would also effectively shut out older OSX versions.
  • Apple tends to cut off developers when they don't use the latest Xcode as well.
  • The free TravisCI is afaik too slow to build Sage, let alone test it.

comment:5 in reply to: ↑ 4 Changed 3 years ago by mkoeppe

Replying to vbraun:

  • The free TravisCI is afaik too slow to build Sage, let alone test it.

Yes, I tried it (see https://travis-ci.org/mkoeppe/sage/jobs/167999674) and even on a build without gcc, we're hitting a "per-job time limit" , which turns out to be ... 50 minutes (https://docs.travis-ci.com/user/customizing-the-build/#Build-Timeouts).

Note: See TracTickets for help on using tickets.