19 Apr
2012
19 Apr
'12
7:25 p.m.
Hi
First Problem:
When I try to Build libdect (libnl was build and Installed without any critical errors):
root@bt:/home/libdect# sh configure
checking for gcc... gcc
checking whether the C compiler works... yes
checking for C compiler default output file name... a.out
checking for suffix of executables...
checking whether we are cross compiling... no
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ISO C89... none needed
checking for a thread-safe mkdir -p... /bin/mkdir -p
checking for a BSD-compatible install... /usr/bin/install -c
checking whether ln -s works... yes
checking for a sed that does not truncate output... /bin/sed
configure: Documentation build disabled
checking for nl_socket_alloc in -lnl... no
configure: error: No suitable version of libnl found
Second Problem:
When I Put in my com-on-air PCMCIA Card, and look in Kern.log:
Apr 19 19:06:26 bt kernel: [ 13.847922] com_on_air_cs 0.0: DECTDataDevice PCMCIA F22
Apr 19 19:06:26 bt kernel: [ 13.888290] com_on_air_cs 0.0: Radio type U2785B
Apr 19 19:06:26 bt kernel: [ 13.901784] com_on_air_cs 0.0: Loading firmware ...
Apr 19 19:06:26 bt kernel: [ 13.996529] pcmcia 0.1: pcmcia: registering new device
pcmcia0.1 (IRQ: 3)
Apr 19 19:06:26 bt kernel: [ 13.996740] com_on_air_cs 0.1: DECTDataDevice PCMCIA F22
Apr 19 19:06:26 bt kernel: [ 13.996818] com_on_air_cs 0.1: failed to enable PCMCIA
device
Apr 19 19:06:26 bt kernel: [ 13.996880] com_on_air_cs: probe of 0.1 failed with error
-13
20 Apr
20 Apr
10:54 a.m.
Hi
First Problem:
When I try to Build libdect (libnl was build and Installed without any critical errors):
root@bt:/home/libdect# sh configure
checking for gcc... gcc
checking whether the C compiler works... yes
checking for C compiler default output file name... a.out
checking for suffix of executables...
checking whether we are cross compiling... no
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ISO C89... none needed
checking for a thread-safe mkdir -p... /bin/mkdir -p
checking for a BSD-compatible install... /usr/bin/install -c
checking whether ln -s works... yes
checking for a sed that does not truncate output... /bin/sed
configure: Documentation build disabled
checking for nl_socket_alloc in -lnl... no
configure: error: No suitable version of libnl found
Second Problem:
When I Put in my com-on-air PCMCIA Card, and look in Kern.log:
Apr 19 19:06:26 bt kernel: [ 13.847922] com_on_air_cs 0.0: DECTDataDevice PCMCIA F22
Apr 19 19:06:26 bt kernel: [ 13.888290] com_on_air_cs 0.0: Radio type U2785B
Apr 19 19:06:26 bt kernel: [ 13.901784] com_on_air_cs 0.0: Loading firmware ...
Apr 19 19:06:26 bt kernel: [ 13.996529] pcmcia 0.1: pcmcia: registering new device
pcmcia0.1 (IRQ: 3)
Apr 19 19:06:26 bt kernel: [ 13.996740] com_on_air_cs 0.1: DECTDataDevice PCMCIA F22
Apr 19 19:06:26 bt kernel: [ 13.996818] com_on_air_cs 0.1: failed to enable PCMCIA
device
Apr 19 19:06:26 bt kernel: [ 13.996880] com_on_air_cs: probe of 0.1 failed with error
-13
3:04 p.m.
Which Version seems suitable?
I Installed the Version from dect.osmocom.org. Maybe something went wrong?
3:32 p.m.
On Fri, Apr 20, 2012 at 03:04:41PM +0200, Sebastian --- wrote:
Which Version seems suitable?
I Installed the Version from dect.osmocom.org. Maybe something went wrong?
Most likely libnl is okay but is not found.
The emphasis was on "install", not on "suitable version".
Take a look at the check that is done in configure.ac, there isn't any
version checking.
Reading config.log also helps in understanding why a configure run
failed.
Make sure the linker can find the .so.
Actually, if you just enter the commands from the "Build instructions"
page, it won't work.
Kind regards,
-Alexander Huemer
3:56 p.m.
Perhaps posting the last lines of config.log might help us to find out,
what went wrong with libnl.
Am Freitag, den 20.04.2012, 15:32 +0200 schrieb Alexander Huemer:
On Fri, Apr 20, 2012 at 03:04:41PM +0200, Sebastian
--- wrote:
Which Version seems suitable?
I Installed the Version from dect.osmocom.org. Maybe something went wrong?
Most likely libnl is okay but is not found.
The emphasis was on "install", not on "suitable version".
Take a look at the check that is done in configure.ac, there isn't any
version checking.
Reading config.log also helps in understanding why a configure run
failed.
Make sure the linker can find the .so.
Actually, if you just enter the commands from the "Build instructions"
page, it won't work.
Kind regards,
-Alexander Huemer
21 Apr
21 Apr
5:57 a.m.
Alexander Huemer wrote:
Most likely libnl is okay but is not found.
The emphasis was on "install", not on "suitable version".
Take a look at the check that is done in configure.ac, there isn't any
version checking.
Reading config.log also helps in understanding why a configure run
failed.
Make sure the linker can find the .so.
Actually, if you just enter the commands from the "Build instructions"
page, it won't work.
Configure won't be looking for the .so. It will be looking for the .h file or
the pkgconfig info. You need to install the dev or devel package for libnl.
24 Apr
24 Apr
8:55 a.m.
Date: Fri, 20 Apr 2012 20:57:56 -0700
From: samuel(a)sieb.net
To: linux-dect(a)lists.osmocom.org
Subject: Re: Problems Building DECT Stack
Alexander Huemer wrote:
I Uninstalled the devel Package, then it worked.
But I still have problems with:
Apr 19 19:06:26 bt kernel: [ 13.847922] com_on_air_cs 0.0: DECTDataDevice PCMCIA F22
Apr 19 19:06:26 bt kernel: [ 13.888290] com_on_air_cs 0.0: Radio type U2785B
Apr 19 19:06:26 bt kernel: [ 13.901784] com_on_air_cs 0.0: Loading firmware ...
Apr 19 19:06:26 bt kernel: [ 13.996529] pcmcia 0.1: pcmcia: registering new device
pcmcia0.1 (IRQ: 3)
Apr 19 19:06:26 bt kernel: [ 13.996740] com_on_air_cs 0.1: DECTDataDevice PCMCIA F22
Apr 19 19:06:26 bt kernel: [ 13.996818] com_on_air_cs 0.1: failed to enable PCMCIA
device
Apr 19 19:06:26 bt kernel: [ 13.996880] com_on_air_cs: probe of 0.1 failed with error
-13
When I try to scan for FPs with dectmon, it doesnt find anything.
Help?
Most likely libnl is okay but is not found.
The emphasis was on "install", not on "suitable version".
Take a look at the check that is done in configure.ac, there isn't any
version checking.
Reading config.log also helps in understanding why a configure run
failed.
Make sure the linker can find the .so.
Actually, if you just enter the commands from the "Build instructions"
page, it won't work.
Configure won't be looking for the .so. It will be looking for the .h file or
the pkgconfig info. You need to install the dev or devel package for libnl.
9:42 a.m.
Hi Samuel,
In configure.ac of libdect I see:
# Checks for libraries.
AC_CHECK_LIB([nl], [nl_socket_alloc], ,
[AC_MSG_ERROR([No suitable version of libnl found])])
The resulting conftest is:
configure:3400: gcc -o conftest -g -O2 conftest.c -lnl >&5
/usr/bin/ld: cannot find -lnl
collect2: ld returned 1 exit status
configure:3400: $? = 1
configure: failed program was:
| /* confdefs.h */
| #define PACKAGE_NAME "libdect"
| #define PACKAGE_TARNAME "libdect"
| #define PACKAGE_VERSION "0.0.1"
| #define PACKAGE_STRING "libdect 0.0.1"
| #define PACKAGE_BUGREPORT "kaber(a)trash.net"
| #define PACKAGE_URL ""
| #define RELEASE_NAME "libdect"
| #define _GNU_SOURCE /**/
| #define _STDC_FORMAT_MACROS /**/
| /* end confdefs.h. */
|
| /* Override any GCC internal prototype to avoid an error.
| Use char because int might match the return type of a GCC
| builtin and then its argument prototype would still apply. */
| #ifdef __cplusplus
| extern "C"
| #endif
| char nl_socket_alloc ();
| int
| main ()
| {
| return nl_socket_alloc ();
| ;
| return 0;
| }
configure:3409: result: no
configure:3419: error: No suitable version of libnl found
* No PKG_CHECK_MODULES used
* No AC_CHECK_HEADERS used
* AC_CHECK_LIB used
On Fri, Apr 20, 2012 at 08:57:56PM -0700, Samuel Sieb wrote:
Configure won't be looking for the .so. It will
be looking for the
.h file or the pkgconfig info. You need to install the dev or devel
package for libnl.
Are you really sure that this is correct?
Kind regards,
-Alexander Huemer
7:16 p.m.
Alexander Huemer wrote:
On Fri, Apr 20, 2012 at 08:57:56PM -0700, Samuel Sieb
wrote:
Ok, I should have said "usually". :-)
You will still need the devel package for the headers anyways. Although looking
back at the earlier messages, he said he compiled libnl himself, so adding the
packages may mix things up.
Configure won't be looking for the .so. It
will be looking for the
.h file or the pkgconfig info. You need to install the dev or devel
package for libnl.
Are you really sure that this is correct?
4387
days inactive
4392
days old
9 comments
4 participants
participants (4)
-
Alexander Huemer -
Erik Tews -
Samuel Sieb -
Sebastian ---