Hard float is fine, and the BBB's chip uses armv7. It all works out. Until I try and compile the examples, of course! I'm trying to find out what's wrong with the makefiles now, oc_logger and related libraries aren't compiling into their .a files.
-Eric On Tue, Jan 27, 2015 at 8:52 PM, Zhang, Caiwen <caiwen.zhang at intel.com> wrote: > You should use arm-linux-gnueabi-gcc, arm-linux-gnueabihf-gcc is for > armhf, it doesn?t support ?armv5te?. > > > > Regards, > > Caiwen > > *From:* Eric Feuvrier Danziger [mailto:ericdanziger at cmu.edu] > *Sent:* Wednesday, January 28, 2015 8:56 AM > *To:* Zhang, Caiwen > *Cc:* iotivity-dev at lists.iotivity.org > *Subject:* Re: [dev] Building Iotivity 0.90 on ARM > > > > I found an interesting problem in the SConscript file in > build_common/linux. It goes through a check on TARGET_ARCH, but with > options you can't actually set from the command line! It is looking for > v7a-hard, or v7a, but it doesn't like anything other than arm or arm64 on > the command line when you set TARGET_ARCH. I got it to compile on the > beaglebone black by changing the default (last else) to armv7-a from > armv5te. > > > > -Eric > > > > > > On Tue, Jan 27, 2015 at 11:28 AM, Eric Feuvrier Danziger < > ericdanziger at cmu.edu> wrote: > > I looked at config.log, and it gives this: > > > > gcc -o .sconf_temp/conftest_0.o -c -Os -march=armv5te -DNDEBUG > -Iextlibs/cereal/include .sconf_temp/conftest_0$ > > .sconf_temp/conftest_0.c:1:0: error: bad value (armv5te) for -march= switch > > > > the boost library I installed in /usr/local/lib I compiled with > arm-linux-gnueabihf-g++-4.8 > > > > I've tried this both on the BBB (running Arm Ubuntu) and on my laptop, > same results. > > > > Is there something in addition to scons TARGET_OS=linux TARGET_ARCH=arm > that I need to do? > > > > I'm still getting: > > > > Checking for C library boost_program_options... no > > Did not find boost_program_options, exiting! > > > > Thanks, > > Eric > > > > > > > > > > > > On Mon, Jan 26, 2015 at 10:00 PM, Zhang, Caiwen <caiwen.zhang at intel.com> > wrote: > > Seems you are doing cross compiling. ARM toolchain and libraries are > required. That?s to say, you should build with arm-gcc and the boost > library also should be > > For arm. > > > > In the top directory, you will find ?config.txt? which is generated by > scons. There you can find more useful information. > > > > Regards, > > Caiwen > > *From:* iotivity-dev-bounces at lists.iotivity.org [mailto: > iotivity-dev-bounces at lists.iotivity.org] *On Behalf Of *Eric Feuvrier > Danziger > *Sent:* Tuesday, January 27, 2015 7:56 AM > *To:* iotivity-dev at lists.iotivity.org > *Subject:* [dev] Building Iotivity 0.90 on ARM > > > > I am trying to compile Iotivity 0.90 using scons on a Beaglebone Black > with Ubuntu (target os is linux and target arch is arm). I can't seem to > get scons to find the boost_program_options. The libraries are all > installed and either in or soft linked to /usr/local/lib. It just checks > for boost_program_options in the third party scons file, then fails the > check and exits. Any ideas of why this is? I have also tried > appendUnique-ing lib_env before it gets passed to conf [in the line conf = > Configure(lib_env) ]. > > > > I have never used scons before, so please use small words! > > > > Thanks, > > Eric > > > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20150127/ba3986c1/attachment.html>
