All of lore.kernel.org
 help / color / mirror / Atom feed
From: Lee Revell <rlrevell@joe-job.com>
To: Fernando Lopez-Lezcano <nando@ccrma.Stanford.EDU>
Cc: Ingo Molnar <mingo@elte.hu>, linux-kernel@vger.kernel.org
Subject: Re: 2.6.13-rc7-rt4, fails to build
Date: Mon, 29 Aug 2005 21:45:22 -0400	[thread overview]
Message-ID: <1125366322.4598.101.camel@mindpipe> (raw)
In-Reply-To: <1125364522.7630.108.camel@cmn37.stanford.edu>

On Mon, 2005-08-29 at 18:15 -0700, Fernando Lopez-Lezcano wrote:
> On Mon, 2005-08-29 at 01:35, Ingo Molnar wrote: 
> > * Fernando Lopez-Lezcano <nando@ccrma.Stanford.EDU> wrote:
> > 
> > > I'm getting a build error for 2.6.13-rc7-rt4 with PREEMPT_DESKTOP for 
> > > i386:
> > 
> > hm, cannot reproduce this build problem on my current tree - could you 
> > try 2.6.13-rt1? (and please send the 2.6.13-rt1 .config if it still 
> > occurs)
> 
> I still get the error, it is happening in the _smp_ build, I don't know
> what's wrong...
> 
> arch/i386/mach-generic/built-in.o(.text+0x1183): In function
> `es7000_rename_gsi':

Well you could certainly work around it by using CONFIG_X86_PC rather
than CONFIG_X86_GENERICARCH unless you really needs to support the IBM
x440, Unisys ES7000, or something with more than 8 CPUs...

Lee


  reply	other threads:[~2005-08-30  1:45 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-29  1:02 2.6.13-rc7-rt4, fails to build Fernando Lopez-Lezcano
2005-08-29  8:35 ` Ingo Molnar
2005-08-29 16:57   ` Fernando Lopez-Lezcano
2005-08-30  5:48     ` Ingo Molnar
2005-08-30 19:47       ` Fernando Lopez-Lezcano
2005-08-30 20:59         ` Alan Cox
2005-08-30  1:15   ` Fernando Lopez-Lezcano
2005-08-30  1:45     ` Lee Revell [this message]
2005-08-30  1:58       ` Fernando Lopez-Lezcano
2005-08-30  6:28     ` Ingo Molnar
2005-08-30  9:50       ` Karsten Wiese

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=1125366322.4598.101.camel@mindpipe \
    --to=rlrevell@joe-job.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=nando@ccrma.Stanford.EDU \
    /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.