qt4-mac-devel fails on Catalina

[barracuda156]

@RJVB Something does not work on Catalina. Initially I took my port (which is somewhat tweaked), it built, but failed to destroot at:

--->  Patching qttracereplay: s|@BUNDLEEXEC@|/Applications/MacPorts/Qt4/qttracereplay.app/Contents/MacOS/qttracereplay|g
Error: Failed to destroot qt4-mac-devel: error renaming "/opt/local/var/macports/build/_opt_local_var_macports_sources_macos-powerpc.org_macos-powerpc_PPCPorts_ports_aqua_qt4-mac-devel/qt4-mac-devel/work/destroot/opt/local/libexec/qt4/tests/qt4": no such file or directory
Error: See /opt/local/var/macports/logs/_opt_local_var_macports_sources_macos-powerpc.org_macos-powerpc_PPCPorts_ports_aqua_qt4-mac-devel/qt4-mac-devel/main.log for details.
Error: Follow https://guide.macports.org/#project.tickets if you believe there
is a bug.
Error: Processing of port qt4-mac-devel failed

Apparently this is the command in the portfile which fails:

move ${destroot_qt}/tests/qt4 ${destroot}${qt_data_dir}/tests

This is with clang and libc++, so pretty much standard set-up, though with my PGs.

Anyway, I thought maybe I accidentally messed something up for Intel, since never really cared about it, so I borrowed the original port and qt4* PGs from here, put into a local overlay, and then it failed immediately, right on configure:

--->  Configuring qt4-mac-devel
qt_arch_types=x86_64 but os.arch==i386 ; ignoring and building optimised qmake anyway
Error: Failed to configure qt4-mac-devel: extra characters after close-quote
Error: See /opt/local/var/macports/logs/_opt_CatalinaPorts_aqua_qt4-mac-devel/qt4-mac-devel/main.log for details.
Error: Follow https://guide.macports.org/#project.tickets if you believe there
is a bug.
Error: Processing of port qt4-mac-devel failed

Has it been confirmed to build on x86 in the current version?

[barracuda156]

This is with the original port from here:

qt4-mac-devel.log.txt

[RJVB]

On Sunday May 11 2025 06:40:18 Sergey Fedorov wrote: Sorry, forgot about this one

Has it been confirmed to build on x86 in the current version?

Yes, on my machine, but thus against a patched "base". The only explanation I can see for the specific error you're getting about a close quote is that you're not using (all) my "base" patches and thus don't have the added function to fetch the name of the logfile. That means that the `save_configure_cmd` PG will change the configure.*args options. You can test that by adding some trace output in the block that starts at line 31 of save_configure_cmd-1.0.tcl . This *may* have to do with the line ``` configure.args-append -arch \"${qt_arch_types}\" ``` in the Portfile. I'm afraid it's not a good idea to remove the backslashes or even the quoting altogether, but you can try that too (but try a universal build in that case!)

[barracuda156]

The only explanation I can see for the specific error you're getting about a close quote is that you're not using (all) my "base" patches

@RJVB Yes, that is definitely the case, for MacOS I have only borrowed what was needed to fix portgroups search plus a couple of extra patches, not everything.

[RJVB]

On Thursday May 15 2025 12:29:13 Sergey Fedorov wrote: @RJVB Yes, that is definitely the case, for MacOS I have only borrowed what was needed to fix portgroups search plus a couple of extra patches, not everything.

I find the save_configure_cmd PG particularly useful, as it allows me to know exactly how a port was configured without having to keep the workdir around. IIRC I added the functions to obtain info about the logfile (and flush it) because of errors of the kind you're seeing now with port:qt4-mac-devel