R. David Murray added the comment:
Since no example was forthcomming, let's close this.
--
nosy: +r.david.murray
resolution: - rejected
stage: - resolved
status: open - closed
___
Python tracker rep...@bugs.python.org
Changes by Mark Lawrence breamore...@yahoo.co.uk:
--
nosy: -BreamoreBoy
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue2276
___
___
Mark Lawrence added the comment:
Is this still a problem or not? If yes what can be done about it? If no can
we close it?
--
nosy: +BreamoreBoy
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue2276
Ronald Oussoren ronaldousso...@mac.com added the comment:
Could you provide an example that shows why adding support for the -rpath
option on OSX would be useful? (As in a set of source files that shows how
this support would be used).
As I mentioned before the OSX support for -rpath behaves
Changes by Daniel Diniz aja...@gmail.com:
--
nosy: +tarek
versions: +Python 2.7, Python 3.1 -Python 2.5
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue2276
___
Ronald Oussoren [EMAIL PROTECTED] added the comment:
Do you mean the -rpath option?
Note that this is (IMHO) less useful than on other systems because the
linked-to library needs to have a specific link path (@rpath/mylib.dylib).
It can be useful for linking extentions though.
Using this
Bill Janssen [EMAIL PROTECTED] added the comment:
Yes, we were looking at using this for linking PyLucene's JCC extension.
I believe we came up with a different way of doing it. It would still
be useful to have distutils.unixccompiler.runtime_library_dir_option()
updated to understand the
New submission from Bill Janssen [EMAIL PROTECTED]:
The OS X linker now understands -R, but distutils continues to pass the
wrong flags back in
distutils.unixccompiler.runtime_library_dir_option(). I'm checking with
the Apple folks as to exactly what the right flag is.
--
assignee:
