I would like to cross compile the bluez v3.8 on samsung S3C2440 Arm processor. I am using the arm cross compiler and then compile and installed bluez-lib-3.8 into the tool chain directory as following
/usr/local/arm/arm-gcc-3.4.4/gcc-3.4.4-glibc-2.3.3/arm-linux-gnu/arm-linux-gnu/lib
Then I set the libdir and includedir path as above when I configure the blue-util-3.8. However it return following error during the configuration.
checking for BLUEZ... no
configure: error: Bluetooth library is required
Do anyone know how to configurate and make it work?
The following log may be useful
***************************************************************************************
> ./configure CC=arm-linux-gnu-gcc --host=arm-linux-gnu --libdir=/usr/local/arm/arm-gcc-3.4.4/gcc-3.4.4-glibc-2.3.3/arm-linux-gnu/arm-linux-gnu/lib --includedir=/usr/local/arm/arm-gcc-3.4.4/gcc-3.4.4-glibc-2.3.3/arm-linux-gnu/arm-linux-gnu/include --with-bluez=/usr/local/arm/arm-gcc-3.4.4/gcc-3.4.4-glibc-2.3.3/arm-linux-gnu/arm-linux-gnu/libconfigure:
WARNING: If you wanted to set the --build type, don't use --host.
If a cross compiler is detected then cross compile mode will be used.
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking for arm-linux-gnu-strip... arm-linux-gnu-strip
checking whether to enable maintainer-specific portions of Makefiles... no
checking for arm-linux-gnu-gcc... arm-linux-gnu-gcc
checking for C compiler default output file name... a.out
checking whether the C compiler works... yes
checking whether we are cross compiling... yes
checking for suffix of executables...
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether arm-linux-gnu-gcc accepts -g... yes
checking for arm-linux-gnu-gcc option to accept ANSI C... none needed
checking for style of include used by make... GNU
checking dependency style of arm-linux-gnu-gcc... gcc3
checking whether arm-linux-gnu-gcc accepts -fPIE... yes
checking for a BSD-compatible install... /usr/bin/install -c
checking for bison... bison -y
checking for flex... flex
checking for yywrap in -lfl... no
checking for yywrap in -ll... no
checking lex output file root... lex.yy
checking whether yytext is a pointer... no
checking build system type... i686-redhat-linux-gnu
checking host system type... arm-unknown-linux-gnu
checking for a sed that does not truncate output... /bin/sed
checking for egrep... grep -E
checking for ld used by arm-linux-gnu-gcc... /usr/local/arm/arm-gcc-3.4.4/gcc-3.4.4-glibc-2.3.3/arm-linux-gnu/arm-linux-gnu/bin/ld
checking if the linker (/usr/local/arm/arm-gcc-3.4.4/gcc-3.4.4-glibc-2.3.3/arm-linux-gnu/arm-linux-gnu/bin/ld) is GNU ld... yes
checking for /usr/local/arm/arm-gcc-3.4.4/gcc-3.4.4-glibc-2.3.3/arm-linux-gnu/arm-linux-gnu/bin/ld option to reload object files... -r
checking for BSD-compatible nm... /usr/local/arm/arm-gcc-3.4.4/gcc-3.4.4-glibc-2.3.3/arm-linux-gnu/bin//arm-linux-gnu-nm -B
checking whether ln -s works... yes
checking how to recognise dependent libraries... pass_all
checking how to run the C preprocessor... arm-linux-gnu-gcc -E
checking for ANSI C header files... yes
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for unistd.h... yes
checking dlfcn.h usability... yes
checking dlfcn.h presence... yes
checking for dlfcn.h... yes
checking the maximum length of command line arguments... 32768
checking command to parse /usr/local/arm/arm-gcc-3.4.4/gcc-3.4.4-glibc-2.3.3/arm-linux-gnu/bin//arm-linux-gnu-nm -B output from arm-linux-gnu-gcc object... ok
checking for objdir... .libs
checking for arm-linux-gnu-ar... arm-linux-gnu-ar
checking for arm-linux-gnu-ranlib... arm-linux-gnu-ranlib
checking for arm-linux-gnu-strip... (cached) arm-linux-gnu-strip
checking if arm-linux-gnu-gcc supports -fno-rtti -fno-exceptions... no
checking for arm-linux-gnu-gcc option to produce PIC... -fPIC
checking if arm-linux-gnu-gcc PIC flag -fPIC works... yes
checking if arm-linux-gnu-gcc static flag -static works... yes
checking if arm-linux-gnu-gcc supports -c -o file.o... yes
checking whether the arm-linux-gnu-gcc linker (/usr/local/arm/arm-gcc-3.4.4/gcc-3.4.4-glibc-2.3.3/arm-linux-gnu/arm-linux-gnu/bin/ld) supports shared libraries... yes
checking whether -lc should be explicitly linked in... no
checking dynamic linker characteristics... GNU/Linux ld.so
checking how to hardcode library paths into programs... immediate
checking whether stripping libraries is possible... yes
checking if libtool supports shared libraries... yes
checking whether to build shared libraries... yes
checking whether to build static libraries... no
configure: creating libtool
checking for ppoll... no
checking for arm-linux-gnu-pkg-config... no
checking for pkg-config... /usr/bin/pkg-config
checking pkg-config is at least version 0.9.0... yes
checking for BLUEZ... no
configure: error: Bluetooth library is required
*****************************************************************************
Regards
_______________________________________
YM - ???u?T??
?N???A?S???W???A?A???B?ͤ??i?H?d?U?T?????A?A???A?W???ɴN???ߧY?ݨ??A???????ܳ??N?????C
http://messenger.yahoo.com.hk
Thanks. it is done after setting the PKG_CONFIG_PATH
siddhant tewari <[email protected]> ???G hi,
After doing make install , while building bluez ,bluez.pc file should be there in the /usr/local/arm/arm-gcc-3.4.4/gcc-3.4.4-glibc-2.3.3/arm-linux-gnu/arm-linux-gnu /lib/pkgconfig folder ... then you can set PKG_CONFIG_PATH variable to ask pkg-config to use this file. I hope this should work.
regards
siddhant
On 1/2/07, KS H <[email protected]> wrote: I would like to cross compile the bluez v3.8 on samsung S3C2440 Arm processor. I am using the arm cross compiler and then compile and installed bluez-lib-3.8 into the tool chain directory as following
/usr/local/arm/arm- gcc-3.4.4/gcc-3.4.4-glibc-2.3.3/arm-linux-gnu/arm-linux-gnu/lib
Then I set the libdir and includedir path as above when I configure the blue-util-3.8. However it return following error during the configuration.
checking for BLUEZ... no
configure: error: Bluetooth library is required
Do anyone know how to configurate and make it work?
The following log may be useful
***************************************************************************************
> ./configure CC=arm-linux-gnu-gcc --host=arm-linux-gnu --libdir=/usr/local/arm/arm-gcc-3.4.4/gcc-3.4.4-glibc-2.3.3/arm-linux-gnu/arm-linux-gnu/lib --includedir=/usr/local/arm/arm-gcc-3.4.4/gcc-3.4.4-glibc-2.3.3/arm-linux-gnu/arm-linux-gnu/include --with-bluez=/usr/local/arm/arm-gcc-3.4.4/gcc-3.4.4-glibc-2.3.3/arm-linux-gnu/arm-linux-gnu/libconfigure:
WARNING: If you wanted to set the --build type, don't use --host.
If a cross compiler is detected then cross compile mode will be used.
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking for arm-linux-gnu-strip... arm-linux-gnu-strip
checking whether to enable maintainer-specific portions of Makefiles... no
checking for arm-linux-gnu-gcc... arm-linux-gnu-gcc
checking for C compiler default output file name... a.out
checking whether the C compiler works... yes
checking whether we are cross compiling... yes
checking for suffix of executables...
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether arm-linux-gnu-gcc accepts -g... yes
checking for arm-linux-gnu-gcc option to accept ANSI C... none needed
checking for style of include used by make... GNU
checking dependency style of arm-linux-gnu-gcc... gcc3
checking whether arm-linux-gnu-gcc accepts -fPIE... yes
checking for a BSD-compatible install... /usr/bin/install -c
checking for bison... bison -y
checking for flex... flex
checking for yywrap in -lfl... no
checking for yywrap in -ll... no
checking lex output file root... lex.yy
checking whether yytext is a pointer... no
checking build system type... i686-redhat-linux-gnu
checking host system type... arm-unknown-linux-gnu
checking for a sed that does not truncate output... /bin/sed
checking for egrep... grep -E
checking for ld used by arm-linux-gnu-gcc... /usr/local/arm/arm-gcc-3.4.4/gcc-3.4.4-glibc-2.3.3/arm-linux-gnu/arm-linux-gnu/bin/ld
checking if the linker (/usr/local/arm/arm-gcc-3.4.4/gcc-3.4.4-glibc-2.3.3/arm-linux-gnu/arm-linux-gnu/bin/ld) is GNU ld... yes
checking for /usr/local/arm/arm-gcc-3.4.4/gcc-3.4.4-glibc-2.3.3/arm-linux-gnu/arm-linux-gnu/bin/ld option to reload object files... -r
checking for BSD-compatible nm... /usr/local/arm/arm-gcc-3.4.4/gcc-3.4.4-glibc-2.3.3/arm-linux-gnu/bin//arm-linux-gnu-nm -B
checking whether ln -s works... yes
checking how to recognise dependent libraries... pass_all
checking how to run the C preprocessor... arm-linux-gnu-gcc -E
checking for ANSI C header files... yes
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for unistd.h... yes
checking dlfcn.h usability... yes
checking dlfcn.h presence... yes
checking for dlfcn.h... yes
checking the maximum length of command line arguments... 32768
checking command to parse /usr/local/arm/arm-gcc-3.4.4/gcc-3.4.4-glibc-2.3.3/arm-linux-gnu/bin//arm-linux-gnu-nm -B output from arm-linux-gnu-gcc object... ok
checking for objdir... .libs
checking for arm-linux-gnu-ar... arm-linux-gnu-ar
checking for arm-linux-gnu-ranlib... arm-linux-gnu-ranlib
checking for arm-linux-gnu-strip... (cached) arm-linux-gnu-strip
checking if arm-linux-gnu-gcc supports -fno-rtti -fno-exceptions... no
checking for arm-linux-gnu-gcc option to produce PIC... -fPIC
checking if arm-linux-gnu-gcc PIC flag -fPIC works... yes
checking if arm-linux-gnu-gcc static flag -static works... yes
checking if arm-linux-gnu-gcc supports -c -o file.o... yes
checking whether the arm-linux-gnu-gcc linker (/usr/local/arm/arm-gcc-3.4.4/gcc-3.4.4-glibc-2.3.3/arm-linux-gnu/arm-linux-gnu/bin/ld) supports shared libraries... yes
checking whether -lc should be explicitly linked in... no
checking dynamic linker characteristics... GNU/Linux ld.so
checking how to hardcode library paths into programs... immediate
checking whether stripping libraries is possible... yes
checking if libtool supports shared libraries... yes
checking whether to build shared libraries... yes
checking whether to build static libraries... no
configure: creating libtool
checking for ppoll... no
checking for arm-linux-gnu-pkg-config... no
checking for pkg-config... /usr/bin/pkg-config
checking pkg-config is at least version 0.9.0... yes
checking for BLUEZ... no
configure: error: Bluetooth library is required
*****************************************************************************
Regards
_______________________________________
YM - ???u?T??
?N???A?S???W???A?A???B?ͤ??i?H?d?U?T?????A?A???A?W???ɴN???ߧY?ݨ??A???????ܳ??N?????C
http://messenger.yahoo.com.hk
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Bluez-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-users
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV_______________________________________________
Bluez-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-users
_______________________________________
YM - ???u?T??
?N???A?S???W???A?A???B?ͤ??i?H?d?U?T?????A?A???A?W???ɴN???ߧY?ݨ??A???????ܳ??N?????C
http://messenger.yahoo.com.hk
hi,
After doing make install , while building bluez ,bluez.pc file should be
there in the /usr/local/arm/arm-gcc-3.4.4/gcc-3.4.4-glibc-2.3.3
/arm-linux-gnu/arm-linux-gnu
>
> /lib/pkgconfig folder ... then you can set PKG_CONFIG_PATH variable to ask
> pkg-config to use this file. I hope this should work.
regards
siddhant
On 1/2/07, KS H <[email protected]> wrote:
>
> I would like to cross compile the bluez v3.8 on samsung S3C2440 Arm
> processor. I am using the arm cross compiler and then compile and installed
> bluez-lib-3.8 into the tool chain directory as following
>
> /usr/local/arm/arm-gcc-3.4.4/gcc-3.4.4-glibc-2.3.3
> /arm-linux-gnu/arm-linux-gnu/lib
>
> Then I set the libdir and includedir path as above when I configure the
> blue-util-3.8. However it return following error during the configuration.
>
> checking for BLUEZ... no
> configure: error: Bluetooth library is required
>
> Do anyone know how to configurate and make it work?
>
> The following log may be useful
>
> ***************************************************************************************
> > ./configure CC=arm-linux-gnu-gcc --host=arm-linux-gnu
> --libdir=/usr/local/arm/arm-gcc-3.4.4/gcc-3.4.4-glibc-2.3.3/arm-linux-gnu/arm-linux-gnu/lib
> --includedir=/usr/local/arm/arm-gcc-3.4.4/gcc-3.4.4-glibc-2.3.3/arm-linux-gnu/arm-linux-gnu/include
> --with-bluez=/usr/local/arm/arm-gcc-3.4.4/gcc-3.4.4-glibc-2.3.3/arm-linux-gnu/arm-linux-gnu/libconfigure:
>
>
> WARNING: If you wanted to set the --build type, don't use --host.
> If a cross compiler is detected then cross compile mode will be used.
> checking for a BSD-compatible install... /usr/bin/install -c
> checking whether build environment is sane... yes
> checking for gawk... gawk
> checking whether make sets $(MAKE)... yes
> checking for arm-linux-gnu-strip... arm-linux-gnu-strip
> checking whether to enable maintainer-specific portions of Makefiles... no
> checking for arm-linux-gnu-gcc... arm-linux-gnu-gcc
> checking for C compiler default output file name... a.out
> checking whether the C compiler works... yes
> checking whether we are cross compiling... yes
> checking for suffix of executables...
> checking for suffix of object files... o
> checking whether we are using the GNU C compiler... yes
> checking whether arm-linux-gnu-gcc accepts -g... yes
> checking for arm-linux-gnu-gcc option to accept ANSI C... none needed
> checking for style of include used by make... GNU
> checking dependency style of arm-linux-gnu-gcc... gcc3
> checking whether arm-linux-gnu-gcc accepts -fPIE... yes
> checking for a BSD-compatible install... /usr/bin/install -c
> checking for bison... bison -y
> checking for flex... flex
> checking for yywrap in -lfl... no
> checking for yywrap in -ll... no
> checking lex output file root... lex.yy
> checking whether yytext is a pointer... no
> checking build system type... i686-redhat-linux-gnu
> checking host system type... arm-unknown-linux-gnu
> checking for a sed that does not truncate output... /bin/sed
> checking for egrep... grep -E
> checking for ld used by arm-linux-gnu-gcc... /usr/local/arm/arm-gcc-3.4.4
> /gcc-3.4.4-glibc-2.3.3/arm-linux-gnu/arm-linux-gnu/bin/ld
> checking if the linker (/usr/local/arm/arm-gcc-3.4.4/gcc-3.4.4-glibc-2.3.3/arm-linux-gnu/arm-linux-gnu/bin/ld)
> is GNU ld... yes
> checking for /usr/local/arm/arm-gcc-3.4.4/gcc-3.4.4-glibc-2.3.3/arm-linux-gnu/arm-linux-gnu/bin/ld
> option to reload object files... -r
> checking for BSD-compatible nm... /usr/local/arm/arm-gcc-3.4.4/gcc-
> 3.4.4-glibc-2.3.3/arm-linux-gnu/bin//arm-linux-gnu-nm -B
> checking whether ln -s works... yes
> checking how to recognise dependent libraries... pass_all
> checking how to run the C preprocessor... arm-linux-gnu-gcc -E
> checking for ANSI C header files... yes
> checking for sys/types.h... yes
> checking for sys/stat.h... yes
> checking for stdlib.h... yes
> checking for string.h... yes
> checking for memory.h... yes
> checking for strings.h... yes
> checking for inttypes.h... yes
> checking for stdint.h... yes
> checking for unistd.h... yes
> checking dlfcn.h usability... yes
> checking dlfcn.h presence... yes
> checking for dlfcn.h... yes
> checking the maximum length of command line arguments... 32768
> checking command to parse /usr/local/arm/arm-gcc-3.4.4/gcc-
> 3.4.4-glibc-2.3.3/arm-linux-gnu/bin//arm-linux-gnu-nm -B output from
> arm-linux-gnu-gcc object... ok
> checking for objdir... .libs
> checking for arm-linux-gnu-ar... arm-linux-gnu-ar
> checking for arm-linux-gnu-ranlib... arm-linux-gnu-ranlib
> checking for arm-linux-gnu-strip... (cached) arm-linux-gnu-strip
> checking if arm-linux-gnu-gcc supports -fno-rtti -fno-exceptions... no
> checking for arm-linux-gnu-gcc option to produce PIC... -fPIC
> checking if arm-linux-gnu-gcc PIC flag -fPIC works... yes
> checking if arm-linux-gnu-gcc static flag -static works... yes
> checking if arm-linux-gnu-gcc supports -c -o file.o... yes
> checking whether the arm-linux-gnu-gcc linker (/usr/local/arm/arm-
> gcc-3.4.4/gcc-3.4.4-glibc-2.3.3/arm-linux-gnu/arm-linux-gnu/bin/ld)
> supports shared libraries... yes
> checking whether -lc should be explicitly linked in... no
> checking dynamic linker characteristics... GNU/Linux ld.so
> checking how to hardcode library paths into programs... immediate
> checking whether stripping libraries is possible... yes
> checking if libtool supports shared libraries... yes
> checking whether to build shared libraries... yes
> checking whether to build static libraries... no
> configure: creating libtool
> checking for ppoll... no
> checking for arm-linux-gnu-pkg-config... no
> checking for pkg-config... /usr/bin/pkg-config
> checking pkg-config is at least version 0.9.0... yes
> checking for BLUEZ... no
> configure: error: Bluetooth library is required
>
> *****************************************************************************
>
> Regards
>
> _______________________________________
> YM - ???u?T??
> ?N???A?S???W???A?A???B?ͤ??i?H?d?U?T?????A?A???A?W???ɴN???ߧY?ݨ??A???????ܳ??N?????C
> http://messenger.yahoo.com.hk
>
> -------------------------------------------------------------------------
> Take Surveys. Earn Cash. Influence the Future of IT
> Join SourceForge.net's Techsay panel and you'll get the chance to share
> your
> opinions on IT & business topics through brief surveys - and earn cash
> http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
>
> _______________________________________________
> Bluez-users mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/bluez-users
>
>
>