[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[fluid-dev] Re: fluidsynth and jack on mac

From: Josh Green
Subject: [fluid-dev] Re: fluidsynth and jack on mac
Date: Sun, 07 Mar 2004 13:32:48 -0800

On Mon, 2004-03-08 at 11:51, Ebrahim Mayat wrote:
> Hi
> I am trying to compile fluidsynth(1.0.3) on Mac OS X.3.2. Having
> readwith much interest the thread entitled "fluidsynth and jack on
> mac" inthe [fluid-dev] archives, I wondered if you had since
> compiledfluidsynth. I have installed Jack-0.82.0 that I obtained
> from<http://www.jackosx.com>  and MidiShare-1.87 downloaded from the
> ftpsite of IRCAM.
> My configure command was:
>         ./configure CPPFLAGS="-I/sw/include"
>         LDFLAGS="-L/sw/lib"--enable-midishare="-L/usr/lib"
> --enable-jack-support="/usr/local/bin"JACK_CFLAGS="/usr/local/include-L/Library/Frameworks/Jack.framework/Headers"JACK_LIBS="--L/usr/local/lib
>  -framework jack -ldl -lpthread -lSystem"
> While the configuration summary shows that both MidiShare and Jackhave
> been detected:
>         **************************************************************
>         Summary:
>         ALSA:                  no
>         OSS:                   no
>         MidiShare:             yes
>         JACK:                  yes
>         CoreAudio:             yes
>         Readline:              yes
>         LADCCA support:        no
>         Debug:                 no
>         Profiling:             no
>         LADSPA support:        no
>         use long long:         no
>         Pentium 3+ SSE:        no
>         **************************************************************
> configure also warns me that Midishare.h could not becompiled and the
> JACK_LIBS variable still indicates -ljack and -lrt.So, in the Makefile
> 1. I systematically changed "-ljack" to "framework jack" according
> toSt├ęphane Letz's advice and 
> 2."-lrt" to "-lSystem" since the real time extensions library
> (librt)which exists on Linux is not present on OS X, and libSystem
> containsthe interface functions on OS X.
> Consequently, "make" compiles a substantial part of the source
> filesbut finally complains about linking and undefined symbols: 
>         ld: warning prebinding disabled because dependent
>         library:/usr/local/lib/libfluidsynth.1.dylib is not prebound
>         ld: warning multiple definitions of symbol _BC
>         /sw/lib/libreadline.dylib(terminal.so) definition of _BC
>         /sw/lib/libncurses.dylib(lib_termcap.o) definition of _BC
>         ld: warning multiple definitions of symbol _UP
>         /sw/lib/libreadline.dylib(terminal.so) definition of _UP
>         /sw/lib/libncurses.dylib(lib_termcap.o) definition of _UP
>         ld: warning multiple definitions of symbol _PC
>         /sw/lib/libreadline.dylib(terminal.so) definition of _PC
>         /sw/lib/libncurses.dylib(lib_tputs.o) definition of _PC
>         ld: Undefined symbols:
>         _jack_activate
>         _jack_client_close
>         _jack_client_new
>         _jack_connect
>         _jack_get_ports
>         _jack_get_sample_rate
>         _jack_on_shutdown
>         _jack_port_get_buffer
>         _jack_port_name
>         _jack_port_register
>         _jack_set_buffer_size_callback
>         _jack_set_process_callback
>         _jack_set_sample_rate_callback
>         make[2]: *** [fluidsynth] Error 1
>         make[1]: *** [all] Error 2
>         make: *** [all-recursive] Error 1
> I find this strange since these undefined symbols are all declared
> inthe "jack.h" header present in
> "/Library/Frameworks/Jack.framework/Headers".
> I presume that you have succeeded in compiling fluidsynth togetherwith
> MidiShare and Jack support. I would appreciate it if you couldshare
> some of your wisdom with me on this subject. 
> Many thanks.
> Ebrahim Mayat 
> ---------------------------------------------------------------------------------------------------
> Ebrahim Mayat Ph.D. (Neurochemist & Cell Biologist)
> 64 Mint Road
> Fordsburg
> Johannesburg 2092
> South Africa

I'm CC'ing the FluidSynth developers list since this is a good thread to
continue discussion on. I myself have not given the OS X version a try
(beyond some of the work I was doing last year).
Its nice to hear that OS X has Jack support. This sounds like the best
option, since the native CoreAudio driver has had some problems. What
does the link command look like during the build? Does it have -ljack,
or something similar? Make sure the Jack library is being linked in at
the last stage. It would be nice to provide a package of FluidSynth for
OS X eventually, to make things nice and convenient. Regards,
        Josh Green

reply via email to

[Prev in Thread] Current Thread [Next in Thread]