#7115: [with spkg, needs review] building cliquer (with cliquer-1.2.p0.spkg)
fails
on 32bit OS X 10.4
-----------------------+----------------------------------------------------
Reporter: was | Owner: tbd
Type: defect | Status: needs_review
Priority: blocker | Milestone: sage-4.1.2
Component: build | Keywords:
Work_issues: | Author:
Reviewer: | Merged:
-----------------------+----------------------------------------------------
Comment(by GeorgSWeber):
It does feel good to be part of a team!
I created a new spkg (with the adapted "spkg-install" as above, and
updated "SPKG.txt" and hg repo), here it is:
http://sage.math.washington.edu/home/weberg/spkg/cliquer-1.2.p1.spkg
Tested successfully on both MacIntel OS X 10.4 and MacPPC OS X 10.4, and
also:
{{{
sage -t -long "devel/sage/sage/graphs/cliquer.pyx"
[8.3 s]
----------------------------------------------------------------------
All tests passed!
}}}
Two final remarks. I work often from the command line (more precisely:
bash shell), started with "./sage -sh" in the root directory of the Sage
version I want to work with. Issuing "hg" then fires up exactly the hg of
the respective Sage install. I don't even have a system-wide hg
installation. Mercurial repositories are also used in spkg's. Just use
"sage -f -s foobar.spkg" to leave the spkg resp. its contents undeleted in
spkg/build/foobar/. "cd" there and do "hg export default" to see the
latest commit checked in. After doing some changes (and checking with "hg
diff" what I would check in ...), I do firstly
{{{
hg commit -m "fix for trac ticket #12345"
}}}
and if then, I want to create a patch (and not the spkg as a whole), I do
what I do usually for Sage library patches, too:
{{{
hg export default >> ../../../../patches/trac_12345.patch
}}}
Secondly, regarding the MACOSX_DEPLOYMENT_TARGET="10.3" thing: I knew that
essentially. However, I was not working on my clean-room OS partition, but
from my work installation. There I have MACOSX_DEPLOYMENT_TARGET="10.4" in
my .bashrc file, because it was so annoying to add it every now and again.
So I simply forgot about that, sorry! If you take any "install.log" from a
recent Sage install on Mac OS X, and search for "-undefined
dynamic_lookup", you'll find tons of occurences. There seems to by another
method to tell the compiler that it is OK to use this, by adding this
option to the other linker options:
{{{
-mmacosx-version-min=10.4
}}}
Probably that way is the better way in light of cross-compiling Sage (if
we ever will get to this anytime soon).
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/7115#comment:12>
Sage <http://www.sagemath.org>
Sage: Creating a Viable Open Source Alternative to Magma, Maple, Mathematica,
and MATLAB
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"sage-trac" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/sage-trac?hl=en
-~----------~----~----~----~------~----~------~--~---
