On 04/16/2015 12:09 PM, Joel (Xi Zhou) Zhou wrote:
> We have a "GLIBC_2.14" not found issue on RHEL6 when using
> gcc-linaro-4.9-2014.11-x86_64_arm-linux-gnueabihf. I may need to re-build
> toolchain on RHEL6. When I hit the rock, I know who I can refer to;)
The new binaries are built using LS
to:rob.sav...@linaro.org]
Sent: Thursday, April 16, 2015 1:07 PM
To: Joel (Xi Zhou) Zhou; Kevin Petit; linaro-toolchain@lists.linaro.org
Cc: Ian Spray; Mark Hambleton; James King
Subject: Re: Issue building busybox using aarch64-linux-gnu 2014.11
On 04/16/2015 09:35 AM, Joel (Xi Zhou) Zhou wrote:
> In p
On 04/16/2015 09:35 AM, Joel (Xi Zhou) Zhou wrote:
> In previous email, you mentioned that the crosstool-ng is no longer used.
> Could you share some information how do you build the toolchain now?
We stopped using crosstool-ng last Fall, and switched to our new ABE
tool. ABE is designed to pl
On Thu, Apr 16, 2015 at 8:35 AM, Joel (Xi Zhou) Zhou
wrote:
> In previous email, you mentioned that the crosstool-ng is no longer used.
> Could you share some information how do you build the toolchain now?
We wrote a tool called ABE that we use for building toolchains. You
can see some documen
Sent: Thursday, April 16, 2015 6:00 AM
To: Rob Savoye; linaro-toolchain@lists.linaro.org
Cc: Ian Spray; Mark Hambleton; James King
Subject: RE: Issue building busybox using aarch64-linux-gnu 2014.11
Hi Rob,
Thanks for the info and pointers. It's good to know what is distributed is now
what has
: 15 April 2015 22:56
To: Kevin Petit; linaro-toolchain@lists.linaro.org
Cc: Ian Spray; Mark Hambleton; James King
Subject: Re: Issue building busybox using aarch64-linux-gnu 2014.11
On 04/15/2015 10:51 AM, Kevin Petit wrote:
> I (and several other people) am (are) having trouble to build busybo
inaro.org; Ian Spray; Mark Hambleton; James King
Subject: Re: Issue building busybox using aarch64-linux-gnu 2014.11
On Wed, Apr 15, 2015 at 9:51 AM, Kevin Petit wrote:
> It seems none of the built-in library search paths (gcc –print-search-dirs)
> allow to find crt[1i].o. They seem to be
Kévin
-Original Message-
From: luther.ge [mailto:luther...@linaro.org]
Sent: 16 April 2015 06:28
To: Kevin Petit; linaro-toolchain@lists.linaro.org
Cc: Ian Spray; Mark Hambleton; James King
Subject: Re: Issue building busybox using aarch64-linux-gnu 2014.11
Hi Kevin
it works fine in my side
Sent: 16 April 2015 06:28
To: Kevin Petit; linaro-toolchain@lists.linaro.org
Cc: Ian Spray; Mark Hambleton; James King
Subject: Re: Issue building busybox using aarch64-linux-gnu 2014.11
Hi Kevin
it works fine in my side, the busybox & aarch64-linux-gnu version like
these:
1.
http://releases.l
Hi Kevin
it works fine in my side, the busybox & aarch64-linux-gnu version like
these:
1.
http://releases.linaro.org/14.11/components/toolchain/binaries/aarch64-linux-gnu/gcc-linaro-4.9-2014.11-x86_64_aarch64-linux-gnu.tar.xz
2. git clone git://git.busybox.net/busybox
3. git log -n 1
luther@gli
On 04/15/2015 10:51 AM, Kevin Petit wrote:
> I (and several other people) am (are) having trouble to build busybox with
> the latest aarch64-linux-gnu 2014.11 binaries we got from linaro.org.
Binary releases built prior to 2014.11 used crosstool-ng to build the
binaries, and that process appli
On Wed, Apr 15, 2015 at 9:51 AM, Kevin Petit wrote:
> It seems none of the built-in library search paths (gcc –print-search-dirs)
> allow to find crt[1i].o. They seem to be expected in a multiarch location
> but aren’t (libc/usr/lib64). We’re working around this with a symlink. Is
> this a bug? H
12 matches
Mail list logo
