linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Colin Beckingham <colbec@start.ca>
To: Hendrik Sattler <post@hendrik-sattler.de>
Cc: "linux-bluetooth@vger.kernel.org" <linux-bluetooth@vger.kernel.org>
Subject: Re: Installation from git did not proceed cleanly?
Date: Tue, 27 Sep 2011 07:46:50 -0400	[thread overview]
Message-ID: <4E81B7AA.7040108@start.ca> (raw)
In-Reply-To: <20110927132332.23237dubrv7x0k08@mail.hendrik-sattler.de>



On 09/27/2011 07:23 AM, Hendrik Sattler wrote:
> Zitat von Colin Beckingham <colbec@start.ca>:
>
>> Hi, a few observations on installation from git repository on a
>> reasonably fresh install of OpenSUSE 11.4. (Previous installations
>> from tar.gz have all run correctly first time.)
>>
>> 1. Fetching the clone from the temporary repo not a problem
>> 2. ./configure instruction from README/INSTALL did not work, no
>> configure found
>
> That one is called boot-strapping and is the same for many projects
> using autoconf. For convenience reasons, it's done before creating
> tarballs. That's probably the reason you are not used to it.
>
> So to create the configure script (and other files), either run "chmod
> +x bootstrap; ./bootstrap" or just "autoreconf -f -i".
>

Thanks for this advice. Works no problem.

In an earlier thread "Permission denied (13) on Samsung WEP475 headset?" 
I reported an issue. I see that in this latest version it is still 
necessary to issue an

hciconfig 0 sspmode 0

before the unit will connect. Not a problem. If this is unexpected 
behaviour from the programme I can provide more feedback.

Colin Beckingham

      reply	other threads:[~2011-09-27 11:46 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-27 10:49 Installation from git did not proceed cleanly? Colin Beckingham
2011-09-27 11:23 ` Hendrik Sattler
2011-09-27 11:46   ` Colin Beckingham [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=4E81B7AA.7040108@start.ca \
    --to=colbec@start.ca \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=post@hendrik-sattler.de \
    /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;
as well as URLs for NNTP newsgroup(s).