On 11/15/10 07:03 PM, John H Palmieri wrote:
On Nov 15, 3:06 am, "Dr. David Kirkby"<david.kir...@onetel.net>
wrote:
There are to my knowledge a few problems with making binaries with Sage

1) It is slow

2) It fails to work on Solaris, unless on installs the GNU binutils and uses a
GNU version of 'cp'

Is this still true? For a while now, sage-bdist has used "cp -pPr",
not "cp -a".  Maybe it should use tar instead, but does it really fail
on Solaris?  I'm pretty sure I used sage-bdist successfully on t2 a
few months ago, for example.  When I just now tried sage-bdist on
hawk, it prints some warning messages, but it does produce a tar.gz
file which seems to unpack successfully.  I haven't run all tests yet,
but it looks okay right now.

--
John

Thank you John. I forgot that had been fixed. I noticed that the buildbot failed on t2 to build a binary

It is still very verbose, it must be said. I don't think we need the 'v' option on tar. Jeroen remarked, the log file 12 MB. Much of that is probably due to the 'v' option on tar.

Dave

--
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
URL: http://www.sagemath.org

Reply via email to