On Thu, Aug 20, 2009 at 12:20 AM, Nathann Cohen<nathann.co...@gmail.com> wrote: > Hello !! > > I am really sorry but I do not feel like I know more about Cliquer than > anyone of us. I mainly built the spkg ( and it took me some time because I > did not know how ), and in the end was told to use SCons to avoid > platform-dependent issues.. > > My only answer to theses tickets is that perhaps 64-bits systems are not > supported by SCons ( but I know next to nothing about them ). If it is > possible to have an access on a 64-bit system, I will of course try to do
Scons works fine on 64-bit systems in general... however, see below. > what I can but I have always used tools such as SConc as if they were black > boxes ^^; > > In the mean time, I wil try to check whether I have friends/colleagues using > a 64-bit machine and make them try Cliquer. So far me in all my testing (which is extensive) your cliquer spkg works fine with Sage on everything except 64-bit OS X, which is the *only* bi-arch architecture we support for Sage (i.e., one can build both 32 and 64-bit binaries). (I'm ignoring Kiran's problem on 64-bit Fedora 10, since I couldn't replicate it, and it is probably different anyways.) Essentially every single spkg that makes a C library has to explicitly do something if the SAGE64 environment variable is set. If an spkg involving a C library doesn't do something in the presence of that variable, the probability it won't work is high, since then the C library will be built in 32-bit mode, which is the default. I'm guessing this is what happened. What login name do you want on the OS X box, when I make accounts next Monday? -- William --~--~---------~--~----~------------~-------~--~----~ To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URLs: http://www.sagemath.org -~----------~----~----~----~------~----~------~--~---
