Ticket #424 (closed bug: invalid)

Opened 13 years ago

Last modified 13 years ago

tools/dev/mk_native_pbc failed on Solaris/sparc32/SunPro cc

Reported by: doughera Owned by:
Priority: normal Milestone:
Component: none Version:
Severity: medium Keywords:
Cc: rg@… Language:
Patch status: Platform: solaris


I have never actually gotten this tool to work. Attached is my most recent attempt. It claims to have generated new files, but then it fails the test for t/native_pbc/integer_6.pbc with the unhelpful error message:

# Unable to open filehandle
# current instr.: '(null)' pc -1 ((unknown file):-1)
# called from Sub '(null)' pc -1 ((unknown file):-1)
# called from Sub '(null)' pc 0 (-:1)

(see attachment for full log.)


solaris-sparc32-mk_native_pbc.txt Download (3.4 KB) - added by doughera 13 years ago.

Change History

Changed 13 years ago by doughera

in reply to: ↑ description   Changed 13 years ago by rg

Replying to doughera:

I have never actually gotten this tool to work.

The tools works well enough for me, as you can see from the native_pbc files I'm posting to the list. However, I do agree that it's quite quirky. It must be run with bash and it assumes parrot was configured without gmake (it explicitly calls make, which fails if gmake was found). Also, I've never used it without the --noconf argument. (I don't think it can pass all the arguments I'm using to configure parrot.) Can you be more clear on how you're running it?

  Changed 13 years ago by rg

  • cc rg@… added

  Changed 13 years ago by doughera

I am running it with --noconf as well, for the same reasons -- the script is indeed quite "quirky", and the make/gmake issue hit me as well. I ran into so many other problems today trying to get to just this point that I have run out of time and am giving up for now.

  Changed 13 years ago by doughera

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

This issue proved difficult to reproduce reliably, and the tool is not used at present. As part of TT #357, it will likely be sensible to re-visit this script. At that point, it would make sense to open fresh tickets to deal with specific issues that may arise. For now, though, I have marked this as "invalid". ("Abandoned" would be a better description, but that label is not available.)

Note: See TracTickets for help on using tickets.