RE: [lcd4linux] rpl_malloc?

[Luis.F.Correia <Lui...@se...>]

> [...]
> > dvb.c: In function `DVB':
> > dvb.c:57: warning: implicit declaration of function `error'
> 
> This has been fixed in CVS. But it's only a warning :-)

No problem. I do tend to ignore such errors

> > lcd4linux.o: In function `main':
> > /bering/lcd4linux-0.9.9/lcd4linux.c:308: undefined 
> reference to `rpl_malloc'
> > collect2: ld returned 1 exit status
> 
> Hmm... I looked things up on the internet, and found this a little 
> glitch or bug in the autoconf area.
> 
> Could you please try to comment out the "AC_FUNC_MALLOC" line from 
> configure.in?
> 

I did commented out the #define malloc rpl_malloc in config.h, and
all went well

Now I do have another issue, since our firewall distro came out,
Bering-uClibc, i have been using lcdproc as a primary display.

But now that we have secured our firewall with the grsecurity
patches, 'previledge io' (ioperm()) does not work anymore...

So, logically i switched to test LCD4linux, using the parport
device.

Our firewall's filesystem is in RAM and is rebuilt on every boot.
Meaning that all /dev entries must be created also.

I need some help here, to use parport.o and to have the device
correctly created, what do I need to do?

Thanks!