From: Abramo Bagnara <abramo.bagnara@libero.it>
To: Thomas Roeder <rdr@emt.iis.fhg.de>
Cc: Paul Davis <pbd@op.net>, alsa-devel@lists.sourceforge.net
Subject: Re: libasound and libpthread
Date: Mon, 29 Jul 2002 15:40:27 +0200 [thread overview]
Message-ID: <3D4545CB.579EA77C@libero.it> (raw)
In-Reply-To: E17Z9Fw-00028n-00@usw-sf-list1.sourceforge.net
Paul Davis wrote:
>
> >I am working with Alsa 0.9.0beta12 version and I am also using posix
> >threads (libpthread) in my project. In the release version of the
> >program I link both libraries (libpthread, libasound) dynamically and
> >everything works well. In the debug version however, I have to do static
> >linking of the libpthread for proper debugging.
>
> why? i use pthreads a great deal, and i have never had to do this.
>
> and no, libasound does not use pthreads or any other form of threads.
Thomas, you should know to not rely too strong to Paul's words.
He own a big heart, but unfortunately a big mouth too, that he's often
unable to keep under control ;-)
Some portions of libasound *do* use pthreads.
--
Abramo Bagnara mailto:abramo.bagnara@libero.it
Opera Unica Phone: +39.546.656023
Via Emilia Interna, 140
48014 Castel Bolognese (RA) - Italy
-------------------------------------------------------
This sf.net email is sponsored by: Dice - The leading online job board
for high-tech professionals. Search and apply for tech jobs today!
http://seeker.dice.com/seeker.epl?rel_code=31
next prev parent reply other threads:[~2002-07-29 13:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-29 8:06 libasound and libpthread Thomas Roeder
2002-07-29 12:05 ` Paul Davis
2002-07-29 13:40 ` Abramo Bagnara [this message]
2002-07-29 15:15 ` Thomas Roeder
2002-07-29 16:04 ` Paul Davis
2002-07-29 16:00 ` Paul Davis
2002-07-29 17:34 ` Patrick Shirkey
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=3D4545CB.579EA77C@libero.it \
--to=abramo.bagnara@libero.it \
--cc=alsa-devel@lists.sourceforge.net \
--cc=pbd@op.net \
--cc=rdr@emt.iis.fhg.de \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox