From: Luca Capello <luca@pca.it>
To: ML bluez-devel <bluez-devel@lists.sourceforge.net>
Subject: [Bluez-devel] [btsco] configure/make errors
Date: Tue, 18 Jan 2005 22:24:29 +0100 [thread overview]
Message-ID: <41ED7E8D.8030709@pca.it> (raw)
[-- Attachment #1: Type: text/plain, Size: 1116 bytes --]
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hello again,
after having solved the automake error, configure gave me another one
and googling solved it [1]. But, again, no dependencies from libao-dev
is present in the README (and, strangely, automake doesn't complain).
This wasn't enough: make gave me other errors, because it could not find
the Bluetooth dev libraries.
Attached a patch against the current CVS:
* bootstrap:
checking for the existence of /usr/share/aclocal/ao.m4 and exiting with
an error if not present (we cannot use the pkg-config because ao.m4 is
used to generate the configure script)
* configure.in:
used pkg-config to check the presence of the Bluetooth dev libraries
* README:
added more info about dependencies (section Build.0)
Thx, bye,
Gismo / Luca
[1] https://www.redhat.com/archives/fedora-list/2004-December/msg03679.html
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (GNU/Linux)
Comment: Using GnuPG with Debian - http://enigmail.mozdev.org
iD8DBQFB7X6NVAp7Xm10JmkRAtPlAJ46nBk7st7KfzBsSc3+W+4tuc2kNwCfSRBM
uNAdtpcWbvjUmLOm83oUT+E=
=wdn3
-----END PGP SIGNATURE-----
[-- Attachment #2: btsco_cvs-20050118-2128_libao-libbluetooth-check.diff --]
[-- Type: text/plain, Size: 1982 bytes --]
diff -Naur btsco_cvs-20050118-2128/bootstrap btsco/bootstrap
--- btsco_cvs-20050118-2128/bootstrap 2005-01-18 18:11:21.000000000 +0100
+++ btsco/bootstrap 2005-01-18 22:04:32.000000000 +0100
@@ -1,10 +1,19 @@
#! /bin/sh
+# Test for the right automake
if [ ! `which automake-1.7` ]; then
echo -e "\n*** You need automake-1.7 to compile this software ***\n"
exit 1
elif [ ! `automake --version | grep -q 1.7` ]; then
AUTOMAKE_VERSION="-1.7"
fi
-
+
+# Test for the presence of libao-dev (this cannot be done with
+# pkg-config because we need libao-dev for automake)
+if [ ! -s "/usr/share/aclocal/ao.m4" ]; then
+ echo -e "\n*** You need libao-dev to compile this software ***\n"
+ exit 1
+fi
+
+# All we need for the autotools is installed, so go on
aclocal$AUTOMAKE_VERSION && autoheader && automake$AUTOMAKE_VERSION --add-missing --copy --ignore-deps && autoconf
diff -Naur btsco_cvs-20050118-2128/configure.in btsco/configure.in
--- btsco_cvs-20050118-2128/configure.in 2004-11-28 07:44:49.000000000 +0100
+++ btsco/configure.in 2005-01-18 22:13:23.000000000 +0100
@@ -5,6 +5,8 @@
AC_PREREQ(2.50)
AC_INIT()
+PKG_CHECK_MODULES(BTSCO, bluez)
+
AM_INIT_AUTOMAKE(btsco, 0.2)
AM_CONFIG_HEADER(config.h)
diff -Naur btsco_cvs-20050118-2128/README btsco/README
--- btsco_cvs-20050118-2128/README 2005-01-18 18:11:20.000000000 +0100
+++ btsco/README 2005-01-18 22:04:46.000000000 +0100
@@ -31,10 +31,14 @@
Build
+ 0. In order to build this project, you need:
+ automake-1.7
+ libao-dev
+ libbluetooth-dev
1. The CVS repository must be checked out:
cvs -d:pserver:anonymous@cvs.sf.net:/cvsroot/bluetooth-alsa login
cvs -d:pserver:anonymous@cvs.sf.net:/cvsroot/bluetooth-alsa co btsco
- 2. After that it must be compiled (you need automake 1.7):
+ 2. After that it must be compiled:
./bootstrap
./configure
make
next reply other threads:[~2005-01-18 21:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-18 21:24 Luca Capello [this message]
2005-01-19 12:15 ` [Bluez-devel] [btsco] configure/make errors Marcel Holtmann
2005-01-19 14:18 ` Luca Capello
2005-01-19 16:21 ` Marcel Holtmann
2005-01-19 19:25 ` Brad Midgley
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=41ED7E8D.8030709@pca.it \
--to=luca@pca.it \
--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