On 03/25/2013 02:50 PM, K F wrote: > I'm using bash shell as well. > > My automake is version 1.11.6. > Autoconf is 2.69.
Mine are very close to that 1.11.1 and 2.69. > > Using: > 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 > > I get: > -I > /home/shaman/Beagle_stuff/libnl-3.2.7/../out/home/shaman/Beagle_stuff/libnl-3.2.7/../out/include/libnl3 > > -L > /home/shaman/Beagle_stuff/libnl-3.2.7/../out/home/shaman/Beagle_stuff/libnl-3.2.7/../out/lib > -lnl-genl-3 -lnl-3 > > (i.e. $STAGING/$STAGING again) Then your pkg-config is borked. You said the .pc files were right, but they can't possibly be. Check them again ($STAGING/lib/pkgconfig/) They're generated by libnl, so build libnl until they are right. > I've already had a look through the config script but it's too > complicated for my (non-existent) scripting skillz! Too many > variables... Still, it was an eye-opener and will look into the script > a bit more because it's intriguing at the very least. > You already found the problem. It's the pkg-config (.pc) files. Alan. ------------------------------------------------------------------------------ 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
