From: Steve deRosier <derosier@pianodisc.com>
To: Alsa development <alsa-devel@alsa-project.org>
Subject: lib version?
Date: Tue, 27 Apr 2004 11:06:07 -0700 [thread overview]
Message-ID: <408EA10F.6070309@pianodisc.com> (raw)
Ok, here's my stupid question of the day:
Is there any way for a program to query the alsa-lib to determine the version number? Ie... Assuming I'm using the relase of alsa-lib-1.0.4, I'd like to query and get back something that would indicate that I'm using that release (and I don't even care so much if my program is what queries it, I just need some way to figure what version the libasound.so.2.0.0 file is).
Basically here's the senerio I've got:
We've been developing a box for quite a while using alsa, and we've gone through regular upgrades of alsa on each release. Unfortunately I'm trying to track down a rather serious problem in my client program, but I'm getting stymied due to what I suspect is a library version mismatch. I got my program hacked up and working ok to a point and then it segfaults. I replace libasound with a known 1.0.4 and it fails earlier in a different way (perhaps due to one of my hacks to get it working on whatever lib version I had in there). I'm just trying to figure out why... and knowing the library version # might get me there.
Any help would be appreciated.
Thanks,
- Steve
-------------------------------------------------------
This SF.net email is sponsored by: The Robotic Monkeys at ThinkGeek
For a limited time only, get FREE Ground shipping on all orders of $35
or more. Hurry up and shop folks, this offer expires April 30th!
http://www.thinkgeek.com/freeshipping/?cpg=12297
next reply other threads:[~2004-04-27 18:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-27 18:06 Steve deRosier [this message]
2004-04-28 7:05 ` lib version? Clemens Ladisch
2004-04-28 15:57 ` Giuliano Pochini
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=408EA10F.6070309@pianodisc.com \
--to=derosier@pianodisc.com \
--cc=alsa-devel@alsa-project.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.