Quantcast
Channel: Wireless Connectivity
Viewing all articles
Browse latest Browse all 116964

Forum Post: RE: OMAP-L138 + WL1271 is it possible?

$
0
0

Hi, Inderjit.

From expat/config.log, which is first package that is built I see the following:

"configure:6787: checking whether the arm-none-linux-gnueabi-gcc linker (arm-none-linux-gnueabi-ldd) supports shared libraries
configure:7745: result: no
configure:7812: checking dynamic linker characteristics
configure:8400: result: GNU/Linux ld.so
configure:8409: checking how to hardcode library paths into programs
configure:8434: result: unsupported
configure:8448: checking whether stripping libraries is possible
configure:8453: result: yes
configure:9287: checking if libtool supports shared libraries
configure:9289: result: no
configure:9292: checking whether to build shared libraries
configure:9313: result: no"

From some reason configure decides that shared libraries cannot be built and does not builds shared libraries neither for expat nor for other packages. All other packages fail from the same reason and in addition they cannot find shared objects of the libraries they depend on, dbus, for example, cannot find libexpat.so, since it has not been built because of false conclusion of the configure script inside expat package.

So, to figure out what is the reason of this problem I need you to perform a number of actions in debug mode:

  1. cd  <workspace-dir>expat-2.0.1
  2. source <path with build scripts>/setup-env
  3. env > log-file
  4. bash -x ./configure --host=arm-none-linux-gnueabi  --prefix=/usr --sysconfdir=/etc --localstatedir=/var >> log-file 2>&1

This will give me more information about runtime environment and configure decisions.

Best regards,

Vita.


Viewing all articles
Browse latest Browse all 116964

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>