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: Wed, 12 May 2004 14:38:42 +0100	[thread overview]
Message-ID: <1084369122.4426.106.camel@hades.cambridge.redhat.com> (raw)
In-Reply-To: <1084368666.25099.38.camel@pegasus>

On Wed, 2004-05-12 at 15:31 +0200, Marcel Holtmann wrote:
> Hi David,
> 
> > I cannot build libs2. The autoconf stuff is broken. The last thing it
> > says is this:
> > 
> > configure.in:19: required file `./ltmain.sh' not found
> > 
> > Please can we ditch this crap and use sane makefiles instead?
> 
> I heard of that problem, but I can't reproduce it. If you call
> "./bootstrap" every that is necessary should be created.

Still no substitute for proper makefiles. Do we _really_ need the system
to check for itself how to build Fortran shared libraries? Yes, that's
one of the things it does.

Btw, swave() in hciattach still uses 10 characters of a 9-char array. 

--- bluez-utils-2.7/tools/hciattach.c.orig	2004-05-11 23:08:57.668856200 +0100
+++ bluez-utils-2.7/tools/hciattach.c	2004-05-11 23:11:43.626626784 +0100
@@ -640,7 +640,7 @@
 static int swave(int fd, struct uart_t *u, struct termios *ti)
 {
 	struct timespec tm = {0, 500000};
-	char cmd[9], rsp[100];
+	char cmd[10], rsp[100];
 	int r;
 
 	// Silicon Wave set baud rate command


-- 
dwmw2

  reply	other threads:[~2004-05-12 13:38 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 [this message]
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

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=1084369122.4426.106.camel@hades.cambridge.redhat.com \
    --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