All of lore.kernel.org
 help / color / mirror / Atom feed
From: Baruch Siach <baruch@tkos.co.il>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCHv2 4/6] binutils: enable for aarch64
Date: Thu, 24 Apr 2014 07:04:46 +0300	[thread overview]
Message-ID: <20140424040446.GC22908@tarshish> (raw)
In-Reply-To: <1398301235-8445-4-git-send-email-gustavo@zacarias.com.ar>

Hi Gustavo,

On Wed, Apr 23, 2014 at 10:00:33PM -0300, Gustavo Zacarias wrote:
> Versions lower than 2.24 fail to build a working kernel as in:
> 
> Freeing unused kernel memory: 184K (ffffffc00059a000 - ffffffc0005c8000)
> init[1]: unhandled level 2 translation fault (11) at 0x00000008, esr
> 0x92000006
> pgd = ffffffc876403000
> [00000008] *pgd=00000008f6ea0003, *pmd=0000000000000000
> 
> Signed-off-by: Gustavo Zacarias <gustavo@zacarias.com.ar>
> ---

The subject line is misleading. This patch actually disables aarch64 for
binutils < 2.24.

baruch

>  package/binutils/Config.in.host | 12 ++++++------
>  1 file changed, 6 insertions(+), 6 deletions(-)
> 
> diff --git a/package/binutils/Config.in.host b/package/binutils/Config.in.host
> index 58738e8..2f86f51 100644
> --- a/package/binutils/Config.in.host
> +++ b/package/binutils/Config.in.host
> @@ -14,30 +14,30 @@ choice
>  		bool "binutils 2.18-avr32-1.0.1"
>  
>  	config BR2_BINUTILS_VERSION_2_20_1
> -		depends on !BR2_avr32
> +		depends on !BR2_avr32 && !BR2_aarch64
>  		depends on !BR2_ARM_EABIHF
>  		bool "binutils 2.20.1"
>  
>  	config BR2_BINUTILS_VERSION_2_21
> -		depends on !BR2_avr32
> +		depends on !BR2_avr32 && !BR2_aarch64
>  		depends on !BR2_ARM_EABIHF
>  		bool "binutils 2.21"
>  
>  	config BR2_BINUTILS_VERSION_2_21_1
> -		depends on !BR2_avr32
> +		depends on !BR2_avr32 && !BR2_aarch64
>  		depends on !BR2_ARM_EABIHF
>  		bool "binutils 2.21.1"
>  
>  	config BR2_BINUTILS_VERSION_2_22
> -		depends on !BR2_avr32
> +		depends on !BR2_avr32 && !BR2_aarch64
>  		bool "binutils 2.22"
>  
>  	config BR2_BINUTILS_VERSION_2_23_1
> -		depends on !BR2_avr32
> +		depends on !BR2_avr32 && !BR2_aarch64
>  		bool "binutils 2.23.1"
>  
>  	config BR2_BINUTILS_VERSION_2_23_2
> -		depends on !BR2_avr32
> +		depends on !BR2_avr32 && !BR2_aarch64
>  		bool "binutils 2.23.2"
>  
>  	config BR2_BINUTILS_VERSION_2_24
> -- 
> 1.8.3.2

-- 
     http://baruch.siach.name/blog/                  ~. .~   Tk Open Systems
=}------------------------------------------------ooO--U--Ooo------------{=
   - baruch at tkos.co.il - tel: +972.2.679.5364, http://www.tkos.co.il -

  reply	other threads:[~2014-04-24  4:04 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-24  1:00 [Buildroot] [PATCHv2 1/6] toolchain: add gcc 4.9 series Gustavo Zacarias
2014-04-24  1:00 ` [Buildroot] [PATCHv2 2/6] arm: update processor types Gustavo Zacarias
2014-04-24  1:00 ` [Buildroot] [PATCHv2 3/6] package/gcc: disable libsanitizer for uClibc Gustavo Zacarias
2014-04-24  1:00 ` [Buildroot] [PATCHv2 4/6] binutils: enable for aarch64 Gustavo Zacarias
2014-04-24  4:04   ` Baruch Siach [this message]
2014-04-24 13:20     ` Peter Korsgaard
2014-04-24  1:00 ` [Buildroot] [PATCHv2 5/6] gcc: " Gustavo Zacarias
2014-04-24  1:00 ` [Buildroot] [PATCHv2 6/6] toolchain: enable internal " Gustavo Zacarias
2014-04-24 13:22 ` [Buildroot] [PATCHv2 1/6] toolchain: add gcc 4.9 series Peter Korsgaard

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=20140424040446.GC22908@tarshish \
    --to=baruch@tkos.co.il \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.