[prev in list] [next in list] [prev in thread] [next in thread] 

List:       aspell-user
Subject:    Re: [Aspell-user] aspell-0.60 Compile Problem: undefined reference
From:       Richard Plana <RPlana () zicorp ! com>
Date:       2005-11-16 20:50:21
Message-ID: 1132174221.1940.5.camel () localhost ! localdomain
[Download RAW message or body]

On Thu, 2005-11-10 at 09:59 -0600, Gary Setter wrote:

> Longer answer
> The HashTable and BlockSList classes are template classes. The
> actual code is generated by the compiler as needed. They are
> declared in hash.hpp and block_slist.hpp. However, some of their
> methods are defined in hash-t.hpp and block_slist-t.hpp.
> 
> Why the separation? Why not define all the methods in one file? I
> believe the idea is that in many cases the definitions are not
> needed. When they are not, a module need only include hash.hpp.
> When they are, we include hash-t.hpp.
> 
> The compiler I use had the same problems as you are experiencing.
> My response was to move from including hash.hpp to including
> hash-t.hpp. Yes, that gives the compiler more to do and negates
> the separation between declaration and definition, but I was able
> to get a successful build.

Thanks, Gary and Kevin. For now, I've taken Gary's suggestion and
modified the source as follows:

---
aspell-0.60.4/common/string_map.hpp.fixmissingmethod        2005-11-16
13:29:18.000000000 -0700
+++ aspell-0.60.4/common/string_map.hpp 2005-11-16 13:29:18.000000000
-0700
@@ -11,7 +11,7 @@
 #include "parm_string.hpp"
 #include "posib_err.hpp"
 #include "string_pair.hpp"
-#include "hash.hpp"
+#include "hash-t.hpp"
 #include "objstack.hpp"
 
 
Until a proper fix has been committed, I'll use this for now. aspell at
least compiles on my system (FC4).


________________________________________________________________________


Richard Plana
Lead Software Engineer
Zi Corporation



[prev in list] [next in list] [prev in thread] [next in thread]