Hi All,
Up until now, I have had no choice but to test toolchain correctness on
A8 hardware. It made sense to use the same -mfpu settings as the
Linaro/Ubuntu package builds use. This did not match the policy that the
interesting platform was A9-NEON, but I didn't have that option.
That's ch
Hi all,
I've had comments that getting hold of binaries for the linaro
toolchain can be trick for people unfamiliar with the linaro tools.
One reason is that we don't release binaries as such -- but a visitor
browsing in through http://www.linaro.org/downloads/ won't discover
this, and may waste
On Wed, 2 Mar 2011, Dave Martin wrote:
> On the other hand, the cross toolchain packages are likely to be of
> interest to such visitors, but aren't obviously advertised -- maybe
> I'm looking in the wrong place, but if so then new visitors to the
> linaro pages are likely to look in the wrong pla
On Wed, Mar 02, 2011, Nicolas Pitre wrote:
> Building a cross-compiler is already a challenge in itself. Would be
> better to build a version that can be installed anywhere like the
> CodeSourcery releases and offer that as a tar download.
This comes up frequently; I'm sure many people would b
On 02/03/11 17:52, Nicolas Pitre wrote:
Building a cross-compiler is already a challenge in itself. Would be
better to build a version that can be installed anywhere like the
CodeSourcery releases and offer that as a tar download.
Binaries that can be run anywhere are challenging. You either h
On 02.03.2011 19:02, Andrew Stubbs wrote:
> On 02/03/11 17:52, Nicolas Pitre wrote:
>> Building a cross-compiler is already a challenge in itself. Would be
>> better to build a version that can be installed anywhere like the
>> CodeSourcery releases and offer that as a tar download.
>
> Binaries
FWIW, Michael's recipe for building here
https://code.launchpad.net/~michaelh1/+junk/cross-build has worked
well for me.
On Wed, Mar 2, 2011 at 11:09 AM, Matthias Klose wrote:
> On 02.03.2011 19:02, Andrew Stubbs wrote:
>> On 02/03/11 17:52, Nicolas Pitre wrote:
>>> Building a cross-compiler is a
On 2 March 2011 18:44, John Rigby wrote:
> FWIW, Michael's recipe for building here
> https://code.launchpad.net/~michaelh1/+junk/cross-build has worked
> well for me.
It's OK for people familiar with toolchains; the problem is where you
have a subject specialist
who knows how to write C or ARM a
I agree with Nicolas' proposal to deliver a cross-compiler. A lot of people
request this
Yves
-Original Message-
From: linaro-toolchain-boun...@lists.linaro.org
[mailto:linaro-toolchain-boun...@lists.linaro.org] On Behalf Of Nicolas Pitre
Sent: Wednesday, March 02, 2011 11:52 AM
To: Dav
On Thu, Mar 3, 2011 at 4:23 AM, Andrew Stubbs wrote:
> Hi All,
>
> Up until now, I have had no choice but to test toolchain correctness on A8
> hardware. It made sense to use the same -mfpu settings as the Linaro/Ubuntu
> package builds use. This did not match the policy that the interesting
> pla
(top posting as summarising)
It's funny how things happen at the same time. I've been asked a few
times about how to compile Linaro GCC so I started this page a few
days ago:
https://wiki.linaro.org/WorkingGroups/ToolChain/Using
The goal is to describe how to build the toolchain outputs such as
On Wed, 2 Mar 2011, Andrew Stubbs wrote:
> On 02/03/11 17:52, Nicolas Pitre wrote:
> > Building a cross-compiler is already a challenge in itself. Would be
> > better to build a version that can be installed anywhere like the
> > CodeSourcery releases and offer that as a tar download.
>
> Binari
12 matches
Mail list logo
