Compiling bluez for python in /usr/local

Linux bluetooth development
 help / color / mirror / Atom feed

* Compiling bluez for python in /usr/local
@ 2009-09-24 10:05 John Frankish
  2009-09-24 16:55 ` Marcel Holtmann
  0 siblings, 1 reply; 2+ messages in thread
From: John Frankish @ 2009-09-24 10:05 UTC (permalink / raw)
  To: linux-bluetooth@vger.kernel.org

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?

Regards, John

^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: Compiling bluez for python in /usr/local
  2009-09-24 10:05 Compiling bluez for python in /usr/local John Frankish
@ 2009-09-24 16:55 ` Marcel Holtmann
  0 siblings, 0 replies; 2+ messages in thread
From: Marcel Holtmann @ 2009-09-24 16:55 UTC (permalink / raw)
  To: John Frankish; +Cc: linux-bluetooth@vger.kernel.org

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



^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2009-09-24 16:55 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2009-09-24 10:05 Compiling bluez for python in /usr/local John Frankish
2009-09-24 16:55 ` Marcel Holtmann

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox