All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ Mailing List <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] btsco under FC3
Date: Thu, 06 Jan 2005 18:26:30 +0100	[thread overview]
Message-ID: <1105032390.4299.92.camel@pegasus> (raw)
In-Reply-To: <v04020a1dbe030e257568@[192.168.49.19]>

Hi Bob,

> OK, from scratch - get @AO.. problem
> 
> [root@hoho2 blue]# mv btsco btsco.save
> [root@hoho2 blue]# mkdir btsco
> [root@hoho2 blue]# cp -r btsco.save/CVS btsco
> [root@hoho2 blue]# cd btsco
> [root@hoho2 btsco]# cvs update -d
> ...
> [root@hoho2 btsco]# ./bootstrap 2>&1 | tee bootstrap.out
> configure.in: installing `./install-sh'
> configure.in: installing `./missing'
> [root@hoho2 btsco]# ./configure 2>&1 | tee config.out
> checking for a BSD-compatible install... /usr/bin/install -c
> checking whether build environment is sane... yes
> checking for gawk... gawk
> checking whether make sets $(MAKE)... yes
> checking for gcc... gcc
> checking for C compiler default output file name... a.out
> checking whether the C compiler works... yes
> checking whether we are cross compiling... no
> checking for suffix of executables...
> checking for suffix of object files... o
> checking whether we are using the GNU C compiler... yes
> checking whether gcc accepts -g... yes
> checking for gcc option to accept ANSI C... none needed
> checking for style of include used by make... GNU
> checking dependency style of gcc... none
> checking for a BSD-compatible install... /usr/bin/install -c
> checking for ranlib... ranlib
> checking for ALSA CFLAGS...
> checking for ALSA LDFLAGS...  -lasound -lm -ldl -lpthread
> checking for libasound headers version >= 1.0.3... found.
> checking for snd_ctl_open in -lasound... yes
> ./configure: line 3249: XIPH_PATH_AO: command not found

and again, the development files from the AO library are missing. Check
your Fedora Core 3 distribution.

Regards

Marcel




-------------------------------------------------------
The SF.Net email is sponsored by: Beat the post-holiday blues
Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

  reply	other threads:[~2005-01-06 17:26 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-06 15:51 [Bluez-devel] btsco under FC3 Bob Gustafson
2005-01-06 17:26 ` Marcel Holtmann [this message]
2005-01-07  3:30   ` Peter Robinson
2005-01-07  4:20     ` Brad Midgley
2005-01-07  3:43   ` Bob Gustafson
     [not found]   ` <v04020a21be03b42174eb@192.168.49.19>
2005-01-07  6:06     ` Peter Robinson
  -- strict thread matches above, loose matches on Subject: below --
2005-01-06 16:21 Bob Gustafson
2005-01-06 15:36 Bob Gustafson
2005-01-06  4:46 Peter Robinson
2005-01-06  7:28 ` Bob Gustafson
2005-01-06 12:24 ` Marcel Holtmann
2005-01-06 14:23   ` Bob Gustafson
2005-01-06 14:51     ` Marcel Holtmann
2005-01-06 15:33       ` Bob Gustafson
2005-01-07  6:15   ` Peter Robinson
2005-01-07  7:14     ` Brad Midgley
2005-01-07  7:19       ` Peter Robinson
2005-01-07 11:08         ` Lars Grunewaldt
2005-01-07 11:01     ` Henryk Plötz
2005-01-07 11:10       ` Lars Grunewaldt
2005-01-08  1:42       ` Peter Robinson

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=1105032390.4299.92.camel@pegasus \
    --to=marcel@holtmann.org \
    --cc=bluez-devel@lists.sourceforge.net \
    /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.