LCDproc development and user support list

Text archives Help

[Lcdproc] CVS: reporting patch

Chronological Thread 
  • From: reenoo AT (Rene Wagner)
  • Subject: [Lcdproc] CVS: reporting patch
  • Date: Fri Nov 30 16:40:01 2001

"Joris Robijn"
<joris AT>
> > 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 ?

Well ... no ;)
I'll have a look at lcdm001.c anyway, so I can modify MtxOrb.c as well.
Changing joy.c shouldn't be too much as well ;)

> Or
> shall I reinstall the debug_level variable and give it the same value
> as report_level from report.h ?

For compatiblity reasons you should do so, I think ;)

> 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)

I don't know anything about that driver :(

> It does compile, but it does not link.
Well, of course ;) Sorry!

> The rest compiles and links.

Good to hear ;)


Archive powered by MHonArc 2.6.18.

Top of page