LCDproc development and user support list

Text archives Help


[Lcdproc] CVS: reporting patch


Chronological Thread 
  • From: joris AT robijn.net (Joris Robijn)
  • Subject: [Lcdproc] CVS: reporting patch
  • Date: Fri Nov 30 16:28:01 2001

On 30 Nov 2001, at 16:37, Rene Wagner wrote:

> Hi all!
>
> I've added #include <string.h> to report.c.
> Now gcc returns no warnings any more ;)

Ah. I had not seen it. Maybe I did not get it because the definition
was also in an other header.

> Joris,
> what changes have to be applied to the drivers, so that LCDd compiles
> again?

None. report.h is a new file. If debug.h is used that still works.
I did adapt the text and sed1330 driver to use report.h.

> drivers/libLCDdrivers.a(lcdm001.o): In function `lcdm001_init':
> lcdm001.o(.text+0x19a): undefined reference to `debug_level'
> drivers/libLCDdrivers.a(lcdm001.o): In function `lcdm001_clear':
> lcdm001.o(.text+0x41d): undefined reference to `debug_level'
> drivers/libLCDdrivers.a(lcdm001.o): In function `lcdm001_vbar':
> lcdm001.o(.text+0x455): undefined reference to `debug_level'
> lcdm001.o(.text+0x4bd): undefined reference to `debug_level'
> lcdm001.o(.text+0x4ef): undefined reference to `debug_level'
> drivers/libLCDdrivers.a(lcdm001.o)(.text+0x591): more undefined references
> to
> `debug_level' follow
> collect2: ld returned 1 exit status

Hmm. the lcdm001.h, MtxOrb and joy drivers expect debug_level to be
defined somewhere. Shall I modify these drivers to use report.h ? Or
shall I reinstall the debug_level variable and give it the same value
as report_level from report.h ?

Also, it seems t6963 wants some inb_p and outb_p that are unknown on
my system (Debian):
server/drivers/t6963.c:150: undefined reference to `inb_p'
(many of these messages)
It does compile, but it does not link.

The rest compiles and links.

Joris

--
Joris Robijn
<joris AT robijn.net>
Home: 053 4311 553
Mobile: 06 288 41 964

// To understand recursion, we must first understand recursion




Archive powered by MHonArc 2.6.18.

Top of page