From: Bob Tracy <rct@gherkin.frus.com>
To: Helge Deller <deller@gmx.de>
Cc: "Maciej W. Rozycki" <macro@linux-mips.org>,
Matt Turner <mattst88@gmail.com>,
linux-alpha <linux-alpha@vger.kernel.org>,
Debian Alpha Mailing List <debian-alpha@lists.debian.org>,
Michael Cree <mcree@orcon.net.nz>,
Richard Henderson <rth@twiddle.net>
Subject: Re: [BUG] 4.9.0 build error on Alpha
Date: Sat, 31 Dec 2016 01:20:32 -0600 [thread overview]
Message-ID: <20161231072032.GA3544@gherkin.frus.com> (raw)
In-Reply-To: <20161231064337.GA3209@gherkin.frus.com>
On Sat, Dec 31, 2016 at 12:43:37AM -0600, Bob Tracy wrote:
> On Fri, Dec 30, 2016 at 10:07:06PM +0100, Helge Deller wrote:
> > (...)
> > Another possibility could be to put all the lib functions into
> > a "alphalib" section into the final vmlinux.
> > For that add at the top of each of the .S files in lib/
> > .section .alphalib,"ax"
> > and apply the attached patch for arch/alpha/kernel/vmlinux.lds.S
> > Patch and suggestion is completely untested.
>
> Worth a try. I'll get going on this and report back with the results in
> a few hours.
Apologies in advance if the formatting isn't properly preserved :-(.
Syntax error on line 294 of the generated "vmlinux.lds" file, which is
right where the added ".alphalib:" stanza begins:
(...)
OUTPUT_FORMAT("elf64-alpha")
OUTPUT_ARCH(alpha)
ENTRY(__start)
PHDRS { kernel PT_LOAD; note PT_NOTE; }
jiffies = jiffies_64;
SECTIONS
{
. = 0xfffffc0000310000;
_text = .; /* Text and read-only data */
.text : {
*(.head.text)
.alphalib: {
*(.alphalib)
} :kernel
. = ALIGN(8); *(.text.hot .text .text.fixup .text.unlikely) *(.ref.text)
. = ALIGN(8); __sched_text_start = .; *(.sched.text) __sched_text_end = .;
. = ALIGN(8); __cpuidle_text_start = .; *(.cpuidle.text) __cpuidle_text_end = .;
. = ALIGN(8); __lock_text_start = .; *(.spinlock.text) __lock_text_end = .;
*(.fixup)
*(.gnu.warning)
} :kernel
swapper_pg_dir = (0xfffffc0000000000 +0x300000);
_etext = .; /* End of text section */
.notes : AT(ADDR(.notes) - 0) { __start_notes = .; *(.note.*) __stop_notes = .; } :kernel
:note
.dummy : {
*(.dummy)
} :kernel
(...)
--Bob
next prev parent reply other threads:[~2016-12-31 7:20 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-30 3:08 [BUG] 4.9.0 build error on Alpha Bob Tracy
2016-12-30 3:23 ` Matt Turner
2016-12-30 3:37 ` Bob Tracy
2016-12-30 16:02 ` Maciej W. Rozycki
2016-12-30 21:07 ` Helge Deller
2016-12-31 6:43 ` Bob Tracy
2016-12-31 7:20 ` Bob Tracy [this message]
2016-12-31 10:11 ` Maciej W. Rozycki
2016-12-31 15:20 ` Bob Tracy
2016-12-31 19:38 ` Michael Cree
2016-12-31 21:09 ` Bob Tracy
2017-01-01 1:23 ` Maciej W. Rozycki
2017-01-01 3:32 ` Bob Tracy
2017-01-01 20:29 ` Bob Tracy
2017-01-03 0:15 ` Bob Tracy
2017-01-12 12:52 ` Maciej W. Rozycki
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=20161231072032.GA3544@gherkin.frus.com \
--to=rct@gherkin.frus.com \
--cc=debian-alpha@lists.debian.org \
--cc=deller@gmx.de \
--cc=linux-alpha@vger.kernel.org \
--cc=macro@linux-mips.org \
--cc=mattst88@gmail.com \
--cc=mcree@orcon.net.nz \
--cc=rth@twiddle.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.