From: Finn Thain <fthain@telegraphics.com.au>
To: Thorsten Glaser <tg@mirbsd.de>
Cc: linux-m68k@vger.kernel.org
Subject: Re: [PATCH 1/1] m68k: add missing I/O macros {in,out}{w,l}_p() for !CONFIG_ISA
Date: Mon, 4 Oct 2010 21:22:52 +1100 (EST) [thread overview]
Message-ID: <alpine.OSX.2.00.1010042115260.285@localhost> (raw)
In-Reply-To: <Pine.BSM.4.64L.1010040906400.22591@herc.mirbsd.org>
[-- Attachment #1: Type: TEXT/PLAIN, Size: 1263 bytes --]
It builds for me if I disable CONFIG_SPEAKUP. Otherwise, I get:
drivers/staging/speakup/speakup_dtlk.c: In function 'synth_probe':
drivers/staging/speakup/speakup_dtlk.c:339: error: implicit declaration of function 'inw_p'
make[3]: *** [drivers/staging/speakup/speakup_dtlk.o] Error 1
make[2]: *** [drivers/staging/speakup] Error 2
make[1]: *** [drivers/staging] Error 2
make: *** [drivers] Error 2
OTOH, I am using my own build of gcc 4.4.4-8 and none of this was built
with apt, so YMMV...
I suppose another alternative would be to omit or reverse the patch that
adds speakup in the first place, if that's more convenient.
Finn
On Mon, 4 Oct 2010, Thorsten Glaser wrote:
> Finn Thain dixit:
>
> >It would be better if we used the same .config, don't you think?
>
> *sigh*
>
> # apt-get source linux-2.6
> # cd linux-2.6-2.6.32
>
> optionally:
> # $EDITOR debian/config/m68k/defines
> ⇒ in [base] comment out everything except “flavours:” and “atari”
> to save time compiling the other images
>
> then:
> # debian/rules clean
> (this may give you an error message)
> # dpkg-buildpackage -B
>
>
> So, no modifications to stock Debian. Well, except for #598893…
>
> bye,
> //mirabilos
>
next prev parent reply other threads:[~2010-10-04 10:22 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-03 18:38 [PATCH 0/1] m68k: add missing I/O macros {in,out}{w,l}_p() for !CONFIG_ISA Thorsten Glaser
2010-10-03 18:48 ` [PATCH 1/1] " Thorsten Glaser
2010-10-04 0:51 ` Finn Thain
2010-10-04 7:40 ` Thorsten Glaser
2010-10-04 8:47 ` Finn Thain
2010-10-04 9:10 ` Thorsten Glaser
2010-10-04 10:22 ` Finn Thain [this message]
2010-10-04 11:30 ` Thorsten Glaser
2010-10-04 13:18 ` Geert Uytterhoeven
2010-10-04 13:33 ` Finn Thain
2010-10-04 13:40 ` Thorsten Glaser
2010-10-04 14:01 ` Geert Uytterhoeven
2010-10-04 14:13 ` Thorsten Glaser
2010-10-04 19:20 ` Thorsten Glaser
2010-10-13 20:17 ` Thorsten Glaser
2010-10-05 12:56 ` Stephen R. Marenka
2010-10-05 14:10 ` debian kernel config, was " Finn Thain
2010-10-06 0:57 ` Stephen R. Marenka
2010-10-06 9:26 ` Thorsten Glaser
2010-10-06 13:09 ` Stephen R. Marenka
2010-10-06 14:15 ` Finn Thain
2010-10-04 7:57 ` Michael Schmitz
2010-10-04 8:13 ` Thorsten Glaser
2010-10-04 9:08 ` Finn Thain
2010-10-04 10:18 ` Thorsten Glaser
2010-10-04 10:51 ` Finn Thain
2010-10-04 11:37 ` Thorsten Glaser
2010-10-04 12:45 ` Finn Thain
2010-10-16 17:12 ` Geert Uytterhoeven
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=alpine.OSX.2.00.1010042115260.285@localhost \
--to=fthain@telegraphics.com.au \
--cc=linux-m68k@vger.kernel.org \
--cc=tg@mirbsd.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