Hi all,

I have been having linking errors for the past week or so (haven't had
much time to try) with csound5, I think having to do with FLTK and X
libs (perhaps they're out of order, not sure what it was).  I gave up on
that and went for a non-gui compile and was met with other linking
errors.  I had to modify the SConstruct file to add the dl, pthread, and
m to get past all those linking errors.

Before I commit anything, I'd like to make sure if this seems correct
that those libs should be necessary for a non-FLTK compile.

Thanks,
steven

On Sat, 8 May 2004, stevenyi wrote:

> Hi all,
> 
> I have been having linking errors for the past week or so (haven't had
> much time to try) with csound5, I think having to do with FLTK and X
> libs (perhaps they're out of order, not sure what it was).  I gave up on
> that and went for a non-gui compile and was met with other linking
> errors.  I had to modify the SConstruct file to add the dl, pthread, and
> m to get past all those linking errors.
> 

the dl library/bundle is certainly needed for opcode loading.  The m 
library should (in a sane C system) be scanned automatically, but with gcc 
is certainly always nbeeded.  Not so sure about pthread, but I would have 
zero surprise if it were required.  I assume this is OSX?  I was going to 
try that later today.

==John ff

Oh no, this is on Fedora Linux.  I sort of hacked up the SConstruct file
when I put the libs in so I'll check in something when I can get it done
cleanly.

steven

On Sun, 2004-05-09 at 02:16, John ffitch wrote:
> On Sat, 8 May 2004, stevenyi wrote:
> 
> > Hi all,
> > 
> > I have been having linking errors for the past week or so (haven't had
> > much time to try) with csound5, I think having to do with FLTK and X
> > libs (perhaps they're out of order, not sure what it was).  I gave up on
> > that and went for a non-gui compile and was met with other linking
> > errors.  I had to modify the SConstruct file to add the dl, pthread, and
> > m to get past all those linking errors.
> > 
> 
> the dl library/bundle is certainly needed for opcode loading.  The m 
> library should (in a sane C system) be scanned automatically, but with gcc 
> is certainly always nbeeded.  Not so sure about pthread, but I would have 
> zero surprise if it were required.  I assume this is OSX?  I was going to 
> try that later today.
> 
> ==John ff
> 
>