Hi Stefan! I really appreciate the quick reply. I also tried to run the FSA tools with att input files - nothing special, just some toy examples. But it seems, that they aren't processed correctly: fsa att:toydict.fsm info gives <information component="fsa"> <fsa-info> <type>acceptor</type> <describe>static</describe> <properties>linear storage</properties> <semiring>tropical</semiring> <max-state-id>0</max-state-id> <states>0</states> <arcs>0</arcs> <final-states>0</final-states> <epsilon-arcs>0</epsilon-arcs> </fsa-info> </information> which can't be, this is a nonempty dictionary transducer. The same happens with the text version of this fsm file: fsa att:toydict.txt info gives <information component="fsa"> <fsa-info> <type>acceptor</type> <describe>static</describe> <properties>linear storage</properties> <semiring>tropical</semiring> <max-state-id>0</max-state-id> <states>0</states> <arcs>0</arcs> <final-states>0</final-states> <epsilon-arcs>0</epsilon-arcs> </fsa-info> </information> I'm sending you the both files as attachments to this e-mail. Best, Emilian On Wed, 15 Dec 2004 21:45:18 +0100, Stephan Kanthak <stylon@gmx.de> wrote:
Hi Emilian!
On Wednesday 15 December 2004 20:31, Emilian Stoimenov wrote:
Hi Stefan, I tried to compile and run FSA on our Suse Linux x86_64 machine (uname: Linux 2.6.4-52-smp #1 SMP Wed Apr 7 01:58:54 UTC 2004 x86_64 x86_64 x86_64 GNU/Linux) with a little succes. I got some warnings in Unicode.cc, namely:
You can safely ignore them (see the README file). They are due to missing const in the declaration of iconv.
Also, I had to explicitly typecast in the call to std::min // u32 bufferSize = std::min(bufferThreshold_ - putBackBufferSize, formatted_.size()); u32 bufferSize = std::min(size_t(bufferThreshold_ - putBackBufferSize), formatted_.size()); Otherwise it complained that it cannot find std::min:
TextStream.cc: In member function `virtual int Core::TextInputStream::Buffer::underflow()': TextStream.cc:422: error: no matching function for call to `min(unsigned int, size_t)'
I also fixed that in the mean time. I missed to compile the release on our x86_64 machine and unfortunately someone from our group did some changes to the CVS since my last test.
Ignoring the warnings and modifying the code a bit got me the executable, which unfortunately I couldn't run, because it gave me a segmentation fault. Running gdb on fsa.linux-x86_64-standard and backtracing printed this output:
On our x86_64 machine (dual opteron, 8 gb ram, debian x86_64) my executable also exits with a segmentation fault right after starting it when I use the installed compiler (gcc version 3.3.5 (Debian 1:3.3.5-3)). However, we also have a special unified built environment where we compiled gcc on our own (stock gcc 3.3.2) and using that one everything runs fine. In both cases I used the installed glibc so that shouldn't be the problem. I will look after that problem soon, but I can't promise that it happens till beginning of next week. I will put a maintainance update (0.9.1) on the website when I am finished with that bug. Hopefully, I reach version 1.0 till the end of the year....
Everything compiled and ran OK on a 32bit machine. Is there anything that I can do to run FSA on the 64bit machine?
At least some success. You are the first one reporting successful compilation outside our institute....
Stephan
_______________________________________________ fsa mailing list fsa@lists.rwth-aachen.de http://mailman.rwth-aachen.de/mailman/listinfo/fsa