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?
When I skip the pkg-config, the make procedure get pasts the previous error
point but crashes later on with various "undefined references", e.g.:
izcoordinator-coordinator.o: In function `cleanup':
/home/shaman/Beagle_stuff/linux-zigbee/src/coordinator.c:239: undefined
reference to `nl_close'
izcoordinator-coordinator.o: In function `seq_check':
/home/shaman/Beagle_stuff/linux-zigbee/src/coordinator.c:215: undefined
reference to `nlmsg_get_src'
/home/shaman/Beagle_stuff/linux-zigbee/src/coordinator.c:218: undefined
reference to `nlmsg_hdr'
...
...
collect2: error: ld returned 1 exit status
make[2]: *** [izcoordinator] Error 1
make[2]: Leaving directory `/home/shaman/Beagle_stuff/linux-zigbee/src'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/home/shaman/Beagle_stuff/linux-zigbee'
make: *** [all] Error 2
As a comic relief, I should mention that, since it's getting late here
and I need to crash, I actually created the $STAGING/$STAGING directory
structure with the required contents and the make/make install worked fine.
So, at least I have a (hopefully) working copy of the tools. ;p
[Which I already had - thanks to Joao - but still did it for the fun of
it.. ;p]
Kostas F.
2013/3/25 Alan Ott <a...@signal11.us>
> On 03/24/2013 08:24 AM, K F wrote:
> > I just noticed that the Makefile produced, defines the following:
> >
> > NL_CFLAGS =
> >
> -I/home/shaman/Beagle_stuff/../out/home/shaman/Beagle_stuff/../out/include/libnl3
> >
> > NL_LIBS =
> > -L/home/shaman/Beagle_stuff/../out/home/shaman/Beagle_stuff/../out/lib
> > -lnl-genl-3 -lnl-3
>
> Clearly those paths are wrong...
>
> In the instructions here:
>
> https://sourceforge.net/apps/trac/linux-zigbee/wiki/BuildingUserspaceTools
>
> $STAGING must be an absolute path (so use $PWD if you want to use the
> current path, etc).
>
> See if your pkg-config files are right:
> $STAGING/lib/pkgconfig/
>
> If not, rebuild libnl until they are.
>
> run:
> make V=1
>
> and see if you can determine what's wrong from the output.
>
> Alternatively, skip pkg-config and do something like:
> NL_CFLAGS=-I$STAGING/include/libnl3 \
> NL_LIBS=-L$STAGING/lib \
> ./configure --prefix=/ --host=$HOST
>
> But seriously, get the pkg-config method to work.
>
> Alan.
>
> >
> > i.e. the absolute path to folder "out"
> > (/home/shaman/Beagle_stuff/.../out) is used twice.
> >
>
> No it's not.
>
>
> /home/shaman/Beagle_stuff/../out/home/shaman/Beagle_stuff/../out/include/libnl3
>
> is used, and that's not a real path. Something is messed up in your
> pkg-config file.
>
> 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
