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

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

Closed
sagetrac-mabshoff mannequin opened this issue Jan 23, 2009 · 3 comments
Closed

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

sagetrac-mabshoff mannequin opened this issue Jan 23, 2009 · 3 comments

Comments

@sagetrac-mabshoff
Copy link
Mannequin

sagetrac-mabshoff mannequin commented Jan 23, 2009

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.

Thoughts?

Cheers,

Michael

Component: build

Reviewer: Jeroen Demeyer

Issue created by migration from https://trac.sagemath.org/ticket/5062

@sagetrac-mabshoff sagetrac-mabshoff mannequin added this to the sage-5.11 milestone Jan 23, 2009
@sagetrac-mabshoff sagetrac-mabshoff mannequin self-assigned this Jan 23, 2009
@jdemeyer jdemeyer modified the milestones: sage-5.11, sage-5.12 Aug 13, 2013
@jdemeyer
Copy link

comment:3

No idea really what this is about...

@jdemeyer
Copy link

Reviewer: Jeroen Demeyer

@jdemeyer jdemeyer removed this from the sage-6.1 milestone Dec 19, 2013
@vbraun
Copy link
Member

vbraun commented Dec 20, 2013

comment:5

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants