This is because somebody has #included an X header from a FLTK source file
or header file. You should easily be able to fix it.

Original Message:
-----------------
From: steven stevenyi@csounds.com
Date: Mon, 08 Dec 2003 13:10:16 -0800
To: csound-dev@eartha.mills.edu
Subject: [CSOUND-DEV:3726] Re: csound4 - configure.ac, main.c


Almost.  But it's an unrelated error:

libcsound.a(winFLTK.o)(.text+0x11): In function `Graphable_':
/cygdrive/f/eclipse/workspace/csound4/csound/winFLTK.c:44: undefined 
reference t
o `_XOpenDisplay'

Don't know much about this one.  I'm going to disable graphics and fltk 
and give it another whirl in a second.

steven

John D. Ramsdell wrote:

>So is it now building for you once again?
>
>John
>
>steven  writes:
>
>  
>
>>Hi all,
>>
>>I changed the setting on configure.ac to binary so that it will
>>maintain it's unix endlines.  Also, I've changed main.c to #ifdef for
>>SIGALRM as mentioned in a previous email. Thanks,
>>steven
>>    
>>
>
>
>
>  
>


--------------------------------------------------------------------
mail2web - Check your email from the web at
http://mail2web.com/ .

I'll try again tomorrow for this one (want to spend time back on csound5 
to update the plugin opcodes to compile with the ENVIRON changes).  For 
the time being, csound compiles fine using:

configure --enable-cygwin=no --with-fltk=no

So that's working great.

steven

gogins@pipeline.com wrote:

>This is because somebody has #included an X header from a FLTK source file
>or header file. You should easily be able to fix it.
>
>Original Message:
>-----------------
>From: steven stevenyi@csounds.com
>Date: Mon, 08 Dec 2003 13:10:16 -0800
>To: csound-dev@eartha.mills.edu
>Subject: [CSOUND-DEV:3726] Re: csound4 - configure.ac, main.c
>
>
>Almost.  But it's an unrelated error:
>
>libcsound.a(winFLTK.o)(.text+0x11): In function `Graphable_':
>/cygdrive/f/eclipse/workspace/csound4/csound/winFLTK.c:44: undefined 
>reference t
>o `_XOpenDisplay'
>
>Don't know much about this one.  I'm going to disable graphics and fltk 
>and give it another whirl in a second.
>
>steven
>
>  
>
>  
>

It is because, as stated in earlier e-mail, I have only used the FLTY 
graphics on X, and I used the same check as X uses to see if there is a 
screen on which to draw.  The correct fix is to find something else to see 
if there is a screen.
==John ff