On 12/06/10 20:48, Julian Seward wrote:
> Hmm, doesn't work with the stock perl on redhat9 (prehistoric, I know,
> but certainly post-dates perl 5.005). Am I doing something wrong?
Don't you need to explicitly make $x a Math::BigInt?
> $ cat ascript.pl
> #! /usr/bin/perl
>
> use Math::BigInt;
On Monday, June 07, 2010, Tom Hughes wrote:
> On 07/06/10 07:15, Julian Seward wrote:
> >> Probably best just to use Math::BigInt then you can do arbitrary
> >> precision integer arithmetic regardless of the underlying platform.
> >
> > Is Math::BigInt is supported as standard in Perl? and also,
Hi all,
Just let me know when you have something for me to test.
Regards,
Robert
--
Robert Berger
Embedded Software Specialist
Reliable Embedded Systems
Consulting Training Engineering
Tel.: (+30) 697 593 3428
Fax.:(+30) 210 684 7881
URL: http://www.reliableembeddedsystems.com
~~~
On 07/06/10 07:15, Julian Seward wrote:
>> Probably best just to use Math::BigInt then you can do arbitrary
>> precision integer arithmetic regardless of the underlying platform.
>
> Is Math::BigInt is supported as standard in Perl? and also, in older
> Perls? Obviously if the build process is g
> Why Perl ? Perl isn't used anywhere yet during the Valgrind build --
> that would introduce an additional dependency.
It just seems convenient, plus it is already a dependency and is checked
for by the configure script. Some of the analysis scripts for Cachegrind
and Massif are written in Perl
On Sun, Jun 6, 2010 at 10:41 PM, Julian Seward wrote:
> Oh, darn. It looks like I broke cross compilation recently by
> introducing link_tool_exe.c as part of the build process.
>
> Honestly .. the your best bet is to rewrite link_tool_exe.c as
> a perl script, so it can run on the host. I actua
> Probably best just to use Math::BigInt then you can do arbitrary
> precision integer arithmetic regardless of the underlying platform.
Is Math::BigInt is supported as standard in Perl? and also, in older
Perls? Obviously if the build process is going to rely on it then
it needs to be availabl
On 06/06/10 21:41, Julian Seward wrote:
> Honestly .. the your best bet is to rewrite link_tool_exe.c as
> a perl script, so it can run on the host. I actually started out
> to write it as a perl script, but couldn't find a way to make it
> portably do 64-bit arithmetic, which it needs to do on s
Oh, darn. It looks like I broke cross compilation recently by
introducing link_tool_exe.c as part of the build process.
Honestly .. the your best bet is to rewrite link_tool_exe.c as
a perl script, so it can run on the host. I actually started out
to write it as a perl script, but couldn't find
Hi,
I'm trying to get valgrind running with an AMCC PPC kilauea board,
ELDK4.2, and a recent kernel.
That's what I did so far:
svn co svn://svn.valgrind.org/valgrind/trunk valgrind
cp dispatch-ppc32-linux.S valgrind/coregrind/m_dispatch
(that's a patched version, which gets rid of the altivec ins
10 matches
Mail list logo
