Reg - Libnl compilation for powerpc

Senthil K Senthil.K at aricent.com
Wed Jan 4 09:20:50 EST 2012 

Hi Heiko,

Thanks for the immediate reply.

I have downloaded the libnl3.2.3 and compiled for x86 in CentOS5.0 version but that also throws an error.
Please help us to resolve the issue.

Please find the logs for your reference.
==========================
[root at localhost libnl-3.2.3]# sed -i "/^#include.*<stdlib.h>/a\#include <limits.h>" include/netlink-local.h && ./configure
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... /bin/mkdir -p
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
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 style of include used by make... GNU
checking dependency style of gcc... gcc3
checking whether gcc and cc understand -c and -o together... yes
checking build system type... i686-pc-linux-gnu
checking host system type... i686-pc-linux-gnu
checking how to print strings... printf
checking for a sed that does not truncate output... /bin/sed
checking for grep that handles long lines and -e... /bin/grep
checking for egrep... /bin/grep -E
checking for fgrep... /bin/grep -F
checking for ld used by gcc... /usr/bin/ld
checking if the linker (/usr/bin/ld) is GNU ld... yes
checking for BSD- or MS-compatible name lister (nm)... /usr/bin/nm -B
checking the name lister (/usr/bin/nm -B) interface... BSD nm
checking whether ln -s works... yes
checking the maximum length of command line arguments... 98304
checking whether the shell understands some XSI constructs... yes
checking whether the shell understands "+="... yes
checking how to convert i686-pc-linux-gnu file names to i686-pc-linux-gnu format... func_convert_file_noop
checking how to convert i686-pc-linux-gnu file names to toolchain format... func_convert_file_noop
checking for /usr/bin/ld option to reload object files... -r
checking for objdump... objdump
checking how to recognize dependent libraries... pass_all
checking for dlltool... no
checking how to associate runtime and link libraries... printf %s\n
checking for ar... ar
checking for archiver @FILE support... @
checking for strip... strip
checking for ranlib... ranlib
checking command to parse /usr/bin/nm -B output from gcc object... ok
checking for sysroot... no
checking for mt... mt
checking if mt is a manifest tool... no
checking how to run the C preprocessor... 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 for dlfcn.h... yes
checking for objdir... .libs
checking if gcc supports -fno-rtti -fno-exceptions... no
checking for gcc option to produce PIC... -fPIC -DPIC
checking if gcc PIC flag -fPIC -DPIC works... yes
checking if gcc static flag -static works... yes
checking if gcc supports -c -o file.o... yes
checking if gcc supports -c -o file.o... (cached) yes
checking whether the gcc linker (/usr/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... yes
checking for flex... flex
checking lex output file root... lex.yy
checking lex library... -lfl
checking whether yytext is a pointer... yes
checking for bison... bison -y
checking for an ANSI C-conforming const... yes
checking for inline... inline
checking for pow in -lm... yes
checking for pthread_mutex_lock in -lpthread... yes
configure: creating ./config.status
config.status: creating Makefile
config.status: creating libnl-3.0.pc
config.status: creating libnl-route-3.0.pc
config.status: creating libnl-genl-3.0.pc
config.status: creating libnl-nf-3.0.pc
config.status: creating libnl-cli-3.0.pc
config.status: creating doc/Doxyfile
config.status: creating doc/Makefile
config.status: creating lib/Makefile
config.status: creating include/Makefile
config.status: creating src/Makefile
config.status: creating src/lib/Makefile
config.status: creating man/Makefile
config.status: creating python/Makefile
config.status: creating python/setup.py
config.status: creating python/netlink/Makefile
config.status: creating python/netlink/route/Makefile
config.status: creating include/netlink/version.h
config.status: creating lib/defs.h
config.status: lib/defs.h is unchanged
config.status: executing depfiles commands
config.status: executing libtool commands
-------------------------------------------------------------------------------
                                  NOTE
 There have been some changes starting with 3.2 regarding where and how libnl
 is being installed on the system in order to allow multiple libnl versions
 to be installed in parallel:
    - Headers will be installed in ${prefix}/include/libnl3, therefore
      you will need to add "-I/usr/include/libnl3" to CFLAGS
    - The library basename was renamed to libnl-3, i.e. the SO names become
      libnl-3.so., libnl-route-3.so, etc.
    - libtool versioning was assumed, to ease detection of compatible library
      versions. libnl-3.so.CURRENT.REVISION.AGE where.
          CURRENT  := 100 * $MINOR_VERSION + $MICRO_VERSION
          REVISION := nth revision if API was unchanged
          AGE      := nth revision that is backwards compatible.
 If you are using pkg-config for detecting and linking against the library
 things will continue magically as if nothing every happened. If you are
 linking manually you need to adapt your Makefiles or switch to using
 pkg-config files.
-------------------------------------------------------------------------------
[root at localhost libnl-3.2.3]# make
Making all in include
make[1]: Entering directory `/home/senthil/wifi_open_src/libnl-3.2.3/include'
make[1]: Nothing to be done for `all'.
make[1]: Leaving directory `/home/senthil/wifi_open_src/libnl-3.2.3/include'
Making all in lib
make[1]: Entering directory `/home/senthil/wifi_open_src/libnl-3.2.3/lib'
  GEN    route/cls/ematch_grammar.c
flex: unknown flag '-'.  For usage, try
        flex --help
make[1]: *** [route/cls/ematch_grammar.c] Error 1
make[1]: Leaving directory `/home/senthil/wifi_open_src/libnl-3.2.3/lib'
make: *** [all-recursive] Error 1
[root at localhost libnl-3.2.3]#


Thanks and Regards
K.Senthil


________________________________________
From: Heiko Stübner [heiko at sntech.de]
Sent: Wednesday, January 04, 2012 7:37 PM
To: libnl at lists.infradead.org
Cc: Senthil K; Uday Kiran K
Subject: Re: Reg - Libnl compilation for powerpc

Hi,

Am Mittwoch, 4. Januar 2012, 14:30:21 schrieb Senthil K:
> Hi ,
>
> I was trying to compile the libnl for powerpc.I am facing the compilation
> errror. The Following are the compilation steps.
>
> 1.I used the libnl3.0 version and compiled in the host centOS-5.0.
> 2.sed -i "/^#include.*<stdlib.h>/a\#include <limits.h>"
> include/netlink-local.h && ./configure --host=powerpc
> CC=powerpc-linux-gnu-gcc [ I did n't face any issues during configuration
> ] 3.make

please try a current libnl3 first (i.e. 3.2.3).
The Debian version built just fine on all architectures Debian supports [1]
including powerpc.


Heiko


[1] https://buildd.debian.org/status/package.php?p=libnl3




===============================================================================
Please refer to http://www.aricent.com/legal/email_disclaimer.html
for important disclosures regarding this electronic communication.
===============================================================================

More information about the libnl mailing list