From: Frans Pop <elendil@planet.nl>
To: Kyle McMartin <kyle@mcmartin.ca>
Cc: Carlos O'Donell <carlos@systemhalted.org>, linux-parisc@vger.kernel.org
Subject: Re: vmlinux.lds:319: undefined symbol `THREAD_SIZE'
Date: Fri, 2 Oct 2009 02:25:28 +0200 [thread overview]
Message-ID: <200910020225.29192.elendil@planet.nl> (raw)
In-Reply-To: <20091001163244.GS11961@bombadil.infradead.org>
On Thursday 01 October 2009, Kyle McMartin wrote:
> On Thu, Oct 01, 2009 at 05:35:38AM +0200, Frans Pop wrote:
> > On Thursday 01 October 2009, Carlos O'Donell wrote:
> > > On Wed, Sep 30, 2009 at 9:39 PM, Frans Pop <elendil@planet.nl> wrote:
> > > > arch/parisc/kernel/vmlinux.lds:319: undefined symbol `THREAD_SIZE'
> > > > referenced in expression
> > > > make[5]: *** [.tmp_vmlinux1] Error 1
> > >
> > > Fixed upstream?
> > >
> > > http://git.kernel.org/?p=linux/kernel/git/kyle/parisc-2.6.git;a=comm
> > >itdi ff;h=f32ed3954c5e365907738b1206e849b6bbe9bcef
> >
> > Nope. With that patch applied I still get the error, even for an
> > 'allnoconfig" build.
>
> You need this one too:
> http://git.kernel.org/?p=linux/kernel/git/kyle/parisc-2.6.git;a=commitdi
>ff;h=8cf06fc9bd660c28afea4115fd91a2cc4978eb54
Yep, that fixed it.
The resulting kernel boots fine on my box, but there does seem to be a
regression. With 2.6.31 I not had any problems running aptitude, but with
this kernel it's segfaulted on me once and frozen twice. Unfortunately
it's not reliably reproducible,
Thanks,
FJP
next prev parent reply other threads:[~2009-10-02 0:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-01 1:39 vmlinux.lds:319: undefined symbol `THREAD_SIZE' Frans Pop
2009-10-01 2:05 ` Carlos O'Donell
2009-10-01 3:35 ` Frans Pop
2009-10-01 16:32 ` Kyle McMartin
2009-10-02 0:25 ` Frans Pop [this message]
2009-10-01 2:24 ` Frans Pop
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=200910020225.29192.elendil@planet.nl \
--to=elendil@planet.nl \
--cc=carlos@systemhalted.org \
--cc=kyle@mcmartin.ca \
--cc=linux-parisc@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 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.