[prev in list] [next in list] [prev in thread] [next in thread]
List: linaro-toolchain
Subject: Re: Configuration specifics of prebuilt libc binaries
From: Evan Carson <carson.evan () gmail ! com>
Date: 2014-02-11 22:03:37
Message-ID: CAKEVZEaAJC=g1mJQPFckYfDADKTr8qbLO1sF7GrEGjA1UkMuKQ () mail ! gmail ! com
[Download RAW message or body]
[Attachment #2 (multipart/alternative)]
Hi,
Thank you for the info, it was very helpful.
I ran make-sysroot.sh and found that a package on the mirror in the script
was stale. By adding some others into the sources.list creation step I was
able to get it mostly working. There was a debuild bug I ran into
specifically with the libc6-dbg package but by removing this from the list
in the script it was able to complete without this.
The packages pulled in by the script appear to also be binaries? What it
did show me though is that the packages are
"libc6-dev_2.13-20ubuntu5_armel" and I think I can build from these.
Thanks again,
Evan
On Fri, Feb 7, 2014 at 8:32 PM, Zhenqiang Chen <zhenqiang.chen@linaro.org>wrote:
> On 8 February 2014 07:37, Evan Carson <carson.evan@gmail.com> wrote:
> > Hello,
> >
> > I'm maintaining an older release we have which uses the older toolchian
> > binaries in gcc-linaro-arm-linux-gnueabi-2012.03-20120326_linux. I've
> > identified a bug in glibc we appear to be encountering and would like to
> > port the fix back.
> >
> > I initially went the route of compiling the above toolchain binaries from
> > source as described in the readme.txt but then found that the cross
> compiler
> > binary build does not include the e/glibc build and these appear to be
> > sucked in in binary form (oneiric-sysroot-r1).
> >
> > Are there any documents how these prebuilt libc binaries were created?
>
> The prebuilt sysroot was from Ubuntu distribution. We did not build
> them from source.
>
> If you had downloaded the
>
> https://launchpad.net/linaro-toolchain-binaries/trunk/2012.03/+download/crosstool-ng-linaro-1.13.1-2012.03-20120326.tar.bz2
> ,
> please try the scripts: contrib/linaro/make-sysroot.sh
>
> > Please note that I'm not asking in general how to build glibc. I've
> built a
> > version with and without this bug patched to verify that it is indeed
> what
> > we are hitting. I'm more hoping to get an idea of how the specific
> binaries
> > mentioned above were built.
>
> From 4.8 release, we build the libc from Linaro release
>
> https://launchpad.net/linaro-toolchain-binaries/support/01/+download/linaro-prebuilt-sysroot-2013.10.tar.bz2
>
> .
> The source tarball is
>
> http://releases.linaro.org/13.10/components/toolchain/eglibc-linaro/eglibc-linaro-2.18-2013.10.tar.bz2
>
> It is built by
> http://releases.linaro.org/13.10/components/toolchain/binaries/crosstool-ng-linaro-1.13.1-4.8-2013.10.tar.bz2
>
> .
> Please refer the aarch64-linux-gnu config at
> crosstool-ng-linaro-1.13.1-4.8-2013.10
> /samples/linaro-aarch64-linux-gnu/crosstool.config.
>
> If you can contribute your patch back to glibc/eglibc upstream, that
> will be great.
>
> Thanks!
> -Zhenqiang
>
> > Thanks in advance for any help!
> >
> > Evan Carson
> >
> > _______________________________________________
> > linaro-toolchain mailing list
> > linaro-toolchain@lists.linaro.org
> > http://lists.linaro.org/mailman/listinfo/linaro-toolchain
> >
>
[Attachment #5 (text/html)]
<div dir="ltr">Hi,<div><br></div><div>Thank you for the info, it was very \
helpful.</div><div><br></div><div>I ran make-sysroot.sh and found that a package on \
the mirror in the script was stale. By adding some others into the sources.list \
creation step I was able to get it mostly working. There was a debuild bug I ran into \
specifically with the libc6-dbg package but by removing this from the list in the \
script it was able to complete without this.<br> </div><div><br></div><div>The \
packages pulled in by the script appear to also be binaries? What it did show me \
though is that the packages are "libc6-dev_2.13-20ubuntu5_armel" and I \
think I can build from these.</div> <div><br></div><div>Thanks \
again,</div><div><br></div><div>Evan</div><div><br></div><div><br></div></div><div \
class="gmail_extra"><br><br><div class="gmail_quote">On Fri, Feb 7, 2014 at 8:32 PM, \
Zhenqiang Chen <span dir="ltr"><<a href="mailto:zhenqiang.chen@linaro.org" \
target="_blank">zhenqiang.chen@linaro.org</a>></span> wrote:<br> <blockquote \
class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc \
solid;padding-left:1ex"><div class="">On 8 February 2014 07:37, Evan Carson <<a \
href="mailto:carson.evan@gmail.com">carson.evan@gmail.com</a>> wrote:<br>
> Hello,<br>
><br>
> I'm maintaining an older release we have which uses the older toolchian<br>
> binaries in gcc-linaro-arm-linux-gnueabi-2012.03-20120326_linux. I've<br>
> identified a bug in glibc we appear to be encountering and would like to<br>
> port the fix back.<br>
><br>
> I initially went the route of compiling the above toolchain binaries from<br>
> source as described in the readme.txt but then found that the cross compiler<br>
> binary build does not include the e/glibc build and these appear to be<br>
> sucked in in binary form (oneiric-sysroot-r1).<br>
><br>
> Are there any documents how these prebuilt libc binaries were created?<br>
<br>
</div>The prebuilt sysroot was from Ubuntu distribution. We did not build<br>
them from source.<br>
<br>
If you had downloaded the<br>
<a href="https://launchpad.net/linaro-toolchain-binaries/trunk/2012.03/+download/crosstool-ng-linaro-1.13.1-2012.03-20120326.tar.bz2" \
target="_blank">https://launchpad.net/linaro-toolchain-binaries/trunk/2012.03/+download/crosstool-ng-linaro-1.13.1-2012.03-20120326.tar.bz2</a>,<br>
please try the scripts: contrib/linaro/make-sysroot.sh<br>
<div class=""><br>
> Please note that I'm not asking in general how to build glibc. I've \
built a<br> > version with and without this bug patched to verify that it is \
indeed what<br> > we are hitting. I'm more hoping to get an idea of how the \
specific binaries<br> > mentioned above were built.<br>
<br>
</div>From 4.8 release, we build the libc from Linaro release<br>
<a href="https://launchpad.net/linaro-toolchain-binaries/support/01/+download/linaro-prebuilt-sysroot-2013.10.tar.bz2" \
target="_blank">https://launchpad.net/linaro-toolchain-binaries/support/01/+download/linaro-prebuilt-sysroot-2013.10.tar.bz2</a>.<br>
The source tarball is<br>
<a href="http://releases.linaro.org/13.10/components/toolchain/eglibc-linaro/eglibc-linaro-2.18-2013.10.tar.bz2" \
target="_blank">http://releases.linaro.org/13.10/components/toolchain/eglibc-linaro/eglibc-linaro-2.18-2013.10.tar.bz2</a><br>
<br>
It is built by <a href="http://releases.linaro.org/13.10/components/toolchain/binaries/crosstool-ng-linaro-1.13.1-4.8-2013.10.tar.bz2" \
target="_blank">http://releases.linaro.org/13.10/components/toolchain/binaries/crosstool-ng-linaro-1.13.1-4.8-2013.10.tar.bz2</a>.<br>
Please refer the aarch64-linux-gnu config at<br>
crosstool-ng-linaro-<a href="tel:1.13.1-4.8-2013.10" \
value="+13148201310">1.13.1-4.8-2013.10</a>/samples/linaro-aarch64-linux-gnu/crosstool.config.<br>
<br>
If you can contribute your patch back to glibc/eglibc upstream, that<br>
will be great.<br>
<br>
Thanks!<br>
-Zhenqiang<br>
<div class=""><br>
> Thanks in advance for any help!<br>
><br>
> Evan Carson<br>
><br>
</div>> _______________________________________________<br>
> linaro-toolchain mailing list<br>
> <a href="mailto:linaro-toolchain@lists.linaro.org">linaro-toolchain@lists.linaro.org</a><br>
> <a href="http://lists.linaro.org/mailman/listinfo/linaro-toolchain" \
target="_blank">http://lists.linaro.org/mailman/listinfo/linaro-toolchain</a><br> \
><br> </blockquote></div><br></div>
_______________________________________________
linaro-toolchain mailing list
linaro-toolchain@lists.linaro.org
http://lists.linaro.org/mailman/listinfo/linaro-toolchain
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic