All of lore.kernel.org
 help / color / mirror / Atom feed
From: Colin Beckingham <colbec@start.ca>
To: "linux-bluetooth@vger.kernel.org" <linux-bluetooth@vger.kernel.org>
Subject: Installation from git did not proceed cleanly?
Date: Tue, 27 Sep 2011 06:49:09 -0400	[thread overview]
Message-ID: <4E81AA25.6090907@start.ca> (raw)

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
3. Found a related advice to run: aclocal, autoheaders,automake and 
autoconf and ran these
4. repeated automake with --add-missing - this added several programmes 
but was not able to deal with missing ltmain.sh
5. I copied ltmain.sh from my previous install of version 4.96, this 
allowed configure to proceed a bit further, ran into problems with 
"package_revision" number in ltmain, hand edited
6. Also a problem with missing Makefile.in - copied from 4.96 - bad way 
to proceed but nothing ventured...
7. ./configure, make, make install all ok from this point.
8. restart of bluez-coldplug service ok.

Result: bluetoothd is working as before. It reports version as 4.96. 
However expected patch for previously reported problem still produces 
same error, so my install may be bad.

Please advise where I went wrong so that I and others can do it 
correctly next time. Any need for additional instructions in INSTALL?
-- 
---
Colin Beckingham

             reply	other threads:[~2011-09-27 10:49 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-27 10:49 Colin Beckingham [this message]
2011-09-27 11:23 ` Installation from git did not proceed cleanly? Hendrik Sattler
2011-09-27 11:46   ` Colin Beckingham

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=4E81AA25.6090907@start.ca \
    --to=colbec@start.ca \
    --cc=linux-bluetooth@vger.kernel.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 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.