From: Guenter Roeck <linux@roeck-us•net>
To: Alan Modra <amodra@gmail•com>
Cc: Stephen Rothwell <sfr@canb•auug.org.au>, linuxppc-dev@lists•ozlabs.org
Subject: Re: powerpc/ppc64: Allow allmodconfig to build (finally !)
Date: Thu, 15 May 2014 03:46:38 -0700 [thread overview]
Message-ID: <53749B0E.4050900@roeck-us.net> (raw)
In-Reply-To: <20140515094716.GQ5162@bubble.grove.modra.org>
On 05/15/2014 02:47 AM, Alan Modra wrote:
> On Wed, May 14, 2014 at 08:34:30AM -0700, Guenter Roeck wrote:
>> Bummer. Confirmed, if I replace "@h" with "@high" in just one place,
>> the builds pass with binutils 2.24. Unfortunately the same builds then
>> fails with binutils 2.23.
>>
>> Any idea how to get it to compile with both old and new versions ?
>
> The standard way with GNU software would be to write a configure test,
> that checks for @high support in the assembler, and defines a macro
> if the assembler passes the check. I'm not that familiar with the
> linux kernel these days, but a little grepping around says that
> something like
>
> ashigh := $(call as-instr,lis 9$(comma)foo@high,-DHAVE_AS_ATHIGH=1)
> KBUILD_AFLAGS += $(ashigh)
>
> might work.
>
Yes, it does.
Thanks!
Guenter
next prev parent reply other threads:[~2014-05-15 10:46 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-12 5:57 [PATCH] powerpc/ppc64: Allow allmodconfig to build (finally !) Benjamin Herrenschmidt
2014-05-13 0:28 ` Guenter Roeck
2014-05-13 9:16 ` Benjamin Herrenschmidt
2014-05-13 12:35 ` Guenter Roeck
2014-05-13 17:17 ` Guenter Roeck
2014-05-14 3:34 ` Stephen Rothwell
2014-05-14 5:16 ` Guenter Roeck
2014-05-14 5:52 ` Alan Modra
2014-05-14 15:34 ` Guenter Roeck
2014-05-15 9:47 ` Alan Modra
2014-05-15 10:46 ` Guenter Roeck [this message]
2014-05-15 12:22 ` Benjamin Herrenschmidt
2014-05-15 13:09 ` Guenter Roeck
2014-05-14 5:42 ` Alan Modra
2014-05-13 19:41 ` Guenter Roeck
2014-06-12 12:26 ` Guenter Roeck
2014-06-12 21:57 ` Benjamin Herrenschmidt
2014-06-12 22:17 ` Guenter Roeck
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=53749B0E.4050900@roeck-us.net \
--to=linux@roeck-us$(echo .)net \
--cc=amodra@gmail$(echo .)com \
--cc=linuxppc-dev@lists$(echo .)ozlabs.org \
--cc=sfr@canb$(echo .)auug.org.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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