chime it?
>
> Is a $*UNICODE dynamic variable a possibility?
>
> Related: I'm re-reading Matéu's comment, which (I think) says to let ICU
> live in a module somewhere.
>
> Best Regards, Bill.
>
>> On Sep 29, 2020, at 21:19, Matthew Stuckwisch wrote:
>
Nudging this conversation, ...to follow progress since 2020.
Anyone want to chime it?
Is a $*UNICODE dynamic variable a possibility?
Related: I'm re-reading Matéu's comment, which (I think) says to let ICU live
in a module somewhere.
Best Regards, Bill.
> On Sep 29, 2020, at 2
In #raku it was mentioned that it would be nice to have a $*UNICODE variable of
sorts that reports back the version, but not sure how that would be from an
implementation POV.
I'm also late to the discussion, so pardon me jumping back a bit. Basically,
ICU is something that lets you qu
st, Bill.
W. Michels, Ph.D.
On Sun, Sep 27, 2020 at 4:03 AM Samantha McVey wrote:
>
> So MoarVM uses its own database of the UCD. One nice thing is this can
> probably be faster than calling to the ICU to look up information of each
> codepoint in a long string. Secondly it impl
So MoarVM uses its own database of the UCD. One nice thing is this can
probably be faster than calling to the ICU to look up information of each
codepoint in a long string. Secondly it implements its own text data
structures, so the nice features of the UCD to do that would be difficult to
use
On Fri, Sep 25, 2020 at 12:37:49PM +0200, Elizabeth Mattijsen wrote:
> > On 25 Sep 2020, at 04:25, Brad Gilbert wrote:
> > Rakudo does not use ICU
> >
> > It used to though.
> >
> > Rakudo used to run on Parrot.
> > Parrot used ICU for its Unicode featu
> On 25 Sep 2020, at 04:25, Brad Gilbert wrote:
> Rakudo does not use ICU
>
> It used to though.
>
> Rakudo used to run on Parrot.
> Parrot used ICU for its Unicode features.
Ah, the days.
I do remember that in the Parrot days, any non-ASCII character in any string,
wou
Rakudo does not use ICU
It used to though.
Rakudo used to run on Parrot.
Parrot used ICU for its Unicode features.
(Well maybe the JVM backend does currently, I don't actually know.)
MoarVM just has Unicode as one of its features.
Basically it has something similar to ICU already.
---
I think more to the point is which version of Unicode is supported,
rather than the ICU libraries. It might be worth writing some tests
that check that Raku's unicode handling matches the ICU libraries.
On 9/24/20, William Michels wrote:
> Thanks everyone for the replies. I guess
Thanks everyone for the replies. I guess the two questions I have
pertain mainly to 1) lineage and 2) versioning:
Regarding lineage, I'm interested in knowing if
Pugs/Parrot/Niecza/STD/Perlito/viv/JVM/Rakudo ever used the ICU
Libraries--even if now that data has been extracted into a Raku-n
Elizabeth Mattijsen wrote:
> https://www.codesections.com/blog/raku-unicode/
Thanks, yes I was just reading through that. It makes it clear that
the "Unicode Character Database" is built-in to the MoarVM, but I'm
not that clear what the ICU libraries do for you, and I thou
https://www.codesections.com/blog/raku-unicode/
> On 24 Sep 2020, at 20:00, Joseph Brenner wrote:
>
> I'm not sure myself, but my first guess would be probably not...I
> *think* Raku is doing it's own Unicode thing, and isn't using any
> system ICU libraries (but
I'm not sure myself, but my first guess would be probably not...I
*think* Raku is doing it's own Unicode thing, and isn't using any
system ICU libraries (but I'm willing to stand corrected on that).
As far as perl (the-language-formerly-known-as-perl5) is concerned:
That
Hi,
I stumbled across the "ICU - International Components for Unicode" website:
http://site.icu-project.org/
https://github.com/unicode-org/icu
There's a list of programming languages using the ICU libraries here:
http://site.icu-project.org/related
Should Raku be added to th
These tests are actually passing. I unfudged the tests with commit
https://github.com/perl6/roast/commit/c9e7946599
On Mon, Jul 2, 2012 at 9:08 AM, Patrick R. Michaud wrote:
> This is now fixed in HEAD and will appear in the next release:
nice, thank you!
Gabor
On Thu, Jun 28, 2012 at 08:24:31AM -0700, Patrick R. Michaud wrote:
> > Am 28.06.2012 14:31, schrieb Gabor Szabo:
> > >The following script generates an exception
> > >
> > >use v6;
> > >
> > >my %count;
> > >my $s = 'שלום';
>
gt; Am 28.06.2012 14:31, schrieb Gabor Szabo:
> >The following script generates an exception
> >
> >use v6;
> >
> >my %count;
> >my $s = 'שלום';
> >%count{$s} = 1;
> >say $s;
> >say %count.perl;
> >
> >no ICU lib loaded
> >
On Thu, Jun 28, 2012 at 02:40:40PM +0200, Moritz Lenz wrote:
> Am 28.06.2012 14:31, schrieb Gabor Szabo:
> >The following script generates an exception
> >
> >use v6;
> >
> >my %count;
> >my $s = 'שלום';
> >%count{$s} = 1;
> >say $s;
>
Am 28.06.2012 14:31, schrieb Gabor Szabo:
The following script generates an exception
use v6;
my %count;
my $s = 'שלום';
%count{$s} = 1;
say $s;
say %count.perl;
no ICU lib loaded
in method perl at src/gen/CORE.setting:3892
in method perl at src/gen/CORE.setting:5921
in m
The following script generates an exception
use v6;
my %count;
my $s = 'שלום';
%count{$s} = 1;
say $s;
say %count.perl;
no ICU lib loaded
in method perl at src/gen/CORE.setting:3892
in method perl at src/gen/CORE.setting:5921
in method perl at src/gen/CORE.setting:6115
in bloc
On Fri Oct 14 13:04:52 2011, pmichaud wrote:
> > It would be helpful if someone (not necessarily the original poster)
> > provided a recipe to build a perl6 without ICU so this bug can be
> tested
> > against a recent version.
>
> The following should work:
>
> It would be helpful if someone (not necessarily the original poster)
> provided a recipe to build a perl6 without ICU so this bug can be
tested
> against a recent version.
The following should work:
perl Configure.pl --gen-parrot --parrot-option="--without-icu"
Pm
On Fri Aug 14 06:53:05 2009, masak wrote:
> $ svn info # Parrot
> [...]
> Revision: 40543
>
> $ git show # Rakudo
> commit 0d4fe08d2e6f249211a33a8f9b122599fadbe862
>
> $ perl6 -e 'my $x = "\x[5ea]\x[5ea]"; $x++; say $x.perl'
> no ICU lib loaded
>
On Wed Sep 16 05:49:12 2009, cognominal wrote:
> the report is not relevant anymore. you can close the ticket. Thx
>
Closing.
the report is not relevant anymore. you can close the ticket. Thx
On 9/16/09, James Keenan via RT wrote:
> On Sun Apr 20 08:58:20 2008, cognominal wrote:
>> When testing, got that error message.
>> Probably linked to icu and the version used.
>> I have 3.4.1 and 3.8.1 aro
On Fri Aug 14 06:53:05 2009, masak wrote:
> $ svn info # Parrot
> [...]
> Revision: 40543
>
> $ git show # Rakudo
> commit 0d4fe08d2e6f249211a33a8f9b122599fadbe862
>
> $ perl6 -e 'my $x = "\x[5ea]\x[5ea]"; $x++; say $x.perl'
> no ICU lib loaded
>
Rakudo
commit 0d4fe08d2e6f249211a33a8f9b122599fadbe862
$ perl6 -e 'my $x = "\x[5ea]\x[5ea]"; $x++; say $x.perl'
no ICU lib loaded
in Main (:1)
$ perl6 -e 'my $x = "\x[5ea]\x[5ea]"; $x++; say try { $x.perl }'
Null PMC access in type()
in Main (:1)
$ perl6 -e 'my $x =
my $content = $*IN.slurp;
$content = uc $content;
%
% perl6 test.p6.pl < test.p6.pl
no ICU lib loaded
in method Any::uc (src/gen_setting.pm:392)
called from Main (test.p6.pl:2)
%
Strangely, the problem is unique to "uc". If you replace "uc" by "lc"
the problem goes
Updated information: we added recently a workaround to the utf8 downcase
function, by moving code already present out of the ICU #if block.
This workaround delegates to the ascii downcase when the string has only
codepoints in the ascii range (the way used to do that check is
debatable, must be
On Mie. Mar. 14 11:46:38 2007, [EMAIL PROTECTED] wrote:
> I keep getting a test failure on t/op/stringu.t with test 25 on
> ppc-darwin(and likely all big endian systems with icu installed).
> Parrot outputs "\x00A\x00B" when the test expects "A\x00B\x00" to be
Closing ticket
Patch applied in r29301
I changed the test, because the unicode: prefixed string is utf8 by
default according the specs, and the current implementation seems to
agree, so the result in utf8 is the expectation both with or without
icu.
--
Salu2
The attached patch changes string_rep_compatible so that when called
with utf8_encoding and iso_8859_1_encoding returns utf8. Looks that this
solves the problem and breaks nothing.
Index: src/string.c
===
--- src/string.c (revisión:
# New Ticket Created by Stephane Payrard
# Please include the string: [perl #53104]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=53104 >
When testing, got that error message.
Probably linked to icu and the version u
On Tuesday 04 December 2007 08:14:41 Patrick R.Michaud wrote:
> If ICU isn't present, Parrot's C opcode always throws
> an exception. It does this even if the string contains codepoints
> only in the ascii and/or iso-8859-1 range.
>
> For example:
>
> $
# New Ticket Created by Patrick R. Michaud
# Please include the string: [perl #48108]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=48108 >
If ICU isn't present, Parrot's C opcode always throws
an exception.
ely all big endian systems with icu installed).
Parrot outputs "\x00A\x00B" when the test expects "A\x00B\x00" to be
printed. I got a hint to the problem at the icu
faq(http://icu.sourceforge.net/userguide/icufaq.html). "A Unicode
string is currently represented as UTF
ist ...
http://beta.nntp.perl.org/group/perl.perl6.internals/2006/12/
msg35794.html
Nick Clark referred to ICU.
Newbie that I am, I did not know what that abbreviation referred to.
So I acked the Parrot codebase and found only one place where ICU was
spelled out:
languages/dotnet/doc/building.pod
als/2006/12/
msg35794.html
Nick Clark referred to ICU.
Newbie that I am, I did not know what that abbreviation referred to.
So I acked the Parrot codebase and found only one place where ICU was
spelled out:
languages/dotnet/doc/building.pod
14:=item * ICU (International Components For Unicode),
# New Ticket Created by Patrick R. Michaud
# Please include the string: [perl #39930]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=39930 >
Found this bug while doing stuff --without-icu today...
Concatenation o
On Mon, Jul 24, 2006 at 03:57:25PM -0700, Pm wrote:
> Found this bug while doing stuff --without-icu today...
>
> Concatenation of a unicode string with an ASCII string
> works even if ICU isn't available.
>
> Concatenation of a unicode string with a Unicode string
&g
On Sat, Jul 22, 2006 at 08:54:36PM -0400, Bob Rogers wrote:
Content-Description: message body text
>After building Parrot without ICU, 01-regex.t test 118 fails as
> follows:
> t/compilers/pge/p6regex/01-regex.
> # Failed test (t/compilers/pge/p6regex/01-reg
After building Parrot without ICU, 01-regex.t test 118 fails as
follows:
t/compilers/pge/p6regex/01-regex.
# Failed test (t/compilers/pge/p6regex/01-regex.t at line 59)
# got: 'no ICU lib loaded
# current instr.: 'parrot;PG
On Jul 21, 2006, at 1:12 PM, Mr. Shawn H. Corey wrote:
Chris Dolan wrote:
This would be a good entry for the FAQs for a cage cleaner.
If you're collect questions for the FAQ, here are some Andy Lester
answered for me:
I'm not, actually. :-(
Could you do one of the following, in order of p
On Fri, Jul 21, 2006 at 02:12:57PM -0400, Mr. Shawn H. Corey wrote:
> Chris Dolan wrote:
> > 1. Do I need root privileges to install Parrot? Do I need it for Cage
> > Cleaners?
>
> You don't even need root at all. You can build in a local directory and
> not install.
In fact, for those who are d
Chris Dolan wrote:
> On Jul 21, 2006, at 9:48 AM, Jonathan Rockway wrote:
>
>>> I have downloaded the icu4j_3_4_4.jar but have no idea what to do with
>>> it. Could someone please help?
>>>
>> You'll want to get icu4c (icu for C), not icu4j (for java)
On Jul 21, 2006, at 9:48 AM, Jonathan Rockway wrote:
I have downloaded the icu4j_3_4_4.jar but have no idea what to do
with
it. Could someone please help?
You'll want to get icu4c (icu for C), not icu4j (for java). If you
get the tgz C version, just tar xzvf it, cd source; ./conf
> it seems to me that the icu libs should indeed be added to the config.
> i don't compile with icu, so i'm probably not the best one to test the
> change--but if nobody takes ownership of this issue in the next few
> days, i'll take a look at it.
That would be great
forgot to copy the list on this response
-- Forwarded message --
From: jerry gay <[EMAIL PROTECTED]>
Date: Aug 18, 2005 8:05 AM
Subject: Re: Is Configure.pl missing ICU ?
To: Adrian Lambeck <[EMAIL PROTECTED]>
On 8/18/05, Adrian Lambeck <[EMAIL PROTECTED]> wro
Since nobody responded to my question up to now I had a look at the parrot
source. Just to remind you what I was asking:
Eventough parrot is compiled with icu support this does not show up when I
query parrot for it (i.e. # /usr/lib/parrot-0.2.3/parrot parrot-config.imc
libs).
So I looked at
I got a problem concerning ICU.
# /usr/lib/parrot-0.2.3/parrot parrot-config.imc ldflags
returns:
"-lpthread -lnsl -ldl -lm -lcrypt -lutil -lrt -lgmp"
eventhough I compiled against icu (Configure find is) so I am missing
"-licuuc" here.
Anybody got an idea? I am using
François" PERRAD <[EMAIL PROTECTED]> wrote:
> This patch allows the inclusion of ICU DLL in the installer.
Thanks, applied.
leo
# New Ticket Created by FranÃois PERRAD
# Please include the string: [perl #35084]
# in the subject line of all future correspondence about this issue.
# https://rt.perl.org/rt3/Ticket/Display.html?id=35084 >
This patch allows the inclusion of ICU DLL in the installer.
Francois Per
On Fri, 2005-04-15 at 05:38 -0700, François PERRAD wrote:
> small mistake in [perl #34986] :
> with ICU 3.2, the library icudata.lib is renamed icudt.lib.
Thanks, applied.
-- c
# New Ticket Created by FranÃois PERRAD
# Please include the string: [perl #35000]
# in the subject line of all future correspondence about this issue.
# https://rt.perl.org/rt3/Ticket/Display.html?id=35000 >
small mistake in [perl #34986] :
with ICU 3.2, the library icudata.lib is rena
jerry gay wrote:
> On Apr 12, 2005 12:06 PM, Solinski, Mark <[EMAIL PROTECTED]> wrote:
>> > Has anyone successfully built Parrot on Win32 (MSVC 13.10.3077)
>> > recently?
> parrot builds fine on win32--vc-7.1-perl-5.8.6 for me, without icu. i have
> been bu
On Apr 12, 2005 12:06 PM, Solinski, Mark <[EMAIL PROTECTED]> wrote:
>
> > Has anyone successfully built Parrot on Win32 (MSVC 13.10.3077)
> > recently?
parrot builds fine on win32--vc-7.1-perl-5.8.6 for me, without icu. i have
been building this way for some time now.
c
to
> perl6-language...
>
> > Following the instructions in README.Win32 (which has been successful
> > for me in the past), no longer works successfully. First, I cannot
> > run Configure.pl successfully; it complains about --icudatadir not
> > being defined (again not one of the --i
gt; being defined (again not one of the --icu* options mentioned in
> > README.Win32 AND not necessary before). Defining --icudatadir, I now
> > get the following error during make:
> >
> > Src\string_primitives.c(24) : fatal error C1083: Cannot open include
> > file:
icudatadir not
> being defined (again not one of the --icu* options mentioned in
> README.Win32 AND not necessary before). Defining --icudatadir, I now
> get the following error during make:
>
> Src\string_primitives.c(24) : fatal error C1083: Cannot open include
> file: 'unico
Solinski, Mark <[EMAIL PROTECTED]> wrote:
> Following the instructions in README.Win32 (which has been successful
> for me in the past), no longer works successfully. First, I cannot run
> Configure.pl successfully; it complains about --icudatadir not being
> defined (again no
On Tuesday 12 April 2005 19:10, Andy Dougherty wrote:
> # New Ticket Created by Andy Dougherty
> # Please include the string: [perl #34932]
> # in the subject line of all future correspondence about this issue.
> # https://rt.perl.org/rt3/Ticket/Display.html?id=34932 >
>
>
# New Ticket Created by Andy Dougherty
# Please include the string: [perl #34932]
# in the subject line of all future correspondence about this issue.
# https://rt.perl.org/rt3/Ticket/Display.html?id=34932 >
If the user has ICU installed in a location not normally searched by
the compi
Hi Mark,
I was able to compile parrot yesterday night. I compiled icu and
copied the contents of the directory icu/include (two directories)
manually to parrot/src. After that the compiler didn't complain
anymore and I got a working parrot.exe. The --icudatadir I pointed to
the out directo
Following the instructions in README.Win32 (which has been successful
for me in the past), no longer works successfully. First, I cannot run
Configure.pl successfully; it complains about --icudatadir not being
defined (again not one of the --icu* options mentioned in README.Win32
AND not
At 11:03 05/04/2005 +0200, you wrote:
Please verify the build on Windows platforms,
$ perl Configure.pl -cc=gcc --without-icu
$ mingw32-make
Build OK with MinGW.
Francois
thanks
leo
Jarkko Hietaniemi wrote:
3) we could probably lift the restriction that we link with c++
I replaced LINK = c++ with LINK = cc in the Makefile and it works.
Maybe I'm missing some previous discussion but as long as we are linking
ICU in, there is no way that any other linker than the C++ com
Leopold Toetsch wrote:
> 5) if you move $parrot/icu e.g. to $parrot/_icu you can run
>$ perl Configure.pl --nomanicheck
> Please verify the build on Windows platforms,
> thanks
Looks good on Windows XP, VC++ 7.1. F complains,
quite expectedly.
Ron
1) a hint, if you want to verify a config step:
$ perl Configure.pl --verbose-step=ICU
2) verify that you link against the correct libicu
$ nm -u parrot | grep isdigit
u_isdigit_3_2
3) we could probably lift the restriction that we link with c++
I replaced LINK = c++ with LINK = cc in the
Jens Rieks <[EMAIL PROTECTED]> wrote:
> I've attached the patch that implements --without-icu.
> Comments welcome.
1) --without-icu works fine
Needed a few changes to get rid of warnings in lib/Parrot/Test.pm when
running make src_tests
replaced isblank, it's a gcc
On Sunday 03 April 2005 14:06, Ron Blaschke wrote:
> I'd reckon once C<--without-icu> is in place, one should be able to
> run
>
> $rm -rf icu
> $perl Configure --without-icu --nomanicheck
>
> So it shouldn't really matter when exactly F is removed
Jens Rieks wrote:
> On Sunday 03 April 2005 10:06, Leopold Toetsch wrote:
>> Jens Rieks wrote:
[snip]
>> then we verify that we can build with a system ICU or without. Then we
>> can move over to SVN and procede with step 4).
> Why don't we remove the support for the
On Sunday 03 April 2005 10:06, Leopold Toetsch wrote:
> Jens Rieks wrote:
> > On Thursday 31 March 2005 12:01, Leopold Toetsch wrote:
> >>4) Makefile cleanups to remove in-tree icu build stuff
> >
> > Patch ready. When should I commit it?
>
> This was the 4th st
Jens Rieks wrote:
On Thursday 31 March 2005 12:01, Leopold Toetsch wrote:
4) Makefile cleanups to remove in-tree icu build stuff
Patch ready. When should I commit it?
This was the 4th step in the plan. First we need:
1) patches are very welcome that
$ perl Configure.pl --without-icu
then we
On Thu, 31 Mar 2005, Leopold Toetsch wrote:
We gonna switch to SVN soon.
3) If no one utters a killer argument against, we'll switch to SVN
I tried svn again. I'm happy to report it worked much better than it did
the last time I tried it. For one thing, it actually compiled for me.
It's still
e really cheap
branches / tags are quite nice.
> Announcement should
> also mention that we're not going to move icu over, so people should
> download libicu and/or submit patches to build without it.
No problem on Windows, never managed to get the ICU distributed with
parrot running,
We gonna switch to SVN soon.
citing Chip:
I think it would be a Good Thing for Parrot to live under Subversion
rather than CVS. Just the change sets and rename tracking is enough
reason, IMO.
and:
Announcement should
also mention that we're not going to move icu over, so people should
dow
dme.
> if parrot runs successfully with different versions of icu (anyone?) then a
> patch can be applied with more specific language on installing with the
> versions of icu known to work, and hints on installing with unproven
> versions.
The ICU folks seem to have changed the name betw
i tried to build parrot on win32 yesterday. i too found the readme out of
date.
i didn't know how version-dependent parrot was with unicode, so i tracked
down the 2.8 version of icu at
ftp://ftp.software.ibm.com/software/globalization/icu/2.8
with this version installed, 'icudata.l
windows,
and noticed just doing "perl Configure.pl" + "nmake" didn't work.
According to the README.win32, ICU should be downloaded, extracted and
its path should be included in the PATH variable. In README.win32 there
are 2 errors. Both are corrected with this patch.
1: the
Leopold Toetsch wrote:
> Ron Blaschke <[EMAIL PROTECTED]> wrote:
>> I've put the precompiled ICU into a directory, and supply the
>> --icushared and --icuheaders. This precompiled package contains only
>> the bin, include and lib. There's no data directory.
Ron Blaschke <[EMAIL PROTECTED]> wrote:
> I've put the precompiled ICU into a directory, and supply the
> --icushared and --icuheaders. This precompiled package contains only
> the bin, include and lib. There's no data directory. This is because
> the ICU buil
; Why is DEFAULT_ICU_DATA_DIR empty? Where is icu actually and which
> config variable is pointing at it?
I've put the precompiled ICU into a directory, and supply the
--icushared and --icuheaders. This precompiled package contains only
the bin, include and lib. There's no data direct
Ron Blaschke <[EMAIL PROTECTED]> wrote:
> I'd like to clean up string_init, because it currently backfires
> (segfaults) on Windows if parrot is installed (empty
> DEFAULT_ICU_DATA_DIR ...).
Why is DEFAULT_ICU_DATA_DIR empty? Where is icu actually and which
config variable is
I'd like to clean up string_init, because it currently backfires
(segfaults) on Windows if parrot is installed (empty
DEFAULT_ICU_DATA_DIR ...).
Could someone please tell me what string_init is supposed to do, where
it _should_ look for the ICU data directory (if at all)?
...
build
Leopold Toetsch <[EMAIL PROTECTED]> wrote:
> Will Coleda wrote:
> > I don't know if this is related to my build problems on OS X which have
> > gone warnocked. Trying to build without specifying a --prefix to
> > Configure causes all the dynclasses to fail
>
> I can't reproduce that here - it test
Sriram Krishnan wrote:
> Thanks for the reply. Readme.Win32 should have a notice about building in
> anything other than Visual Studio 6. Since 'msdev' is hardcoded inside the
> ICU build stuff, it *won't build on anything other than Visual Studio 6*.
> For anyone inter
Jonathan Worthington wrote:
> "Ron Blaschke" <[EMAIL PROTECTED]> wrote:
>> Leopold Toetsch wrote:
>>> Sriram Krishnan <[EMAIL PROTECTED]> wrote:
>> Failed TestStat Wstat Total Fail Failed List of Failed
>> --
Will Coleda wrote:
I don't know if this is related to my build problems on OS X which have
gone warnocked. Trying to build without specifying a --prefix to
Configure causes all the dynclasses to fail
I can't reproduce that here - it tests 100% fine. Strange.
leo
issues.
I'm running Windows XP, VS.NET 2003 and (precompiled) ICU 3.0, and can
confirm the offending "nci_dlvar_vv" and the failed tests.
Failed TestStat Wstat Total Fail Failed List of Failed
-
XP, VS.NET 2003 and (precompiled) ICU 3.0, and can
confirm the offending "nci_dlvar_vv" and the failed tests.
Failed TestStat Wstat Total Fail Failed List of Failed
---
t\dynclass\pybuiltin.t5 1
Thanks for the reply. Readme.Win32 should have a notice about building in
anything other than Visual Studio 6. Since 'msdev' is hardcoded inside the
ICU build stuff, it *won't build on anything other than Visual Studio 6*.
For anyone interested, I've written step-by-step in
Sriram Krishnan wrote:
> Post #1
> Post #2
> I managed to get it to build finally. I built ICU 2.8 and co-py-pasted
> the data output to the blib folder.I don't think this is the- way to do
> it - but hey..it works :)
> Post #3
[snip]
I have set up the things as de
Will Coleda wrote:
> Ron Blaschke writes:
>> On a personal note, I (still) really like to help in win32, though
>> it's quite hard for me to get a grip on this collaboration thingy.
> *looks around* Apparently, you're not the only one. =-)
;-)
I've been blinking in and out this group for some ti
Leopold Toetsch wrote:
> Ron Blaschke <[EMAIL PROTECTED]> wrote:
>> I am not sure what things are known (expected?) to broken,
> The normal CVS state is that "make test" succeeds on linux and OS X.
> Intermittent expected failures are announced here.
Great, that will do for me.
>> ... or who el
Ron Blaschke <[EMAIL PROTECTED]> wrote:
> On a personal note, I (still) really like to help in win32, though
> it's quite hard for me to get a grip on this collaboration thingy.
Great, thanks.
> I am not sure what things are known (expected?) to broken,
The normal CVS state is that "make test"
Ron Blaschke writes:
Should I file bug reports for every different looking problem, and
start looking for what's going wrong?
Yes please. email to parrotbug at parrotcode.org for each new issue.
On a personal note, I (still) really like to help in win32, though
it's quite hard for me to get a gri
Leopold Toetsch wrote:
> Sriram Krishnan <[EMAIL PROTECTED]> wrote:
>> I'm trying to build Parrot (from CVS) on Win XP Sp2 with VS.-NET 2003.
> Please folks with Windows installed: have a look at these issues.
I'm running Windows XP, VS.NET 2003 and (precompiled)
Sriram Krishnan <[EMAIL PROTECTED]> wrote:
> I'm trying to build Parrot (from CVS) on Win XP Sp2 with VS.-NET 2003.
Please folks with Windows installed: have a look at these issues.
leo
1 - 100 of 340 matches
Mail list logo