#7013: [with patch, needs work] prime_pi and nth_prime
---------------------------+------------------------------------------------
Reporter: kevin.stueve | Owner: kevin.stueve
Type: enhancement | Status: new
Priority: major | Milestone:
Component: number theory | Keywords: primes, sieve, table,LMO
Reviewer: was | Author: Kevin Stueve
Merged: |
---------------------------+------------------------------------------------
Comment(by GeorgSWeber):
Hi Kevin,
you posted a *.lzma-compressed file. On my Mac, neither 7-zip installs out
of the box (seems to be MS Windows-only, see http://www.7-zip.org/), nor
do I intend to install DarwinPorts or Fink, which contain packages to
unpack such files, nor did I find some standalone *.dmg for OS X by
googling some minutes around. So I'm unable to unpack this file on my
computer.
Sorry, but that's a problem of your patch, not of my system installation.
Patches in trac are supposed to be created by hg/mercurial and to apply
seamlessly to Sage, or you should provide a link (!) to some file in
*.spkg format, or both. Did you read the respective parts of the "Sage
Programming Guide", by the way?
From what you write in the sage-devel thread ("Be sure to use the -m32
option when compiling the c code ...") it seems that (some C part of) your
code lacks anyway build scripts that work "out of the box" on each of the
platforms supported by Sage. For a start, have a look at the
"Cliquer.spkg" already in Sage, or at the "Frobby.spkg", not yet in Sage
due to build problems on Solaris (see trac ticket #6416), in case your C
code is rather "external" to the Sage library.
On the other hand, if your code is intended to "go directly into the Sage
library", you need anyway to tell the then-necessary Cython bridge how to
compile your code correctly (see module_list.py). And probably some
database integration, if I understand correctly what you want to do.
Better still, drop the necessity of "-m32" by using, in your code, fixed-
sized C types like "uint32_t" from (ISO/ANSI C99) stdlib.h (wich exists
even for msvc, although provided by third parties), and not plain
"int"/"long"/... if your algorithm depends on that. But without being able
to even have a single look at your code, I'll stop here.
And please, please, don't post MB-sized compressed files into trac itself,
but rather post links to some accessible webspace instead. I did that
myself for one of my first patches for Sage, and got pretty washed my head
(see trac ticket #4857, if you want to), the file itself being erased from
trac by the admin almost immediately ... (the reason is that trac is best
used "text-based", and any compressed blob has to remain in there for
eternity, which is bad for both size-archive-backup issues, and
performance).
Heads up! ;-)
Cheers,
Georg
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/7013#comment:2>
Sage <http://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
-~----------~----~----~----~------~----~------~--~---
