From: Neilen Marais <brick@adept.co.za>
To: linux-kernel@vger.kernel.org
Subject: aty128fb.c does not compile in linux 2.5.46
Date: Sat, 9 Nov 2002 19:04:05 +0200 [thread overview]
Message-ID: <20021109190405.A17671@brickbox.egghead> (raw)
Hi.
I don't know if its currently considered important, but just for the
record.
Please CC any replies to me, since I am not subscribed to the list.
I'm running an AMD Duron/Via kt133, with Debian testing. Nothing
unusual that
I am aware of. If I choose to use the ATI Rage128 framebuffer console,
I get
the following compile error:
gcc -Wp,-MD,drivers/video/.aty128fb.o.d -D__KERNEL__ -Iinclude -Wall
-Wstrict-prototypes -Wno-trigraphs -O2 -fomit-frame-pointer
-fno-strict-aliasing -fno-common -pipe -mpreferred-stack-boundary=2
-march=i686 -malign-functions=4 -Iarch/i386/mach-generic
-nostdinc -iwithprefix include -DKBUILD_BASENAME=aty128fb -c -o
drivers/video/aty128fb.o drivers/video/aty128fb.c
drivers/video/aty128fb.c:419: unknown field `fb_get_fix' specified in
initializer
drivers/video/aty128fb.c:419: warning: initialization from incompatible
pointer type
drivers/video/aty128fb.c:420: unknown field `fb_get_var' specified in
initializer
drivers/video/aty128fb.c:420: warning: initialization from incompatible
pointer type
drivers/video/aty128fb.c: In function `aty128fb_set_var':
drivers/video/aty128fb.c:1379: structure has no member named `visual'
drivers/video/aty128fb.c:1380: structure has no member named `type'
drivers/video/aty128fb.c:1381: structure has no member named `type_aux'
drivers/video/aty128fb.c:1382: structure has no member named `ypanstep'
drivers/video/aty128fb.c:1383: structure has no member named `ywrapstep'
drivers/video/aty128fb.c:1384: structure has no member named
`line_length'
make[2]: *** [drivers/video/aty128fb.o] Error 1
make[1]: *** [drivers/video] Error 2
make: *** [drivers] Error 2
Cheers
Neilen
next reply other threads:[~2002-11-09 17:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-09 17:04 Neilen Marais [this message]
2002-11-09 19:40 ` Matt Reppert
2002-11-11 18:14 ` James Simmons
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=20021109190405.A17671@brickbox.egghead \
--to=brick@adept.co.za \
--cc=linux-kernel@vger.kernel.org \
/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®