From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ Mailing List <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] [btsco] configure/make errors
Date: Wed, 19 Jan 2005 13:15:20 +0100 [thread overview]
Message-ID: <1106136920.8190.96.camel@pegasus> (raw)
In-Reply-To: <41ED7E8D.8030709@pca.it>
Hi Luca,
> 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)
And again. The bootstrap thing is for making the developer happy,
because he must call only one program/script for getting the repository
ready. It is not for others ;)
> * configure.in:
> used pkg-config to check the presence of the Bluetooth dev libraries
You can also use AM_PATH_BLUEZ. Since bluez-libs-2.13 it is also
available now, because not all systems use pkg-config.
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
next prev parent reply other threads:[~2005-01-19 12:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-18 21:24 [Bluez-devel] [btsco] configure/make errors Luca Capello
2005-01-19 12:15 ` Marcel Holtmann [this message]
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=1106136920.8190.96.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.