Quote:
Originally Posted by medoc
|
Thank you for replying, medoc.
I have downloaded the files from the locations you gave. I unpacked the midi-0.2.1.tar.gz into directory midi-0.2.1, installed swig (which was a missing dependency the first time through), then ran "python setup.py install". The setup failed because of some missing files:
Code:
running install
running build
running build_py
running build_ext
building '_sequencer_alsa' extension
swigging src/sequencer_alsa/sequencer_alsa.i to src/sequencer_alsa/sequencer_alsa_wrap.c
swig -python -o src/sequencer_alsa/sequencer_alsa_wrap.c src/sequencer_alsa/sequencer_alsa.i
src/sequencer_alsa/sequencer_alsa.i:145: Error: Unable to find 'include/seq.h'
src/sequencer_alsa/sequencer_alsa.i:146: Error: Unable to find 'include/seqmid.h'
src/sequencer_alsa/sequencer_alsa.i:147: Error: Unable to find 'include/seq_event.h'
src/sequencer_alsa/sequencer_alsa.i:148: Error: Unable to find 'include/seq_midi_event.h'
src/sequencer_alsa/sequencer_alsa.i:149: Error: Unable to find 'include/error.h'
error: command 'swig' failed with exit status 1
I found that alsa-lib-devel provides all these headers under /usr/include/alsa/, so I installed that package. Unfortunately, that did not satisfy the dependencies, which is not surprising as the directory declaration is different. I found these files are referred to in ./src/sequencer_alsa/sequencer_alsa.i, so I edited that file to explicitly refer to /usr/include/alsa/[filename]. Now when I run the python installer, it throws a different error:
Code:
/usr/include/alsa/seq_event.h:260: Error: Syntax error in input(3).
error: command 'swig' failed with exit status 1
/usr/include/alsa/seq_event.h:260 is the last line (__attribute__ line) of this typedef:
Code:
/** external stored data */
typedef struct snd_seq_ev_ext {
unsigned int len; /**< length of data */
void *ptr; /**< pointer to data (note: can be 64-bit) */
} __attribute__((packed)) snd_seq_ev_ext_t;
This looks to be a Swig problem, so I have subscribed to the Swig mailing list and posted the question there. If you happen to know what is needed to fix the error, however, feel free to reply <grin>.