linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@mandrakesoft.com>
To: Michael Schmitz <schmitz@opal.biophys.uni-duesseldorf.de>
Cc: Paul Mackerras <paulus@linuxcare.com>,
	Linux/PPC Developer list <linuxppc-dev@lists.linuxppc.org>
Subject: Re: PPC should not use -fno-builtin (was Re: 2.3.47 imac build?)
Date: Tue, 29 Feb 2000 12:51:01 -0500	[thread overview]
Message-ID: <38BC0705.93C1D390@mandrakesoft.com> (raw)
In-Reply-To: Pine.LNX.4.10.10002291744130.4907-100000@opal.biophys.uni-duesseldorf.de


Michael Schmitz wrote:
> Patch appended (adbmouse.o is only built if CONFIG_BUSMOUSE is set and
> make complained about getting busmouse.o twice in the target line, so
> there).

Ignore the complaint, this patch is wrong.

With the "new-style" makefiles, adding busmouse.o to the end of the line
is the correct way to specify dependencies.  If your patch is applied, I
cannot build adbmouse into my kernel, as busmouse.o is never referenced
nor built.



> --- 2.3.48-devel/drivers/char/Makefile.org      Tue Feb 29 17:52:59 2000
> +++ 2.3.48-devel/drivers/char/Makefile  Tue Feb 29 16:42:32 2000
> @@ -154,7 +154,7 @@
>  obj-$(CONFIG_MIXCOMWD) += mixcomwd.o
>  obj-$(CONFIG_AMIGAMOUSE) += amigamouse.o
>  obj-$(CONFIG_ATARIMOUSE) += atarimouse.o
> -obj-$(CONFIG_ADBMOUSE) += adbmouse.o busmouse.o
> +obj-$(CONFIG_ADBMOUSE) += adbmouse.o
>  obj-$(CONFIG_PC110_PAD) += pc110pad.o
>  obj-$(CONFIG_WDT) += wdt.o
>  obj-$(CONFIG_RTC) += rtc.o

--
Jeff Garzik              | "Are you the police?"
Building 1024            |
MandrakeSoft, Inc.       | "No ma'am.  We're musicians."

** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

  reply	other threads:[~2000-02-29 17:51 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <38BAF958.E31D88A3@mandrakesoft.com>
2000-02-29  0:49 ` PPC should not use -fno-builtin (was Re: 2.3.47 imac build?) Paul Mackerras
2000-02-29 17:03   ` Michael Schmitz
2000-02-29 17:51     ` Jeff Garzik [this message]
2000-02-29 18:24     ` Benjamin Herrenschmidt
2000-02-29 19:21       ` Michael Schmitz
2000-02-29 23:07         ` Andreas Tobler
2000-03-01  8:49           ` Michael Schmitz

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=38BC0705.93C1D390@mandrakesoft.com \
    --to=jgarzik@mandrakesoft.com \
    --cc=linuxppc-dev@lists.linuxppc.org \
    --cc=paulus@linuxcare.com \
    --cc=schmitz@opal.biophys.uni-duesseldorf.de \
    /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).