Problem compiling bristol-0.30.3

Help
cinder
2009-01-07
2013-05-23
  • cinder

    cinder - 2009-01-07

    I'm running 64studio and Just tried to compile after reading a HOW-TO at the 64studio forums.
    After ./configure:

    checking for a BSD-compatible install... /usr/bin/install -c
    checking whether build environment is sane... yes
    checking for gawk... no
    checking for mawk... mawk
    checking whether make sets $(MAKE)... yes
    checking build system type... i686-pc-linux-gnu
    checking host system type... i686-pc-linux-gnu
    checking for style of include used by make... GNU
    checking for gcc... gcc
    checking for C compiler default output file name... a.out
    checking whether the C compiler works... yes
    checking whether we are cross compiling... no
    checking for suffix of executables...
    checking for suffix of object files... o
    checking whether we are using the GNU C compiler... yes
    checking whether gcc accepts -g... yes
    checking for gcc option to accept ISO C89... none needed
    checking dependency style of gcc... gcc3
    checking for a sed that does not truncate output... /bin/sed
    checking for grep that handles long lines and -e... /bin/grep
    checking for egrep... /bin/grep -E
    checking for ld used by gcc... /usr/bin/ld
    checking if the linker (/usr/bin/ld) is GNU ld... yes
    checking for /usr/bin/ld option to reload object files... -r
    checking for BSD-compatible nm... /usr/bin/nm -B
    checking whether ln -s works... yes
    checking how to recognize dependent libraries... pass_all
    checking how to run the C preprocessor... gcc -E
    checking for ANSI C header files... yes
    checking for sys/types.h... yes
    checking for sys/stat.h... yes
    checking for stdlib.h... yes
    checking for string.h... yes
    checking for memory.h... yes
    checking for strings.h... yes
    checking for inttypes.h... yes
    checking for stdint.h... yes
    checking for unistd.h... yes
    checking dlfcn.h usability... yes
    checking dlfcn.h presence... yes
    checking for dlfcn.h... yes
    checking for g++... g++
    checking whether we are using the GNU C++ compiler... yes
    checking whether g++ accepts -g... yes
    checking dependency style of g++... gcc3
    checking how to run the C++ preprocessor... g++ -E
    checking for g77... no
    checking for xlf... no
    checking for f77... no
    checking for frt... no
    checking for pgf77... no
    checking for cf77... no
    checking for fort77... no
    checking for fl32... no
    checking for af77... no
    checking for xlf90... no
    checking for f90... no
    checking for pgf90... no
    checking for pghpf... no
    checking for epcf90... no
    checking for gfortran... no
    checking for g95... no
    checking for xlf95... no
    checking for f95... no
    checking for fort... no
    checking for ifort... no
    checking for ifc... no
    checking for efc... no
    checking for pgf95... no
    checking for lf95... no
    checking for ftn... no
    checking whether we are using the GNU Fortran 77 compiler... no
    checking whether  accepts -g... no
    checking the maximum length of command line arguments... 98304
    checking command to parse /usr/bin/nm -B output from gcc object... ok
    checking for objdir... .libs
    checking for ar... ar
    checking for ranlib... ranlib
    checking for strip... strip
    checking if gcc supports -fno-rtti -fno-exceptions... no
    checking for gcc option to produce PIC... -fPIC
    checking if gcc PIC flag -fPIC works... yes
    checking if gcc static flag -static works... yes
    checking if gcc supports -c -o file.o... yes
    checking whether the gcc linker (/usr/bin/ld) supports shared libraries... yes
    checking whether -lc should be explicitly linked in... no
    checking dynamic linker characteristics... GNU/Linux ld.so
    checking how to hardcode library paths into programs... immediate
    checking whether stripping libraries is possible... yes
    checking if libtool supports shared libraries... yes
    checking whether to build shared libraries... yes
    checking whether to build static libraries... yes
    configure: creating libtool
    appending configuration tag "CXX" to libtool
    checking for ld used by g++... /usr/bin/ld
    checking if the linker (/usr/bin/ld) is GNU ld... yes
    checking whether the g++ linker (/usr/bin/ld) supports shared libraries... yes
    checking for g++ option to produce PIC... -fPIC
    checking if g++ PIC flag -fPIC works... yes
    checking if g++ static flag -static works... yes
    checking if g++ supports -c -o file.o... yes
    checking whether the g++ linker (/usr/bin/ld) supports shared libraries... yes
    checking dynamic linker characteristics... GNU/Linux ld.so
    checking how to hardcode library paths into programs... immediate
    appending configuration tag "F77" to libtool
    checking for gcc... (cached) gcc
    checking whether we are using the GNU C compiler... (cached) yes
    checking whether gcc accepts -g... (cached) yes
    checking for gcc option to accept ISO C89... (cached) none needed
    checking dependency style of gcc... (cached) gcc3
    checking for a BSD-compatible install... /usr/bin/install -c
    checking whether make sets $(MAKE)... (cached) yes
    checking X11/X.h usability... yes
    checking X11/X.h presence... yes
    checking for X11/X.h... yes
    checking X11/Xlib.h usability... yes
    checking X11/Xlib.h presence... yes
    checking for X11/Xlib.h... yes
    checking X11/Xutil.h usability... yes
    checking X11/Xutil.h presence... yes
    checking for X11/Xutil.h... yes
    checking X11/Xos.h usability... yes
    checking X11/Xos.h presence... yes
    checking for X11/Xos.h... yes
    checking X11/Xatom.h usability... yes
    checking X11/Xatom.h presence... yes
    checking for X11/Xatom.h... yes
    checking for pkg-config... /usr/bin/pkg-config
    checking pkg-config is at least version 0.9.0... yes
    checking for ALSA... yes
    checking for JACK... yes
    checking for JACK... yes
    configure: creating ./config.status
    config.status: creating Makefile
    config.status: creating libbrightonX11/Makefile
    config.status: creating libbrighton/Makefile
    config.status: creating libbristolaudio/Makefile
    config.status: creating libbristolmidi/Makefile
    config.status: creating libbristol/Makefile
    config.status: creating brighton/Makefile
    config.status: creating bristol/Makefile
    config.status: creating bin/startBristol
    config.status: creating config.h
    config.status: executing depfiles commands

    bristol 0.30.3 :

    | Build with ALSA support ........................ : true
    | Build with JACK support ........................ : true
    | Build with JACK MIDI support ................... : true
    | Installing data into ........................... : /usr/local/share/bristol

    execute 'make install' then 'startBristol'

    .. then: make install

    compiling, compiling, compiling and then:

    midiJACKDevMan.o
    midiJACKDevMan.c: In function 'jackMidiRoutine':
    midiJACKDevMan.c:50: error: too few arguments to function 'jack_midi_get_event_count'
    midiJACKDevMan.c:59: error: too few arguments to function 'jack_midi_event_get'
    midiJACKDevMan.c:72: warning: implicit declaration of function 'checkcallbacks'
    make[1]: *** [midiJACKDevMan.lo] Error 1
    make[1]: Leaving directory `/usr/local/src/bristol-0.30.3/libbristolmidi'
    make: *** [install-recursive] Error 1

    What does this mean?

    This looks like great software. I can't wait to try.

     
    • Nick Copeland

      Nick Copeland - 2009-01-07

      There is probably an incompatibility with your Jack version - there have been changes to the Jack Midi interface and either my code is not up to date or perhaps you have an older version of Jack installed.

      You might want to try the following;

      ./configure --disable-jack-midi && make install

      And also have a look at

      jackd --version

      My installation has the following:
      jackd version 0.109.2 tmpdir /dev/shm protocol 22

      With Jack 0.109.2 things compile here although the Jack midi has only been lightly tested. Perhaps I should make it default disabled and allow people to enable it during the configure?

      Kind regards,

      Nick.

       
    • cinder

      cinder - 2009-01-08

         Thanks for your prompt reply Nick.  That sounds about right.  I've got v.103.0-6.  Might I ask where you got v.109?  It doesn't seem to be available from my 64studio repository(debian based), nor the jack web site.

      Thank you kindly.

       
    • cinder

      cinder - 2009-01-08

      ... never mind! I just found it right here at sourceforge:p.  Thanks again. I'm excited!:o

       
    • Nick Copeland

      Nick Copeland - 2009-01-08

      It is always a good idea to keep up to date however you should still be able to use the v0.103 drivers from your distribution and then configure --disable-jack-midi. As I was explaining, Jack Midi support is quite new for Bristol and unless there are specific things you want to do you may not need it yet.

      Let me know how you get on. Bristol changes quite a lot between releases and some of the emulators are stronger than others.

      Kind regards,

      Nick

       

Log in to post a comment.

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:

JavaScript is required for this form.





No, thanks