Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

wails v2.8.2 Build error - could not determine kind of name for C.free #3538

Open
fanspace opened this issue Jun 15, 2024 · 3 comments
Open
Labels
Bug Something isn't working

Comments

@fanspace
Copy link

fanspace commented Jun 15, 2024

Description

wails build occur error
Compiling application: # github.com/wailsapp/wails/v2/pkg/assetserver/webview
../../go/pkg/mod/github.com/wailsapp/wails/[email protected]/pkg/assetserver/webview/responsewriter_linux.go:113:2: could not determine kind of name for C.free

To Reproduce

When running either wails dev or wails build, the same error occurs

Expected behaviour

finish the compilation

Screenshots

1718465106994
1718465119906

Attempted Fixes

No response

System Details

# Wails
Version         | v2.8.2
Package Manager | apt   

# System
┌──────────────────────────────────────────────────────────┐
| OS           | Ubuntu                                    |
| Version      | 16.04                                     |
| ID           | ubuntu                                    |
| Go Version   | go1.22.4                                  |
| Platform     | linux                                     |
| Architecture | amd64                                     |
| CPU          | Intel(R) Core(TM) i7-4790K CPU @ 4.00GHz  |
| GPU          | SVGA II Adapter (VMware) - Driver: vmwgfx |
| Memory       | 8GB                                       |
└──────────────────────────────────────────────────────────┘

# Dependencies
┌───────────────────────────────────────────────────────────────────────────┐
| Dependency | Package Name          | Status    | Version                  |
| *docker    | docker.io             | Available | 18.09.7-0ubuntu1~16.04.7 |
| gcc        | build-essential       | Installed | 12.1ubuntu2              |
| libgtk-3   | libgtk-3-dev          | Installed | 3.18.9-1ubuntu3.3        |
| libwebkit  | libwebkit2gtk-4.0-dev | Installed | 2.20.5-0ubuntu0.16.04.1  |
| npm        | npm                   | Installed | 7.10.0                   |
| *nsis      | nsis                  | Available | 2.50-1                   |
| pkg-config | pkg-config            | Installed | 0.29.1-0ubuntu1          |
└───────────────────────── * - Optional Dependency ─────────────────────────┘

Additional context

Both on Ubuntu 18 and Ubuntu 20, Wails operates smoothly. However, due to various constraints with my client's computer which prevents an upgrade, it necessitates the use of glibc 2.23; hence, I am compelled to utilize an older version of Ubuntu as the compilation machine.
No response

@fanspace fanspace added the Bug Something isn't working label Jun 15, 2024
@leaanthony
Copy link
Member

The go version in your CLI screenshot is 1.20 but 1.22 in doctor....

@fanspace
Copy link
Author

The go version in your CLI screenshot is 1.20 but 1.22 in doctor....

Yes, initially, I had installed Go version 1.22 and encountered this issue. Suspecting that the problem might be due to the newer version of Go, I downgraded to version 1.20. However, I found that this action did not resolve the issue.

@fanspace
Copy link
Author

The go version in your CLI screenshot is 1.20 but 1.22 in doctor....

Due to various constraints, the client's computer is stuck with Ubuntu 16.04, unable to be upgraded or altered. Consequently, I've been attempting to package the application using Ubuntu 18.04 and then run it on 16.04, encountering issues along the way related to glibc version discrepancies and errors such as 'undefined symbol: gdk_display_get_monitor_at_window' with libgtk. I'm quite curious about the feasibility of running Wails version 2 on Ubuntu 16.04 and would greatly appreciate your guidance on how to proceed. Thank you very much.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants