[Lcdproc] lis driver fails to compile

[Daryl F]

On Thu, 1 Nov 2007 20:41:23 +0100
Peter Marschall <peter@adpm.de> wrote:

> Hi Mrkus,
> 
> thanks for reporting it,
> 
> On Thursday, 1. November 2007, Markus Dolze wrote:
> > as mentioned in my previous mail, the lis driver fails to compile.
> > The error is:
> >
> > if gcc -DHAVE_CONFIG_H -I. -I. -I../..  -I../..
> > -I/usr/local/include -fPIC -Wall -O2 -fno-strict-aliasing -pipe  -g
> > -Wno-unused-function -MT lis-lis.o -MD -MP -MF ".deps/lis-lis.Tpo"
> > -c -o lis-lis.o `test -f 'lis.c' || echo './'`lis.c;  then mv -f
> > ".deps/lis-lis.Tpo" ".deps/lis-lis.Po"; else rm -f
> > ".deps/lis-lis.Tpo"; exit 1; fi lis.c: In function `lis_init':
> > lis.c:512: warning: implicit declaration of function `clone'
> > lis.c:512: error: `CLONE_VM' undeclared (first use in this function)
> > lis.c:512: error: (Each undeclared identifier is reported only once
> > lis.c:512: error: for each function it appears in.)
> > lis.c:512: error: `CLONE_THREAD' undeclared (first use in this
> > function) lis.c:512: error: `CLONE_SIGHAND' undeclared (first use
> > in this function) *** Error code 1
> >
> > Stop in /usr/home/mmdolze/smoketest/lcdproc/testing/server/drivers.
> >
> > It reads like something thread programming related. Currently I
> > have no clue how to do these sort of things in FreeBSD.
> 
> The clone() call is indeed Linux-specific, I fear.
> 
> So I see little chance to get it working unchanged in other OSes.
> I guess, a possible (kludgy) workaround might be to disable the
> compilation of this driver for other OSes than Linux and mention
> it in the docs.
> 
> Another alternative is to have the original author of the driver,
> which I Cc'ed this mail, have another look on it and maybe find a way
> to get rid of the Linux-specific way of controlling the display.
> 
> Daryl,
> is there a chance to get the lis driver working without that clone()
> call that seems to only exist in Linux?
> 
> Kind Regards
> Peter
> 

Peter,
I'll take a look at it and see if Rene's suggestion, in a later
posting, to use POSIX threads will allow better portability. I don't
want this to be a Linux-centric driver unless it absolutely must.

On another topic, I first tried to reply to your request using
daryl@rainyday.ca but I'm in the process of migrating to
wyatt@prairieturtle.ca. I've already deleted my old daryl@rainday.ca
membership to this list so my first reply went into moderation due to
non-membership. Sorry about that.

Regards,
Daryl