Thanks for your good thoughts. I had hoped that the greenstone
team will have a clue on this problem :-D .
For the moment I do not have time to check it. I have switched
my code back to 2.51 version because I will have another project
here in Ruby (for the next three months) and also I have
exams. So for the next three months I will not have
time to check the problem.
The problem is either in Perl side or on C++ (MGPP) side.
My first check will be to make MGPP code from 2.51 to build
a collection with the Perl code from 2.71 to see if the
problem is on Perl side.
If I will find time before May I will let you know my progress.
I will monitor this list so if you find something please post it.
Jens sorry that I can't help you now. I suggest for the moment
to take an older version (2.51 is working for me)
From: Michael Dewsnip [mailto:firstname.lastname@example.org]
Sent: Friday, January 26, 2007 3:15 AM
To: jens wille
Cc: email@example.com; Emanuel Dejanu / Simple Words
Subject: Re: [greenstone-devel] MGPP (2.71 build problem)
>>Thanks for letting us know. Unfortunately, we haven't been able
>>to reproduce the "bit buffer overrun" problem here, on either
>>Linux or Windows, or with either your collection or the demo
>that's a pity! and raises the question what might have introduced
>this issue... either on greenstone or OS side.
Yes, it's a real mystery at the moment...
>>Do you have access to Microsoft Visual Studio? If so, you could
>>try recompiling MGPP with some debug statements that might help
>>locate the problem.
>uh, dunno... it's the client's machine and i don't know if we can
>install it. what about some kind of GNU make? (i'm obviously not
>quite familiar with windoze in this respect ;-)
I think you can install Cygwin and compile it using GCC, but I've never
We have our fingers crossed that Emanuel Dejanu has a little bit of time
to try to debug this (Emanuel is a good programmer and experienced in
Sorry I couldn't be more help!
All the best,
__________ NOD32 2000 (20070123) Information __________
This message was checked by NOD32 antivirus system.