All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Topper <topper@virginia.edu>
To: alsa-devel@alsa-project.org
Subject: Problem with ncurses and alsamixer (cannot open terminal: vt100 or xterm)
Date: Sat, 02 Jun 2007 16:34:12 -0400	[thread overview]
Message-ID: <4661D444.4090006@virginia.edu> (raw)

I finally managed to get the alsa-1.0.4 utils to compile on an ARM based 
SBC.  When I launch alsamixer, however, I get an error:

Error opening terminal:  xterm

When I ssh into the board.  Or:

Error opening terminal:  vt100

When connected via serial cable.

I suspect this has something to do with the linking (or lack thereof) of 
alsamixer for ncurses.  The ncurrses library, by the way, I cross 
compiled with the following command:

CC=/opt/crosstool/arm-unknown-linux-gnu/gcc-3.3.4-glibc-2.3.2/bin/arm-unknown-linux-gnu-gcc 
./configure --host=arm-linux --prefix=/home/topper/ts-packages/ 
--exec-prefix=/home/topper/ts-packages/

But for the alsa utils, I simple ran ./configure, and the script 
detected the ncurses library, ran through and compiled.  Yet, something 
seems amuck because:

root@ts7000:root# ldd /bin/alsamixer
        libasound.so.2 => /lib/libasound.so.2 (0x2aac8000)
        libm.so.6 => /lib/libm.so.6 (0x2ab6f000)
        libdl.so.2 => /lib/libdl.so.2 (0x2abe9000)
        libpthread.so.0 => /lib/libpthread.so.0 (0x2abf3000)
        libc.so.6 => /lib/libc.so.6 (0x2ac4b000)
        /lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x2aaab000)

Whereas on my Linux Intel laptop:

awn:~$ ldd /usr/bin/alsamixer
        libncurses.so.5 => /lib/libncurses.so.5 (0x4002c000)
        libasound.so.2 => /usr/lib/libasound.so.2 (0x40069000)
        libm.so.6 => /lib/libm.so.6 (0x4010d000)
        libdl.so.2 => /lib/libdl.so.2 (0x40130000)
        libpthread.so.0 => /lib/libpthread.so.0 (0x40133000)
        libc.so.6 => /lib/libc.so.6 (0x40184000)
        /lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x40000000)

So I have two questions:

1.  How might ensure proper linking of the ncurses library.
2.  Is there another way to tell alsa to activate various cards, set 
volume, etc.. so I can test to see if the alsa driver is even working on 
this board.

Thanks,

Dave Topper

-- 
Technical Director - Virginia Center for Computer Music
http://www.virginia.edu/music/VCCM/

             reply	other threads:[~2007-06-02 20:32 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-02 20:34 David Topper [this message]
2007-06-04 10:36 ` Problem with ncurses and alsamixer (cannot open terminal: vt100 or xterm) Takashi Iwai

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=4661D444.4090006@virginia.edu \
    --to=topper@virginia.edu \
    --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.