From: Michael Cree <mcree@orcon.net.nz>
To: Will L Givens <wlgivens@gmail.com>
Cc: linux-kernel@vger.kernel.org, linux-alpha@vger.kernel.org
Subject: Re: Will's kernel compilation error
Date: Tue, 16 Mar 2010 20:08:06 +1300 [thread overview]
Message-ID: <4B9F2E56.2060303@orcon.net.nz> (raw)
In-Reply-To: <001e01cac4cc$98072ce0$c81586a0$@com>
On 16/03/10 18:50, Will L Givens wrote:
> 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.
As has been suggested your best bet for help is to post your .config.
If you don't want that publicly available then feel free to email it
privately to Matt and myself.
FWIW, I have two Hauppauge cards (PVR350 card and a Nova-T-500 DVB-T
card) in my Alpha, and have had no problems compiling the kernel, the
ivtv modules, the DVB modules, and the IR modules.
If we cannot track down what you are doing differently than the rest of
us, then there is little chance we can help you.
Cheers
Michael.
next prev parent reply other threads:[~2010-03-16 7:08 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 [this message]
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
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=4B9F2E56.2060303@orcon.net.nz \
--to=mcree@orcon.net.nz \
--cc=linux-alpha@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=wlgivens@gmail.com \
/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).