From: Andreas Tobler <toa@pop.agri.ch>
To: Stefan Jeglinski <jeglin@4pi.com>
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: can't build 2.4.0-test1; matroxfb parse error?
Date: Wed, 21 Jun 2000 07:59:36 +0200 [thread overview]
Message-ID: <395059C7.25168900@pop.agri.ch> (raw)
In-Reply-To: v04220800b575b0dd6382@[192.168.0.1]
Stefan Jeglinski wrote:
>
> I just rsynced to the linux-pmac-devel tree to try the latest compile
> on my PM6500. I believe this is 2.4.0-test1. With all default config
> options, I get this error:
>
> matroxfb_base.c:1146: parse error before `matroxfb_set_cmap'
> make[4]: *** [matroxfb_base.o] Error 1
>
> I'm using /gcc version 2.95.2 19991024 (release/franzo)/ if that
> makes any difference. I don't know how to handle a "parse error."
> What is it and how might I fix it (or do I just not compile with
> matrox support for now)?
diff -u --recursive linux-2.4.0-test1-ac21.orig/drivers/video/matrox/matroxfb_base.c
linux-2.4.0-test1-ac21/drivers/video/matrox/matroxfb_base.c
--- linux-2.4.0-test1-ac21.orig/drivers/video/matrox/matroxfb_base.c
Sun Jun 18 17:41:02 2000
+++ linux-2.4.0-test1-ac21/drivers/video/matrox/matroxfb_base.c Sun Jun
18 18:24:44 2000
@@ -1143,7 +1143,7 @@
fb_get_var: matroxfb_get_var,
fb_set_var: matroxfb_set_var,
fb_get_cmap: matroxfb_get_cmap,
- fb_set_cmap matroxfb_set_cmap,
+ fb_set_cmap: matroxfb_set_cmap,
fb_pan_display: matroxfb_pan_display,
fb_ioctl: matroxfb_ioctl,
};
If you get more look on the lkml there is a patch for that topic.
Subject:[PATCH] 2.4.0-test1-ac1 - misc typo in drivers/video II 18.6
Andreas
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
prev parent reply other threads:[~2000-06-21 5:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-06-20 23:39 can't build 2.4.0-test1; matroxfb parse error? Stefan Jeglinski
2000-06-21 5:59 ` Andreas Tobler [this message]
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=395059C7.25168900@pop.agri.ch \
--to=toa@pop.agri.ch \
--cc=jeglin@4pi.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 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).