On 03/24/2013 08:35 PM, Alan Ott wrote:
> On 03/24/2013 08:19 PM, K F wrote:
>> Hi Alan,
>>
>> Yes, I'm using the absolute path and using echo $STAGING I can confirm
>> that the environment variable is set properly (i.e. points to the
>> right directory).
>>
>> Also, the pkg-config files are OK as well.
>> They all start with:
>>
>> prefix=/home/shaman/Beagle_stuff/libnl-3.2.7/../out
>> exec_prefix=${prefix}
>> libdir=${exec_prefix}/lib
>> includedir=${prefix}/include
>>
>> [For this run, STAGING points inside the Beagle_stuff directory; its
>> not an error.]
>>
>> Still, strangely enough, the linux-zigbee Makefile points to:
>> /home/shaman/Beagle_stuff/libnl-3.2.7/../out/home/shaman/Beagle_stuff/libnl-3.2.7/../out/
>>
>> This equals $STAGING/$STAGING.
>> Perhaps $STAGINS is referenced in a way that gets it appended twice
>> to the target paths?
> Can you do some debugging into your ./configure script to find out where
> and why this happens? What version of automake/autoconf do you have?
Also, please verify that
PKG_CONFIG_DIR= \
PKG_CONFIG_LIBDIR=$STAGING/lib/pkgconfig:$STAGING/share/pkgconfig \
PKG_CONFIG_SYSROOT_DIR=$STAGING DESTDIR=$STAGING \
pkg-config libnl-genl-3.0 --cflags --libs
Gives the expected result.
------------------------------------------------------------------------------
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today:
http://p.sf.net/sfu/appdyn_d2d_mar
_______________________________________________
Linux-zigbee-devel mailing list
Linux-zigbee-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-zigbee-devel
