Opened 13 months ago

Last modified 9 months ago

#67286 assigned defect

podofo @0.9.8_0 - Does it need a newer lua version?

Reported by: snowflake (Dave Evans) Owned by: dbevans (David B. Evans)
Priority: Normal Milestone:
Component: ports Version: 2.8.99
Keywords: Cc: mascguy (Christopher Nielsen)
Port: podofo

Description

podofo failed with linking errors:

Undefined symbols for architecture x86_64:
  "_luaL_loadfilex", referenced from:
      imp_lua_dofile(lua_State*, char const*) in luaconverter.cpp.o
  "_lua_callk", referenced from:
      LuaConverter::StartPage(PoDoFo::PdfPage*, int) in luaconverter.cpp.o
      LuaConverter::EndPage(PoDoFo::PdfPage*, int) in luaconverter.cpp.o
      LuaConverter::StartXObject(PoDoFo::PdfXObject*) in luaconverter.cpp.o
      LuaConverter::EndXObject(PoDoFo::PdfXObject*) in luaconverter.cpp.o
      LuaConverter::SetStrokingColorGray(PoDoFo::PdfColor const&) in luaconverter.cpp.o

and many more.

I tested on El Capitan and Ventura.

I changed the default lua version in the lua portgroup:

diff --git a/_resources/port1.0/group/lua-1.0.tcl b/_resources/port1.0/group/lua-1.0.tcl
index 98dafea7d2c..56e203edaeb 100644
--- a/_resources/port1.0/group/lua-1.0.tcl
+++ b/_resources/port1.0/group/lua-1.0.tcl
@@ -54,7 +54,7 @@ default lua.finds_versioned {no}
 
 # default Lua version
 options lua.default_version
-default lua.default_version {5.3}
+default lua.default_version {5.4}
 global  lua.default_version
 
 # all Lua versions

and it now builds. I realise that this is a hack and it is not the recommended way to change it.

I do not know why the buildbots are succeeding where my local build failed.

Change History (3)

comment:1 Changed 13 months ago by ryandesign (Ryan Carsten Schmidt)

Are you using trace mode, to rule out opportunistic use of non-dependencies?

You can get the buildbot logs at https://ports.macports.org/port/podofo/builds/ and compare them with yours to see what's different.

comment:2 Changed 13 months ago by snowflake (Dave Evans)

On El Capitan, building in trace mode does work.

Cleaning the port and building without trace mode now also works, so whatever dependency it requires has now been installed. It remains a mystery as to what dependency has been installed by this process.

On Ventura, building in trace mode generates an Apple crash report. This may be caused by

/opt/local/var/macports/sip-workaround/501/usr/bin/sandbox-exec
/opt/local/var/macports/sip-workaround/502/usr/bin/sandbox-exec

not being codesigned

The error is

Exception Type:  EXC_CRASH (SIGKILL (Code Signature Invalid))
Exception Codes: 0x0000000000000000, 0x0000000000000000
Termination Reason: CODESIGNING 4 Launch Constraint Violation

comment:3 Changed 9 months ago by mascguy (Christopher Nielsen)

Cc: mascguy added
Note: See TracTickets for help on using tickets.