xercesc3 @3.3.0: Ports using libxerces-c-3.3.dylib fail: symbol not found in flat namespace '_xercesc_messages_3_2_dat'

[matty0ung (Matt Young)]

Up until a day or two ago, xalanc was working just fine. However, after xercesc3 was upgraded yesterday or the day before from 3.2.4 to 3.3.0, xalanc no longer installs. During the install you get an error "symbol not found in flat namespace '_xercesc_messages_3_2_dat'" during "Linking CXX executable MsgCreator"

[reneeotten (Renee Otten)]

please add the main.log file that is mentioned in the error message as an attachment to this ticket

[matty0ung (Matt Young)]

I don't have direct access to the main.log file. I don't own a Mac and am doing everything remotely via GitHub Actions. (It's for the automated builds of ​https://github.com/Brewtarget/brewtarget, which runs on Windows, Mac and Linux, courtesy of Qt.) But I'll see what extra diagnostics I can get.

[matty0ung (Matt Young)]

Output from port installed and port -v install xercesc3

[ryandesign (Ryan Carsten Schmidt)]

--->  Scanning binaries for linking errors
Could not open /opt/local/lib/libxerces-c-3.2.dylib: Error opening or reading file (referenced from /opt/local/bin/Xalan)

So the libxerces install_name has changed, so all ports that link with that library (including xalanc) need to have their revisions increased. This was done three hours ago in [4fed8441fb0295a152ad273b6bba7f4c0f5278e6/macports-ports]. In addition, at least xalanc apparently needs a patch for compatibility with xercesc version 3.3.

[ryandesign (Ryan Carsten Schmidt)]

I am able to reproduce the xalanc build failure but I now think this is a bug in xercesc3 @3.3.0 because other ports fail with the same message. nco for example fails to configure; its config.log says:

configure:5274: checking whether we are cross compiling
configure:5282: ccache /usr/bin/clang -o conftest -pipe -Os -isysroot/Library/Developer/CommandLineTools/SDKs/MacOSX12.sdk -arch x86_64 -I/opt/local/include -I/opt/local/include/udunits2 -I/opt/local/include -DENABLE_NETCDF4 -isysroot/Library/Developer/CommandLineTools/SDKs/MacOSX12.sdk -L/opt/local/lib -Wl,-headerpad_max_install_names -lxerces-c -Wl,-rpath,/opt/local/lib/libgcc -Wl,-syslibroot,/Library/Developer/CommandLineTools/SDKs/MacOSX12.sdk -arch x86_64 conftest.c  >&5
configure:5286: $? = 0
configure:5293: ./conftest
dyld[5155]: symbol not found in flat namespace (_xercesc_messages_3_2_dat)
./configure: line 5295:  5155 Abort trap: 6           ./conftest$ac_cv_exeext
configure:5297: $? = 134
configure:5304: error: in '/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_science_nco/nco/work/nco-5.2.9':
configure:5306: error: cannot run C compiled programs.

enigma builds and installs but it fails to run:

% enigma
dyld[17071]: symbol not found in flat namespace (_xercesc_messages_3_2_dat)
zsh: abort      enigma

I believe the problem is in the file ​src/xercesc/util/MsgLoaders/ICU/ICUMsgLoader.cpp which says:

/*
 *  Resource Data Reference.
 *
 *  The data is packaged as a dll (or .so or whatever, depending on the platform) that exports a data symbol.
 *  The application (this *.cpp) references that symbol here, and will pass the data address to ICU, which
 *  will then  be able to fetch resources from the data.
 */
#define ENTRY_POINT xercesc_messages_3_2_dat
#define BUNDLE_NAME "xercesc_messages_3_2"

Surely for version 3.3.x that should be 3_3 not 3_2.

[ryandesign (Ryan Carsten Schmidt)]

I've filed this bug report to see if the developers concur: ​https://issues.apache.org/jira/browse/XERCESC-2257

[ryandesign (Ryan Carsten Schmidt)]

Replying to ryandesign:

Surely for version 3.3.x that should be 3_3 not 3_2.

Making that change works for me: ​https://github.com/macports/macports-ports/pull/26597