Hi
Updated sysroots for binary toolchain are available at [1]. This time I split -dev and -dbg sysroots so as long as dbgsym are not needed less disk space is used.
Please take a look at them and report any issues.
1. http://people.linaro.org/~hrw/generic-linux/sysroots/20120301/
On Wed, Mar 7, 2012 at 1:08 AM, Marcin Juszkiewicz marcin.juszkiewicz@linaro.org wrote:
Hi
Updated sysroots for binary toolchain are available at [1]. This time I split -dev and -dbg sysroots so as long as dbgsym are not needed less disk space is used.
Please take a look at them and report any issues.
Zhenqiang, could you have a look at these please? I'll have a poke around in the nano-dev image out of interest.
-- Michael
On 7 March 2012 05:55, Michael Hope michael.hope@linaro.org wrote:
On Wed, Mar 7, 2012 at 1:08 AM, Marcin Juszkiewicz marcin.juszkiewicz@linaro.org wrote:
Hi
Updated sysroots for binary toolchain are available at [1]. This time I split -dev and -dbg sysroots so as long as dbgsym are not needed less disk space is used.
Please take a look at them and report any issues.
Zhenqiang, could you have a look at these please? I'll have a poke around in the nano-dev image out of interest.
Sure. I will do some tests based on 2012.02 release.
-Zhenqiang
On 7 March 2012 09:39, Zhenqiang Chen zhenqiang.chen@linaro.org wrote:
On 7 March 2012 05:55, Michael Hope michael.hope@linaro.org wrote:
On Wed, Mar 7, 2012 at 1:08 AM, Marcin Juszkiewicz marcin.juszkiewicz@linaro.org wrote:
Hi
Updated sysroots for binary toolchain are available at [1]. This time I split -dev and -dbg sysroots so as long as dbgsym are not needed less disk space is used.
Please take a look at them and report any issues.
Zhenqiang, could you have a look at these please? I'll have a poke around in the nano-dev image out of interest.
I try the sysroots to build small cases (with additional header files like <X11/Xlib.h>). All can pass after coping the libgcc* to /lib (https://bugs.launchpad.net/linaro-toolchain-binaries/+bug/939143).
There is an "arm-linux-gnueabihf" dir in sysroot-*-dbg. Does this mean the binary toolcahin need support two different archs? How to confiure to support it?
Thanks! -Zhenqiang
W dniu 07.03.2012 10:21, Zhenqiang Chen pisze:
I try the sysroots to build small cases (with additional header files like <X11/Xlib.h>).
Ok. Inform me if any header will be missing.
BTW: which sysroot you are using to test?
All can pass after coping the libgcc* to /lib (https://bugs.launchpad.net/linaro-toolchain-binaries/+bug/939143).
So it does not finds libgcc_s.so in usr/lib/gcc/arm-linux-gnueabi/4.6/ directory?
There is an "arm-linux-gnueabihf" dir in sysroot-*-dbg. Does this mean the binary toolchain need support two different archs?
Those sysroots are for 'armel' architecture. I will drop armhf binaries from sysroot.
How to configure to support it?
Debian/Ubuntu gcc-4.6 handles that by multilib patches.
On Wed, Mar 7, 2012 at 10:42 PM, Marcin Juszkiewicz marcin.juszkiewicz@linaro.org wrote:
W dniu 07.03.2012 10:21, Zhenqiang Chen pisze:
I try the sysroots to build small cases (with additional header files like <X11/Xlib.h>).
Ok. Inform me if any header will be missing.
BTW: which sysroot you are using to test?
All can pass after coping the libgcc* to /lib (https://bugs.launchpad.net/linaro-toolchain-binaries/+bug/939143).
So it does not finds libgcc_s.so in usr/lib/gcc/arm-linux-gnueabi/4.6/ directory?
In some ways it should. The binary toolchain has the multiarch patches and should use the same search path. Should the sysroot contain libgcc and libstdc++ at all?
Separately we need to shift the libgcc and libstdc++ made as part of the binary toolchain build out of the sysroot. This lets you nuke the sysroot and replace it without losing the support libraries.
-- Michael
In some ways it should. The binary toolchain has the multiarch patches and should use the same search path. Should the sysroot contain libgcc and libstdc++ at all?
The sysroot contain libgcc and libstdc++. But they are not in the search path. In the sysroot, they are at: /lib/arm-linux-gnueabi/libgcc_s.so.1 /usr/lib/gcc/arm-linux-gnueabi/4.6/libgcc_s.so /usr/lib/gcc/arm-linux-gnueabi/4.6.1/libgcc_s.so
But the binary toolchain expects /lib/libgcc_s.so /lib/libgcc_s.so.1
-Zhenqiang
On 7 March 2012 17:42, Marcin Juszkiewicz marcin.juszkiewicz@linaro.org wrote:
W dniu 07.03.2012 10:21, Zhenqiang Chen pisze:
I try the sysroots to build small cases (with additional header files like <X11/Xlib.h>).
Ok. Inform me if any header will be missing.
BTW: which sysroot you are using to test?
I try the three sysroot: alip and ubuntu-desktop have Xlib.h. nano do not have X11/Xlib.h.
-Zhenqiang
On Wed, Mar 7, 2012 at 10:21 PM, Zhenqiang Chen zhenqiang.chen@linaro.org wrote:
On 7 March 2012 09:39, Zhenqiang Chen zhenqiang.chen@linaro.org wrote:
On 7 March 2012 05:55, Michael Hope michael.hope@linaro.org wrote:
On Wed, Mar 7, 2012 at 1:08 AM, Marcin Juszkiewicz marcin.juszkiewicz@linaro.org wrote:
Hi
Updated sysroots for binary toolchain are available at [1]. This time I split -dev and -dbg sysroots so as long as dbgsym are not needed less disk space is used.
Please take a look at them and report any issues.
Zhenqiang, could you have a look at these please? I'll have a poke around in the nano-dev image out of interest.
I try the sysroots to build small cases (with additional header files like <X11/Xlib.h>).
Sorry, what are these changes? Patches to the source themselves?
How about something meaty like qemu? It's designed to cross compile and uses interesting libraries like SDL, X, and OpenGL.
All can pass after coping the libgcc* to /lib (https://bugs.launchpad.net/linaro-toolchain-binaries/+bug/939143).
There is an "arm-linux-gnueabihf" dir in sysroot-*-dbg. Does this mean the binary toolcahin need support two different archs? How to confiure to support it?
This is the same architecture but using the hard float calling convention. We don't need to support that right now, but Ubuntu has switched to hard float by default. We need a plan for that.
-- Michael
linaro-toolchain@lists.linaro.org