public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Luca Capello <luca@pca.it>
To: ML bluez-devel <bluez-devel@lists.sourceforge.net>
Subject: [Bluez-devel] [btsco] automake error
Date: Tue, 18 Jan 2005 15:50:54 +0100	[thread overview]
Message-ID: <41ED224E.9030702@pca.it> (raw)

[-- Attachment #1: Type: text/plain, Size: 1432 bytes --]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hello,

I'm new to the list, so hello to everyone :-)

I just bought a Bluetake i-Phono and I was trying to test it (Debian
unstable, kernel 2.6.10, ALSA 1.0.8), but I got an automake error:
=====
luca@gismo:~/src/kernel/bluetooth$ cvs
- -d:pserver:anonymous@cvs.sf.net:/cvsroot/bluetooth-alsa login
Logging in to :pserver:anonymous@cvs.sf.net:2401/cvsroot/bluetooth-alsa
CVS password:
luca@gismo:~/src/kernel/bluetooth$ cvs
- -d:pserver:anonymous@cvs.sf.net:/cvsroot/bluetooth-alsa co btsco
cvs checkout: Updating btsco
<cut>
U btsco/sbc/sbcinfo.c

luca@gismo:~/src/kernel/bluetooth$ cd btsco/
luca@gismo:~/src/kernel/bluetooth/btsco$ ./bootstrap
automake: unrecognized option -- `--ignore-deps'
Try `automake --help' for more information.

luca@gismo:~/src/kernel/bluetooth/btsco$ automake --help | grep ignore
luca@gismo:~/src/kernel/bluetooth/btsco$ automake --version | grep automake
automake (GNU automake) 1.4-p6
=====

So, the attached patch check for automake-1.7 during the bootstrap
process and add an info in the README.

But I still have some compilation problems... (new post, IMHO it's better).

Thx, bye,
Gismo / Luca
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (GNU/Linux)
Comment: Using GnuPG with Debian - http://enigmail.mozdev.org

iD8DBQFB7R1mVAp7Xm10JmkRAsS6AJ0cJCqjyaxxDdVW2HafWJFWwJbatQCdF002
OXtjJYOo4mfeYcpDZyGT9Y0=
=eIey
-----END PGP SIGNATURE-----

[-- Attachment #2: btsco_cvs-20050118-1520_automake1.7-check.diff --]
[-- Type: text/plain, Size: 1224 bytes --]

diff -Naur btsco_cvs-20050118-1520/bootstrap btsco/bootstrap
--- btsco_cvs-20050118-1520/bootstrap	2005-01-18 15:22:44.000000000 +0100
+++ btsco/bootstrap	2005-01-18 15:19:38.000000000 +0100
@@ -1,2 +1,10 @@
 #! /bin/sh
-aclocal && autoheader && automake --add-missing --copy --ignore-deps && autoconf
+
+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
+ 
+aclocal$AUTOMAKE_VERSION && autoheader && automake$AUTOMAKE_VERSION --add-missing --copy --ignore-deps && autoconf
diff -Naur btsco_cvs-20050118-1520/README btsco/README
--- btsco_cvs-20050118-1520/README	2005-01-18 15:23:32.000000000 +0100
+++ btsco/README	2004-11-25 01:51:40.000000000 +0100
@@ -37,7 +37,7 @@
     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 automake1.7 to do it:
+    2. After that it must be compiled:
         ./bootstrap
         ./configure
         make

             reply	other threads:[~2005-01-18 14:50 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-18 14:50 Luca Capello [this message]
2005-01-18 17:11 ` [Bluez-devel] [btsco] automake error Brad Midgley
2005-01-18 19:56   ` Marcel Holtmann
2005-01-18 20:10   ` Luca Capello

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=41ED224E.9030702@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