Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Romain Naour <romain.naour@openwide.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 5/7] toolchain-external: bump CodeSourcery aarch64 to 2014.11
Date: Tue, 24 Nov 2015 22:29:16 +0100	[thread overview]
Message-ID: <5654D6AC.40908@openwide.fr> (raw)
In-Reply-To: <565482C8.5030609@imgtec.com>

Hi Vicente,

Le 24/11/2015 16:31, Vicente Olivert Riera a ?crit :
> Dear Romain Naour,
> 
> the patch subject is wrong. You are bumping to 2015.11 instead of
> 2014.11. I guess the maintainer will not mind to fix it for you.

Thanks for the review and testing :)

Actually the patch subject is correct, this is the aarch64 CodeSourcery 2014.11
toolchain... but the typo is in the Config.in prompt:

s/2015.11/2014.11/

Dear maintainer, can you fix it while applying. Thanks!

Best regards,
Romain

> 
> On 21/11/15 16:36, Romain Naour wrote:
>> Like for 2014.05 [1], this toolchain need a small fixup:
>>
>> Buildroot picks up aarch64-linux-gnu/libc/lib64 and all its contents, but
>> does not pickup aarch64-linux-gnu/libc/lib to populate the staging directory.
>> aarch64-linux-gnu/libc/lib contain a single symlink which is lost during
>> Buildroot staging install :
>>   aarch64-linux-gnu/libc/lib/ld-linux-aarch64.so.1 -> ../lib64/ld-2.20.so
>>
>> Add a custom post install staging hook to create it manually.
>>
>> A runtime testing show that /lib/ld-2.20.so and /lib/ld-linux-aarch64.so.1
>> are missing in the file system.
>>
>> Add another post install target hook to copy ld-2.20.so and create the
>> symlink.
>>
>> Runtime tested using qemu_aarch64_virt_defconfig.
>>
>> [1] http://patchwork.ozlabs.org/patch/467857/
>>
>> Signed-off-by: Romain Naour <romain.naour@openwide.fr>
>> Cc: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
> Tested-by: Vicente Olivert Riera <Vincent.Riera@imgtec.com>
> 
> Build a minimal rootfs using that toolchain after applying this patch.
> 
> Regards,
> 
> Vincent.
> 

  reply	other threads:[~2015-11-24 21:29 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-21 16:36 [Buildroot] [PATCH 1/7] toolchain-external: CodeSourcery AMD64: support only one version Romain Naour
2015-11-21 16:36 ` [Buildroot] [PATCH 2/7] toolchain-external: bump CodeSourcery AMD64 to 2015.11 Romain Naour
2015-11-24 15:10   ` Vicente Olivert Riera
2015-11-21 16:36 ` [Buildroot] [PATCH 3/7] toolchain-external: CodeSourcery NIOSII: support only one version Romain Naour
2015-11-24 15:16   ` Vicente Olivert Riera
2015-11-21 16:36 ` [Buildroot] [PATCH 4/7] toolchain-external: bump CodeSourcery NIOSII to 2015.11 Romain Naour
2015-11-24 15:22   ` Vicente Olivert Riera
2015-12-06 20:07     ` Romain Naour
2015-11-21 16:36 ` [Buildroot] [PATCH 5/7] toolchain-external: bump CodeSourcery aarch64 to 2014.11 Romain Naour
2015-11-24 15:31   ` Vicente Olivert Riera
2015-11-24 21:29     ` Romain Naour [this message]
2015-11-21 16:36 ` [Buildroot] [PATCH 6/7] toolchain-external: CodeSourcery MIPS: support only one version Romain Naour
2015-11-24 15:34   ` Vicente Olivert Riera
2015-11-21 16:36 ` [Buildroot] [PATCH 7/7] toolchain-external: bump CodeSourcery MIPS to 2015.11 Romain Naour
2015-11-24 15:43   ` Vicente Olivert Riera
2015-11-24 15:05 ` [Buildroot] [PATCH 1/7] toolchain-external: CodeSourcery AMD64: support only one version Vicente Olivert Riera
2015-12-19 12:57 ` Thomas Petazzoni
2015-12-19 16:53   ` Romain Naour
2015-12-29  0:55   ` Romain Naour

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=5654D6AC.40908@openwide.fr \
    --to=romain.naour@openwide.fr \
    --cc=buildroot@busybox.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox