On Thu Jan 17 17:26:45 2008, [EMAIL PROTECTED] wrote:
The following text shows the result of attempting to install Parrot
using
bcc32. The program appeared to hang at the Generating CPU specific
stuff
stage until killed.
C:\parrotConfigure.pl --cc=bcc32
Parrot Version 0.5.2 Configure 2.0
On Sun Mar 18 12:21:18 2007, ptc wrote:
I don't know if this is a BUG or what so I'm just sending it plain.
I've just tried to build parrot with icc (not 100% sure if my build
flags are correct either), and I'm getting this build error:
icc -o miniparrot compilers/imcc/main.o \
On Sun Mar 18 12:21:18 2007, ptc wrote:
I don't know if this is a BUG or what so I'm just sending it plain.
I've just tried to build parrot with icc (not 100% sure if my build
flags are correct either), and I'm getting this build error:
icc -o miniparrot compilers/imcc/main.o \
On Mon Apr 09 23:01:35 2007, [EMAIL PROTECTED] wrote:
On Sunday 08 April 2007 18:07, Steve Peters via RT wrote:
On Sun Apr 08 16:08:05 2007, stmpeters wrote:
The attached patch includes several cleanups needed to silence
warnings
when compiling Parrot with Intel C++.
It helps
On Sun Apr 08 16:08:05 2007, stmpeters wrote:
The attached patch includes several cleanups needed to silence
warnings
when compiling Parrot with Intel C++.
It helps to attach the right patch
Steve
intel_cleanups.out
Description: Binary data
On Mon Apr 02 17:16:45 2007, stmpeters wrote:
Here's some additional cleanups for making Parrot a bit more friendly
to a wider variety of C compilers.
It is always good to actually include the attachment you are sending.
Steve
Index: src/encoding.c
On Thu Mar 15 05:30:31 2007, nahoo wrote:
On Mi. 14. Mär. 2007, 23:00:18, nahoo wrote:
Index: include/parrot/sub.h
===
--- include/parrot/sub.h(Revision 17473)
+++ include/parrot/sub.h(Arbeitskopie)
@@ -87,7
On Tue Mar 27 10:54:17 2007, doughera wrote:
On Tue, 27 Mar 2007, Steve Peters wrote:
# New Ticket Created by Steve Peters
# Please include the string: [perl #42151]
# in the subject line of all future correspondence about this issue.
# URL:
On Tue Mar 27 05:32:41 2007, doughera wrote:
On Mon, 26 Mar 2007, Steve Peters wrote:
# New Ticket Created by Steve Peters
# Please include the string: [perl #42110]
# in the subject line of all future correspondence about this issue.
# URL:
On Tue Mar 27 10:54:17 2007, doughera wrote:
On Tue, 27 Mar 2007, Steve Peters wrote:
# New Ticket Created by Steve Peters
# Please include the string: [perl #42151]
# in the subject line of all future correspondence about this issue.
# URL:
On Sun Jan 07 08:27:28 2007, [EMAIL PROTECTED] wrote:
On Jan 7, 2007, at 8:44 AM, Steve Peters via RT wrote:
What is your c++ symlink pointing at?
[parrot] 512 $ ls -l /usr/bin/c++
lrwxr-xr-x 1 root wheel 7 Aug 9 2004 /usr/bin/c++ - g++-3.3
[parrot] 513 $ ls -l /usr/bin/g
On Thu Jan 11 08:57:22 2007, coke wrote:
Need details.
A recent patch has gotten Parrot to the point that it can be compiled
with Borland C++ on Win32. Unfortunately, it does not link correctly to
actually create a valid parrot executable. Additional configuration is
needed to make Borland
What is your c++ symlink pointing at?
On Sun Dec 17 19:29:46 2006, [EMAIL PROTECTED] wrote:
With ICU optional these days, is this still necessary?
I have a Visual C++ Toolkit 2003 lying around (I think), so, if I do,
I'll give this a try along with my Borland work.
On Mon Nov 20 06:24:00 2006, stmpeters wrote:
It took some tweaking to get some of the warnings shut off, but the
attached patch actually gets the files to compile, although it doesn't
actually build a parrot to test with. Expect a few more patches over
the
next week to finish this
On Sat Dec 16 18:59:18 2006, stmpeters wrote:
This patch silences a minor warning on Cygwin.
Steve Peters
[EMAIL PROTECTED]
$ diff -u parrot/src/pmc/parrotio.pmc parrot-patch/src/pmc/parrotio.pmc
--- parrot/src/pmc/parrotio.pmc 2006-12-16 20:46:58.37500 -0600
+++
On Sat Nov 11 10:17:33 2006, [EMAIL PROTECTED] wrote:
perl Configure.pl --without-gmp --cc=gcc --ccflags='-fno-common -pipe
-I/usr/local/include -pipe -fno-common'
Then chromatic suggested manually editing the Makefile to delete '-
bundle' from the following line.
LD_LOAD_FLAGS =
[jhoblitt - Sun Jan 01 18:49:23 2006]:
I've commited a possible fix for openbsd, cygwin, solaris as
changesets
r10839 r10843. I basically applied what Steve Peters proposed but
with the changes in math.c instead of creating init.c (as agreed to on
#parrot).
This doesn't appear to
[stmpeters - Tue Mar 22 15:41:12 2005]:
When running testing parrot-HEAD, I get a test failure in
t/op/trans.t on
OpenBSD. Running the same tests on Linux seem to work just fine...
perl -Ilib t/op/trans.t
1..19
ok 1 - sin
ok 2 - cos
ok 3 - tan
ok 4 - sec
ok 5 - atan
ok 6 - asin
[EMAIL PROTECTED] - Wed Dec 28 14:07:26 2005]:
A quick demonstration of the issue:
--
#include stdio.h
#include math.h
int main ()
{
printf(%f\n, atan2(0.0, 0.0));
printf(%f\n, atan2(-0.0, -0.0));
}
--
--
$ gcc foo.c -lm
$ ./a.out
0.00
0.00
--
This is
[jrieks - Mon Apr 11 12:17:57 2005]:
It looks like atan -0.0, -0.0 == 0.0 on OpenBSD 3.5/i386:
t/op/trans.NOK 13# Failed test (t/op/trans.t
at line
307)
# got: 'ok 1
# ok 2
# ok 3
# ok 4
# ok 5
# ok 6
# ok 7
# ok 8
# ok 9
# ok 10
# ok 11
# ok
[leo - Thu Mar 24 07:07:31 2005]:
Comments, takers?
Since I'm fixing this in Perl, I take a whack at it in Parrot as well.
Steve
[EMAIL PROTECTED] - Thu Jan 08 05:18:53 2004]:
$Test-diag(1,2,3,4);
yields # 1# 2# 3# 4 which is not right.
It seems like the intent was for each argument to be a line,
so it should yield something like:
# 1
# 2
# 3
# 4
The fix is to modify the
23 matches
Mail list logo
