ruby-lorcon build problem

[asussex at googlemail.com (Andrew Sussex)]

I've installed Lorcon from SVN but ruby-lorcon refuses to build:

ruby-lorcon# ruby extconf.rb
checking for tx80211_txpacket() in -lorcon... no
Error: the lorcon library was not found, please see the README
ruby-lorcon#

The log file looks like this:

have_library: checking for tx80211_txpacket() in -lorcon...
-------------------- no

"gcc -o conftest -I. -I/usr/lib/ruby/1.8/i486-linux -I.  -Wall -g
-fno-strict-aliasing -O2  -fPIC conftest.c  -L"/usr/lib"  -rdynamic
-Wl,-export-dynamic     -lruby1.8-static -lorcon  -lpthread -ldl
-lcrypt -lm   -lc"
conftest.c: In function `t':
conftest.c:3: error: `tx80211_txpacket' undeclared (first use in this function)
conftest.c:3: error: (Each undeclared identifier is reported only once
conftest.c:3: error: for each function it appears in.)
checked program was:
/* begin */
1: /*top*/
2: int main() { return 0; }
3: int t() { void ((*volatile p)()); p = (void
((*)()))tx80211_txpacket; return 0; }
/* end */

"gcc -o conftest -I. -I/usr/lib/ruby/1.8/i486-linux -I.  -Wall -g
-fno-strict-aliasing -O2  -fPIC conftest.c  -L"/usr/lib"  -rdynamic
-Wl,-export-dynamic     -lruby1.8-static -lorcon  -lpthread -ldl
-lcrypt -lm   -lc"
conftest.c: In function `t':
conftest.c:3: warning: implicit declaration of function `tx80211_txpacket'
/usr/lib/libc_nonshared.a(elf-init.oS)(.text.__i686.get_pc_thunk.bx+0x0):
In function `__i686.get_pc_thunk.bx':
: multiple definition of `__i686.get_pc_thunk.bx'
/tmp/ccGUddTi.o(.gnu.linkonce.t.__i686.get_pc_thunk.bx+0x0):/home/user1/proj/frameworks/metasploit/3.0/framework-3.0-beta-3/external/ruby-lorcon/conftest.c:2:
first defined here
collect2: ld returned 1 exit status
checked program was:
/* begin */
1: /*top*/
2: int main() { return 0; }
3: int t() { tx80211_txpacket(); return 0; }
/* end */

--------------------

Lorcon is definitey installed. I even wrote a quick test program to
enumerate available drivers.

I'm using Debian 3.1 stable, gcc 3.3.5 (Debian 1:3.3.5-13), ruby1.8
and latest metasploit revision (4540.)

Can anyone shed any light on this?

Cheers,

- as