undefined reference to symbol 'sem_timedwait@@GLIBC_2.2.5'

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Use Ubuntu 13.04 64 bit
2. compile the libxbee with make
3. go to the samples directory and call the ./buildall script
4. Compilation will fail with
undefined reference to symbol 'sem_timedwait@@GLIBC_2.2.5'

What is the expected output? 
- Compile the samples

What do you see instead?
- Compilation fail

What version of the product are you using? On what operating system?
- latest git 

Solution:
- Add -lpthreads linker flag to the makefile after the -lxbee flag

Please provide any additional information below.

Original issue reported on code.google.com by martonmi...@gmail.com on 7 Nov 2013 at 6:18

[GoogleCodeExporter]

Hello,

Thanks for reporting this issue.
Do you see any other undefined symbols?
Are you able to determine if libxbee is trying to link with a version of the 
symbol that is not in the library in Ubuntu 13.04?

Please could you give the output of the following command:
ldd ./lib/libxbee.so

This should really be handled by libxbee specifying libpthread as a 
dependancy...

Thanks,
Attie

Original comment by attie@attie.co.uk on 7 Nov 2013 at 8:13

[GoogleCodeExporter]

Hallo,

- No I do not have any: http://pastebin.com/DJph7hJr
- mm@lapos:~/Projektek/libxbee.libxbee-v3$ ldd ./lib/libxbee.so
        linux-vdso.so.1 =>  (0x00007fff7bbfe000)
        libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 (0x00007f174892c000)
        librt.so.1 => /lib/x86_64-linux-gnu/librt.so.1 (0x00007f1748724000)
        libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007f174835a000)
        /lib64/ld-linux-x86-64.so.2 (0x00007f1748da5000)
mm@lapos:~/Projektek/libxbee.libxbee-v3$ dpkg -S 
/lib/x86_64-linux-gnu/libpthread.so.0
libc6:amd64: /lib/x86_64-linux-gnu/libpthread.so.0

So as I see  the libxbee is linked with the correct libpthread which is shipped 
with the libc6 package.

Yes I thought the same.  

Original comment by martonmi...@gmail.com on 9 Nov 2013 at 10:45

[GoogleCodeExporter]

Sorry for the delayed response. I keep replying to the notification emails, 
which doesn't work!

I believe that this has been fixed as-of 
aad1fce3864eccc80a003b3b93010e6f56bb87dd (16 Nov 2013)

Attie

Original comment by attie@attie.co.uk on 15 Jul 2014 at 9:19

• Changed state: Fixed

[GoogleCodeExporter]

Cool, I will give it a try soon. Or later ;)

Original comment by martonmi...@gmail.com on 15 Jul 2014 at 12:45