Ticket #441 (closed bug: fixed)

Opened 6 years ago

Last modified 6 years ago

make parrot_utils blows up on darwin

Reported by: dukeleto Owned by:
Priority: normal Milestone:
Component: none Version: 0.9.0
Severity: medium Keywords:
Cc: Language:
Patch status: Platform: darwin

Description

rsync -av --delete svn.perl.org::parrot-HEAD parrot  &&  cd parrot && perl Configure.pl && make parrot_utils

It finally dies with

powerpc-apple-darwin9-g++-4.0.1: src/parrot_config.o: No such file or directory

after many ominous warnings.

Attachments

parrot_utils-bug.txt Download (37.8 KB) - added by dukeleto 6 years ago.
Full output of perl Configure.pl && make parrot_utils

Change History

Changed 6 years ago by dukeleto

Full output of perl Configure.pl && make parrot_utils

in reply to: ↑ description ; follow-ups: ↓ 2 ↓ 4   Changed 6 years ago by jkeenan

This looks to me like a make failure, i.e., a failure that has nothing specifically to do with make parrot_utils.

Do you get this error when you simply call make?

Can you post your myconfig information? The OS/platform combination is likely to be relevant here?

Thank you very much.
kid51

in reply to: ↑ 1   Changed 6 years ago by jkeenan

Replying to jkeenan:

This looks to me like a make failure, i.e., a failure that has nothing specifically to do with make parrot_utils.

OTOH, I concede that make parrot_utils does not seem to require that Parrot itself be built. From Makefile:

parrot_utils : $(PDUMP) $(DIS) $(PINFO) $(PDB) $(PBCMERGE) $(PBC_TO_EXE) $(PARROT_CONFIG)

This does not require make target all to have succeeded.

kid51

  Changed 6 years ago by coke

Your command here is pulling from the old repository's rsync mirrors, which stopped updating after the repository switched to parrot.org.

in reply to: ↑ 1   Changed 6 years ago by jkeenan

Using Mac OS X 10.4.11 PPC, I was able to call make, make clean and then make parrot_utils all successfully. So my original hunch was wrong: You should be able to call make parrot_utils without a pre-existing Parrot executable.

So let me speculate. You have a configuration problem at auto::readline:

auto::readline -      Does your platform support readline...dyld: lazy symbol binding failed: Symbol not found: _rl_get_keymap
  Referenced from: /private/var/folders/Ag/AgvwlP-c2Rqw7++BYodms++++TI/-Tmp-/k9PDlLzxnS/parrot/./test_19588
  Expected in: dynamic lookup

dyld: Symbol not found: _rl_get_keymap
  Referenced from: /private/var/folders/Ag/AgvwlP-c2Rqw7++BYodms++++TI/-Tmp-/k9PDlLzxnS/parrot/./test_19588
  Expected in: dynamic lookup

.............done.

We saw this problem quite a bit about a year ago (see  RT 52212 and  RT 56030) and I don't think we ever fully corrected it. On Darwin/PPC, I do not get the problem -- but there were points where people proposed patches that did give me the problem. But I believe the problem does occur on different combinations of OS X version and chip (perhaps the early 10.5s on PPC).

I suspect that the problem at config step auto::readline is connected to the fact that it was while attempting to configure the Parrot debugger that your parrot_utils blew up.

follow-up: ↓ 6   Changed 6 years ago by dukeleto

I tried this with trunk on the same machine, and while I still get many of the same warnings, parrot_utils builds successfully and make fulltest passes all tests as well.

 http://smolder.plusthree.com/app/public_projects/report_details/18985

Motion to close this ticket and open up tickets to fix warnings.

in reply to: ↑ 5   Changed 6 years ago by jkeenan

Replying to dukeleto:

I tried this with trunk on the same machine,

Does that imply that your original post was not run on trunk?

follow-up: ↓ 8   Changed 6 years ago by coke

jkeenan: As I noted in comment #3:

"Your command here is pulling from the old repository's rsync mirrors, which stopped updating after the repository switched to parrot.org."

So, he was not pulling from parrot.org's trunk, no. He was getting whatever the last revision was on the old perl.org servers.

in reply to: ↑ 7   Changed 6 years ago by jkeenan

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

Replying to coke:

Thanks for the clarification. Closing ticket.

Note: See TracTickets for help on using tickets.