From: "Will L Givens" <wlgivens@gmail.com>
To: dl8bcu@dl8bcu.de
Cc: linux-kernel@vger.kernel.org, linux-alpha@vger.kernel.org
Subject: RE: Will's kernel compilation error
Date: Tue, 16 Mar 2010 16:23:01 -0500 [thread overview]
Message-ID: <006e01cac54e$dd6b7b10$98427130$@com> (raw)
In-Reply-To: <20100316182534.GA818@ds20.borg.net>
> >
> > It seems the problem, GPREL16, is pretty wide spread. I've tried
> building
> > the drivers as modules, since that doesn't appear to be a problem
> *knock on
> > wood* but one driver after another, after another, after another
> generates a
> > new GPREL16 error! Raid0 drivers, numerous NetFilter modules, IR
> drivers
> > (guess I can't use a Hauppauge card), and various other components.
> I'm
> > going to try a few more configurations... then hit the sack. I'm
> pretty sure
> > this is going to be a long process.
>
> when I hit the relocation overflow a couple of releases before, I
> locally
> applied this patch, which fixes it for me. I assume the kernel is
> slightly
> bigger this way, but I didn't measure it.
>
> ev6, everything built in, gcc 4.4 I think
>
> Thorsten
>
>
> diff --git a/arch/alpha/Makefile b/arch/alpha/Makefile
> index 4759fe7..2cc3cc5 100644
> --- a/arch/alpha/Makefile
> +++ b/arch/alpha/Makefile
> @@ -12,7 +12,7 @@ NM := $(NM) -B
>
> LDFLAGS_vmlinux := -static -N #-relax
> CHECKFLAGS += -D__alpha__ -m64
> -cflags-y := -pipe -mno-fp-regs -ffixed-8 -msmall-data
> +cflags-y := -pipe -mno-fp-regs -ffixed-8
> cflags-y += $(call cc-option, -fno-jump-tables)
>
> cpuflags-$(CONFIG_ALPHA_EV4) := -mcpu=ev4
>
>
> --
> | Thorsten Kranzkowski Internet: dl8bcu@dl8bcu.de
> |
> | Mobile: ++49 170 1876134 Snail: Kiebitzstr. 14, 49324 Melle,
> Germany |
> | Ampr: dl8bcu@db0lj.#rpl.deu.eu, dl8bcu@marvin.dl8bcu.ampr.org
> [44.130.8.19] |
That patch did the trick!!!! Everything built without issue... I'll post
your patch at bugzilla.kernel.org. Now, just have to test the AIC7xxx driver
and see if it works! Nope it doesn't, same error as before... aic7xxx
unable to handle kernel paging address at 036b***** I'm going to try
swapping some memory around and see what happens if anything.
next prev parent reply other threads:[~2010-03-16 21:23 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-15 23:09 Will's kernel compilation error Matt Turner
2010-03-15 23:21 ` Will L Givens
2010-03-16 2:34 ` Will L Givens
2010-03-16 4:25 ` Matt Turner
2010-03-16 5:50 ` Will L Givens
2010-03-16 7:08 ` Michael Cree
2010-03-16 16:17 ` Will L Givens
2010-03-16 17:09 ` Will L Givens
2010-03-16 17:32 ` Will L Givens
2010-03-16 18:25 ` Thorsten Kranzkowski
2010-03-16 18:38 ` Will L Givens
2010-03-16 21:23 ` Will L Givens [this message]
2010-03-16 21:39 ` Matt Turner
2010-03-16 22:05 ` Michael Cree
2010-03-16 22:42 ` Will L Givens
2010-03-16 19:34 ` Raúl Porcel
2010-03-17 7:34 ` Michael Cree
2010-03-17 8:55 ` Will L Givens
2010-03-17 9:13 ` Justin P. Mattock
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='006e01cac54e$dd6b7b10$98427130$@com' \
--to=wlgivens@gmail.com \
--cc=dl8bcu@dl8bcu.de \
--cc=linux-alpha@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).