[MacPorts] #34509: fail to upgrade openjdk6_bootstrap b16-r1_0 with broken files
MacPorts
noreply at macports.org
Wed Oct 17 02:02:07 PDT 2012
#34509: fail to upgrade openjdk6_bootstrap b16-r1_0 with broken files
---------------------------------+-------------------------
Reporter: flier.lu@… | Owner: landonf@…
Type: defect | Status: new
Priority: Normal | Milestone:
Component: ports | Version: 2.1.0
Resolution: | Keywords: rev-upgrade
Port: openjdk6_bootstrap |
---------------------------------+-------------------------
Comment (by supermanberger@…):
Replying to [comment:2 cal@…]:
> Actually, after taking an in-depth look, I think rev-upgrade's claim
here is valid:
>
> - e.g. `/opt/local/share/java/openjdk6_bootstrap/bin/appletviewer` is
i386, and references `/opt/local/lib/libX11.6.dylib`, which is present,
but not i386 on my system.
> - some files reference non-existant files, e.g.
`/opt/local/share/java/openjdk6_bootstrap/jre/lib/i386/headless/libmawt.dylib`
links against `/opt/local/var/macports/build
/_data_Users_landonf_Documents_Code_MacPorts_macports-
trunk_dports_java_openjdk6/work/build/bsd-i586/lib/i386/libjava.dylib`.
Those paths should be fixed using `install_name_tool(1)`.
> - some files link against relative paths, e.g.
`/opt/local/share/java/openjdk6_bootstrap/jre/lib/i386/headless/libmawt.dylib`
against `libjvm.dylib`. Those should be changed to absolute paths using
`install_name_tool(1)` where possible.
>
> I'm not sure this has ever worked on a non-i386 macports or in a
macports installation with different prefix than `/opt/local`.
Sorry, I can't follow your answer, so I need to use the install_name_tool
to do what? I've never used this command and the syntax for it has me
baffled.
Is this a fixable problem?
--
Ticket URL: <https://trac.macports.org/ticket/34509#comment:19>
MacPorts <http://www.macports.org/>
Ports system for Mac OS
More information about the macports-tickets
mailing list