All of lore.kernel.org
 help / color / mirror / Atom feed
From: Clemens Ladisch <clemens@ladisch.de>
To: Vinod Koul <vinod.koul@intel.com>,
	Jaroslav Kysela <perex@perex.cz>, Takashi Iwai <tiwai@suse.de>
Cc: alsa-devel@alsa-project.org
Subject: Re: builidng alsa-utils
Date: Tue, 19 Jan 2016 12:16:44 +0100	[thread overview]
Message-ID: <569E1B1C.8020602@ladisch.de> (raw)
In-Reply-To: <20160119105625.GS11130@localhost>

Vinod Koul wrote:
> I was trying to build alsa-utils (lib built fine) but it seems stuck on
> libpanelw.
> ...
> checking for ncursesw5-config... yes
> checking for curses library... ncursesw
> checking for curses header name... <ncurses.h>
> checking for curses compiler flags... -I/usr/include/ncursesw
> checking for curses NLS support... yes
> ...
> checking for new_panel in -lpanelw... no
> configure: error: panelw library not found
>
> And I have panelw
>
> $ locate libpanelw
> /usr/lib/x86_64-linux-gnu/libpanelw.so.5
> /usr/lib/x86_64-linux-gnu/libpanelw.so.5.9
>
> And created symbolic link
>
> $ ll /usr/lib/x86_64-linux-gnu/libpanelw*
> lrwxrwxrwx 1 root root    40 Jan 19 15:14 /usr/lib/x86_64-linux-gnu/libpanelw.so -> /usr/lib/x86_64-linux-gnu/libpanelw.so.5
>
> Any reasons this would happen?

So it works now?  That missing link would appear to be a bug of your
distribution's package.

> Btw if it do
> ./gitcompile --with-curses=ncurses --disable-xmlto
> it works fine

This does not uses libpanelw but libpanel (which apparently exists).
(w = wide-character support for non-ASCII locales)


Regards,
Clemens

  reply	other threads:[~2016-01-19 11:16 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-19 10:56 builidng alsa-utils Vinod Koul
2016-01-19 11:16 ` Clemens Ladisch [this message]
2016-01-19 16:05   ` Vinod Koul
2016-01-19 16:09 ` Takashi Iwai
2016-01-19 16:20   ` Vinod Koul
2016-01-19 16:19     ` 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=569E1B1C.8020602@ladisch.de \
    --to=clemens@ladisch.de \
    --cc=alsa-devel@alsa-project.org \
    --cc=perex@perex.cz \
    --cc=tiwai@suse.de \
    --cc=vinod.koul@intel.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 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.