From: Marcel Holtmann <marcel@holtmann.org>
To: John Frankish <j-frankish@slb.com>
Cc: "linux-bluetooth@vger.kernel.org" <linux-bluetooth@vger.kernel.org>
Subject: Re: Compiling bluez for python in /usr/local
Date: Thu, 24 Sep 2009 09:55:23 -0700 [thread overview]
Message-ID: <1253811323.2931.17.camel@localhost.localdomain> (raw)
In-Reply-To: <6AC5A55546F64545AE996F8200E3AC4E0C80070A@NL0105EXC01V01.eur.slb.com>
Hi John,
> I just compiled bluez-4.53 on a system with python at /usr/local/bin/python - unless I messed up somewhere, it seems simple-agent and the other python scripts still expected to find python at /usr/bin/python.
>
> Whilst this can be fixed with a symlink, it might be better that the scripts refer to the actual location of python?
they are test scripts and not meant to be installed. So we don't care
about the install path of the Python interpreter.
Regards
Marcel
prev parent reply other threads:[~2009-09-24 16:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-24 10:05 Compiling bluez for python in /usr/local John Frankish
2009-09-24 16:55 ` Marcel Holtmann [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=1253811323.2931.17.camel@localhost.localdomain \
--to=marcel@holtmann.org \
--cc=j-frankish@slb.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox