At 3:49 PM -0500 11/4/04, Sam Ruby wrote:
Background: Pmc2c.pm emits code which references Parrot_PMC_typenum. This code is present in libparrot.so, which currently is not referenced as a library by the link step for dynclasses.

Options include:

  1) eliminating this dependency, as it is the only one
  2) directly including extend.o into each shared library
  3) linking to libparrot.so

#3's the right thing here. PMC classes have access to enough of the internals that linking to libparrot's fine. If we're feeling paranoid we can define a PMC API and link against a shared library that exposes it, but that's a bit much for now.


As an added complication, the link step for dynclasses is by default run from a different directory than the main build.

Pfui. Probably ought to be fixed. -- Dan

--------------------------------------it's like this-------------------
Dan Sugalski                          even samurai
[EMAIL PROTECTED]                         have teddy bears and even
                                      teddy bears get drunk

Reply via email to