Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Vinod Koul <vinod.koul@intel.com>
To: Takashi Iwai <tiwai@suse.de>
Cc: alsa-devel@alsa-project.org, Clemens Ladisch <clemens@ladisch.de>
Subject: Re: builidng alsa-utils
Date: Tue, 19 Jan 2016 21:50:25 +0530	[thread overview]
Message-ID: <20160119162025.GU11130@localhost> (raw)
In-Reply-To: <s5h8u3ly2ia.wl-tiwai@suse.de>

On Tue, Jan 19, 2016 at 05:09:49PM +0100, Takashi Iwai wrote:
> On Tue, 19 Jan 2016 11:56:26 +0100,
> Vinod Koul wrote:
> > 
> > Hi,
> > 
> > I was trying to build alsa-utils (lib built fine) but it seems stuck on
> > libpanelw. I did quick google the symbolic links and packages seems to be
> > there, what am i missing
> > 
> > checking for alsa/pcm.h... yes
> > checking for alsa/mixer.h... yes
> > checking for alsa/rawmidi.h... yes
> > checking for alsa/seq.h... yes
> > checking for alsa/use-case.h... yes
> > checking for alsa/topology.h... yes
> > checking for samplerate.h... no
> > 
> > This doesnt block now, but which package is required for this
> > 
> > checking for fftw_malloc in -lfftw3... yes
> > checking for sqrtf in -lm... yes
> > checking for pthread_create in -lpthread... yes
> > checking for librt... checking for clock_gettime in -lrt... yes
> > checking for xmlto... yes
> > checking for ANSI C header files... yes
> > checking for NCURSESW... no
> > 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 sys/types.h... yes
> > checking for sys/stat.h... yes
> > checking for stdlib.h... yes
> > checking for string.h... yes
> > checking for memory.h... yes
> > checking for strings.h... yes
> > checking for inttypes.h... yes
> > checking for stdint.h... yes
> > checking for unistd.h... yes
> > checking panel.h usability... yes
> > checking panel.h presence... yes
> > checking for panel.h... yes
> > checking menu.h usability... yes
> > checking menu.h presence... yes
> > checking for menu.h... yes
> > checking form.h usability... yes
> > checking form.h presence... yes
> > checking for form.h... 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
> 
> It's already wrong.  Most likely you didn't install the proper
> development file needed for libpanelw.  A devel package usually
> contains the proper lib*.so file symlink.

I used ubuntu packages to install, any specfic one which is required here.
No packages were installed manually

-- 
~Vinod

  reply	other threads:[~2016-01-19 16: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
2016-01-19 16:05   ` Vinod Koul
2016-01-19 16:09 ` Takashi Iwai
2016-01-19 16:20   ` Vinod Koul [this message]
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=20160119162025.GU11130@localhost \
    --to=vinod.koul@intel.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=clemens@ladisch.de \
    --cc=tiwai@suse.de \
    /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