Ticket #22 (assigned enhancement)

Opened 2 years ago

Last modified 8 months ago

32/64/32-bit building switch

Reported by: was Assigned to: gfurnish (accepted)
Priority: minor Milestone: sage-3.2.2
Component: build Keywords:
Cc:

Description

Should there be something to keep people from building on 32-bit then 64-bit then 32-bit.

Change History

08/19/2007 01:14:34 AM changed by was 

[01:10] <william> the problem was doing something like "sage -br" on both a 32-bit and 64-bit machine but
[01:10] <william> with a shared filesystem.
[01:10] <mabshoff> Ah, that makes sense.
[01:10] <william> I.e., when you build sage for one architecture, maybe you shouldn't be allowed to
[01:10] <william> do "sage -br" or "sage -i" if the architectrue doesn't match.
[01:11] <mabshoff> okay,
[01:11] <william> or something like that.

09/10/2007 07:17:09 PM changed by mabshoff

  • milestone set to Sage-2.10.

09/18/2007 10:11:52 AM changed by was 

[10:01] <wstein> regarding #22 the idea is that people might do "sage -br" on one machine, then login to another machine that
[10:02] <wstein> nsf mounts the same directory, and muck things up.
[10:02] <wstein> We should cache "uname -p" in SAGE_ROOT, and if it changes not allow "sage -br" unless the user
[10:02] <wstein> (or sage -i) or sage -upgrade, unless the user manually deletes the file.
[10:03] <wstein> Thoughts?

11/25/2007 05:12:02 PM changed by mabshoff

  • owner changed from somebody to mabshoff.
  • status changed from new to assigned.
  • milestone changed from sage-2.10 to sage-2.8.15.

03/21/2008 04:52:02 PM changed by gfurnish

  • owner changed from mabshoff to gfurnish.
  • status changed from assigned to new.

03/21/2008 04:53:04 PM changed by gfurnish

  • status changed from new to assigned.

03/23/2008 05:09:24 AM changed by gfurnish

Fixed in #1261 (PBuild)

04/04/2008 12:55:36 PM changed by gfurnish

  • component changed from basic arithmetic to build.