From: Joshua Uziel <uzi@uzix.org>
To: Horst von Brand <vonbrand@inf.utfsm.cl>
Cc: linux-kernel@vger.kernel.org, sparclinux@vger.kernel.org
Subject: Re: 2.4.0 on sparc64 build problems
Date: Fri, 5 Jan 2001 16:00:21 -0800 [thread overview]
Message-ID: <20010105160021.A18483@gimp.org> (raw)
In-Reply-To: <200101051721.f05HLaP21812@pincoya.inf.utfsm.cl>
In-Reply-To: <200101051721.f05HLaP21812@pincoya.inf.utfsm.cl>; from vonbrand@inf.utfsm.cl on Fri, Jan 05, 2001 at 02:21:35PM -0300
* Horst von Brand <vonbrand@inf.utfsm.cl> [010105 09:24]:
> Sun Ultra 1, RH 6.2 + updates (+ local hacks)
>
> Building modules:
>
> In drivers/sbus/audio:
>
> amd7930.c:113: ../../isdn/hisax/foreign.h: No such file or directory
> amd7930.c:1159: warning: function declaration isn't a prototype
> amd7930.c: In function `amd7930_dxmit':
> amd7930.c:1266: warning: assignment from incompatible pointer type
> amd7930.c: In function `amd7930_drecv':
> amd7930.c:1312: warning: assignment from incompatible pointer type
> amd7930.c: At top level:
> amd7930.c:1486: variable `amd7930_foreign_interface' has initializer but incomplete type
> [Ad nauseam]
>
> dbri.c:67: ../../isdn/hisax/foreign.h: No such file or directory
> [More or less the same junk as above]
I'm wondering why building those drivers are options at all on sparc64
since none of the sparc64 machines (that I know of) currently available
have anything other than the cs4231 or no audio support.
Basically, those two should be removed from the config options for
sparc64... and in the meantime, you should build without 'em. :)
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2001-01-06 0:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-05 17:21 2.4.0 on sparc64 build problems Horst von Brand
2001-01-05 23:44 ` David S. Miller
2001-01-06 2:27 ` Kai Germaschewski
2001-01-06 0:00 ` Joshua Uziel [this message]
2001-01-06 0:15 ` David S. Miller
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=20010105160021.A18483@gimp.org \
--to=uzi@uzix.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sparclinux@vger.kernel.org \
--cc=vonbrand@inf.utfsm.cl \
/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.