Opened 6 years ago

Last modified 3 months ago

#21708 new enhancement

macOS: Detect Xcode version

Reported by: Matthias Köppe Owned by:
Priority: major Milestone: sage-9.8
Component: build: configure Keywords:
Cc: Volker Braun, Erik Bray, Jeroen Demeyer, Travis Scrimshaw, Anne Schilling, Samuel Lelièvre Merged in:
Authors: Reviewers:
Report Upstream: N/A Work issues:
Branch: Commit:
Dependencies: Stopgaps:

Status badges

Change History (14)

comment:1 in reply to:  description Changed 6 years ago by Jeroen Demeyer

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 6 years ago by Matthias Köppe

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:3 Changed 6 years ago by Matthias Köppe

comment:4 Changed 6 years ago by Volker Braun

  • 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 6 years ago by Matthias Köppe

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).

comment:6 Changed 3 years ago by Matthias Köppe

Milestone: sage-7.5sage-9.2

comment:7 Changed 2 years ago by Samuel Lelièvre

Cc: Samuel Lelièvre added
Description: modified (diff)
Summary: Detect XCode versionmacOS: Detect Xcode version

The capitalisation is Xcode rather than XCode.

comment:8 Changed 2 years ago by Matthias Köppe

FWIW, homebrew has an Xcode version check but it does not work very well

Warning: A newer Command Line Tools release is available.
Update them from Software Update in System Preferences or run:
  softwareupdate --all --install --force
$ softwareupdate --all --install --force
Software Update Tool

Finding available software
No updates are available.

comment:9 Changed 2 years ago by Matthias Köppe

Milestone: sage-9.2sage-9.3

comment:10 Changed 21 months ago by Matthias Köppe

Milestone: sage-9.3sage-9.4

Sage development has entered the release candidate phase for 9.3. Setting a new milestone for this ticket based on a cursory review of ticket status, priority, and last modification date.

comment:11 Changed 17 months ago by Matthias Köppe

Milestone: sage-9.4sage-9.5

comment:12 Changed 12 months ago by Matthias Köppe

Milestone: sage-9.5sage-9.6

comment:13 Changed 8 months ago by Matthias Köppe

Milestone: sage-9.6sage-9.7

comment:14 Changed 3 months ago by Matthias Köppe

Milestone: sage-9.7sage-9.8
Note: See TracTickets for help on using tickets.