== Progress ==
* Very short working week.
* Discussions about next steps in Lava integration.
* Followed up on Arndale/GCC build issues.
== Next week ==
* Review pending Backports
* Investigate bootstrap ICE PR56184 further
== Future ==
* Run HOT/COLD partitioning benchmarks
* Analyse
Hi Derek,
Derek Rollend writes:
>
>
> Add the Linaro toolchain bin directory to your PATH environment variable:
> export PATH="/opt/gcc-linaro-arm-linux-gnueabihf-4.7-2013.01-20130125_linux
>>/bin:$PATH"
ok. I thought there was a CMake variable like CMAKE_C_COMPILER_PATH. I use this
http://ww
I added the lib path explicitly so I knew that arm-linux-gnueabihf-g++ was
definitely linking against the correct hard float libraries. Perhaps this
is unnecessary, but I just wanted to be sure. I've been using OpenCV 2.2
because that was the version that was known to compile successfully from
th
I'd say that adding
-L/opt/gcc-linaro-arm-linux-gnueabihf-4.7-2013.01-20130125_linux/arm-linux-gnueabihf/lib
is unnecessary as gcc's driver should be able to find its own
libraries.
Regarding your problems with ffmpeg, I'm sorry that I don't know how
cmake works, but after spending some time tryin
Thanks, I install ia32-lib and now it works, but what a poor error message.
To bad i would at least tell you what file wasn't found.
-- Wink
On Sun, Feb 10, 2013 at 3:23 AM, Mans Rullgard wrote:
> On 10 February 2013 04:36, Wink Saville wrote:
> > I downloaded the aarch64 binaries to a ubuntu
