Opened 14 years ago

Closed 9 years ago

#5062 closed defect (wontfix)

Make sure that "sage -b" checks build compatibility on shared filesystems

Reported by: Michael Abshoff Owned by: Michael Abshoff
Priority: critical Milestone: sage-duplicate/invalid/wontfix
Component: build Keywords:
Cc: Merged in:
Authors: Reviewers: Jeroen Demeyer
Report Upstream: N/A Work issues:
Branch: Commit:
Dependencies: Stopgaps:

Status badges


This is a followup to #22:

Having thought about this and played around a little with uname it seems that it will not work and is not fine grained enough anyway. I would suggest to do write a small C program that identifies the following:

  • mode: i.e. 32, 64 bit
  • os: linux, osx, solaris, freebsd, cygwin
  • release: this would be the distribution on Linux, OSX 10.4/10.5, Solaris 10/Solaris 11/Opensolaris and so on

The way we can properly identify the build platform and decide more intelligently if we issue a warning, i.e running the Fedora 10 build on a Fedora 9 box should abort since it doesn't work. The test should be wrapped in a shell script since the binary will obviously only run on a subset of arches, i.e. if the binary fails to run we just about and print a canned warning together with a config info saved as text that is created when building the binary.

This is enough a task to split it off to a new ticket. I have some basic code that does some of the above already for OSX since I need this kind of code while cleaning up the build system.




Change History (5)

comment:1 Changed 14 years ago by Michael Abshoff

Status: newassigned

comment:2 Changed 9 years ago by Jeroen Demeyer

Milestone: sage-5.11sage-5.12

comment:3 Changed 9 years ago by Jeroen Demeyer

Milestone: sage-6.1sage-duplicate/invalid/wontfix
Report Upstream: N/A
Reviewers: Jeroen Demeyer
Status: newneeds_review

No idea really what this is about...

comment:4 Changed 9 years ago by Jeroen Demeyer

Status: needs_reviewpositive_review

comment:5 Changed 9 years ago by Volker Braun

Resolution: wontfix
Status: positive_reviewclosed

E.g. on skynet one could print an error when trying to run a sparc binary on x86. Though I can assure you there will be an error even without the theck ;-) In any case, implementation would just have to compare some uname entries, no need for a C program.

Note: See TracTickets for help on using tickets.