On Wednesday 14 July 2004 04:08 am, Chris Cannam wrote:
> problem, but at the moment it is. Hence dssi.pc, which just contains
> information about where to find dssi.h and what version you have.
Gotcha. I don't guess I could just copy the header and the .pc file and skip
the rest could I?
> > make[1]: Entering directory `/home/silvan/CVS/dssi/examples'
> > cc dssi_example_host.o message_buffer.o -ljack -lasound
> > -lpthread -llo -o dssi_example_host
> > /usr/bin/ld: cannot find -llo
>
> Not obvious to me either why this should happen. Where is liblo,
> according to, say, ldd on the rosegarden binary? I guess if you run
> "pkg-config liblo --libs" it just says "-llo", with no directory?
It doesn't say, no. There's also a test program with that. testlo?
Something to that effect. It also worked fine. The files are right where
they should be.
->strace -eopen ld -llo
[cut]
open("/usr/lib/liblo.so", O_RDONLY) = -1 ENOENT (No such file or
directory)
[cut]
ld: cannot find -llo
Well hell. It's looking for liblo.so
->ls /usr/lib/liblo*
/usr/lib/liblo@ /usr/lib/liblo.0.0.0* /usr/lib/liblockfile.so.1@
/usr/lib/liblo.0@ /usr/lib/liblo.la* /usr/lib/liblockfile.so.1.0
But...
->ldd `which rosegarden`|grep liblo
liblo.0 => /usr/lib/liblo.0 (0x41419000)
Damn puzzling. Maybe this will be a great revelation to you. .so .a .la, I
don't really appreciate the difference. Something to do with static vs.
dynamic linking, but I don't know which is for which, or how to change from
one behavior to the other at compile time.
->ldd testlo
not a dynamic executable
<shrug> Sorry, Chief. I guess I have some learning to do.
> Dammit, I forgot about all that. Oh dear. It shouldn't require
> libfluidsynth-dev though, because it already requires the fluidsynth
> sources -- it should just need libfluidsynth on top of that.
There's no fluidsynth.h in the *src* directory. That's what it is, now that
I've had a closer look. So installing the -dev package makes it findable
without having to explicitly -I it.
> > I was playing with it yesterday, I think, but it's broken now.
>
> You mean xsynth is broken for you as well? or that just everything is
> generally broken as you just explained?
I can't compile the plugin support into RG until I sort this out, and I didn't
keep a copy of yesterday's binary.
--
Michael McIntyre ---- Silvan <[EMAIL PROTECTED]>
Linux fanatic, and certified Geek; registered Linux user #243621
http://www.geocities.com/Paris/Rue/5407/
-------------------------------------------------------
This SF.Net email sponsored by Black Hat Briefings & Training.
Attend Black Hat Briefings & Training, Las Vegas July 24-29 -
digital self defense, top technical experts, no vendor pitches,
unmatched networking opportunities. Visit www.blackhat.com
_______________________________________________
Rosegarden-devel mailing list
[EMAIL PROTECTED] - use the link below to unsubscribe
https://lists.sourceforge.net/lists/listinfo/rosegarden-devel
