e plot window
dimensions. Apologies if this has already been covered somewhere.
Peter
--~--~-~--~~~---~--~~
To post to this group, send email to sage-devel@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this
n sum(self.list()).sqrt()
The last line should be something like
return sum([x*x for x in self.list()]).sqrt()
(not sure if that is the most efficient way).
--Peter
--~--~-~--~~~---~--~~
To post to this group, send email to sage-devel@googlegroups.com
ematical system like Sage.
(If you sign up at projecteuler.net and use Sage for some solutions,
be sure to select it as your language option.)
Apologies if this should rather have been posted somewhere else...
(please let me know where or repost).
Regard
There is a WYSIWYG equation plugin for TinyMCE that has a demo page at
http://www.imathas.com/editordemo/demo.html .
On Firefox it uses MathML, and on other browsers it uses a graphics
images fallback approach.
--Peter
On Oct 14, 7:38 am, "William Stein" <[EMAIL PROTECTED]>
ression and
SymbolicExpression
(f^3)(x)
Out: f(f(f(x)))
x(10)
Out: Error: SymbolicExpression is not callable
For undergraduates this behavior might be less confusing than having
expressions like
x(x+1) be silently misinterpreted as x+1.
--Peter
On Nov 5, 8:55 pm, Robert Dodier <[EMAIL P
prehensive yet easy to parse linear input form) and would produce
output of the form that has been discussed in this thread.
I think this is feasible and would make (part of) Sage easier to use
for school and undergrad math.
Cheers,
Peter
Robert Bradshaw wrote:
> On Dec 7, 2006, at 5:18 AM
ly enough the following works ok again:
sage: plot3d(lambda x, y: x^2 + y^2, (0,2), (-0,2))
The error checking is meant to catch problems like
sage: plot3d(sin(x), (x,0,2), (x,0,2))
but the check seems to also be applied to plot3d(f, (a,b), (c,d)).
Regards,
Peter
On Jun 2, 5:18 am, Marshall Ha
p icon for the sage_vmx_notebook.vmx file, making
the startup of Sage on Windows almost like starting a native
application.
Personally I have no problem with the current setup, but for some of
my students it would be simpler if they do not have to deal with the
virtual machine directly
Sage.
Thanks,
Peter
Contents of relevant portion of install.log:
--
Successfully installed ecm-6.2.1.p0
Now cleaning up tmp files.
Making Sage/Python scripts relocatable...
Making script relocatable
Finished installing ecm-6.2.1.p0.spkg
sage
Thanks for the answers. I'll see if I can get the system
administrator to install a more current gcc. If I can't get him to,
do you know if it's possible to install a "local" gcc for my own use?
Thanks again,
--Peter
On Jul 13, 11:47 am, William Stein
they couldn't share
worksheets with each others, etc. I think that's not a solution.
Any ideas?
Thanks,
Peter
--~--~-~--~~~---~--~~
To post to this group, send email to sage-devel@googlegroups.com
To unsubscribe from this group, send email to
sage-d
/notebook/templates and restart the server to try it out
with sage-4.1.2.alpha).
Is anyone working on rendering surfaces with shading over the
wireframe?
Also I noticed that the line(...) command does not seem to work with
the canvas3d option.
--Peter
On Sep 26, 10:15 am, Jaap Spies wrote:
> Peter wrote:
> > Hi,
>
> > I really like the canvas3d plot option in 4.1.2 since it will make it
> > easier to implement interactive 3d scenes in Sage and make them also
> > display in browsers that do no
On Sep 25, 6:32 pm, William Stein wrote:
> On Fri, Sep 25, 2009 at 6:01 PM, Peter wrote:
>
> > Hi,
>
> > I really like the canvas3d plot option in 4.1.2 since it will make it
> > easier to implement interactive 3d scenes in Sage and make them also
> > displa
On Sep 25, 6:32 pm, William Stein wrote:
> On Fri, Sep 25, 2009 at 6:01 PM, Peter wrote:
>
> > Hi,
>
> > I really like the canvas3d plot option in 4.1.2 since it will make it
> > easier to implement interactive 3d scenes in Sage and make them also
> > displa
good format for
adding translational and rotational velocities to 3d shapes so that
the .js renderer can do animations.
-- Peter
--~--~-~--~~~---~--~~
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an email
n differential equations")
>
For our Math 380 Introduction to Abstract Algebra course and Math 270
Computatonal Math Tools
Regards,
Peter
> Thanks!!
>
> William
>
> --
> William Stein
> Associate Professor of Mathematics
> University of Washingtonhttp://wstein.org
-
so as not to promise
something it can't deliver?
Regards,
Peter
--~--~-~--~~~---~--~~
To post to this group, send email to sage-devel@googlegroups.com
To unsubscribe from this group, send email to
sage-devel-unsubscr...@googlegroups.com
For more options, visit
pages). E.g. seeing the
neat combinatorics graphic makes me wonder how it was created.
Peter
--~--~-~--~~~---~--~~
To post to this group, send email to sage-devel@googlegroups.com
To unsubscribe from this group, send email to
sage-devel-unsubscr...@googlegroups.com
Hello,
I would like to either develop or find a method for computing with
differential forms in sage. More specifically, the level of
generality I'm looking for is the ability to manipulate differential
forms with values in a Lie algebra. I'd like to define the usual
operations on forms (+, sca
v. = Fext2[]
Fext6. = GF(p**6, name='Y', modulus=v**3 - xi)
Fext6w. = Fext6[]
f = w**2 - Y
f.is_irreducible()
Kind regards,
Peter Schwabe
signature.asc
Description: Digital signature
193536720*X^11 + 92561040*X^10 + 38567100*X^9 + 13884156*X^8 +
4272048*X^7 + 1107568*X^6 + 237336*X^5 + 40920*X^4 + 5456*X^3 + 528*X^2
+ 33*X + 1)*Y
Kind regards,
Peter
signature.asc
Description: Digital signature
it only has a
single FPU shared by all cores. This means FP performance is "poor".
--
Peter Jeremy
pgpmRviaI7gT8.pgp
Description: PGP signature
r, and charging him with a task of making the
>sage homepage as good as the Mathematica one?
IMHO, no. If the Sage Project has spare money, I think it would be
better spent on improving Sage - adding features, fixing bugs or
improving the documentation.
--
Peter Jeremy
pgp6gpatx2MtL.pgp
Description: PGP signature
>this question into the Sage Development Guide; and once you got to
>know the answer, then 2) Update the Sage Development Guide
>accordingly, so the next ones after you will have a yet easier time.
>("Frequently Answered Questions" is just another wording for this.)
This is wor
might
either find a committer willing to run test builds on the cluster or
someone willing to provide you with a shell account on their system.
--
Peter Jeremy
pgpsWsgemihk0.pgp
Description: PGP signature
r thread, there's also nothing about
how trac attachments should be named).
--
Peter Jeremy
pgpnI7WvTSfIf.pgp
Description: PGP signature
I install the TTF TeX fonts, it breaks.
--
Peter Jeremy
pgpUTeCQlhzUE.pgp
Description: PGP signature
r sse sse2 ss ht tm pbe syscall nx lm
constant_tsc arch_perfmon pebs bts rep_good pni monitor ds_cpl vmx est tm2
ssse3 cx16 xtpr dca sse4_1 lahf_lm
If you're using some other OS, you might need a different incantation.
--
Peter Jeremy
pgpJNFHYoyZa2.pgp
Description: PGP signature
ng or build the threaded atlas libraries.
Is mixing thread-enabled code with non-threaded code an oversight within
Sage or is this particular code safe on Linux?
--
Peter Jeremy
pgpb21wgGhlGE.pgp
Description: PGP signature
On 2009-Jul-16 18:16:58 +1000, Minh Nguyen wrote:
>On Thu, Jul 16, 2009 at 9:35 AM, Tom Boothby wrote:
>> Does anybody know/use FreeBSD?
>> bsd #5873 [with patch, needs review] Fix matplotlib build on FreeBSD
>
>I think Peter Jeremy (pjeremy) uses FreeBSD. He has ported
On 2009-Jul-16 20:04:15 +1000, Minh Nguyen wrote:
>Anyone else, besides Peter, who has access to a FreeBSD machine, can
>you please have a look at #5873? I'm not even sure that the machine
>boxen has FreeBSD running in a virtual machine.
boxen is running both 32-bit and 64-b
offer useful input on the first question.
As for the second, without denigrating the effort Kevin has put into it,
I don't think CircuitEngine has a particularly wide range of features.
IMHO, something like SPICE would bea much better choice.
--
Peter Jeremy
pgpnrkxUU1AnR.pgp
Description: PGP signature
cxx/.libs/osfuns.o
cxx/.libs/osmpf.o cxx/.libs/osmpq.o cxx/.libs/osmpz.o -Wl,--rpath
-Wl,/usr/home/peter/sage-4.1/spkg/build/mpir-1.2.p4/src/.libs -Wl,--rpath
-Wl,/usr/home/peter/sage-4.1/local/lib ./.libs/libgmp.so
-L/usr/home/peter/sage-4.1/local/lib
-L/usr/local/lib/gcc43/gcc/i386-portbl
severe.
>I think it would be a good idea to remove the -g flag in general. As
>far as I am aware, there is the SAGE_DEBUG variable, which should be
>set to 1 for debugging.
I tend to agree: Keep in mind that the '-g' flag will only help with
debugging binary code
is wrong and why it didn't obey the "-m64" or
equivalent.
--
Peter Jeremy
pgpl744ZtspQ0.pgp
Description: PGP signature
fically but I've found some parts of
Sage ignore SAGE_FORTRAN (though other parts require it to be
present). My work-around was to create symlinks for the specific
versions of gcc, g++ and gfortran in $SAGE_ROOT/local/bin.
--
Peter Jeremy
pgpDWDWnMx8HL.pgp
Description: PGP signature
(I realise sage-4.1 has been superseded but it seemed less effort to
complete the porting work on a single release and forward-port the
patches in one step rather than continuously forward-porting bits. I
have an equivalent 4.1.1.rc2 patchset in boxen:~peter/sage-4.1.1.rc2.patch
The "make
On 2009-Aug-10 06:53:38 -0700, William Stein wrote:
>On Mon, Aug 10, 2009 at 4:55 AM, Peter Jeremy
>wrote:
>
>> (I realise sage-4.1 has been superseded but it seemed less effort to
>> complete the porting work on a single release and forward-port the
>> patc
th no other changes as part of a major release.
2) If you touch any part of an spkg, you must add 'set -e' and fixup
any subsequent fallout in all scripts in that spkg.
3) If you touch a script, you must fixup that script.
4) Fix it if you feel like it.
--
Peter Jeremy
pgpDJ0B2CDgXH.pgp
Description: PGP signature
On 2009-Aug-11 07:05:42 +1000, Peter Jeremy
wrote:
>I thought I saw a csin() during the build so I'll investigate and
>add code as necessary.
The relevant error in "devel/sage/sage/ext/fast_callable.pyx" is:
ImportError:
/usr/home/peter/sage-4.1.1.rc2/local/lib/pyth
nted yet.
--
Peter Jeremy
pgpvUgtbHQJlo.pgp
Description: PGP signature
usual).
As an alternative scenario, consider TWiki - an "open source" wiki
created/founded by Peter Theony in 1998. By 2008, it had built up
a significant community of developers and was reasonably widely used.
Peter Theony suddenly changed the rules and license and locked out
existing develo
ably an opportune time to refer the readership to
"Reflections on Trusting Trust" by Ken Thompson.
--
Peter Jeremy
pgpTtEEGiw6vw.pgp
Description: PGP signature
ough fairly recently to bring them into line
with the latest values).
--
Peter Jeremy
pgpvlW5W9W4j6.pgp
Description: PGP signature
lines in makefiles need to avoid bash'isms ('source'
is used in at least one makefile) or SHELL needs to be set to bash
at the start of the build process.
--
Peter Jeremy
pgpxEFsUx2jZ3.pgp
Description: PGP signature
d Inf typically add a page of C code.
Even something as simple as cabs(z) aka hypot(z) needs about 70 lines
of C to do properly.
--
Peter Jeremy
pgp5Hu6J03EJz.pgp
Description: PGP signature
s functions.
Patch sage/ext/gen_interpreters.py to include the above:
if UNAME[0] == "Solaris":
ext_modules.append(
Extension('sage.misc.solaris_utilities',
sources = ['sage/misc/solaris_memory_usage.c',
'sage/misc/s
s) of information? For the former,
should it be a vector (eg n-th element is 5-min load average) or a
hash (5-min load average has a key of 'LA5' or similar). (And BTW,
not all OSs measure load averages over the same periods). Once that
is decided, the most natural units for that information can be
determined.
--
Peter Jeremy
pgppG4MXlGmtP.pgp
Description: PGP signature
robably overwhelm it.
There is an associated XO server and I feel that would be a more
logical location for Sage (in notebook format).
--
Peter Jeremy
pgpN3AL84nbOz.pgp
Description: PGP signature
quot;, "Solaris", "FreeBSD" etc)
- Architecture ("SPARC", "x86", "x86_64", etc)
- Anything else I've forgotten.
- CPU type (cpuinfo model name on Linux)
--
Peter Jeremy
pgpV7PVgNSaZ5.pgp
Description: PGP signature
; 16 processes in parallel using
>multiprocessing on t2 and got no speed up. I think 128 at once would
>not be faster than 16 without doing something clever (that I totally
>don't understand).
Given that sage is FP-intensive and a T-2 processor has 8 FPUs (ie the
box t2 has 16 FPUs), there's p
people
who take your scripts and try to use them on (eg) Solaris.
--
Peter Jeremy
pgpx2EwN9YREz.pgp
Description: PGP signature
x27;t get lost.
The current major stumbling block is the lack of C99 complex maths
functions in FreeBSD and I hope to find some time in the next few
weeks to produce and test at least simplistic implementations for
the functions that Sage needs.
--
Peter Jeremy
pgp6kOlqptEpF.pgp
Description: PGP signature
is a nuisance when trying to compare build logs between Linux and FreeBSD).
>Can anyone think of any other variables that might be needed, perhaps
>for OS X, FreeBSD etc?
I can't think of any for FreeBSD.
--
Peter Jeremy
pgpsf887jJ5MQ.pgp
Description: PGP signature
they are not cheap, but the Sun one is free.
You have to pay if you want support for the Sun compiler. Im my
experience, the stock compiler is fairly buggy and patch access
requires a support contract.
--
Peter Jeremy
pgpRuwHFeUKB6.pgp
Description: PGP signature
ly, FreeBSD support in VirtualBox
is still a work-in-progress and isn't production-ready.
Are there any plans to resurrect the FreeBSD guests? As I've mentioned
before, I can't easily develop on anything earlier than FreeBSD 8.x.
--
Peter Jeremy
pgpEsbr3EKiuD.pgp
Description: PGP signature
ointyhat are available
at http://tinderbox.marcuscom.com/. (Note that I'm not suggesting that
either tool is directly applicable to Sage - this is just an indication
of what is possible).
--
Peter Jeremy
pgpqXrqXgAPdu.pgp
Description: PGP signature
gt;I think I'll have to leave any tests for linux (or let someone else
>write them), as I believe there are too many different distributions
>to worry about.
It would be nice to have a list of base OS shared libraries that Sage
expects and do a check against the available libra
limitations that pure
mathematics doesn't. A review of the relevant working group
debates might shed some light on their reasoning.
[1] "Parabola incorporating Function, a mathematics magazine for
secondary schools", ISSN 1446-9723
http://www.maths.unsw.edu.au/highschool/parabola.html
[2] Adjunct Senior Research Fellow in Mathematics & Statistics at
Monash University.
--
Peter Jeremy
pgpJlc6jHmx1W.pgp
Description: PGP signature
x27;s at work but, unfortunately, I
can't think of any way to justify my employer making one available to
the Sage community).
>I would imagine producing a list of what libraries and programs are
>needed for every Sage package would be a very daunting task.
Running 'ldd' on each executable and shared library would be a decent
start, but runs the risk of missing a library that is dlopen'd but
required.
--
Peter Jeremy
pgpVRMfGkqHRW.pgp
Description: PGP signature
till rough edges in both the host and guest sides of
VirtualBox's FreeBSD support. I haven't actually tried VirtualBox.
If William has tried installing it, I'd be interested in the results.
--
Peter Jeremy
pgpDCaUaB1Dv4.pgp
Description: PGP signature
On 2009-Oct-28 23:56:12 -0700, William Stein wrote:
>freebsd tbd
Since I seem to be the only person doing anything with FreeBSD, I
guess I'll take this one.
--
Peter Jeremy
pgpNq7acLO05E.pgp
Description: PGP signature
igest delivery, virtual domain support, and more.
--
Peter Jeremy
pgpIOlXfpOpn0.pgp
Description: PGP signature
Sun for 7 billion USD. For a company to be valued
>at $7,000,000,000 they must have done something right!
Oracle's CEO is also stating that Sun is losing massive amounts of
money - which suggests they aren't doing everything right. The
valuation is also what Oracle is willing to pay
see these as being special fields or just the general trac body?
The only downside I can see is that tickets won't be updated from case
3 to case 4 - but that's still going to be a vast improvement over what
we have now.
--
Peter Jeremy
pgpHpzd9lXoLg.pgp
Description: PGP signature
vious non-GPL spkg
is Python, most of the others are BSD-style licenses.
The OpenSSL licenses are basically BSD but still include the advertising
clause (I haven't found any other spkgs with that). Maybe we need to
revisit and clarify the rationale behind the statement in ticket 478.
--
Pet
virtually every question mandatory
is likely to turn people off or make them pick random answers to
questions they don't want to answer.
--
Peter Jeremy
pgpT27p6kML5e.pgp
Description: PGP signature
so depends on the type expr(1) uses for integer math.
- I wouldn't bet on everyone currently working on Sage being dead in 2100:
If you're in your early 20's now, you'll be less that 115 then - which
is not impossible today and will only become more common in future
(
could replace GLPK, which 4ti2 uses at the
moment, which does not seem that widely used or supported.
Lastly, 4ti2 is listed as an experimental package SAGE. I was
wondering what would need to change in 4ti2 so that it is no longer an
experimental package?
Best regards,
/polynomial/multi_polynomial_ideal.py"
sage -t "devel/sage/sage/rings/padics/padic_base_generic.py"
sage -t "devel/sage/sage/rings/tests.py"
sage -t "devel/sage/sage/rings/real_double.pyx"
sage -t "devel/sage/sage/plot/axes.p
notice this is
done for some tools)? I know that trying to turn sage into a FreeBSD
port in its current form will encounter resistance due to this (there
is pressure on other large ports like OpenOffice.org and the Mozilla
suite to depend on FreeBSD ports rather than embedding equivalent
function
On 2009-Mar-23 20:50:05 +1100, Peter Jeremy
wrote:
>I've been doing some work on getting Sage-3.4 to work natively on
>FreeBSD and I've reached the point where I can compile sage-3.4 on
>FreeBSD-8/amd64 (using gcc/g++/gfortran 4.3) and get it to start.
I've done some
On 2009-Mar-28 20:00:12 -0700, William Stein wrote:
>
>On Sat, Mar 28, 2009 at 7:55 PM, Peter Jeremy
> wrote:
>> sage -t "devel/sage/sage/schemes/elliptic_curves/lseries_ell.py"
>> Runs out of swap.
>
>How much RAM does this machine have? How much
On 2009-Mar-28 21:12:09 -0700, mabshoff wrote:
>On Mar 28, 9:08 pm, Peter Jeremy wrote:
>> On 2009-Mar-28 20:00:12 -0700, William Stein wrote:
>> >On Sat, Mar 28, 2009 at 7:55 PM, Peter Jeremy
>> > wrote:
>> >> sage -t "devel/sage
is far less portable than sysconf() because it _only_ works
on Linux, whereas sysconf() should work on nearly all Unix systems
(and some others).
--
Peter Jeremy
pgpuhAyd6qxwr.pgp
Description: PGP signature
ifies
requires all the values to be queryable. (And you are still up
against Microsoft complying with the letter, rather than the spirit of
POSIX).
--
Peter Jeremy
pgpPpJZQuwc6c.pgp
Description: PGP signature
x27; % ctype)
numpy.distutils.fcompiler.CompilerNotFound: gnu95: f90 nor f77
Error building scipy.
The problem is that numpy/distutils/fcompiler/gnu.py has a number of
names hard-coded (g77, f77, gfortran, g95) and, when building scipy,
appears to not check sage_fortran (which would use SAGE_FORTRAN) and
thus fails if the compiler does not match one of the hard-coded names.
Has anyone else run into this problem?
--
Peter Jeremy
pgpVVvEBqET4a.pgp
Description: PGP signature
, if it worthwhile always trying
pari's fator first and then verifying its output. If it's wrong,
then try Sage's factor.
The only issue I can see would be if pari sometimes incorrectly
reports composite numbers as prime - which means every "prime" number
reported by pari
built by default. Ideally, the 32 vs 64 bit code should be
centralised and the relevant cc/c++/fortran/linker flags passed into
each spkg-install.
--
Peter Jeremy
#!/bin/sh
# Determine the type of C compiler, which can later
# be used to determine the flags the C compiler
# will want. T
On 2009-Dec-29 23:57:13 +, "Dr. David Kirkby"
wrote:
>Peter Jeremy wrote:
>Yes it does. And I can understand why, since for 99% of programs, there is no
>advantage to 64-bit, but some disadvantages (larger pointers, let fit in cache
>etc).
OTOH, programs doing multi-
As a correctly rounded IEEE-754 double precision constant,
e=0x4005BF0A8B145769 (0x2.B7E1 5162 8AED 2), this should convert
to 2.7182818284590451 (rounded to "sufficient" accuracy).
2.7182818284590455 is 1ULP high - this may reflect a rounding error
in either the exp() or double_to_ascii() implementation.
--
Peter Jeremy
pgp4gSQUSA23H.pgp
Description: PGP signature
On 2009-Dec-30 00:49:40 -0800, Robert Bradshaw
wrote:
>On Dec 29, 2009, at 9:14 PM, Peter Jeremy wrote:
>> x86 vs x86_64 isn't as clearcut because the x86 architecture is so
>> badly designed - the relatively small number and lack of orthogonality
...
>I was under the
^^ this needs to be at least 18 to see the problem.
>}
--
Peter Jeremy
pgpjbXnFSiZY1.pgp
Description: PGP signature
te between 64 and 80 bits depending on the
code, optimisation level and whim of the compiler. More precision is
not always good. This extra precision (and particularly the
arbitrariness of its existence) can wreak havoc in a function that
expects 'double' to be 64-bits.
>result m
a
library by pathname then you have to specify the pathname of the wanted
version of the library. I find this a PITA.
As I've mentioned before, and despite claims otherwise, Solaris
behaves very much a 32-bit OS with 64-bit support tacked on.
--
Peter Jeremy
pgp1mRIHbBStx.pgp
Description: PGP signature
al suggestion would be to add 'set -x;env' near the top of
both the original and patched spks-install file, run both (in suitable,
clean environment) and diff the output. If we can see what is actually
different, we might be able to work out what is going wrong.
--
Peter Jeremy
pgpkKkVK29kTC.pgp
Description: PGP signature
there's nothing in prereq which clearly states one way or
the other) but it looks like mpir is building all the assembler
code in 64-bit mode and all the C code in 32-bit mode. That
definitely isn't going to work.
--
Peter Jeremy
pgpKFLqT0jsBD.pgp
Description: PGP signature
64' in LDFLAGS with a gcc frontend, whether
the gcc or Sun linker is actually being used.
This also means that you need to be careful using '-Wl' since you need
to ensure that the arguments are valid for whichever linker is in use.
--
Peter Jeremy
pgphE730rpRGI.pgp
Description: PGP signature
who is
porting Sage to re-engineer all the OS-dependent patches.
My personal feeling is that it would be nice if some of the more generic
packages (eg bzip, zlib, readline, mercurial) were moved out of sage
and made explicit requirements.
--
Peter Jeremy
pgp4h8gNfaYgn.pgp
Description: PGP signature
'exit eval "use Foo::Bar;1";' ; then echo Not Found ;else
echo Found;fi
Not Found
server% if perl -e 'exit eval "use strict;1";' ; then echo Not Found ;else echo
Found;fi
Found
server%
--
Peter Jeremy
pgpyujVrOnuwf.pgp
Description: PGP signature
e assumes /bin/sh is bash -
these all need to be rooted out. Scripts either need to assume that
/bin/sh is Bourne shell (note that /bin/sh on Solaris is pre-POSIX) or
invoke the shell as bash. (A partial workaround is to have
$SAGE_ROOT/local/bin/sh as a symlink to bash).
--
Peter Jeremy
pgpspI9VzUIMw.pgp
Description: PGP signature
- joy.
What is stopping you? Feel free to contact me off-list if you'd like
assistance.
--
Peter Jeremy
pgpnzRMXFqUWU.pgp
Description: PGP signature
On 2010-Jan-24 03:31:17 +, "Dr. David Kirkby"
wrote:
>Peter Jeremy wrote:
>> On 2010-Jan-24 11:00:39 +1300, François Bissey
>> wrote:
>>> Of course I could actually get an actual freebsd machine - joy.
>>
>> What is stopping you?
On 2010-Jan-24 17:55:18 +0300, Aleksej Saushev wrote:
>Peter Jeremy writes:
>> AFAIK, both NetBSD and FreeBSD just inherited PMake from 4.4BSD.
>
>When did that happen? Look at the calendar, it's been 15 years of development
>since.
In FreeBSD's case, May 1994. I am
FP performance would probably count
against it).
Given the Willian has a bucket of money to spend, maybe he should
invest in a UltraSPARC based system - an 2nd hand V440 or V445 or
a new M-series machine. These have much better single-threaded
performance.
--
Peter Jeremy
pgpAviQff70MA.pgp
Description: PGP signature
e longer term,
it might be worthwhile looking at why the Solaris iconv is inadequate
for R and whether R can be adapted to use Solaris iconv.
--
Peter Jeremy
pgpL4zx2z5r2k.pgp
Description: PGP signature
her it's gcc or libtool that is broken
but one of them is.
>But from experience, compiling code on multiple platforms often shows
>up errors not seen on other platforms, but lie in wait, ready to give
>the wrong answers at some point in the future.
Agreed.
--
Peter Jeremy
pgpFNxyUvE2NB.pgp
Description: PGP signature
n output very quickly but by the time you'd double-checked the
calculation, you might as well have done it by hand to start with.
--
Peter Jeremy
pgpxT0fyPN0OP.pgp
Description: PGP signature
be problematic.
Finding the exact restrictions probably means asking the GCC
maintainers. There are also likely to be different restrictions on
compiling an application with gcc-X and trying to run it when only
gcc-Y is installed and compiling bits of an application with gcc-X
and other bits wi
1 - 100 of 327 matches
Mail list logo
