#11307 closed defect (fixed)
BUG: ncurses and ncursesw 5.6 do not work due to incorrect path
Reported by: | vinc17@… | Owned by: | imajes@… |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | ports | Version: | |
Keywords: | Cc: | vincent@… | |
Port: |
Description
Programs using ncurses and ncursesw no longer work after recompilation. The reason is:
prunille:~> otool -L /opt/local/lib/libncurses.5.dylib /opt/local/lib/libncurses.5.dylib: /opt/local/var/db/dports/build/_Users_vinc17_software_dports_devel_ncurses/work/destroot/opt/local/lib/libncurses.5.dylib (compatibility version 5.0.0, current version 5.0.0) /usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 88.1.7) prunille:~> otool -L /opt/local/lib/libncursesw.5.dylib /opt/local/lib/libncursesw.5.dylib: /opt/local/var/db/dports/build/_Users_vinc17_software_dports_devel_ncursesw/work/destroot/opt/local/lib/libncursesw.5.dylib (compatibility version 5.0.0, current version 5.0.0) /usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 88.1.7)
Attachments (1)
Change History (12)
comment:1 Changed 18 years ago by vinc17@…
Summary: | ncurses and ncursesw 5.6 do not work due to incorrect path → BUG: ncurses and ncursesw 5.6 do not work due to incorrect path |
---|
comment:2 Changed 18 years ago by pipping@…
comment:3 Changed 18 years ago by vinc17@…
Yes, 5.5 worked. There's a discussion in the macports-users mailing-list about this bug, and I posted that:
In the ncurses 5.6 release notes: change the way shared libraries (other than libtool) are installed. Rather than copying the build-tree's libraries, link the shared objects into the install directory. This makes the --with-rpath option work except with $(DESTDIR).
I think this is what led to the bug in MacPorts.
comment:4 Changed 18 years ago by cssdev
A temporary workaround is to set DYLD_FALLBACK_LIBRARY_PATH
:
export DYLD_FALLBACK_LIBRARY_PATH=/opt/local/lib:/usr/local/lib
I think the ncurses port should use --without-rpath
when building.
comment:5 Changed 18 years ago by imajes@…
Owner: | changed from mww@… to imajes@… |
---|---|
Status: | new → assigned |
need to push 5.6 again, making it work
comment:6 Changed 18 years ago by master@…
As suggested at http://lists.macosforge.org/pipermail/macports-users/2007-January/001366.html install_name is to be fixed in configure
- MK_SHARED_LIB='${CC} ${CFLAGS} -dynamiclib -install_name ${DESTDIR}${libdir}/
basename $@
...
+ MK_SHARED_LIB='${CC} ${CFLAGS} -dynamiclib -install_name ${libdir}/basename $@
...
comment:7 Changed 18 years ago by pipping@…
Milestone: | → Available Ports |
---|
comment:9 Changed 18 years ago by pipping@…
Resolution: | → fixed |
---|---|
Status: | assigned → closed |
comment:10 Changed 18 years ago by jmpalacios (Juan Manuel Palacios)
Milestone: | Available Ports → Port Bugs |
---|---|
Priority: | Blocker → Expected |
did 5.5 work? (sounds like anything after 5.0 should be affected)