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

build on asahi linux fails at poetry #26485

Closed
treeshateorcs opened this issue Jul 7, 2023 · 14 comments
Closed

build on asahi linux fails at poetry #26485

treeshateorcs opened this issue Jul 7, 2023 · 14 comments
Labels

Comments

@treeshateorcs
Copy link

Steps to reproduce

after i run

poetry run gen_dockerfile | DOCKER_BUILDKIT=1 docker build -t tdesktop:centos_env -

Expected behaviour

build fails

Actual behaviour

$ poetry run gen_dockerfile | DOCKER_BUILDKIT=1 docker build -t tdesktop:centos_env -

[+] Building 2.4s (4/4) FINISHED                                                      
 => [internal] load build definition from Dockerfile                             0.0s
 => => transferring dockerfile: 30.49kB                                          0.0s
 => [internal] load .dockerignore                                                0.0s
 => => transferring context: 2B                                                  0.0s
 => resolve image config for docker.io/docker/dockerfile:1                       1.6s
 => CACHED docker-image://docker.io/docker/dockerfile:1@sha256:39b85bbfa7536a5f  0.0s
failed to solve with frontend dockerfile.v0: failed to solve with frontend gateway.v0: exit code: 1

Operating system

fedora asahi remix (aarch64, arm64)

Version of Telegram Desktop

8bd9293

Installation source

Other (unofficial) source

Crash ID

No response

Logs

i've tried every possible solution from [this](https://stackoverflow.com/questions/64221861/an-error-failed-to-solve-with-frontend-dockerfile-v0) page to no avail
@ilya-fedin
Copy link
Contributor

I don't think it will work, the Dockerfile downloads amd64 executables and uses repos that provide only i386 and amd64 builds

@treeshateorcs
Copy link
Author

so no way to run telegram desktop on asahi fedora?

@ilya-fedin
Copy link
Contributor

You can use flatpak, snap, distro package?

@treeshateorcs
Copy link
Author

flatpak is not an option because of the 16k page size (the same may go to snap too), and it's no longer packaged in fedora.

i'll try archlinuxarm's PKGBUILD!

@ilya-fedin
Copy link
Contributor

ilya-fedin commented Jul 7, 2023

and it's no longer packaged in fedora

AFAIK it is

@dmatora
Copy link

dmatora commented Jul 13, 2023

@treeshateorcs I am having same issue with asahi ubuntu, have you solved this?

@treeshateorcs
Copy link
Author

@dmatora i don't know how to solve this for ubuntu, there must be a third party build, maybe some ppa

@treeshateorcs
Copy link
Author

as a last resort use the commands from this script https://gitlab.archlinux.org/archlinux/packaging/packages/telegram-desktop/-/blob/main/PKGBUILD

@ilya-fedin
Copy link
Contributor

ilya-fedin commented Jul 13, 2023

Ubuntu usually has too old libraries to build latest tdesktop as tdesktop is bleeding edge while both Debian and Ubuntu update packages very rarely, so it would require building half of the system libraries with up-to-date versions just like the Dockerfile with CentOS does and I guess no one really has time to maintain such a PPA.

@ilya-fedin
Copy link
Contributor

The only realistic way (IMO) for you folks is to get jemalloc developers to add support for your hardware out-of-the-box and make jemalloc create a new release so tdesktop can update the bundled version.

@treeshateorcs
Copy link
Author

or you can also try rebuilding jemalloc as i suggested here (but that's for arch, it may or may not work on ubuntu)

@ilya-fedin
Copy link
Contributor

You would need to build tdesktop then what seems to be unrealistic for you folks

@dmatora
Copy link

dmatora commented Jul 13, 2023

Well, I'm a Mac guy and this is little above my head

@ilya-fedin
Copy link
Contributor

Yeah, that's the general problem with having official ARM builds at all. No one from the community has stepped up to create cross-compilation scripts.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Aug 28, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

3 participants