< Previous by Date | Date Index | Next by Date > |
< Previous in Thread | Thread Index |
I was running into the same problem as well. I just got a new subversion checkout and I'm getting exactly the same error while compiling repro. The stack compiles fine however...
Andreas
-----Original Message-----
From: resiprocate-devel-bounces@xxxxxxxxxxxxxxxxxxx [mailto:resiprocate-devel-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of Mike Lehmann
Sent: Tuesday, January 10, 2006 2:08 PM
To: resiprocate-devel@xxxxxxxxxxxxxxxxxxx
Subject: [reSIProcate] noob make question (from svn)
hi all,
I am trying to add some headers to resip (to allow p2p overlay
information, but that's a long and boring story). To do this I have
to modify the gperf files, so I am using the subversion checkouts.
After pulling down the latest, I ran configure and make, and got the
following error (attached is a fuller version of the error, with the
pertinent make step):
../build/../resip/stack/obj.debug.Linux.i686/libresip.a(MethodTypes.o)(.text+0x48):
In function `resip::getMethodType(char const*, int)':
/home/mlehmann/work/resip_checkout/main/resip/stack/MethodTypes.cxx:63:
undefined reference to `resip::MethodHash::in_word_set(char const*,
unsigned int)'
collect2: ld returned 1 exit status
make[1]: *** [bin.debug.Linux.i686/repro] Error 1
make[1]: Leaving directory `/work/mlehmann/resip_checkout/main/repro'
make: *** [repro] Error 2
Checking through the code, I saw that in_word_set() (with those
params) seems to have been properly defined (in HeaderHash.cxx).
Further, I compared HeaderHash.[ch]xx and MethodHash.[ch]xx between
the svn and the latest tarball, and found only cosmetic differences,
none relating to in_word_set().
I then checked the sipfoundry archives, to see if this problem had
popped up before. I found a reference to the question in Dec 2004,
but couldn't find an answer...
I'm about to look at the makefile, to make sure that the linker is
referencing whatever object file HeaderHash.cxx turns into, but I
thought it might be a good idea to also seek out the thoughts of
people who actually know the product :)
thanks and regards,
Mike Lehmann