[MacPorts] #17998: Linking to Python 2.5 framework is broken due to broken symlinks

[MacPorts]

#17998: Linking to Python 2.5 framework is broken due to broken symlinks
--------------------------+-------------------
  Reporter:  evert.rol@…  |      Owner:  jwa@…
      Type:  defect       |     Status:  new
  Priority:  Normal       |  Milestone:
 Component:  ports        |    Version:  1.6.0
Resolution:               |   Keywords:
      Port:  python25     |
--------------------------+-------------------
Changes (by mf2k@…):

 * cc: macsforever2000@… (removed)
 * keywords:  python boost framework symlink =>


Old description:

> Linking to
> /opt/local/Library/Frameworks/Python.framework/Versions/2.5/lib/python2.5/config/libpython2.5.a
> fails, because the file is a broken symlink (as an aside, the file
> identifies as a dynamically linked shared library, not a static one; is
> that a naming problem?).
>
> This is a result of libpython2.5.a being a symlink to ../../../Python,
> thereby crossing a symlinked directory:
> /opt/local/Library/Frameworks/Python.framework/Versions/2.5/lib/python2.5
> points to /opt/local/lib/python2.5. Traversing this symlinked directory
> manually is no problem, but the symlinked file is broken.
> Comparing to the system installed variant, the symlinked directory is the
> other way around:
>
> {{{
> ls -l  /usr/lib/
> lrwxr-xr-x   1 root  wheel        75  9 Nov  2007 python2.5 ->
> ../../System/Library/Frameworks/Python.framework/Versions/2.5/lib/python2.5
> }}}
>
> Manually fixing this now results in proper linking with libpython2.5 (I
> also added a libpython2.5.dylib in the config/ directory, which is simply
> a copy of libpython2.5.a).
> The directory structure now reads
>
> {{{
> ls -l /opt/local/lib
> lrwxr-xr-x    1 root  admin        66 14 Jan 18:03 python2.5 ->
> ../Library/Frameworks/Python.framework/Versions/2.5/lib/python2.5/
> ls -l
> /opt/local/Library/Frameworks/Python.framework/Versions/2.5/lib/python2.5/config
> total 208
> lrwxr-xr-x  1 root  admin     15 14 Jan 18:02 libpython2.5.a ->
> ../../../Python
> lrwxr-xr-x  1 root  admin     15 14 Jan 18:02 libpython2.5.dylib ->
> ../../../Python
>
> }}}
>

> This ticket originated from ticket [/ticket/17975 #17975]

New description:

 Linking to
 /opt/local/Library/Frameworks/Python.framework/Versions/2.5/lib/python2.5/config/libpython2.5.a
 fails, because the file is a broken symlink (as an aside, the file
 identifies as a dynamically linked shared library, not a static one; is
 that a naming problem?).

 This is a result of libpython2.5.a being a symlink to ../../../Python,
 thereby crossing a symlinked directory:
 /opt/local/Library/Frameworks/Python.framework/Versions/2.5/lib/python2.5
 points to /opt/local/lib/python2.5. Traversing this symlinked directory
 manually is no problem, but the symlinked file is broken.
 Comparing to the system installed variant, the symlinked directory is the
 other way around:

 {{{
 ls -l  /usr/lib/
 lrwxr-xr-x   1 root  wheel        75  9 Nov  2007 python2.5 ->
 ../../System/Library/Frameworks/Python.framework/Versions/2.5/lib/python2.5
 }}}

 Manually fixing this now results in proper linking with libpython2.5 (I
 also added a libpython2.5.dylib in the config/ directory, which is simply
 a copy of libpython2.5.a).
 The directory structure now reads

 {{{
 ls -l /opt/local/lib
 lrwxr-xr-x    1 root  admin        66 14 Jan 18:03 python2.5 ->
 ../Library/Frameworks/Python.framework/Versions/2.5/lib/python2.5/
 ls -l
 /opt/local/Library/Frameworks/Python.framework/Versions/2.5/lib/python2.5/config
 total 208
 lrwxr-xr-x  1 root  admin     15 14 Jan 18:02 libpython2.5.a ->
 ../../../Python
 lrwxr-xr-x  1 root  admin     15 14 Jan 18:02 libpython2.5.dylib ->
 ../../../Python

 }}}


 This ticket originated from ticket #17975

--

-- 
Ticket URL: <https://trac.macports.org/ticket/17998#comment:28>
MacPorts <http://www.macports.org/>
Ports system for OS X