From: Sven Luther <sven.luther@wanadoo.fr>
To: linux-fbdev-devel@lists.sourceforge.net
Subject: radeonfb on linuxppc_2_4 tree ...
Date: Mon, 16 Jun 2003 18:55:34 +0200 [thread overview]
Message-ID: <20030616165534.GA6319@iliana> (raw)
Hello,
I am trying to build a linuxppc_2_4 bk tree checked out with the 2.4.21
tag. But i get this error :
radeonfb.c: Dans la fonction « radeonfb_pci_register »:
radeonfb.c:1004: error: `PCI_DEVICE_ID_RADEON_LY' undeclared (first use in this function)
radeonfb.c:1004: error: (Each undeclared identifier is reported only once
radeonfb.c:1004: error: for each function it appears in.)
radeonfb.c:1005: error: `PCI_DEVICE_ID_RADEON_LZ' undeclared (first use in this function)
radeonfb.c: Hors de toute fonction :
radeonfb.c:820: attention : `OUTMC' declared `static' but never defined
radeonfb.c:821: attention : `INMC' declared `static' but never defined
radeonfb.c:822: attention : `radeon_pm_disable_dynamic_mode' declared `static' but never defined
radeonfb.c:823: attention : `radeon_pm_enable_dynamic_mode' declared `static' but never defined
radeonfb.c:824: attention : `radeon_pm_yclk_mclk_sync' declared `static' but never defined
radeonfb.c:825: attention : `radeon_pm_program_mode_reg' declared `static' but never defined
radeonfb.c:826: attention : `radeon_pm_enable_dll' declared `static' but never defined
radeonfb.c:827: attention : `radeon_pm_full_reset_sdram' declared `static' but never defined
make[4]: *** [radeonfb.o] Erreur 1
Is this an error of my checkout, or a problem with the 2.4.21 tag of the
linuxppc_2_4 tree ?
Friendly,
Sven Luther
-------------------------------------------------------
This SF.NET email is sponsored by: eBay
Great deals on office technology -- on eBay now! Click here:
http://adfarm.mediaplex.com/ad/ck/711-11697-6916-5
next reply other threads:[~2003-06-16 16:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-16 16:55 Sven Luther [this message]
2003-06-16 17:11 ` radeonfb on linuxppc_2_4 tree Benjamin Herrenschmidt
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=20030616165534.GA6319@iliana \
--to=sven.luther@wanadoo.fr \
--cc=linux-fbdev-devel@lists.sourceforge.net \
/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).