Seems dynpmcs (or at least, one of the NQP ones) have ended up with a…

… call to Parrot_x_panic_and_exit; I don't see it used directly in the code, so I guess it's the PMC compiler or a macro that's introducing the call to it. Thus it must be marked PARROT_EXPORT. This unbusts NQP build on MSVC.
parrot · May 11, 2012 · 8fd4d39 · 8fd4d39
1 parent 9dd39b0
commit 8fd4d39
Show file tree

Hide file tree

Showing 2 changed files with 2 additions and 0 deletions.
diff --git a/include/parrot/exit.h b/include/parrot/exit.h
@@ -76,6 +76,7 @@ void Parrot_x_force_error_exit(
 
 PARROT_DOES_NOT_RETURN
 PARROT_COLD
+PARROT_EXPORT
 void Parrot_x_panic_and_exit(
     NULLOK_INTERP,
     ARGIN_NULLOK(const char *message),

diff --git a/src/exit.c b/src/exit.c
@@ -186,6 +186,7 @@ developers. Perform a full core dump and force exit back to the system.
 
 PARROT_DOES_NOT_RETURN
 PARROT_COLD
+PARROT_EXPORT
 void
 Parrot_x_panic_and_exit(NULLOK_INTERP, ARGIN_NULLOK(const char *message),
          ARGIN_NULLOK(const char *file), unsigned int line)