#1045: parrot needs a shared library even if configured with
--parrot_is_shared=0.
-----------------------+----------------------------------------------------
Reporter: doughera | Owner:
Type: bug | Status: new
Priority: normal | Milestone:
Component: configure | Version: 1.6.0
Severity: medium | Keywords:
Lang: | Patch:
Platform: |
-----------------------+----------------------------------------------------
Comment(by doughera):
> So this seems to me to be more of a build failure than a configuration
failure.
Fair enough.
> In contrast, when I modified my standard configuration command on
Darwin/PPC to include this option, I built successfully: [ . . . ]
> So there is something OS-specific going on here.
It's also possible to get a false success if there's a compatible
previously-built libparrot already installed somewhere that will get
picked up by the runtime dynamic loader. For example, on Solaris, you can
get a false positive by installing a compatible version of parrot and then
re-running Configure with the LD_LIBRARY_PATH environment variable set to
include the installation directory. Or, you can get the same effect by
installing parrot to a place where ldd automatically looks.
I suspect something like that is part of what's happening here.
I'd imagine there is also the possibility for OS-specific issues to arise.
Even with --parrot_is_shared=0, the root Makefile still builds both
libparrot.a and libparrot.so, and then links against -lparrot. Which one
gets used by the link editor in the final compilation step? I don't know
that there's any guaranteed unique answer.
--
Ticket URL: <https://trac.parrot.org/parrot/ticket/1045#comment:3>
Parrot <https://trac.parrot.org/parrot/>
Parrot Development
_______________________________________________
parrot-tickets mailing list
[email protected]
http://lists.parrot.org/mailman/listinfo/parrot-tickets
