Ticket #1454 (closed bug: fixed)

Opened 4 years ago

Last modified 3 years ago

make failing for parrot when rakudo git repo path in $PATH environment variable

Reported by: snarkyboojum Owned by: jkeenan
Priority: normal Milestone:
Component: configure Version: trunk
Severity: low Keywords:
Cc: Language:
Patch status: Platform: darwin

Description

I've been debugging a parrot build error on my OS X machine all afternoon and think I have found the source of the issue.

I've previously installed parrot via Rakudo, and was attempting to install Parrot again. 'make' was failing with an error suggesting that libraries couldn't be found ( http://paste.lisp.org/display/95091), specifically -lparrot. It turned out that I had an old rakudo git repo path in my $PATH, and this was causing the parrot build to use the wrong lib paths, so even doing a make on a separate parrot SVN copy was still trying to use rakudo/blib/lib. Removing the rakudo git repo path from my $PATH fixed the issue.

I didn't trace through the whole parrot configure process but it seemed to be something to do with the steps in inter::libparrot? i.e. config/inter/libparrot.pm

Simply removing the rakudo git repo path from $PATH allowed the parrot build ('make') to continue properly from the rakudo configure script, and also from a separate parrot SVN checked out copy.

Change History

in reply to: ↑ description   Changed 4 years ago by jkeenan

Replying to snarkyboojum:

I didn't trace through the whole parrot configure process but it seemed to be something to do with the steps in inter::libparrot? i.e. config/inter/libparrot.pm

To study this more closely, you can run perl Configure.pl --configure_trace, then follow the documentation in lib/Parrot/Configure/Trace.pm to analyze what happens from one config step to the next.

Simply removing the rakudo git repo path from $PATH allowed the parrot build ('make') to continue properly from the rakudo configure script, and also from a separate parrot SVN checked out copy.

It sounds like you solved your own problem. Is there any thing that Parrot needs to do at this point? (If not, I'd like to close the ticket.)

Thank you very much.

kid51

  Changed 3 years ago by jkeenan

  • status changed from new to assigned
  • owner set to jkeenan

Having heard nothing from the OP in this ticket, I am taking it for the purpose of closing it in two or three days.

Thank you very much.

kid51

  Changed 3 years ago by jkeenan

  • status changed from assigned to closed
  • resolution set to fixed

No comments or complaints; closing ticket.

Note: See TracTickets for help on using tickets.