#344: Can't create working installed parrot for macports
---------------------+------------------------------------------------------
Reporter: coke | Owner: coke
Type: bug | Status: new
Priority: major | Milestone: 1.1
Component: install | Version:
Severity: medium | Resolution:
Keywords: | Lang:
Patch: | Platform:
---------------------+------------------------------------------------------
Comment(by tommyd):
Replying to [comment:10 doughera]:
> On Mon, 2 Aug 2010, Parrot wrote:
> > libparrot_soname => '-install_name
> >
/opt/local/var/macports/build/_Users_tommyd_Entwicklung_MacPorts_dports_lang_parrot/work/parrot-2.6.0/blib/lib/libparrot.dylib'
>
> I don't what this is actually used for, so I don't know if it's a
> problem or not.
ld(1) states:
{{{
-install_name name
Sets an internal "install path" (LC_ID_DYLIB) in a
dynamic library. Any clients
linked against the library will record that path as the
way dyld should locate this
library. If this option is not specified, then the -o
path will be used. This
option is also called -dylib_install_name for
compatibility.
}}}
All created binaries which link to libparrot.dylib record currently the
wrong lib (build) path and therefor fail to execute once they're installed
as the library loader of osx can't find the library under the old
(temporary) build path anymore. Ideally, libparrot_soname should be
something like "-install_name $PREFIX/lib/libparrot.dylib", where $PREFIX
is replaced by the value of --prefix on installation time.
Note that this is not only a problem of rakudo, but of all supplied parrot
binaries as well.
--
Ticket URL: <https://trac.parrot.org/parrot/ticket/344#comment:11>
Parrot <https://trac.parrot.org/parrot/>
Parrot Development
_______________________________________________
parrot-tickets mailing list
[email protected]
http://lists.parrot.org/mailman/listinfo/parrot-tickets
