On 4/27/07, Yehoshua Sapir <[EMAIL PROTECTED]> wrote:
See #34994: http://rt.perl.org/rt3/Ticket/Display.html?id=34994 (I tried to reply earlier to #34994 on RT but I guess that wasn't the right way to do it.) Anyway, there seems to be a long discussion about this at #34994. I've now tried running make reallyinstall . The runtime prefix returned is /usr/local, while the runtime/parrot directory gets installed to /usr/local/lib/parrot, and config.fpmc is in /usr/local/lib/parrot/include. That means config.pir is looking for config.fpmc in /usr/local/runtime/parrot/include, which is wrong. I don't know what the runtime prefix is good for right now. grepping in my parrot directory returned just the parts in imcc that handle the command-line, running.pod explaining about it, library.c that provides Parrot_get_runtime_prefix, and inter_misc.c that gives the interpinfo option. IMHO, the runtime prefix should probably be parrot/runtime rather than just the parrot dir, and /usr/local/lib (in my case) when installed rather than just /usr/local. I don't know how this relates to what they were doing regarding #34994. In any case, even if the interpinfo part of my patch will be useful someday, the part in config.pir is probably wrong, and it definitely won't work right now when Parrot's installed. On 4/27/07, Matt Diephouse via RT <[EMAIL PROTECTED] > wrote: > > According to our records, your request regarding > "[PATCH] add runtime_prefix for interpinfo and use it in config.pir" > has been resolved. > > If you have any further questions or concerns, please respond to this > message. > > For other topics, please create a new ticket. > > Please don't feel obligated to say "Thanks" or "Kudos" or "I owe you a > beer" -- if you respond to this message it will reopen the ticket. If you > must, please send email directly to the person who handled your ticket, and > not to the tracking system. > > <URL: http://rt.perl.org/rt3/Ticket/Display.html?id=42558 > > On 4/27/07, Matt Diephouse via RT <[EMAIL PROTECTED]> wrote: > > According to our records, your request regarding > "[PATCH] add runtime_prefix for interpinfo and use it in config.pir" > has been resolved. > > If you have any further questions or concerns, please respond to this > message. > > For other topics, please create a new ticket. > > Please don't feel obligated to say "Thanks" or "Kudos" or "I owe you a > beer" -- if you respond to this message it will reopen the ticket. If you > must, please send email directly to the person who handled your ticket, and > not to the tracking system. > > <URL: http://rt.perl.org/rt3/Ticket/Display.html?id=42558 > >
ok, having looked through some of the source now... I don't know yet what config.pir and config.fpmc are good for, they seem to be just returning the same thing that's stored inside the Parrot executable as getinterp[.IGLOBALS_CONFIG_HASH]. AFAICT, runtime_prefix checks the PARROT_RUNTIME env variable and then defaults to whatever the config hash has under the 'prefix' key. Maybe I'm misunderstanding the function of runtime_prefix (it is used in library.c in Parrot_locate_runtime_file_str as a search path) but I think that if I'm wrong, at the very least the installed Parrot's config hash should contain another 'runtime_prefix' key which would have the values I was expecting. (Assuming runtime/parrot really does get installed to a single directory. If the directories inside runtime/parrot don't necessarily have to be installed in the same place, then there'd be a key for each.)
