Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Pavel Hofman <pavel.hofman@ivitera.com>
To: Daniel Mack <zonque@gmail.com>
Cc: alsa-devel@alsa-project.org,
	Paul Menzel <paulepanter@users.sourceforge.net>
Subject: Re: A debug version of the ALSA lib?
Date: Fri, 02 Sep 2011 15:32:02 +0200	[thread overview]
Message-ID: <4E60DAD2.9050005@ivitera.com> (raw)
In-Reply-To: <CACTFLAPCcoGhSShJtf+iA-WZ7bVUC7jaoOQLX1iRSnkzMV2MYA@mail.gmail.com>

Dne 2.9.2011 14:46, Daniel Mack napsal(a):
> On Fri, Sep 2, 2011 at 12:55 PM, Paul Menzel
> <paulepanter@users.sourceforge.net> wrote:
>> Am Freitag, den 02.09.2011, 12:43 +0200 schrieb Daniel Mack:
>>> On Fri, Sep 2, 2011 at 10:44 AM, Olivier Guillion - Myriad wrote:
>>>>> Or just use the binary Ubuntu packages and be done.
>>>>
>>>> Sorry, but what does it mean?
>>>
>>> That means that Ubuntu (as many other distros) offers you a
>>> ready-made, debug symbols enabled version of the library which you can
>>> just install and use. As you're struggeling with compiling the library
>>> youself, I'd suggest you go for this solution. In Ubuntu, the package
>>> you're looking for is called libasound2-dev.
>>
>> I have not followed the thread, but if you want debugging symbol you
>> need `libasound2-dbg`. (`aptitude search libasound*`)
> 
> That doesn't seem to exist, but according to [1], the -dev variant
> contains the library itself again. Hence I assumed that this is the
> debug-enabled, non-stripped version of the .so that ships with this
> package. Admittedly though, I didn't check as I didn't have an Ubuntu
> box around.
> 

The -dev packages in debian/ubuntu contain headers required for includes
in other builds.

Pavel.

      reply	other threads:[~2011-09-02 13:57 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-01  8:37 A debug version of the ALSA lib? Olivier Guillion - Myriad
2011-09-01  8:50 ` Daniel Mack
2011-09-01  9:00   ` Pavel Hofman
2011-09-01 14:19     ` [Mult]Re: " Olivier Guillion - Myriad
2011-09-01 15:46       ` Daniel Mack
2011-09-01 16:37         ` Olivier Guillion - Myriad
2011-09-01 16:49           ` Daniel Mack
2011-09-02  8:44             ` Olivier Guillion - Myriad
2011-09-02 10:43               ` Daniel Mack
2011-09-02 10:55                 ` Paul Menzel
2011-09-02 12:10                   ` Olivier Guillion - Myriad
2011-09-02 12:26                     ` Pavel Hofman
2011-09-02 15:43                     ` Paul Menzel
2011-09-02 18:16                       ` David Henningsson
2011-09-02 12:46                   ` Daniel Mack
2011-09-02 13:32                     ` Pavel Hofman [this message]

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=4E60DAD2.9050005@ivitera.com \
    --to=pavel.hofman@ivitera.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=paulepanter@users.sourceforge.net \
    --cc=zonque@gmail.com \
    /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