From: Bob Gustafson <bobgus@rcn.com>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] btsco under FC3
Date: Thu, 6 Jan 2005 09:51:20 -0600 [thread overview]
Message-ID: <v04020a1dbe030e257568@[192.168.49.19]> (raw)
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
configure: creating ./config.status
config.status: creating Makefile
config.status: creating sbc/Makefile
config.status: creating avdtp/Makefile
config.status: creating config.h
config.status: executing depfiles commands
[root@hoho2 btsco]# make 2>&1 | tee make.out
make all-recursive
make[1]: Entering directory `/home/user1/blue/btsco'
Making all in sbc
make[2]: Entering directory `/home/user1/blue/btsco/sbc'
gcc -DHAVE_CONFIG_H -I. -I. -I.. @AO_CFLAGS@ -Wall -O2 -c sbc.c
gcc: @AO_CFLAGS@: No such file or directory
make[2]: *** [sbc.o] Error 1
make[2]: Leaving directory `/home/user1/blue/btsco/sbc'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/home/user1/blue/btsco'
make: *** [all] Error 2
[root@hoho2 btsco]#
BobG
Sent by me a minute or so aga
>Whoops - no tarball - loaded from CVS
>
>BobG
>
>
>Hi Marcel
>
>Yes, I did that too. @AO.... did not seem to disappear from the Makefile
>without help from 'vim'
>
>Will build from tarball again to see if my libtool is necessary.
>
>BobG
>
>>Hi Bob,
>>
>>> Yes, I did that too.
>>>
>>> something like 'up2date libao-devel', but the @AO. symbols were still in
>>> the Makefile. I did lots of things, so need to do a clean install and
>>> update to make certain what needs to be done to what.
>>
>>you need to ./bootstrap and ./configure again.
>>
>>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
>
-------------------------------------------------------
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
next reply other threads:[~2005-01-06 15:51 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-06 15:51 Bob Gustafson [this message]
2005-01-06 17:26 ` [Bluez-devel] btsco under FC3 Marcel Holtmann
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='v04020a1dbe030e257568@[192.168.49.19]' \
--to=bobgus@rcn.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox