Ticket #1995 (closed bug: fixed)

Opened 3 years ago

Last modified 3 years ago

building a new release is broken; seem to be: "ops2c" is broken

Reported by: gerd Owned by:
Priority: normal Milestone:
Component: build Version: 3.0.0
Severity: medium Keywords:
Cc: Language:
Patch status: Platform:

Description

A new release build would fail at the moment. "ops2c" seems to be broken. Increasing the version number and running ops2c and make again would fail.

For example if 3.2.0 would be the new version number: The make would stop with:

src/runcore/cores.c: In function 'Parrot_runcore_debugger_init': src/runcore/cores.c:471:24: error: 'Parrot_DynOp_core_3_2_0' undeclared (first use in this function) gmake[1]: *** [src/runcore/cores.o] Error 1

Change History

Changed 3 years ago by gerd

src/runcore/cores.c: In function 'Parrot_runcore_debugger_init':
src/runcore/cores.c:471:24: error: 'Parrot_DynOp_core_3_2_0' undeclared (first use in this function)
gmake[1]: *** [src/runcore/cores.o] Error 1

Changed 3 years ago by cotto

op2c requires a bit of care when bumping Parrot's version number, but this is all documented in the release manager guide. If I follow the instructions there, the build works fine. Can you verify that it works (or doesn't) when following the relevant part of the release manager guide, copy/pasted below? Note the bit about ignoring errors.

To have parrot configured and have run C<make> with the old version number is
condition for this step. Run C<./ops2c --core> (or C<make bootstrap-ops>,
ignoring errors) followed by C<make reconfig> and C<make> to update the names
of version-specific internal functions.

Changed 3 years ago by gerd

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

You are correct. I do not made a step. Apologize!

Note: See TracTickets for help on using tickets.