Cannot build w/- Ubuntu 25.04

[stephematician]

Clean Ubuntu 25.04 image (running in a VM).

I installed golang-go and qtbase5-dev from APT (to ensure I had qmake), then I cloned the goneovim repository, then:

export QT_QMAKE_DIR=/usr/lib/x86_64-linux-gnu/qt5/bin
make qt_bindings

I get the following error:

...
go: downloading github.com/akiyosi/w32 v0.0.0-20240207145154-5d3ee780f6cb
WARN[0000] failed to patch binaries
you won't be able to simply "go build/run" your application, but qtdeploy-ing applications should work nevertheless  error="exit status 1"
INFO[0000] running: 'qtsetup prep'                      
PANI[0000] failed to remove /usr/local/bin/qtrcc         error="unlinkat /usr/local/bin/qtrcc: permission denied"

No clue why it's trying to unlink qtrcc.

[akiyosi]

@stephematician
Thanks for this report.
I don't have an Ubuntu 25.04 environment so I can't investigate immediately.
Looking at the error message, it says “permission denied”, but what happens if I run it as root user or sudo?

[stephematician]

I don't think running it as root and letting it do what it wants is a good idea; it shouldn't have to delete files within /usr that aren't part of goneovim.

This doesn't seem like a problem with goneovim specifically; but there's something missing from the build instructions for Ubuntu (or perhaps Debian-based distributions more generally).

[akiyosi]

@stephematician
Would you please tell me the stdout immediately after running make qt_bindings?

[thjbdvlt]

I experience a similar issue with Debian 12.
Here is the log:

failed to patch binaries
you won't be able to simply "go build/run" your application, but qtdeploy-ing applications should work nevertheless" error="exit status 1
running: 'qtsetup prep'
failed to create qtrcc symlink in your PATH (/sbin/qtrcc); please use /home/USER/go/bin/qtrcc instead
failed to create qtmoc symlink in your PATH (/sbin/qtmoc); please use /home/USER/go/bin/qtmoc instead
failed to create qtminimal symlink in your PATH (/sbin/qtminimal); please use /home/USER/go/bin/qtminimal instead
failed to create qtdeploy symlink in your PATH (/sbin/qtdeploy); please use /home/USER/go/bin/qtdeploy instead
running: 'qtsetup check linux' [docker=false] [vagrant=false]
GOOS:                        'linux'
GOARCH:                      'amd64'
GOVERSION:                   'go1.24.4'
GOROOT:                      '/usr/local/go'
GOPATH:                      '/home/USER/go'
GOBIN:                       '/home/USER/go/bin'
GOMOD:                       '/home/USER/path/to/goneovim/go.mod'
QT_HASH:                     'v0.0.0-20240304155940-b43fff373ad5'
QT_API:                      ''
QT_VERSION:                  '5.13.0'
QT_DIR:                   *  '.'
QT_STUB:                     'false'
QT_DEBUG:                    'false'
QT_QMAKE_DIR:                ''
QT_WEBKIT:                   'false'
QT_STATIC:                   'false'
QT_GEN_GO:                   'false'
QT_GEN_OPENGL:               'false'
QT_GEN_QUICK_EXTRAS:         'false'
QT_RESOURCES_BIG:            'false'
QT_NOT_CACHED:               'false'
QT_DISTRO:                   'ubuntu'
QT_PKG_CONFIG:               'false'
running: 'qtsetup generate linux' [docker=false] [vagrant=false]
failed to run command" _func=RunCmd cmd="5.13.0/gcc_64/bin/qmake -query QT_INSTALL_PREFIX" dir= env= error="fork/exec 5.13.0/gcc_64/bin/qmake: no such file or directory" name="query install prefix path for linux on linux

I cannot try with sudo for now, because go executable is only installed in my user home. Maybe that's part of the issue?

(I've installed Go with the method described here, and have already installed the apt-get dependencies listed here and here.)

[akiyosi]

@thjbdvlt
Hi :)
It looks like the issue is caused by qmake not being found in the expected path.
You can likely resolve this by explicitly setting the QT_QMAKE_DIR environment variable to the full path where qmake is located.
Then rerun qtsetup. This should allow it to correctly locate qmake and proceed without errors.

Let me know if that works for you.

[thjbdvlt]

Well I'm so sorry, I could have found out by myself if I had read the log more consciously. My issue was in no way related to the previous one. Now I have other issues with the qtsetup install part, but I may open a new issue if I can't find a solution by myself.