mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Mikael Pettersson <mikpe@csd.uu.se>
To: Andrew Morton <akpm@osdl.org>
Cc: "Martin J. Bligh" <mbligh@aracnet.com>, linux-kernel@vger.kernel.org
Subject: Re: ppc64 build broke between 2.6.11-bk6 and 2.6.11-bk7
Date: Fri, 18 Mar 2005 10:35:13 +0100	[thread overview]
Message-ID: <16954.41169.665960.627306@alkaid.it.uu.se> (raw)
In-Reply-To: <16954.40800.839009.64848@alkaid.it.uu.se>

Mikael Pettersson writes:
 > Andrew Morton writes:
 >  > "Martin J. Bligh" <mbligh@aracnet.com> wrote:
 >  > >
 >  > > drivers/built-in.o(.text+0x182bc): In function `.matroxfb_probe':
 >  > > : undefined reference to `.mac_vmode_to_var'
 >  > > make: *** [.tmp_vmlinux1] Error 1
 >  > > 
 >  > > Anyone know what that is?
 >  > > 
 >  > 
 >  > ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.11/2.6.11-mm4/broken-out/fbdev-kconfig-fix-for-macmodes-and-ppc.patch
 >  > 
 >  > should fix it.
 > 
 > It seems the culprit is "matroxfb-compile-error.patch" which unconditionally adds
 > macmodes.o to the Makefile line for CONFIG_FB_MATROX. This obviously breaks on !ppc.

!pmac of course; I assume Martin configured for some kind of POWER box and not a G5.

 > The patch Andrew mentions above converts the Kconfig entry for FB_MATROX to do a
 > "select FB_MACMODES if PPC_PMAC", so dropping matroxfb-compile-error.patch should suffice.

  reply	other threads:[~2005-03-18  9:35 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-18  6:32 Martin J. Bligh
2005-03-18  6:44 ` Andrew Morton
2005-03-18  6:46   ` Martin J. Bligh
2005-03-18  9:29   ` Mikael Pettersson
2005-03-18  9:35     ` Mikael Pettersson [this message]
2005-03-18 15:20       ` Martin J. Bligh
2005-03-18 16:24     ` Joel Schopp
2005-03-20  4:58   ` Martin J. Bligh

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=16954.41169.665960.627306@alkaid.it.uu.se \
    --to=mikpe@csd.uu.se \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mbligh@aracnet.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

all inboxes | Powered by JetHome®