I am trying to get Weft installed on Fedora Core 3. I haven''t gotten to
Weft
itself yet, still having trouble with the dependencies, but wondering if
anyone has any suggestions.
The short story is that I am getting a "*** extconf.rb failed ***"
error
when installing sqlite-ruby. The details are below:
So far I installed ruby and sqlite ("yum install ruby", "yum
install
sqlite") and rubygems:
wget http://rubyforge.org/frs/download.php/5207/rubygems-0.8.11.tgz
tar xvzf rubygems-0.8.11.tgz
cd rubygems-0.8.11
ruby setup.rb
I then have been trying to install sqlite-ruby, through rubygems or else but
always getting an error message. With RubyGems:
wget http://rubyforge.org/frs/download.php/2818/sqlite-ruby-2.2.3.gem
gem install sqlite-ruby-2.2.3.gem
or
gem install --remote sqlite-ruby
or
wget http://rubyforge.org/frs/download.php/2820/sqlite-ruby-2.2.3.tar.gz
tar xvzf sqlite-ruby-2.2.3.tar.gz
cd sqlite-ruby-2.2.3
ruby install.rb config
In all three cases I get a variation on:
Attempting local installation of ''sqlite-ruby-2.2.3.gem''
Building native extensions. This could take a while...
*** extconf.rb failed ***
Could not create Makefile due to some reason, probably lack of
necessary libraries and/or headers. Check the mkmf.log file for more
details. You may need configuration options.
I am new to Ruby, so I have no idea what this means. Any suggestions? The
error message suggests that I look at mkmf.log file for details, but I
cannot find the file.
My sqlite is installed as follows:
[root at localhost tmp]# rpm -q sqlite -l
/usr/bin/sqlite
/usr/lib/libsqlite.so.0
/usr/lib/libsqlite.so.0.8.6
/usr/share/doc/sqlite-2.8.16
/usr/share/doc/sqlite-2.8.16/README
/usr/share/man/man1/sqlite.1.gz
I haven''t managed to get wxRuby working either, but this so far seems
to be
a Fedora problem with half-baked wxGTK (which seems to be missing
wx-config). I will work on that one myself for now and report the results.
- yuri
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
http://rubyforge.org/pipermail/weft-qda-users/attachments/20051118/50191a12/attachment-0001.htm
Hi Yuri Thanks for trying Weft and for the error report.> So far I installed ruby and sqlite ("yum install ruby", "yum install > sqlite") and rubygems:You probably also need to install a package/rpm called sqlite-devel or similar. This will have headers which are needed to build sqlite-ruby. If these are installed in standard places (and from your rpm -q output below, it looks like they are), the install should work then.> I then have been trying to install sqlite-ruby, through rubygems or > else but always getting an error message. With RubyGems:Rubygems will probably be using extconf.rb or setup.rb so if it fails with one it will fail with the other. Installing sqlite-ruby manually from a tarball might give you more accurate error reporting. If you have installed sqlite-devel and the ruby-sqlite install.rb is still complaining about not being able to find needed files, you can force install.rb to look in specific directories by specifying a --with-sqlite-include=/path/to/sqlite/include and --with-sqlite-lib=/path/to/sqlite/lib command line arguments. But I doubt you will need these.> I haven''t managed to get wxRuby working either, but this so far seems > to be a Fedora problem with half-baked wxGTK (which seems to be > missing wx-config). I will work on that one myself for now and > report the results.Be careful with what version you are getting. the version of wxruby that Weft uses requires Wx 2.4, not 2.6, the current version. If you end up having to compile your own Wx (which is slow, but usually fairly straightforward), use ./configure with --enable-static and --disable-shared options. Good luck, hope this helps alex
Alex,
Thanks. This was basically enough. It also turned out that the
problem with wxGTK was similarly just due to the lack of wxGTK-devel
package. (I am including the full set of instructions below for the
sake of anyone reading this thread later.)
The bad news is that now that I have Weft installed, it appears to be
really unstable: I tried running it three times and in all three cases
it crashed within 5 minutes: twice while interacting with the text
area (adding a code, etc.), once while saving a project. It was three
different errors:
First a segmentation fault in Ruby (while doing something with the text area):
[yuri at localhost weft_qda-0.9.6]$
./lib/weft/wxgui/inspectors/textcontrols.rb:67: [BUG] Segmentation
fault
ruby 1.8.3 (2005-09-21) [i386-linux]
Then an exception while saving a project:
[yuri at localhost weft_qda-0.9.6]$
/usr/lib/ruby/1.8/fileutils.rb:1182:in `stat'': No such file or
directory - /tmp/Weft29530.0 (Errno::ENOENT)
from /usr/lib/ruby/1.8/fileutils.rb:1182:in `lstat''
from /usr/lib/ruby/1.8/fileutils.rb:1160:in `stat''
from /usr/lib/ruby/1.8/fileutils.rb:1242:in `copy_file''
from /usr/lib/ruby/1.8/fileutils.rb:459:in `copy_file''
from /usr/lib/ruby/1.8/fileutils.rb:383:in `copy''
from /usr/lib/ruby/1.8/fileutils.rb:1377:in `fu_each_src_dest''
from /usr/lib/ruby/1.8/fileutils.rb:1393:in `fu_each_src_dest0''
from /usr/lib/ruby/1.8/fileutils.rb:1375:in `fu_each_src_dest''
from /usr/lib/ruby/1.8/fileutils.rb:382:in `copy''
from ./lib/weft/backend/sqlite.rb:126:in `save''
from ./lib/weft/wxgui.rb:484:in `save_project''
from ./lib/weft/wxgui.rb:484:in `save_project''
from ./lib/weft/wxgui.rb:479:in `on_save_project''
from ./lib/weft/wxgui.rb:100:in `create_menus''
from ./lib/weft/wxgui/workarea.rb:223:in `add_item''
from weft-qda.rb:28
Then a failed assertion in GTK:
Gtk-ERROR **: file gtktext.c: line 4724 (find_line_params): assertion
failed: (lp.end.property)
aborting...
The second problem looks like a Weft Bug, the other two are more
likely problems with underlying libraries. I am using ruby 1.8.3 and
wxGTK-2.4.2. Are there more stable version of those that I should be
using instead?
Now, for the sake of anyone trying to install Weft on Fedora Core 3,
here is exactly what it takes (all commands run as root from /tmp):
yum install ruby
yum install sqlite
yum install sqlite-devel
wget http://rubyforge.org/frs/download.php/2818/sqlite-ruby-2.2.3.gem
gem install sqlite-ruby-2.2.3.gem
("gem install --remote sqlite-ruby" didn''t do it for me)
yum install wxGTK
yum install wxGTK-devel
(Installing wxGTK-devel takes a long time, go get some coffee while it runs.)
After that you need to manually install the missing htmlproc.h:
wget ftp://biolpc22.york.ac.uk/pub/2.4.2/wxGTK-2.4.2.tar.gz
tar xvzf wxGTK-2.4.2.tar.gz.2
cd wxGTK-2.4.2
cp wxGTK-2.4.2/include/wx/html/htmlproc.h /usr/include/wx/html/
Then wxRuby:
wget http://rubyforge.org/frs/download.php/1983/wxruby-0.6-src.tar.gz
tar xvzf wxruby-0.6-src.tar.gz
cd wxruby-0.6-src/src
ruby extconf.rb
make
ruby install.rb
(Make will again take quite a bit. Go get another coffee.)
Finally Weft itself (the link from the project page is dead, btw).
wget http://rubyforge.org/frs/download.php/5138/weft_qda-src-0.9.6.tar.gz
tar xvzf weft_qda-src-0.9.6.tar.gz
All the commands up until now were as root, not running as normal user:
cd /tmp/weft_qda-0.9.6/
ruby weft-qda.rb &
- yuri
I tried using Weft 0.9.5 instead of Weft 0.9.6 and it I don''t seem to
get any segfaults or .c assertions, just unhandled Ruby exceptions,
which is more promising, since those presumably can be fixed.
0.9.5 also crashes when saving the project, but it only seems to
happen less often if I avoid saving it to a file in a different
directory. (It still crashes about half the time, though.)
Also, in 0.9.6 when I code a passage my text display gets mangled. In
0.9.5 coding doesn''t have any visible effect (which I imagine it
should), but it does seem to register, since I can then view the
codes.
The most serious problem I have with 0.9.5, however is that it
typically crashes when I try to view an imported document:
[yuri at localhost weft_qda]$ ./lib/weft/wxgui/sidebar.rb:109:in
`get_current_category'': undefined method `parent'' for
nil:NilClass
(NoMethodError)
from ./lib/weft/wxgui.rb:141:in `current_category''
from ./lib/weft/wxgui/inspectors.rb:32:in `initialize''
from ./lib/weft/wxgui/inspectors.rb:185:in `initialize''
from ./lib/weft/wxgui/inspectors/document.rb:11:in `initialize''
from ./lib/weft/wxgui/workarea.rb:60:in `launch_window''
from ./lib/weft/wxgui/workarea.rb:54:in `launch_window''
from ./lib/weft/wxgui.rb:152:in `on_document_open''
from ./lib/weft/wxgui/sidebar.rb:459:in `construct''
from main.rb:22
- yuri
On 11/19/05, Yuri T. <qaramazov at gmail.com>
wrote:> Alex,
>
> Thanks. This was basically enough. It also turned out that the
> problem with wxGTK was similarly just due to the lack of wxGTK-devel
> package. (I am including the full set of instructions below for the
> sake of anyone reading this thread later.)
>
> The bad news is that now that I have Weft installed, it appears to be
> really unstable: I tried running it three times and in all three cases
> it crashed within 5 minutes: twice while interacting with the text
> area (adding a code, etc.), once while saving a project. It was three
> different errors:
>
> First a segmentation fault in Ruby (while doing something with the text
area):
>
> [yuri at localhost weft_qda-0.9.6]$
> ./lib/weft/wxgui/inspectors/textcontrols.rb:67: [BUG] Segmentation
> fault
> ruby 1.8.3 (2005-09-21) [i386-linux]
>
> Then an exception while saving a project:
>
> [yuri at localhost weft_qda-0.9.6]$
> /usr/lib/ruby/1.8/fileutils.rb:1182:in `stat'': No such file or
> directory - /tmp/Weft29530.0 (Errno::ENOENT)
> from /usr/lib/ruby/1.8/fileutils.rb:1182:in `lstat''
> from /usr/lib/ruby/1.8/fileutils.rb:1160:in `stat''
> from /usr/lib/ruby/1.8/fileutils.rb:1242:in `copy_file''
> from /usr/lib/ruby/1.8/fileutils.rb:459:in `copy_file''
> from /usr/lib/ruby/1.8/fileutils.rb:383:in `copy''
> from /usr/lib/ruby/1.8/fileutils.rb:1377:in
`fu_each_src_dest''
> from /usr/lib/ruby/1.8/fileutils.rb:1393:in
`fu_each_src_dest0''
> from /usr/lib/ruby/1.8/fileutils.rb:1375:in
`fu_each_src_dest''
> from /usr/lib/ruby/1.8/fileutils.rb:382:in `copy''
> from ./lib/weft/backend/sqlite.rb:126:in `save''
> from ./lib/weft/wxgui.rb:484:in `save_project''
> from ./lib/weft/wxgui.rb:484:in `save_project''
> from ./lib/weft/wxgui.rb:479:in `on_save_project''
> from ./lib/weft/wxgui.rb:100:in `create_menus''
> from ./lib/weft/wxgui/workarea.rb:223:in `add_item''
> from weft-qda.rb:28
>
> Then a failed assertion in GTK:
>
> Gtk-ERROR **: file gtktext.c: line 4724 (find_line_params): assertion
> failed: (lp.end.property)
> aborting...
>
> The second problem looks like a Weft Bug, the other two are more
> likely problems with underlying libraries. I am using ruby 1.8.3 and
> wxGTK-2.4.2. Are there more stable version of those that I should be
> using instead?
>
> Now, for the sake of anyone trying to install Weft on Fedora Core 3,
> here is exactly what it takes (all commands run as root from /tmp):
>
> yum install ruby
> yum install sqlite
> yum install sqlite-devel
> wget http://rubyforge.org/frs/download.php/2818/sqlite-ruby-2.2.3.gem
> gem install sqlite-ruby-2.2.3.gem
>
> ("gem install --remote sqlite-ruby" didn''t do it for me)
>
> yum install wxGTK
> yum install wxGTK-devel
>
> (Installing wxGTK-devel takes a long time, go get some coffee while it
runs.)
>
> After that you need to manually install the missing htmlproc.h:
>
> wget ftp://biolpc22.york.ac.uk/pub/2.4.2/wxGTK-2.4.2.tar.gz
> tar xvzf wxGTK-2.4.2.tar.gz.2
> cd wxGTK-2.4.2
> cp wxGTK-2.4.2/include/wx/html/htmlproc.h /usr/include/wx/html/
>
> Then wxRuby:
>
> wget http://rubyforge.org/frs/download.php/1983/wxruby-0.6-src.tar.gz
> tar xvzf wxruby-0.6-src.tar.gz
> cd wxruby-0.6-src/src
> ruby extconf.rb
> make
> ruby install.rb
>
> (Make will again take quite a bit. Go get another coffee.)
>
> Finally Weft itself (the link from the project page is dead, btw).
>
> wget
http://rubyforge.org/frs/download.php/5138/weft_qda-src-0.9.6.tar.gz
> tar xvzf weft_qda-src-0.9.6.tar.gz
>
> All the commands up until now were as root, not running as normal user:
>
> cd /tmp/weft_qda-0.9.6/
> ruby weft-qda.rb &
>
> - yuri
>
--
http://www.freewisdom.org/
Hi Yuri Thanks very much for the detailed error reports - it''s very useful. While working on 0.9.6 I didn''t have a Linux testing environment available; WxWidgets is *meant* to be cross-platform, but there seem to be enough differences to cause bugs. Version 0.9.7 has had more extensive testing on Linux and should address the problems you''ve found. It''s taken a bit longer to do this new version than I''d like, but it should be ready soon!>0.9.5 also crashes when saving the project, but it only seems to >happen less often if I avoid saving it to a file in a different >directory. (It still crashes about half the time, though.) > >I have just made a small change in CVS that I hope will fix this serious problem.>Also, in 0.9.6 when I code a passage my text display gets mangled. In >0.9.5 coding doesn''t have any visible effect (which I imagine it >should), but it does seem to register, since I can then view the >codes. > >The code to highlight coded text in blue was added in version 0.9.6. Unfortunately, there seems to be a problem with either WxWidgets or wxruby on Linux that causes both the segfaults you reported in your last email, and the mangling of text that you report. For the time being, I''m going to disable this functionality on Linux - as you note, the coding still works.>The most serious problem I have with 0.9.5, however is that it >typically crashes when I try to view an imported document: > >[yuri at localhost weft_qda]$ ./lib/weft/wxgui/sidebar.rb:109:in >`get_current_category'': undefined method `parent'' for nil:NilClass >(NoMethodError) >This seems to be caused by undocumented differences in WxWidgets between Windows and Linux. I''ve put a fix in that should address this. cheers alex
I will wait for 0.9.7 then. Meanwhile two questions: 1. Does Weft allows to edit the text after it has been imported? The version I played with doesn''t seem to allow this. Is this on the list of things to do or is such a feature impossible? 2. Are there any plans to add Unicode support? - yuri On 11/21/05, Alex Fenton <alex at pressure.to> wrote:> Hi Yuri > > Thanks very much for the detailed error reports - it''s very useful. > While working on 0.9.6 I didn''t have a Linux testing environment > available; WxWidgets is *meant* to be cross-platform, but there seem to > be enough differences to cause bugs. Version 0.9.7 has had more > extensive testing on Linux and should address the problems you''ve found. > It''s taken a bit longer to do this new version than I''d like, but it > should be ready soon! > > >0.9.5 also crashes when saving the project, but it only seems to > >happen less often if I avoid saving it to a file in a different > >directory. (It still crashes about half the time, though.) > > > > > I have just made a small change in CVS that I hope will fix this serious > problem. > > >Also, in 0.9.6 when I code a passage my text display gets mangled. In > >0.9.5 coding doesn''t have any visible effect (which I imagine it > >should), but it does seem to register, since I can then view the > >codes. > > > > > The code to highlight coded text in blue was added in version 0.9.6. > Unfortunately, there seems to be a problem with either WxWidgets or > wxruby on Linux that causes both the segfaults you reported in your last > email, and the mangling of text that you report. > > For the time being, I''m going to disable this functionality on Linux - > as you note, the coding still works. > > >The most serious problem I have with 0.9.5, however is that it > >typically crashes when I try to view an imported document: > > > >[yuri at localhost weft_qda]$ ./lib/weft/wxgui/sidebar.rb:109:in > >`get_current_category'': undefined method `parent'' for nil:NilClass > >(NoMethodError) > > > This seems to be caused by undocumented differences in WxWidgets between > Windows and Linux. I''ve put a fix in that should address this. > > cheers > alex > _______________________________________________ > Weft-qda-users mailing list > Weft-qda-users at rubyforge.org > http://rubyforge.org/mailman/listinfo/weft-qda-users >-- http://www.freewisdom.org/
Yuri T. wrote:>1. Does Weft allows to edit the text after it has been imported? The >version I played with doesn''t seem to allow this. Is this on the >list of things to do or is such a feature impossible? > >No, it''s not possible at the moment. I''ve explored a little bit in the past, and it''s not impossible to add it either. It''s on the TODO list, but it''s some way down. Could you give some examples of how you would like to use this feature? Eg - appending text to an existing document (eg a diary, or dated notes), or fixing minor typos in text? Would you want to use it on text that has already been coded by categories?>2. Are there any plans to add Unicode support? > >Yes, definitely - it''s a high priority. However, it''ll involve incompatible changes to the storage format, support libraries and the API, so it''ll be part of Weft QDA version 2.x. My plan is that it will import documents in a range of encodings, but all text will be stored, manipulated and output in UTF-8 or perhaps UTF-16. Again, comments welcome. regards alex
> Could you give some examples of how you would like to use this feature? > Eg - appending text to an existing document (eg a diary, or dated > notes), or fixing minor typos in text? Would you want to use it on text > that has already been coded by categories?I work with interviews as MP3s. In the good case I get a transcription done early before any coding. However, when I start working on a paper I verify all quotes and it inevitable that some of them turn out to be off. So, it would be good at this point to correct the text in the tool, rather than just correct it in the paper and leave wrong text in the tool. Other times, however, I don''t have time/funds to do full transcription upfront. So, what I want to do is listen to the interview, select specific parts, and transcribe them, usually just taking notes of the rest. In this case I start coding before transcription is finished, but gradually transcribe more. I don''t think any QDA tool supports this kind of "progressive transcription". I''ve been thinking that I were to finally sit down and try to write my own tool, I might try to attach tags to the audio rather than text, which would make progressive transcription easy. This of course creates zellion other problems. I''ve thought of doing two different types of tags (audio or text), but this of course is complicated too.> My plan is that it will import documents in a range of encodings, but > all text will be stored, manipulated and output in UTF-8 or perhaps > UTF-16. Again, comments welcome.I think this is the right approach. - yuri -- http://www.freewisdom.org/