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

flint always building 32-bit on Solaris even when SAGE64="yes" #7139

Closed
sagetrac-drkirkby mannequin opened this issue Oct 6, 2009 · 1 comment
Closed

flint always building 32-bit on Solaris even when SAGE64="yes" #7139

sagetrac-drkirkby mannequin opened this issue Oct 6, 2009 · 1 comment

Comments

@sagetrac-drkirkby
Copy link
Mannequin

sagetrac-drkirkby mannequin commented Oct 6, 2009

Using

  • A Sun Blade 2000 running Solaris 10 update 7
  • Sage 4.1.2.rc0
  • gcc 4.4.1
  • SAGE64 exported to "yes"

Looking at the directory $SAGE_HOME/local/lib, we can see the flint library is 32-bit, even though SAGE64 was set to "yes", so flint is ignoring the setting of SAGE64. It should also be notes that flint ignores CC and CXX too - see #7024

This is far from the only package building 32-bit when SAGE64 is set to "yes" on Solaris. All of the following do, and I suspect there are many others too.

mpir currently mixes 32 and 64-bit objects, so does not build at all #7132.

I will sort this package out after creating a new sage-env, which exports all the variables properly, including the flag for building 64-bit code, which is not always -m64.

Although there is no support for AIX or HP-UX in Sage yet, we could potentially add it - I personally own machines running AIX and HP-UX.

IBM's compiler on AIX uses -q64, and HP's on HP-UX uses +DD64.

The sensible way to resolve this is to add the correct flag on every platform. This is not a very difficult task really. Whilst any changes to the source that might be necessary for a port would take a lot of time, finding the right flags to build with should be quite easy.

Component: porting: Solaris

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

@sagetrac-drkirkby sagetrac-drkirkby mannequin added this to the sage-4.3.1 milestone Oct 6, 2009
@sagetrac-drkirkby
Copy link
Mannequin Author

sagetrac-drkirkby mannequin commented Jan 2, 2010

comment:1

Like an idiot, I created another ticket for this same problem. I'm closing this one, as the other one has the patch and is more upto date.

@sagetrac-drkirkby sagetrac-drkirkby mannequin closed this as completed Jan 2, 2010
@sagetrac-mvngu sagetrac-mvngu mannequin removed this from the sage-4.3.1 milestone Jan 4, 2010
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

0 participants