GLIBC the plugin is built with is too new

[Zeks]

It's not possible to use the plugin on older linux distributions because it requires glibc version that they simply do not have despite qtcreator 15 working just fine. It's quite possible that it's an oversight than actual requirement to have it.

[Palm1r]

Qt Creator 15 works but plugin not? correct?

[Zeks]

yes, creator itself works just fine. this error message is a symptom of a lib that was built on a cutting edge glibc, seen this a ton of times. you need to build on a reasonably old glibc to support people running it who aren't running the newest systems

[Palm1r]

I use template for creating QtCreator plugin from Qt Creator 15 and Qt Creator binaries that Qt shared. As far as I remember they are for rhel_8.10. Maybe in my github actions some errors and would be wonderful to fix it. You can check it. If not, I don't have resources to make separate build system and create everything manually for old stuff.

[scoute]

I have the same problem.
I use Debian 11 (GLIBC_2.31) and Qt Creator 15 works well on it, but the plugin crashes with a high glibc version error (GLIBC_2.38).

As far as I know, the glibc version of build is inherited from the operating system, not Qt Creator.

P.S.
I want to compile this plugin on Debian 11, but I don't understand how ((
Readme instructions do not contain an example.

P.P.S.
It would be nice to compile the plugin directly from Qt Creator ))

[Palm1r]

@scoute make fork and change in github action platform to ubuntu 22.04. Check released binaries.
Like that, #56, but I can't check on OS

[Palm1r]

@scoute @Zeks please try to use this
QodeAssist-15.0.0-Linux-x64.7z.zip
I built for ubuntu 22.04

[scoute]

Great thanks!
But ubuntu 22.04 is too new also )) the same error.
Debian 11 = ubuntu 20.04. Can you?

[hellowheat]

Thank you for your sharing, it’s been incredibly helpful to me. I’m currently helping our project team integrate AI into an offline intranet environment. However, our company is using very old systems, including: qtcreator 4.6.0, CentOS 7, and glibc 2.17. I have already deployed Ollama and Qwen, and I can interact with them. Now I’m trying to learn and modify your code, hoping to use it with qtcreator 4.6.0. But this environment is really old, and I’m not confident about succeeding 😂.

In any case, I’m very grateful for your sharing (really, really grateful—without it, I’d have to start from scratch with an empty project). If I succeed, I will let you know as soon as possible. ❤❤❤

[Palm1r]

@hellowheat Thank you for your kind words, it's nice to hear.

[Tezcan98]

I had the same error before with Ubuntu 20.04 and Centos 8.5. As a solution, when I built the code myself, the error was resolved. If your project is offline, you can build it from a virtual machine connected to the internet. If you wish, I can even upload my own .so file as a pull request. But I'm not sure if the qt versions are compatible, I used qt 6.8.

[Daguerreo]

Same problem here with Debian 11. Could you provide a version compiled with an older glibc?

[Palm1r]

QodeAssist-15.0.1-Ubuntu-22.04-experimental.7z.zip

@Daguerreo does this work for you?
Previously I added PIC to build, maybe it improve issue with compatibility

[Daguerreo]

QodeAssist-15.0.1-Ubuntu-22.04-experimental.7z.zip

@Daguerreo does this work for you? Previously I added PIC to build, maybe it improve issue with compatibility

As scoute already mentioned, ubuntu 22-04 it's still too new, since Debian 11 = Ubuntu 20.04, but thanks for the fast reply!

[Palm1r]

For ubuntu 20.04 I cant build, error under hood Qt6.8

[p12tic]

In theory this plugin could be built for Ubuntu 20.04 if Qt 6.4 and Qt Creator 15 were used. Qt Creator 16 raises minimum Qt version to 6.5 and thus Ubuntu 20.04 cannot be supported because it's not supported by Qt.

[p12tic]

However, Ubuntu 20.04 is already 2 LTS releases away, so probably it's not worth spending time on. An IDE such as Qt Creator is rather quickly moving target.

[p12tic]

I think this bug can be closed because there's little we can do.

[Palm1r]

agree, I will write conclusion to README and close this bug