public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: David Woodhouse <dwmw2@infradead.org>
To: Marcel Holtmann <marcel@holtmann.org>
Cc: BlueZ Mailing List <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] autoconf breaks portability. Film at 11.
Date: Thu, 13 May 2004 07:53:48 +0100	[thread overview]
Message-ID: <1084431228.21553.75.camel@imladris.demon.co.uk> (raw)
In-Reply-To: <1084398405.25099.118.camel@pegasus>

On Wed, 2004-05-12 at 23:46 +0200, Marcel Holtmann wrote:
> > hades /hades/bluez/libs2 $ ./configure
> > -bash2: ./configure: No such file or directory
> 
> There must be another problem. Please do a clean CVS checkout.

A clean checkout on a third machine shows the same problem. It seems I
can make it build by running 'libtoolize' or manually copying in
ltmain.sh from one of the five different versions of automake which is
installed.

Perhaps someone needs to write 'autoauto' to help people automate all
this gratuitous package automation?

Personally, I'll stick with M-x makefile-mode :)

-- 
dwmw2

      reply	other threads:[~2004-05-13  6:53 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-11  9:47 [Bluez-devel] autoconf breaks portability. Film at 11 David Woodhouse
2004-05-12 13:31 ` Marcel Holtmann
2004-05-12 13:38   ` David Woodhouse
2004-05-12 13:48     ` Marcel Holtmann
2004-05-12 14:11       ` David Woodhouse
2004-05-12 17:23         ` Marcel Holtmann
2004-05-12 18:03           ` David Woodhouse
2004-05-12 21:46             ` Marcel Holtmann
2004-05-13  6:53               ` David Woodhouse [this message]

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=1084431228.21553.75.camel@imladris.demon.co.uk \
    --to=dwmw2@infradead.org \
    --cc=bluez-devel@lists.sourceforge.net \
    --cc=marcel@holtmann.org \
    /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