From: Josh Kindler <josh@antihype.com>
To: <linuxppc-dev@lists.linuxppc.org>
Subject: atyfb problems?
Date: Sun, 13 Aug 2000 11:06:34 -0500 [thread overview]
Message-ID: <B5BC31B9.2C74%josh@antihype.com> (raw)
Hmm... I jsut got the latest (as of last night) rsync of Ben's kernel. When
I compiled it, I got the following error. Previous kernels compiled fine, is
this a known issue or am I just stupid?
atyfb.c:641: redefinition of `reset_GTC_3D_engine'
atyfb.c:631: `reset_GTC_3D_engine' previously defined here
{standard input}: Assembler messages:
{standard input}:525: Fatal error: Symbol reset_GTC_3D_engine already
defined.
atyfb.c: In function `atyfb_set_cmap':
atyfb.c:2318: Internal compiler error:
atyfb.c:2318: output pipe has been closed
cpp: output pipe has been closed
make[3]: *** [atyfb.o] Error 1
make[3]: Leaving directory `/usr/src/linux-pmac-benh/drivers/video'
make[2]: *** [first_rule] Error 2
make[2]: Leaving directory `/usr/src/linux-pmac-benh/drivers/video'
make[1]: *** [_subdir_video] Error 2
make[1]: Leaving directory `/usr/src/linux-pmac-benh/drivers'
make: *** [_dir_drivers] Error 2
Also I have an (AFAIK) unresolved airport problem:
I can compile it fine, but then when I insmod it i get:
airport.o: unresolved symbol isa_io_base
What is this all about?
--
Josh Kindler || antihype.com
ICQ#25956850 || AIM: joeschmo6
Linux users do it in the open.
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next reply other threads:[~2000-08-13 16:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-08-13 16:06 Josh Kindler [this message]
2000-08-13 15:33 ` atyfb problems? Nelson Abramson
2000-08-14 20:34 ` 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=B5BC31B9.2C74%josh@antihype.com \
--to=josh@antihype.com \
--cc=linuxppc-dev@lists.linuxppc.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 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.