On 24 February 2014 17:10, Peter Maydell wrote:
> On 24 February 2014 14:54, Rob Savoye wrote:
> > On 02/24/2014 07:15 AM, Wookey wrote:
> >> Where does a 'boards' file go/come from?
> > It's a DejaGnu config file, used for remote testing.
> >> Yes, or setting QEMU_UNAME on the command line, b
On 24 February 2014 16:06, Rob Savoye wrote:
> On 02/24/2014 08:51 AM, Peter Maydell wrote:
>> Well, do you have the aarch64 dynamic linker in
>> /lib/ld-linux-aarch64.so.1 ? If not, then we won't
>> find it (since you aren't running in a chroot and
>> you aren't using -L to specify a sysroot dire
On 02/24/2014 08:51 AM, Peter Maydell wrote:
> Well, do you have the aarch64 dynamic linker in
> /lib/ld-linux-aarch64.so.1 ? If not, then we won't
> find it (since you aren't running in a chroot and
> you aren't using -L to specify a sysroot directory
> to look in).
Yeah, I have as a symbolic li
On 24 February 2014 15:28, Rob Savoye wrote:
> On 02/24/2014 08:10 AM, Peter Maydell wrote:
>> If you're using qemu master you shouldn't need to set it to
>> anything. It's an emergency-use mechanism in case a future
>> newer glibc wants an even newer kernel, but it shouldn't
>> be necessary right
On 24/02/2014 17:28, Rob Savoye wrote:
On 02/24/2014 08:10 AM, Peter Maydell wrote:
If you're using qemu master you shouldn't need to set it to
anything. It's an emergency-use mechanism in case a future
newer glibc wants an even newer kernel, but it shouldn't
be necessary right now, because qem
On 02/24/2014 08:10 AM, Peter Maydell wrote:
> If you're using qemu master you shouldn't need to set it to
> anything. It's an emergency-use mechanism in case a future
> newer glibc wants an even newer kernel, but it shouldn't
> be necessary right now, because qemu will automatically
> force the re
On 24 February 2014 14:54, Rob Savoye wrote:
> On 02/24/2014 07:15 AM, Wookey wrote:
>> Where does a 'boards' file go/come from?
> It's a DejaGnu config file, used for remote testing.
>> Yes, or setting QEMU_UNAME on the command line, but I don't see how
>> those work well with the binfmt settin
+++ Rob Savoye [2014-02-24 07:54 -0700]:
> On 02/24/2014 07:15 AM, Wookey wrote:
> > Where does a 'boards' file go/come from?
> It's a DejaGnu config file, used for remote testing.
> > Yes, or setting QEMU_UNAME on the command line, but I don't see how
> > those work well with the binfmt settings
On 02/24/2014 07:15 AM, Wookey wrote:
> Where does a 'boards' file go/come from?
It's a DejaGnu config file, used for remote testing.
> Yes, or setting QEMU_UNAME on the command line, but I don't see how
> those work well with the binfmt settings that simply give a binary to
> run when the kernel
+++ Ramana Radhakrishnan [2014-02-24 09:08 +]:
> From: linaro-toolchain-boun...@lists.linaro.org [mailto:linaro-
> > toolchain-boun...@lists.linaro.org] On Behalf Of Wookey
> > Sent: 23 February 2014 20:43
> > To: Rob Savoye
> > Cc: Linaro ToolChain
> > Sub
> -Original Message-
> From: linaro-toolchain-boun...@lists.linaro.org [mailto:linaro-
> toolchain-boun...@lists.linaro.org] On Behalf Of Wookey
> Sent: 23 February 2014 20:43
> To: Rob Savoye
> Cc: Linaro ToolChain
> Subject: Re: [Weekly] 17-21 FEB 2013
>
> ++
On 02/23/2014 01:43 PM, Wookey wrote:
> There is an ubuntu qemu patch which reports later uname on aarch64
> (below). But it turns out that if you build qemu_without_ the
> configure option
Ah, thanks for the patch, it did the trick. Now aarch64-linux builds
via Jenkins are using it for executio
+++ Alex Bennée [2014-02-23 10:09 +]:
>
> Michael Collison writes:
>
> > == This week ==
>
> > - Installed Qemu64 simulator and attempted to test aarch64 backports.
> >- Shared library issue is preventing qemu64 from executing; Rob Savoy
> > is investigating
> Is this a problem with t
+++ Rob Savoye [2014-02-23 08:05 -0700]:
> On 02/23/2014 03:09 AM, Alex Bennée wrote:
> > Is this a problem with the emulated shared libraries not loading (qemu
> > itself should be static)? Wookey did find a problem when built on older
> > distros as the kernel version (CONFIG_UNAME) passed to the
On 02/23/2014 03:09 AM, Alex Bennée wrote:
> Is this a problem with the emulated shared libraries not loading (qemu
> itself should be static)? Wookey did find a problem when built on older
> distros as the kernel version (CONFIG_UNAME) passed to the emulated
> system cause libc to get confused as
Michael Collison writes:
> == This week ==
> - Installed Qemu64 simulator and attempted to test aarch64 backports.
>- Shared library issue is preventing qemu64 from executing; Rob Savoy
> is investigating
Is this a problem with the emulated shared libraries not loading (qemu
itself should
== This week ==
- US Holiday on Monday, January 17th
- Backported 202407 - Fix parameter to vrsqte_f64
- Backported 202259 (on read/write branch) - AARCH64, fix return types
for vaddvq_s64, vaaddvq_u64
- Backported 202321 - Fix vdup_lane_* instrinsics' lane parameter
- Backported 202322 - Fox
17 matches
Mail list logo
