From: Pedro Lopez-Cabanillas <plcl@telefonica.net>
To: Frank Barknecht <barknech@ph-cip.uni-koeln.de>
Cc: rob buse <rcbuse@filter24.org>, alsa-devel@lists.sourceforge.net
Subject: Re: seq24 - midi sequencer released
Date: Sun, 14 Jul 2002 17:50:28 +0200 [thread overview]
Message-ID: <200207141750.28331.plcl@telefonica.net> (raw)
In-Reply-To: <20020714114006.GA5680@fliwatut.scifi>
El Dom 14 Jul 2002 13:40, Frank Barknecht escribió:
> rob buse hat gesagt: // rob buse wrote:
> > I just GPL'd my seq24 midi sequencer.
> > http://www.filter24.org/seq24/index.html
> >
> I'm having a problem compiling it, because I get this error:
>
> sequence.C: In method `sequence::sequence()':
> sequence.C:47: `PTHREAD_MUTEX_RECURSIVE' undeclared (first use this
> function) sequence.C:47: (Each undeclared identifier is reported only once
> sequence.C:47: for each function it appears in.)
> sequence.C:47: implicit declaration of function `int
> pthread_mutexattr_settype(...)' make[1]: *** [sequence.o] Error 1
>
> I tried to add
> #include <pthread.h>
> to sequence.C, but that didn't help. Do you have any idea, where the
> error might come from?
Same results for me. After some googling, I've found that adding the flag
-D_GNU_SOURCE at src/Makefile.am and reconfiguring I could compile it. This
is the line I have changed:
CXXFLAGS = @CXXFLAGS@ $(GTKMM_CFLAGS) -Wall -D_GNU_SOURCE
Pedro
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
next prev parent reply other threads:[~2002-07-14 15:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E17TSLJ-0000Y3-00@usw-sf-list2.sourceforge.net>
2002-07-13 21:16 ` seq24 - midi sequencer released rob buse
2002-07-14 11:40 ` Frank Barknecht
2002-07-14 15:50 ` Pedro Lopez-Cabanillas [this message]
2002-07-14 18:29 ` seq24 - midi sequencer fixed rob buse
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200207141750.28331.plcl@telefonica.net \
--to=plcl@telefonica.net \
--cc=alsa-devel@lists.sourceforge.net \
--cc=barknech@ph-cip.uni-koeln.de \
--cc=rcbuse@filter24.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.