On Apr 12, 2004, at 6:37 AM, Dan Sugalski wrote:
I'll try and get patches to use the system ICU install if there is one
done today.
Also take a look at my [perl #28473], which I don't think has made it
to the list yet. That's a patch to make the location of ICU's data
directory configurable, so
FWIW, taking a look at the Debian-specific ICU patches for their
testing branch might be worthwhile. They've patched the thing up to
get it to build, and since it's the only system I have locally that
*doesn't* build ICU, I suspect there's something either Debian-ish
going wrong, or more Linux
On Apr 11, 2004, at 3:15 PM, Alberto Manuel Brandao Simoes wrote:
Here we go,
It's probably okay. It's alright to close the fd after the mmap, and
it's not really calling mmap twice--it's just the debugger trying to
follow the optimized code.
OK, Just my ignorance :-)
Nope--normally one tries
Here we go,
It's probably okay. It's alright to close the fd after the mmap, and
it's not really calling mmap twice--it's just the debugger trying to
follow the optimized code.
OK, Just my ignorance :-)
Hmm, so it's looking like the error message may be genuine, in that the
problem it's havi
On Apr 11, 2004, at 1:54 PM, Alberto Manuel Brandao Simoes wrote:
Jeff,
I am a little lost in that code as you might imagine :-)
I am a bit as well--I basically went looking for the error message, and
have been trying to figure out where in the code the error is actually
originating.
Breakpo
Jeff,
I am a little lost in that code as you might imagine :-)
BTW, the HAVE_MMAP is defined.
I set a breakpoint at "uprv_mapFile_2_6", and here is some of the gdb
debug...
[New Thread 16384 (LWP 942)]
[Switching to Thread 16384 (LWP 942)]
Breakpoint 1, uprv_mapFile_2_6 (pData=0xbfffd9e0,
On Apr 11, 2004, at 12:38 PM, Alberto Manuel Brandao Simoes wrote:
Some more info...
Thanks!
Jeff Clites wrote:
Hmm, strange indeed. Looking at the ICU code, it appears that it's
not finding a data file it needs at this stage (the error message is
misleading)--I wonder if something failed to
Some more info...
Jeff Clites wrote:
On Apr 11, 2004, at 7:12 AM, Alberto Manuel Brandao Simoes wrote:
If it's still failing, then something else is going on.
If it is, then there's one more thing to try:
1) cd into icu/source/data/out/build
2) Execute this (which will create ja.res in /var/tmp i
On Apr 11, 2004, at 7:12 AM, Alberto Manuel Brandao Simoes wrote:
If it's still failing, then something else is going on.
If it is, then there's one more thing to try:
1) cd into icu/source/data/out/build
2) Execute this (which will create ja.res in /var/tmp if it succeeds):
../../../tools/genrb/g
Here it goes...
It's odd, but try this:
1) cd into icu/source/data
2) Edit the Makefile. Look for this:
$(BUILDDIR)/$(ICUDT)%.res: $(INDEX_FILES) $(TOOLDIR)/genrb/genrb$(EXEEXT)
ICU_DATA=$(BUILDDIR) $(INVOKE) $(TOOLDIR)/genrb/genrb
$(GENRBOPTS) -p $(ICUDATA_PLATFORM_NAME) -d $(BUILDDIR
On Apr 10, 2004, at 12:33 PM, Alberto Manuel Brandao Simoes wrote:
I am not needing parrot (just checking its state) but compilation
failed. Don't know if it is expected or not. In any case, this might
be useful:
../data/locales/ja.txt:15: parse error. Stopped parsing with
U_INVALID_FORMAT_ERR
Le Sat, Apr 10, 2004 at 08:33:04PM +0100, le valeureux mongueur Alberto Manuel Brandao
Simoes a dit:
> Hi
>
> I am not needing parrot (just checking its state) but compilation
> failed. Don't know if it is expected or not. In any case, this might be
> useful:
>
> ../data/locales/ja.txt:15: par
Hi
I am not needing parrot (just checking its state) but compilation
failed. Don't know if it is expected or not. In any case, this might be
useful:
../data/locales/ja.txt:15: parse error. Stopped parsing with
U_INVALID_FORMAT_ERROR
couldn't parse the file ja.txt. Error:U_INVALID_FORMAT_ERROR
13 matches
Mail list logo
