Re: First proposals

2012-01-11 Thread Asa Sandahl
Hi Michael!

Nice! I have some permission issue though. See below.

What happens when you press "Record"?

/Åsa

On 11 January 2012 03:07, Michael Hope  wrote:
>
>> Hi Åsa.  Well, the first proposals have arrived.  I've cc'ed this to
>> linaro-toolchain so we have a record.
>>
>> First, visit:
>>  http://ex.seabright.co.nz/helpers/proposals
>>
>> and see there are new merge requests from Ulrich with new results.
>>
>> Next, login:
>>  http://ex.seabright.co.nz/helpers/login
>>
>

> Your login is your Launchpad OpenID login "
> https://launchpad.net/~asa-sandahl";
>


Looks like I am logged in correctly. I also tried logging out and back in
again...

After logging in, go back to the proposals page.
>>
>> See that the fwprop-subreg merge request has a i686 and x86_64 result.
>>  The i686 one is fine so click 'Record' and follow your nose.
>
>

When I click "Record" I get this URL:
http://ex.seabright.co.nz/helpers/proposals/helpers/login?msg=Permission%20denied
The resulting page just shows a "not found" text.


 The
>> x86_64 is interesting - the fault might be real.  Click 'Record'.
>> Note the subject line has 'regressed' in it.  Ulrich will have to
>> investigate.
>>
>
So, should I notify developers of regressions, or does everyone look after
there merge requests?

The lp-879725 results look fine so record both of those.  Scanning
>> down the page shows that everything else is recorded so you're done!
>>
>> The tool is a bit slow so don't be surprised if an operation takes ~10
>> s.  The tool is backed by a cache so you won't see the results for ~2
>> hours.
>>
>> -- Michael
>>
>
___
linaro-toolchain mailing list
linaro-toolchain@lists.linaro.org
http://lists.linaro.org/mailman/listinfo/linaro-toolchain


Re: First proposals

2012-01-11 Thread Michael Hope
On Wed, Jan 11, 2012 at 9:21 PM, Asa Sandahl  wrote:
> Hi Michael!
>
> Nice! I have some permission issue though. See below.

Give it a go now.

> What happens when you press "Record"?

You'll see soon enough :)  Note the developer will get an email when
you record the result.  Don't record the result if it seems to be an
auto builder error.

-- Michael

___
linaro-toolchain mailing list
linaro-toolchain@lists.linaro.org
http://lists.linaro.org/mailman/listinfo/linaro-toolchain


Re: First proposals

2012-01-11 Thread Asa Sandahl
On 11 January 2012 09:39, Michael Hope  wrote:

> On Wed, Jan 11, 2012 at 9:21 PM, Asa Sandahl 
> wrote:
> > Hi Michael!
> >
> > Nice! I have some permission issue though. See below.
>
> Give it a go now.
>

Works now!

> What happens when you press "Record"?
>
> You'll see soon enough :)

:-)

> Note the developer will get an email when
> you record the result.  Don't record the result if it seems to be an
> auto builder error.
>
> -- Michael
>
___
linaro-toolchain mailing list
linaro-toolchain@lists.linaro.org
http://lists.linaro.org/mailman/listinfo/linaro-toolchain


[PATCH 1/1] hw: Add IGEPv2 board support

2012-01-11 Thread Javier Martinez Canillas
Add ISEE IGEPv2 board definition (an OMAP3730 based board).

Signed-off-by: Javier Martinez Canillas 
---
 Makefile.target |2 +-
 hw/igep.c   |  123 +++
 2 files changed, 124 insertions(+), 1 deletions(-)
 create mode 100644 hw/igep.c

diff --git a/Makefile.target b/Makefile.target
index 409748f..2923dd7 100644
--- a/Makefile.target
+++ b/Makefile.target
@@ -349,7 +349,7 @@ obj-arm-y += omap1.o omap_lcdc.o omap_dma.o omap_clk.o 
omap_mmc.o omap_i2c.o \
 obj-arm-y += omap2.o omap_dss.o soc_dma.o omap_gptimer.o omap_synctimer.o \
omap_gpmc.o omap_sdrc.o omap_spi.o omap_tap.o omap_l4.o
 obj-arm-y += omap3.o omap_usb.o omap3_boot.o omap3_mmc.o dsi.o
-obj-arm-y += twl4030.o beagle.o overo.o
+obj-arm-y += twl4030.o beagle.o overo.o igep.o
 obj-arm-y += omap_sx1.o palm.o tsc210x.o
 obj-arm-y += nseries.o blizzard.o onenand.o vga.o cbus.o tusb6010.o usb-musb.o
 obj-arm-y += mst_fpga.o mainstone.o
diff --git a/hw/igep.c b/hw/igep.c
new file mode 100644
index 000..5254ddf
--- /dev/null
+++ b/hw/igep.c
@@ -0,0 +1,123 @@
+/*
+ * ISEE IGEPv2 board emulation.
+ *
+ * Copyright (c) 2012 ISEE 2007, SL
+ * Written by Javier Martinez Canillas (based on Gumstix Overo emulation code)
+ *
+ *  This program is free software; you can redistribute it and/or modify
+ *  it under the terms of the GNU General Public License version 2 as
+ *  published by the Free Software Foundation.
+ *
+ *  This program is distributed in the hope that it will be useful,
+ *  but WITHOUT ANY WARRANTY; without even the implied warranty of
+ *  MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
+ *  GNU General Public License for more details.
+ *
+ *  You should have received a copy of the GNU General Public License along
+ *  with this program; if not, see .
+ */
+
+#include "qemu-common.h"
+#include "sysemu.h"
+#include "omap.h"
+#include "arm-misc.h"
+#include "boards.h"
+#include "i2c.h"
+#include "net.h"
+#include "devices.h"
+#include "flash.h"
+#include "sysbus.h"
+#include "blockdev.h"
+#include "exec-memory.h"
+
+#define IGEP_NAND_CS   0
+#define IGEP_NET_CS5
+
+struct igep_s {
+struct omap_mpu_state_s *cpu;
+
+DeviceState *nand;
+void *twl4030;
+DeviceState *eth;
+DeviceState *ddc;
+};
+
+static void igep_init(ram_addr_t ram_size,
+   const char *boot_device,
+   const char *kernel_filename,
+   const char *kernel_cmdline,
+   const char *initrd_filename,
+   const char *cpu_model)
+{
+MemoryRegion *sysmem = get_system_memory();
+struct igep_s *s = (struct igep_s *) g_malloc0(sizeof(*s));
+DriveInfo *dmtd = drive_get(IF_MTD, 0, 0);
+DriveInfo *dsd  = drive_get(IF_SD, 0, 0);
+
+if (ram_size > 1024 * 1024 * 1024) {
+fprintf(stderr, "igep: maximum permitted RAM size 1024MB\n");
+exit(1);
+}
+
+if (!dmtd && !dsd) {
+hw_error("%s: SD or NAND image required", __func__);
+}
+s->cpu = omap3_mpu_init(sysmem, omap3630, ram_size,
+NULL, NULL, serial_hds[0], NULL);
+
+s->nand = qdev_create(NULL, "onenand");
+qdev_prop_set_uint16(s->nand, "manufacturer_id", NAND_MFR_STMICRO);
+qdev_prop_set_uint16(s->nand, "device_id", 0x40);
+qdev_prop_set_uint16(s->nand, "version_id", 0x121);
+qdev_prop_set_int32(s->nand, "shift", 1);
+if (dmtd && dmtd->bdrv) {
+qdev_prop_set_drive_nofail(s->nand, "drive", dmtd->bdrv);
+}
+qdev_init_nofail(s->nand);
+omap_gpmc_attach(s->cpu->gpmc, IGEP_NAND_CS,
+  sysbus_mmio_get_region(sysbus_from_qdev(s->nand), 0));
+
+if (dsd) {
+omap3_mmc_attach(s->cpu->omap3_mmc[0], dsd->bdrv, 0, 0);
+}
+
+/* FAB revs >= 2516: 4030 interrupt is GPIO 0 (earlier ones were 112) */
+s->twl4030 = twl4030_init(omap_i2c_bus(s->cpu->i2c, 0),
+  qdev_get_gpio_in(s->cpu->gpio, 0),
+  NULL, NULL);
+
+/* Wire up an I2C slave which returns EDID monitor information;
+ * newer Linux kernels won't turn on the display unless they
+ * detect a monitor over DDC.
+ */
+s->ddc = i2c_create_slave(omap_i2c_bus(s->cpu->i2c, 2), "i2c-ddc", 0x50);
+
+omap_lcd_panel_attach(s->cpu->dss);
+
+/* Strictly this should be a LAN9221 */
+if (nd_table[0].vlan) {
+/* The ethernet chip hangs off the GPMC */
+NICInfo *nd = &nd_table[0];
+qemu_check_nic_model(nd, "lan9118");
+s->eth = qdev_create(NULL, "lan9118");
+qdev_set_nic_properties(s->eth, nd);
+qdev_init_nofail(s->eth);
+omap_gpmc_attach(s->cpu->gpmc, IGEP_NET_CS,
+ sysbus_mmio_get_region(sysbus_from_qdev(s->eth), 0));
+sysbus_connect_irq(sysbus_from_qdev(s->eth), 0,
+   qdev_get_gpio_in(s->cpu->gpio, 176));
+}
+}
+
+QEMU

RE: uImage built with pre-built linaro toolchain failed to start

2012-01-11 Thread Lv Terry-R65388
Hi Michael,

By adding -mno-unaligned-access, kernel can start now.

I've another question, Does this option have some impact on performance?

Thanks~~

Yours
Terry

-Original Message-
From: Michael Hope [mailto:michael.h...@linaro.org] 
Sent: 2012年1月11日 9:16
To: Lv Terry-R65388
Cc: linaro-toolchain@lists.linaro.org
Subject: Re: uImage built with pre-built linaro toolchain failed to start

On Tue, Jan 10, 2012 at 11:58 PM, Lv Terry-R65388  wrote:
> Hi,
>
>        I use pre-built version of linaro toolchain (got from 
> http://people.linaro.org/~michaelh/incoming/binaries/) to build a uImage.
>        The build succeeded, but the uImage couldn't start.
>        The console hangs at:
>
> Using FEC0 device
> TFTP from server 10.193.100.158; our IP address is 10.193.102.233 
> Filename 'uImage_linaro'.
> Load address: 0x7080
> Loading: 
> #
>         
> #
>         
> #
>         ###
> done
> Bytes transferred = 3193292 (30b9cc hex) ## Booting kernel from Legacy 
> Image at 7080 ...
>   Image Name:   Linux-2.6.38-01026-gc9c8ead
>   Image Type:   ARM Linux Kernel Image (uncompressed)
>   Data Size:    3193228 Bytes =  3 MB
>   Load Address: 10008000
>   Entry Point:  10008000
>   Verifying Checksum ... OK
>   Loading Kernel Image ... OK
> OK
>
> Starting kernel ...
>
> Uncompressing Linux... done, booting the kernel.
>
>        Does anyone meet this before?
>
>        How can I fix it?
>
>        Thanks~~

Hi Terry.  Andy's covered the most likely causes.  One thing to watch for is 
that Linaro GCC 2011.11 added unaligned access support for armv6k and later.  
This is fine for userspace but the kernel runs with the hardware unaligned 
access fault turned and this might cause the crash.

Try adding -mno-unaligned-access to your CFLAGS and see if that helps.  See:
 http://lists.linaro.org/pipermail/linaro-android/2011-December/30.html

and:
 http://comments.gmane.org/gmane.linux.ports.arm.kernel/138900

for more.

-- Michael

___
linaro-toolchain mailing list
linaro-toolchain@lists.linaro.org
http://lists.linaro.org/mailman/listinfo/linaro-toolchain


RE: Running pre-built linaro toolchain failed on Ubuntu 11.04, 64bit server

2012-01-11 Thread Lv Terry-R65388
Hi Michael,

I changed the symbol link of /lib/ld-linux.so.2.

sudo ln -s -f /lib32/ld-linux.so.2 /lib/ld-linux.so.2

But it seems the problem is still not resolved.

r65388@shlinux3:~/toolchain_ltib/gcc-linaro-4.6.3-glibc-2.13-singlelib-2011.12/arm-fsl-linux-gnueabi/bin$
 ls -la /lib/ld*
lrwxrwxrwx 1 root root 20 2012-01-11 15:42 /lib/ld-linux.so.2 -> 
/lib32/ld-linux.so.2
r65388@shlinux3:~/toolchain_ltib/gcc-linaro-4.6.3-glibc-2.13-singlelib-2011.12/arm-fsl-linux-gnueabi/bin$
 ./arm-linux-gnueabi-gcc
-bash: ./arm-linux-gnueabi-gcc: No such file or directory

I'll check the server again.
If you have suggestions, pls let me know.

Thanks a lot for your help.

Yours
Terry

-Original Message-
From: Michael Hope [mailto:michael.h...@linaro.org] 
Sent: 2012年1月11日 15:37
To: Lv Terry-R65388
Cc: linaro-toolchain@lists.linaro.org
Subject: Re: Running pre-built linaro toolchain failed on Ubuntu 11.04, 64bit 
server

On Wed, Jan 11, 2012 at 8:23 PM, Lv Terry-R65388  wrote:
> Hi Michael,
>
>        dpkg -S ld-2.13 outputs is:
>
> r65388@shlinux3:~/toolchain_ltib/gcc-linaro-4.6.3-glibc-2.13-singlelib
> -2011.12/arm-fsl-linux-gnueabi/bin$ dpkg -S ld-2.13
> libc6: /lib/x86_64-linux-gnu/ld-2.13.so
> libc6-dbg: /usr/lib/debug/lib32/ld-2.13.so
> libc6-dbg: /usr/lib/debug/lib/x86_64-linux-gnu/ld-2.13.so
> libc6-i386: /lib32/ld-2.13.so
> libc6:i386: /lib/i386-linux-gnu/ld-2.13.so
>
>        ia32-libs-multiarch is a recommended package founded when install 
> ia32-libs.
>
>        Some comments from google:
>        " Multi-arch versions of former ia32-libraries This package 
> depends on i386 versions of packages that were removed from ia32-libs 
> and transitioned to multi-arch. This allows applications using 
> ia32-libs in previous Ubuntu releases to continue functioning without 
> missing libraries. "
>
>        I think ia32-libs-multiarch is similar to ia32-libs, but may have 
> better compatibility.

You mentioned 11.04 earlier which is Ubuntu Natty.  According to 
packages.ubuntu.com, ia32-libs-multiarch first appeared in the next release, 
Oneiric.

Where did ia32-libs-multiarch come from?

FYI, here's what I see on Natty:

cbuild@crucis-natty:/etc/ld.so.conf.d$ apt-cache search multiarch libpango1.0-0 
- Layout and rendering of internationalized text multiarch-support - 
Transitional package to ensure multiarch compatibility apt-cross - retrieve, 
build and install libraries for cross-compiling gdb-multiarch - The GNU 
Debugger (with support for multiple architectures) binutils-multiarch - Binary 
utilities that support multi-arch targets

cbuild@crucis-natty:/etc/ld.so.conf.d$ lsb_release -a
LSB Version:
Distributor ID: Ubuntu
Description:Ubuntu 11.04
Release:11.04
Codename:   natty

-- Michael

___
linaro-toolchain mailing list
linaro-toolchain@lists.linaro.org
http://lists.linaro.org/mailman/listinfo/linaro-toolchain


Re: [Qemu-devel] [PATCH 1/1] hw: Add IGEPv2 board support

2012-01-11 Thread Peter Maydell
On 11 January 2012 08:43, Javier Martinez Canillas  wrote:
> Add ISEE IGEPv2 board definition (an OMAP3730 based board).
>
> Signed-off-by: Javier Martinez Canillas 

It's polite to mention that patches are against qemu-linaro if you cc
qemu-devel.

So my initial reaction to this is to ask what the benefit is of adding another
basically-just-an-OMAP3 model. We already have beagle and overo,
and this is obviously just cut-n-paste from overo (it still has the comment
about "FAB revisions" which is specific to Overo, which doesn't give me a
great deal of confidence that this is actually correctly modelling the IGEPv2
rather than just something random which happens to be able to boot an
IGEPv2 kernel...)

GPLv2-only rather than v2-or-later is also going to be a problem, although
I appreciate that that's because you've based this on the v2-only overo.c
[which is going to be a problem for me later on when I try to upstream that :-)]

-- PMM

___
linaro-toolchain mailing list
linaro-toolchain@lists.linaro.org
http://lists.linaro.org/mailman/listinfo/linaro-toolchain


Re: [Qemu-devel] [PATCH 1/1] hw: Add IGEPv2 board support

2012-01-11 Thread Javier Martinez Canillas
On Wed, Jan 11, 2012 at 12:15 PM, Peter Maydell
 wrote:
> On 11 January 2012 08:43, Javier Martinez Canillas  
> wrote:
>> Add ISEE IGEPv2 board definition (an OMAP3730 based board).
>>
>> Signed-off-by: Javier Martinez Canillas 
>

Hello Peter,

> It's polite to mention that patches are against qemu-linaro if you cc
> qemu-devel.
>

Yes, you are right. Sorry for not mention that in the patch.

> So my initial reaction to this is to ask what the benefit is of adding another
> basically-just-an-OMAP3 model. We already have beagle and overo,
> and this is obviously just cut-n-paste from overo (it still has the comment
> about "FAB revisions" which is specific to Overo, which doesn't give me a
> great deal of confidence that this is actually correctly modelling the IGEPv2
> rather than just something random which happens to be able to boot an
> IGEPv2 kernel...)
>

Yes, the IGEPv2 and the Overo are indeed very similar machines so we
base the hardware modeling on the Overo.

The only differences here are which OMAP version is used to initialize
the MPU (3630 instead of 3430) and the NAND memory used, Numonyx
OneNAND instead of Micron NAND.

What is the benefit to have yet another OMAP3 device? Well.. I don't know ;-)

We just add this device model for our clients so I thought it was a
good idea to post the patch upstream. But feel free to ignore me if
you think that it doesn't add any value to Linaro QEMU.

> GPLv2-only rather than v2-or-later is also going to be a problem, although
> I appreciate that that's because you've based this on the v2-only overo.c
> [which is going to be a problem for me later on when I try to upstream that 
> :-)]
>
> -- PMM
>

Sorry about that, I didn't know that GPLv2 or later was the norm in
the QEMU project.

Also, is good to notice that the Versatile Express board
(hw/vexpress.c) and the StrongARM emulation support (hw/strongarm.c)
also use GPLv2-only license. If you need to fix those too.

Thanks a lot and best regards,
Javier

___
linaro-toolchain mailing list
linaro-toolchain@lists.linaro.org
http://lists.linaro.org/mailman/listinfo/linaro-toolchain


Re: [Qemu-devel] [PATCH 1/1] hw: Add IGEPv2 board support

2012-01-11 Thread Peter Maydell
On 11 January 2012 11:53, Javier Martinez Canillas  wrote:
> Yes, the IGEPv2 and the Overo are indeed very similar machines so we
> base the hardware modeling on the Overo.
>
> The only differences here are which OMAP version is used to initialize
> the MPU (3630 instead of 3430) and the NAND memory used, Numonyx
> OneNAND instead of Micron NAND.

That's pretty minor -- can you just use the overo model as is?
I bet nothing at the software level cares that much about the
OMAP version or NAND manufacturer...

> We just add this device model for our clients so I thought it was a
> good idea to post the patch upstream. But feel free to ignore me if
> you think that it doesn't add any value to Linaro QEMU.

I appreciate the patch. My pushback is really that every new board
we accept carries an implicit future cost for testing/maintenance/etc,
so there needs to be a reasonable set of users who would use this
and not the overo or beagle.

> Sorry about that, I didn't know that GPLv2 or later was the norm in
> the QEMU project.

We've just changed recently to asking people to include the "or later"
clause for new code (this is why, as you note, there are some existing
bits of code which are v2-only).

-- PMM

___
linaro-toolchain mailing list
linaro-toolchain@lists.linaro.org
http://lists.linaro.org/mailman/listinfo/linaro-toolchain


Re: [Qemu-devel] [PATCH 1/1] hw: Add IGEPv2 board support

2012-01-11 Thread Javier Martinez Canillas
On Wed, Jan 11, 2012 at 1:20 PM, Peter Maydell  wrote:
> On 11 January 2012 11:53, Javier Martinez Canillas  
> wrote:
>> Yes, the IGEPv2 and the Overo are indeed very similar machines so we
>> base the hardware modeling on the Overo.
>>
>> The only differences here are which OMAP version is used to initialize
>> the MPU (3630 instead of 3430) and the NAND memory used, Numonyx
>> OneNAND instead of Micron NAND.
>
> That's pretty minor -- can you just use the overo model as is?
> I bet nothing at the software level cares that much about the
> OMAP version or NAND manufacturer...
>

Yes, I guess we can use the Overo as is.

>> We just add this device model for our clients so I thought it was a
>> good idea to post the patch upstream. But feel free to ignore me if
>> you think that it doesn't add any value to Linaro QEMU.
>
> I appreciate the patch. My pushback is really that every new board
> we accept carries an implicit future cost for testing/maintenance/etc,
> so there needs to be a reasonable set of users who would use this
> and not the overo or beagle.
>

Yes, I totally understand. Then just feel free to just ignore the
patch, sorry for the noise.

>> Sorry about that, I didn't know that GPLv2 or later was the norm in
>> the QEMU project.
>
> We've just changed recently to asking people to include the "or later"
> clause for new code (this is why, as you note, there are some existing
> bits of code which are v2-only).
>
> -- PMM

Best regards,
Javier

___
linaro-toolchain mailing list
linaro-toolchain@lists.linaro.org
http://lists.linaro.org/mailman/listinfo/linaro-toolchain


Re: Running pre-built linaro toolchain failed on Ubuntu 11.04, 64bit server

2012-01-11 Thread Michael Hope
On Wed, Jan 11, 2012 at 11:56 PM, Lv Terry-R65388  wrote:
> Hi Michael,
>
>        I changed the symbol link of /lib/ld-linux.so.2.
>
>        sudo ln -s -f /lib32/ld-linux.so.2 /lib/ld-linux.so.2
>
>        But it seems the problem is still not resolved.
>
> r65388@shlinux3:~/toolchain_ltib/gcc-linaro-4.6.3-glibc-2.13-singlelib-2011.12/arm-fsl-linux-gnueabi/bin$
>  ls -la /lib/ld*
> lrwxrwxrwx 1 root root 20 2012-01-11 15:42 /lib/ld-linux.so.2 -> 
> /lib32/ld-linux.so.2
> r65388@shlinux3:~/toolchain_ltib/gcc-linaro-4.6.3-glibc-2.13-singlelib-2011.12/arm-fsl-linux-gnueabi/bin$
>  ./arm-linux-gnueabi-gcc
> -bash: ./arm-linux-gnueabi-gcc: No such file or directory
>
>        I'll check the server again.

Hi Terry.  I couldn't reproduce the problem on a fresh install of
Ubuntu 11.10 x86_64 Server.

I started with a clean install and saw similar to your problem:

cbuild@crucis-oneiric:~$
./gcc-linaro-arm-linux-gnueabi-2011.12-20111219+bzr2309~linux/bin/arm-linux-gnueabi-gcc
-bash: 
./gcc-linaro-arm-linux-gnueabi-2011.12-20111219+bzr2309~linux/bin/arm-linux-gnueabi-gcc:
No such file or directory

I then installed lsb using `sudo apt-get install lsb`.  This changed
the error to one about missing the 32 bit libstdc++:

cbuild@crucis-oneiric:~$
./gcc-linaro-arm-linux-gnueabi-2011.12-20111219+bzr2309~linux/bin/arm-linux-gnueabi-gcc
./gcc-linaro-arm-linux-gnueabi-2011.12-20111219+bzr2309~linux/bin/arm-linux-gnueabi-gcc:
error while loading shared libraries: libstdc++.so.6: cannot open
shared object file: No such file or directory

I then installed the 32 bit libraries using `sudo apt-get install
ia32-libs`. The binary then works:

cbuild@crucis-oneiric:~$
./gcc-linaro-arm-linux-gnueabi-2011.12-20111219+bzr2309~linux/bin/arm-linux-gnueabi-gcc
arm-linux-gnueabi-gcc: fatal error: no input files

For reference, here's the linkers afterwards:

cbuild@crucis-oneiric:~$ ls -la /lib/ld*
lrwxrwxrwx 1 root root 25 2011-10-05 11:07 /lib/ld-linux.so.2 ->
i386-linux-gnu/ld-2.13.so
lrwxrwxrwx 1 root root 13 2012-01-12 12:15 /lib/ld-lsb.so.1 -> ld-linux.so.2
lrwxrwxrwx 1 root root 13 2012-01-12 12:15 /lib/ld-lsb.so.2 -> ld-linux.so.2
lrwxrwxrwx 1 root root 13 2012-01-12 12:15 /lib/ld-lsb.so.3 -> ld-linux.so.2

cbuild@crucis-oneiric:~$ ls -la /lib/i386-linux-gnu/ld*
-rwxr-xr-x 1 root root 126152 2011-10-05 11:07 /lib/i386-linux-gnu/ld-2.13.so
lrwxrwxrwx 1 root root 10 2011-10-05 11:07
/lib/i386-linux-gnu/ld-linux.so.2 -> ld-2.13.so

>From our tests yesterday you have the linker and all of the libraries
needed to run the problem.  The error message from bash is probably
due to a broken symlink.  I recommend you look into that futher.  Good
luck and let me know if I can help!

-- Michael

___
linaro-toolchain mailing list
linaro-toolchain@lists.linaro.org
http://lists.linaro.org/mailman/listinfo/linaro-toolchain


Re: Running pre-built linaro toolchain failed on Ubuntu 11.04, 64bit server

2012-01-11 Thread Javier Martinez Canillas
On Thu, Jan 12, 2012 at 12:28 AM, Michael Hope  wrote:
> On Wed, Jan 11, 2012 at 11:56 PM, Lv Terry-R65388  
> wrote:
>> Hi Michael,
>>
>>        I changed the symbol link of /lib/ld-linux.so.2.
>>
>>        sudo ln -s -f /lib32/ld-linux.so.2 /lib/ld-linux.so.2
>>
>>        But it seems the problem is still not resolved.
>>
>> r65388@shlinux3:~/toolchain_ltib/gcc-linaro-4.6.3-glibc-2.13-singlelib-2011.12/arm-fsl-linux-gnueabi/bin$
>>  ls -la /lib/ld*
>> lrwxrwxrwx 1 root root 20 2012-01-11 15:42 /lib/ld-linux.so.2 -> 
>> /lib32/ld-linux.so.2
>> r65388@shlinux3:~/toolchain_ltib/gcc-linaro-4.6.3-glibc-2.13-singlelib-2011.12/arm-fsl-linux-gnueabi/bin$
>>  ./arm-linux-gnueabi-gcc
>> -bash: ./arm-linux-gnueabi-gcc: No such file or directory
>>
>>        I'll check the server again.
>
> Hi Terry.  I couldn't reproduce the problem on a fresh install of
> Ubuntu 11.10 x86_64 Server.
>
> I started with a clean install and saw similar to your problem:
>
> cbuild@crucis-oneiric:~$
> ./gcc-linaro-arm-linux-gnueabi-2011.12-20111219+bzr2309~linux/bin/arm-linux-gnueabi-gcc
> -bash: 
> ./gcc-linaro-arm-linux-gnueabi-2011.12-20111219+bzr2309~linux/bin/arm-linux-gnueabi-gcc:
> No such file or directory
>
> I then installed lsb using `sudo apt-get install lsb`.  This changed
> the error to one about missing the 32 bit libstdc++:
>
> cbuild@crucis-oneiric:~$
> ./gcc-linaro-arm-linux-gnueabi-2011.12-20111219+bzr2309~linux/bin/arm-linux-gnueabi-gcc
> ./gcc-linaro-arm-linux-gnueabi-2011.12-20111219+bzr2309~linux/bin/arm-linux-gnueabi-gcc:
> error while loading shared libraries: libstdc++.so.6: cannot open
> shared object file: No such file or directory
>
> I then installed the 32 bit libraries using `sudo apt-get install
> ia32-libs`. The binary then works:
>
> cbuild@crucis-oneiric:~$
> ./gcc-linaro-arm-linux-gnueabi-2011.12-20111219+bzr2309~linux/bin/arm-linux-gnueabi-gcc
> arm-linux-gnueabi-gcc: fatal error: no input files
>
> For reference, here's the linkers afterwards:
>
> cbuild@crucis-oneiric:~$ ls -la /lib/ld*
> lrwxrwxrwx 1 root root 25 2011-10-05 11:07 /lib/ld-linux.so.2 ->
> i386-linux-gnu/ld-2.13.so
> lrwxrwxrwx 1 root root 13 2012-01-12 12:15 /lib/ld-lsb.so.1 -> ld-linux.so.2
> lrwxrwxrwx 1 root root 13 2012-01-12 12:15 /lib/ld-lsb.so.2 -> ld-linux.so.2
> lrwxrwxrwx 1 root root 13 2012-01-12 12:15 /lib/ld-lsb.so.3 -> ld-linux.so.2
>
> cbuild@crucis-oneiric:~$ ls -la /lib/i386-linux-gnu/ld*
> -rwxr-xr-x 1 root root 126152 2011-10-05 11:07 /lib/i386-linux-gnu/ld-2.13.so
> lrwxrwxrwx 1 root root     10 2011-10-05 11:07
> /lib/i386-linux-gnu/ld-linux.so.2 -> ld-2.13.so
>
> From our tests yesterday you have the linker and all of the libraries
> needed to run the problem.  The error message from bash is probably
> due to a broken symlink.  I recommend you look into that futher.  Good
> luck and let me know if I can help!
>

Hello,

Not sure if is a useful information but I had a similar error message
on a Fedora16 x86_64 box. But now after installing the Linux Standard
Base (LSB) and LSB 32 compatibility packages is working well.

$ yum install redhat-lsb
$ yum install redhat-lsb.i686

Best regards,

-- 
Javier Martínez Canillas
(+34) 682 39 81 69
Barcelona, Spain

___
linaro-toolchain mailing list
linaro-toolchain@lists.linaro.org
http://lists.linaro.org/mailman/listinfo/linaro-toolchain