From: Hetz Ben Hamo <hetz@softier.com>
To: linux-fbdev-devel@lists.sourceforge.net
Subject: Framebuffer fbtest issues
Date: Wed, 26 Nov 2003 12:15:05 +0200 [thread overview]
Message-ID: <200311261215.05761.hetz@softier.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 644 bytes --]
Hi,
I took the fbtest from the CVS and compiled it. It seems it needs some
updating ;)
in the fbtest/pnmtohex/Makefile - it won't compile, as the NetPBM library has
been changed, so you'll need to install it and change the Makefile to
something like:
LIBS += -lnetpbm
One weird issue - the netpbm package that comes with redhat doesn't compile
the fbtest - any suggestions why? (same in mandrake) - only installing the
netpbm from sourceforge seems to help (and modifying the Makefile)..
I'm also enclosing sort of README to save others the hair tearing I had here
;)
Could someone please commit those changes to CVS?
Thanks,
Hetz
[-- Attachment #2: README --]
[-- Type: text/english, Size: 674 bytes --]
Framebuffer test "suite"
------------------------
This is a package which contains 10 tests to make sure your framebuffer works.
In order to compile it, you'll need NetPBM to be installed first
(http://netpbm.sf.net) and make sure your libnetpbm.so files are correctly known
to the either your LD_LIBRARY_PATH or to your /etc/ld.so.conf (in Linux)
After compiling (a simple "make" should do the job), you can run the test by
runnning: ./fbtest
On some machines, running the fbtest might take a bit of pause and then the demos
will run, so you might want to launch the fbtest with: ./fbtest -d -v
Good Luck,
The framebuffer development team
(http://linux-fbdev.sf.net)
next reply other threads:[~2003-11-26 10:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-26 10:15 Hetz Ben Hamo [this message]
2003-11-27 3:39 ` Framebuffer fbtest issues John Zielinski
2003-11-27 10:04 ` Geert Uytterhoeven
2003-11-28 2:46 ` John Zielinski
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=200311261215.05761.hetz@softier.com \
--to=hetz@softier.com \
--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).