From: Takashi Iwai <tiwai@suse.de>
To: mgd@technosis.de
Cc: alsa-devel@lists.sourceforge.net
Subject: Re: Compilation error with alsa-plugins-1.0.14rc3: gcd.h not found
Date: Thu, 08 Mar 2007 12:56:18 +0100 [thread overview]
Message-ID: <s5h7itskkyl.wl%tiwai@suse.de> (raw)
In-Reply-To: <200703081209.17773.mgd@technosis.de>
At Thu, 8 Mar 2007 12:09:05 +0100,
Michael Gerdau wrote:
>
> Hi list,
>
> while trying to compile alsa-plugins-1.0.14rc3 I get this error:
>
> gcc -DHAVE_CONFIG_H -I. -I. -I.. -Wall -g -I/usr/include/alsa -g -O2 -MT rate_lavcrate.lo -MD -MP -MF .deps/rate_lavcrate.Tpo -c rate_lavcrate.c -fPIC -DPIC -o .libs/rate_lavcrate.o
> rate_lavcrate.c:23:17: error: gcd.h: No such file or directory
> rate_lavcrate.c: In function 'pcm_src_init':
> rate_lavcrate.c:85: warning: implicit declaration of function 'gcd'
> make[2]: *** [rate_lavcrate.lo] Fehler 1
> make[2]: Leaving directory `/home/mgd/src/alsa-plugins-1.0.14rc3/rate-lavc'
> make[1]: *** [all-recursive] Fehler 1
> make[1]: Leaving directory `/home/mgd/src/alsa-plugins-1.0.14rc3'
> make: *** [all] Fehler 2
>
> Where am I supposed to get gcd.h from ?
Looks like it's missing in Makefile.am. Should be fixed in the next
release. You can get the file from alsa-plugin HG tree.
Takashi
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
prev parent reply other threads:[~2007-03-08 11:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-08 11:09 Compilation error with alsa-plugins-1.0.14rc3: gcd.h not found Michael Gerdau
2007-03-08 11:56 ` Takashi Iwai [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=s5h7itskkyl.wl%tiwai@suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@lists.sourceforge.net \
--cc=mgd@technosis.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