Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Clemens Ladisch <clemens@ladisch.de>
To: john@swajime.com
Cc: alsa-devel@alsa-project.org
Subject: Re: Compiler errors in alsa-lib-1.0.22/test/*.c
Date: Wed, 21 Jul 2010 08:58:08 +0200	[thread overview]
Message-ID: <4C469A80.4050806@ladisch.de> (raw)
In-Reply-To: <AANLkTimjK6fzRKxtj0fnQ3xPDOyXHAWikq6MZxqy-sj2@mail.gmail.com>

John Simpson wrote:
> Playback open error: Inappropriate ioctl for device

Make sure that both your kernel and your alsa-lib use the correct
compiler and compiler flags (where "correct" usually means "whatever
the vendor's distribution uses").

> This time, checking out https://vcs.maemo.org/svn/dsp-alsa

It would be nice to know what the changes from the original alsa-lib
are; in theory, they should go upstream.

> $ cd dsp-alsa/trunk/alsa-lib
> #### cvscompile does not succeed

Why?

> $ .libs/pcm -D 'default' -vf 440
> Playback device is default
> Stream parameters are 44100Hz, S16_LE, 1 channels
> Sine wave rate is 440.0000Hz
> Using transfer method: write
> 
> Still no sound :-(

Mixer controls not set?  (amixer and alsamixer are in alsa-utils)


Regards,
Clemens

  reply	other threads:[~2010-07-21  6:58 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-12 15:20 Compiler errors in alsa-lib-1.0.22/test/*.c John Simpson
2010-07-13  6:18 ` Clemens Ladisch
2010-07-18  2:43   ` John Simpson
2010-07-18  2:45     ` John Simpson
2010-07-18  2:46       ` John Simpson
2010-07-19  8:52         ` Jaroslav Kysela
2010-07-19 22:27           ` John Simpson
2010-07-19 22:54             ` John Simpson
2010-07-19 23:25               ` John Simpson
2010-07-20 16:19             ` John Simpson
2010-07-21  6:58               ` Clemens Ladisch [this message]
2010-07-21 16:17                 ` John Simpson

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=4C469A80.4050806@ladisch.de \
    --to=clemens@ladisch.de \
    --cc=alsa-devel@alsa-project.org \
    --cc=john@swajime.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