<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Recent changes to bugs</title><link>https://sourceforge.net/p/popsearch/bugs/</link><description>Recent changes to bugs</description><atom:link href="https://sourceforge.net/p/popsearch/bugs/feed.rss" rel="self"/><language>en</language><lastBuildDate>Fri, 05 Nov 2004 22:28:33 -0000</lastBuildDate><atom:link href="https://sourceforge.net/p/popsearch/bugs/feed.rss" rel="self" type="application/rss+xml"/><item><title>Link errors in WordNet library</title><link>https://sourceforge.net/p/popsearch/bugs/6/</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;Having fixed the problem whereby wn.h is not found, the build &lt;br /&gt;
continues fine until it tries to link against libwn. Then I get the &lt;br /&gt;
following errors:&lt;/p&gt;
&lt;p&gt;/home/rrt/download/popsearch-0.3.1/src/irs/.libs/libirs.so: &lt;br /&gt;
undefined reference to `free_syns'&lt;br /&gt;
/home/rrt/download/popsearch-0.3.1/src/irs/.libs/libirs.so: &lt;br /&gt;
undefined reference to `in_wn'&lt;br /&gt;
/home/rrt/download/popsearch-0.3.1/src/irs/.libs/libirs.so: &lt;br /&gt;
undefined reference to `wninit'&lt;br /&gt;
/home/rrt/download/popsearch-0.3.1/src/irs/.libs/libirs.so: &lt;br /&gt;
undefined reference to `findtheinfo_ds'&lt;/p&gt;
&lt;p&gt;These symbols are all defined in /usr/lib/libwn.so, which is on &lt;br /&gt;
the library path (because it's in the default directory). I have no &lt;br /&gt;
idea why they are not being linked.&lt;/p&gt;
&lt;p&gt;I am using the default wordnet-dev and wordnet packages from &lt;br /&gt;
Debian sarge.&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Reuben Thomas</dc:creator><pubDate>Fri, 05 Nov 2004 22:28:33 -0000</pubDate><guid isPermaLink="false">https://sourceforge.neted706884c54a718d596e53db570e40613c2b3be1</guid></item><item><title>configure script doesn't find wn.h</title><link>https://sourceforge.net/p/popsearch/bugs/5/</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;The configure script doesn't find wn.h in /usr/include. There are &lt;br /&gt;
standard autotools ways to look for include files...&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Reuben Thomas</dc:creator><pubDate>Fri, 05 Nov 2004 22:13:37 -0000</pubDate><guid isPermaLink="false">https://sourceforge.net6dcb71ef8ed9c809874a2e59d2339440fe13b088</guid></item><item><title>configure doesn't complain if wordnet dev files missing</title><link>https://sourceforge.net/p/popsearch/bugs/4/</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;Specifically, it didn't notice that I didn't have wn.h, and I only got &lt;br /&gt;
problems during the build.&lt;/p&gt;
&lt;p&gt;This is with popsearch 0.3.0.&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Reuben Thomas</dc:creator><pubDate>Wed, 03 Nov 2004 23:56:03 -0000</pubDate><guid isPermaLink="false">https://sourceforge.net4db2c949a2010c591f6111ce524224f7dee052a6</guid></item><item><title>popsearch 0.1.5 won't build with g++ 3.4</title><link>https://sourceforge.net/p/popsearch/bugs/3/</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;Since I had problems building popsearch with g++ 3.3, I tried 3.4. &lt;br /&gt;
Unfortunately, popsearch falls foul of the stricter checking in g++ 3.4. I can &lt;br /&gt;
give specifics if you're interested.&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Reuben Thomas</dc:creator><pubDate>Tue, 05 Oct 2004 17:32:21 -0000</pubDate><guid isPermaLink="false">https://sourceforge.net30bb19f591a89b93fa29faf2d48b33057dfb92ea</guid></item><item><title>Out of memory compiling TopicManager.cc</title><link>https://sourceforge.net/p/popsearch/bugs/2/</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;g++ 3.3.4 on my Debian sarge x86 system chews through 1.5Gb of total &lt;br /&gt;
virtual memory trying to compile this monstrous file before giving up (at the &lt;br /&gt;
standard -O2 setting).&lt;/p&gt;
&lt;p&gt;Whether you think this is a reasonable amount of memory to consume to &lt;br /&gt;
compile a 10k-plus line method is a matter for debate; however, it's fairly &lt;br /&gt;
certain that g++ 3.3 will soon be widespread, and that it's not something the &lt;br /&gt;
GCC people are likely to fix, so breaking up this method into smaller chunks &lt;br /&gt;
is probably the way to go.&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Reuben Thomas</dc:creator><pubDate>Sat, 18 Sep 2004 18:07:23 -0000</pubDate><guid isPermaLink="false">https://sourceforge.net4175271ebfebd3db92c8b105dea8c1242642e8e4</guid></item><item><title>0.1.4: flex parser doesn't build</title><link>https://sourceforge.net/p/popsearch/bugs/1/</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;Two problems:&lt;/p&gt;
&lt;p&gt;1. The pre-generated flex parser won't build against a recent flex. To fix this, &lt;br /&gt;
don't ship the .cc file.&lt;/p&gt;
&lt;p&gt;2. flex on my system isn't called flex++. To fix this, don't hardwire its name &lt;br /&gt;
into the makefile.&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Reuben Thomas</dc:creator><pubDate>Sat, 18 Sep 2004 18:04:43 -0000</pubDate><guid isPermaLink="false">https://sourceforge.netdc26b92848e4cf9e5302e294155bcaa160373b7f</guid></item></channel></rss>