Re: Correct linux kerenl for eglibc in Linaro tool chain

2015-05-14 Thread Ganesan, Aravind


On 5/13/2015 9:35 PM, Wookey wrote:
> +++ Ganesan, Aravind [2015-05-13 20:58 -0600]:
>> On 5/13/2015 7:12 PM, Wookey wrote:
>>> +++ Ganesan, Aravind [2015-05-13 18:35 -0600]:
 Hi Guys,
I have two questions:
 (1) I have download gcc-4.9 tool chain from
 http://releases.linaro.org/14.08/components/toolchain/binaries.
 The kernel for the release
 (http://releases.linaro.org/14.08/components/kernel/linux-linaro) is
 3.16. So can we assume the kernel headers found in the tool chain
 installation from the link above belongs to linux version 3.16?

 (2) Also, I ubuntu wiki indicates that starting with Ubuntu 12.04 they
 are using linaro gcc packages for arm64
>>>
>>> Not linaro packages directly, but the same source tree/patch set.
>>>
 (https://wiki.ubuntu.com/ToolChain). Is there an easy way to find what
 linaro-release (for tool chain) will be compatible with Ubuntu 14.10
 aarch64 image?
>>>
>>> If building on Ubuntu it's much easier to use the ubuntu-packaged
>>> toolchains (or cross-toolchains) which should function just the same
>>> but have multiarch enabled and be properly packaged.
>>>
>>> That should make your Q1 moot as you the kernel-headers are a separate
>>> package from the cross-toolchain and normal package-management tools
>>> will make it obvious what versions are available/installed.
>>>
>>> You only want to try using a linaro toolchain release directly if
>>> there is some super-recent feature that you need, but which hasn't yet
>>> made it into the Ubuntu toolchain (they will always be somewhat behind
>>> 'current' especially if building on stable).
>>>
>> Thanks Wookey. I'm developing on a X86_64 machine runningUbuntu-12.04
>> (which, AFAIK, doesn't have aarch64 toolchain) .
> 
> Correct - that appeared in 14.04
> 
>> I'm trying to find a
>> cross-compilation tool-chain for building Linux kernel and applications
>> targeting a qemu-aarch64 machine-emulation running Ubuntu 14.10. 
> 
> Build in a 14.04 chroot, and thus use 14.04 toolchain, and libraries.
> 
> Use any of debootstrap, or sbuild-createchroot or the ubuntu-specific
> mksbuild to make at 14.04 chroot.
> 
> You can either make a qemu arm64 chroot and native-build in it, or
> make an amd64 chroot and cross-build in it.
> 
> This tells you how make a qemu-ready arm64 chroot (adjust instructions
> debian-> ubuntu) https://wiki.debian.org/Arm64Port#Debootstrap_arm64
> 
> This tells you how to make an amd64 chroot:
> https://help.ubuntu.com/community/DebootstrapChroot
> I prefer to use sbuild-createchroot because it does all those sbuild
> config runes for you (and can make a tarball chroot for clean builds
> every time).
> 
> sbuild-createchroot --components=main,universe
> --make-sbuild-tarball=/srv/chroots/precise-cross-buildd.tgz precise
> /srv/chroots/precise http://archive.ubuntu.com/ubuntu/
>   sbuild-adduser 
>   
>   
>   Contents
>   
>   Cross Compiling using Multi-Arch
>   Preparing multiarch chroot
> Manually preparing multiarch chroot
> Multiarch cross-building requirements
> Crossbuilding requirements
> Cross toolchain
> Cross
> pkg-config support
> dpkg-cross support
>   Environment variables
>   Adding qemu support
>   Configuring dpkg
>   Installing
> cross-build deps
> Running the build
>   Cross Compiling examples
>   Steps to proceed from here
>   
>   Cross Compiling using Multi-Arch
>   
>   This page details what is required to do
> multiarch crossbuilding. If you just want to use it then read
> 'Preparing multiarch chroot'. The building itself is trivial (sbuild
> does all the work), the intial chroot setup is most of it. You can do
> cross-builds without setting up a chroot, but it is not recommended
> because it puts a lot of guff in your system and mulitarch problems
> are much more likely on a more fully-populated system.
> 
> Preparing multiarch chroot
> 
> There is now a helper script to do the work dsescribed below (in
> xbuilder 0.8) so if you just want to make a cross-build chroot and use
> it this is the way to do it. This currently assumes Ubuntu, and would
> need some minor adjustements for Debian (changing the /etc/apt/sources
> in the chroot because of the different archive layout).
> 
> Install xbuilder 0.8 from the Linaro cross-tools PPA
> 
> apt-add-repository ppa:linaro-foundations/cross-build-tools
> apt-get update
> apt-get install xbuilder
> 
> Setup the chroot
> 
> xbuild-chroot-setup precise /srv/chroots/precise-cross

Re: 502 connecting to abe.tcwglab.linaro.org

2015-05-14 Thread Virendra Kumar Pathak
Hi,

I tried on abe 'stable' branch and with below configuration build was
successful.

../abe/configure --with-fileserver=148.251.136.42 --with-remote-snapshots=
http://148.251.136.42/snapshots-ref
../abe/abe.sh --target aarch64-linux-gnu --build all
(Additionally I had to increase the wget_timeout=100)


But on master branch, with below commands (as suggested in above mail)
following error were observed.
../abe/configure --with-fileserver=148.251.136.42
--with-remote-snapshots=/snapshots-ref
../abe/abe.sh --target aarch64-linux-gnu --build all
ERROR (#144): fetch_http (md5sums doesn't exist and you disabled updating.)

Looks like following commit is causing problem on the abe master branch.
On removing it, build successfully downloaded the packages from
148.251.136.42.

commit 5a5ab3582851d52d903846d34c79850f5d7ebda5
don't try to fetch anything is updates are disabled.

Thanks
Virendra

On 6 May 2015 at 17:30,  wrote:

> Send linaro-toolchain mailing list submissions to
> linaro-toolchain@lists.linaro.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
> https://lists.linaro.org/mailman/listinfo/linaro-toolchain
> or, via email, send a message with subject or body 'help' to
> linaro-toolchain-requ...@lists.linaro.org
>
> You can reach the person managing the list at
> linaro-toolchain-ow...@lists.linaro.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of linaro-toolchain digest..."
>
>
> Today's Topics:
>
>1. Re: 502 connecting to abe.tcwglab.linaro.org (Tim Entinger)
>2. Re: 502 connecting to abe.tcwglab.linaro.org (Victor Chong)
>3. [ANNOUNCE] Linaro GCC 4.9 2015.04 snapshot re-spin (Yvan Roux)
>
>
> --
>
> Message: 1
> Date: Tue, 5 May 2015 12:44:44 + (UTC)
> From: Tim Entinger 
> To: linaro-toolchain@lists.linaro.org
> Subject: Re: 502 connecting to abe.tcwglab.linaro.org
> Message-ID: 
> Content-Type: text/plain; charset=us-ascii
>
> Rob Savoye  writes:
>
> >
> > On 04/21/2015 04:23 PM, Christopher Covington wrote:
> > > abe$ ./abe.sh --target aarch64-linux-gnu
> > > NOTE: Downloading md5sums to abe/snapshots
> > > RUN: /usr/bin/wget  --timeout=10 --tries=2 --directory-
> prefix=abe/snapshots/ http://abe.tcwglab.linaro.org/snapshots/md5sums
> >
> >   We're having a major security related issue, so the entire TCWG lab
> > got taken offline yesterday till this is fixed and more secured. No
> idea
> > what the ETA is for all of that. ABE will work regardless other than
> > some warning messages about not being able to download the md5sums
> file,
> > or anything under 'infrastructure'. Most of what ABE needs is at
> > git.linaro.org, and that's still online. The only files ABE downloads
> > from abe.tcwglab.linaro.org are source tarballs, which don't change
> very
> > often. As long as you have them already downloaded, you can build a
> > toolchain still. I work offline pretty frequently, so have tried to
> make
> > ABE work without the upstream access to anything.
> >
> >   Try adding '--disable update' to your command line for abe.sh, and
> > it'll stop trying.
> >
> > - rob -
> >
> > ___
> > linaro-toolchain mailing list
> > linaro-toolchain  lists.linaro.org
> > https://lists.linaro.org/mailman/listinfo/linaro-toolchain
> >
>
>
>  Is there any update for when the TCWG lab will be back online? I was
> trying to use ABE for the first time and got the 503 Service Unavailable
> message. Is there a way to specify different locations for the source
> tarballs in the meantime? I'm hoping to work around the issue if a
> timeline is still unknown.
>
>
>
> --
>
> Message: 2
> Date: Tue, 5 May 2015 23:12:28 +0900
> From: Victor Chong 
> To: Tim Entinger 
> Cc: Linaro Toolchain Mailman List 
> Subject: Re: 502 connecting to abe.tcwglab.linaro.org
> Message-ID:
>  q...@mail.gmail.com>
> Content-Type: text/plain; charset="iso-8859-1"
>
> Hi Tim,
>
> On Tue, May 5, 2015 at 9:44 PM, Tim Entinger 
> wrote:
>
> > Rob Savoye  writes:
> >
> > >
> > > On 04/21/2015 04:23 PM, Christopher Covington wrote:
> > > > abe$ ./abe.sh --target aarch64-linux-gnu
> > > > NOTE: Downloading md5sums to abe/snapshots
> > > > RUN: /usr/bin/wget  --timeout=10 --tries=2 --directory-
> > prefix=abe/snapshots/ http://abe.tcwglab.linaro.org/snapshots/md5sums
> > >
> > >   We're having a major security related issue, so the entire TCWG lab
> > > got taken offline yesterday till this is fixed and more secured. No
> > idea
> > > what the ETA is for all of that. ABE will work regardless other than
> > > some warning messages about not being able to download the md5sums
> > file,
> > > or anything under 'infrastructure'. Most of what ABE needs is at
> > > git.linaro.org, and that's still online. The only files ABE downloads
> > > from abe.tcwglab.linaro.org are source tarballs, which don'