Package Details: translatelocally-git r002.e81917c-1

Git Clone URL: https://aur.archlinux.org/translatelocally-git.git (read-only, click to copy)
Package Base: translatelocally-git
Description: A fast privacy focused machine translation client that translates on your own machine.
Upstream URL: https://github.com/XapaJIaMnu/translateLocally
Licenses: MIT
Submitter: Dheart
Maintainer: Dheart
Last Packager: Dheart
Votes: 0
Popularity: 0.000000
First Submitted: 2021-05-03 15:36 (UTC)
Last Updated: 2022-08-15 14:04 (UTC)

Latest Comments

1 2 Next › Last »

yochananmarqos commented on 2023-12-09 20:04 (UTC) (edited on 2023-12-09 20:05 (UTC) by yochananmarqos)

@nmset: Use my PKGBUILD I linked below for now.

nmset commented on 2023-12-09 20:00 (UTC)

A quick note.

Build fails with clang version 16.0.6

and succeeds with gcc (GCC) 13.2.1 20230801.

With clang, build error occurs on line 221 of 3rd_party/bergamot-translator/3rd_party/marian-dev/src/3rd_party/sentencepiece/src/trainer_interface.cc

with message Integer value -1 is outside the valid range of values [0, 255] for this enumeration type.

yochananmarqos commented on 2023-12-07 15:07 (UTC)

@Dheart: I see. Using Release it reduced the package size by 1.61 MiB which I wasn't expecting.

My i7-12700H apparently doesn't support AVX512--at least support wasn't detected during build.

Dheart commented on 2023-12-07 02:06 (UTC)

This is a neural network inference toolkit. Everything will work fine even with O0, but it will be slow.

In particular O3 does more loop aggressive loop unrolls and vectorisations which are most apparent on AVX512 systems. If this was to make it to a repository, i totally agree with O2, but since it's self built and caters to the user's specific hardware, I would prefer to keep O3. These are our current build flags that we use everywhere:

https://github.com/browsermt/marian-dev/blob/master/CMakeLists.txt#L361

yochananmarqos commented on 2023-12-07 01:54 (UTC)

@Dheart: Why do you need O3? Everything seems to be fine without it.

Dheart commented on 2023-12-07 01:50 (UTC)

I don't have access to my main desktop for a few weeks, I'll update the package in late December. Thanks again for your explanations!

Dheart commented on 2023-12-07 01:48 (UTC)

Thank you. I will keep the release build as we definitely need O3 (I'm one of the main developers of the upstream project and some of its dependencies)

yochananmarqos commented on 2023-12-07 01:44 (UTC)

@Dheart: See Cmake package guidelines

Dheart commented on 2023-12-07 01:42 (UTC)

@yochananmarqos any reason CMAKE_BUILD_TYPE is set to None? We set release so we can set the proper optimisation flags. Does this interfere with the CFLAGS and CXXFLAGS set in makepkg.conf. I've seen other PKGBUILDs do unset CFLAGS && unset CXXFLAGS. Would that be a preferred approach?

yochananmarqos commented on 2023-12-07 01:33 (UTC)

@Dheart: The goal is to not have anything downloaded during build. Sources should be in the source() array and anything else like submodules should be done in the prepare() function.

Since there are a lot of submodules and it would be more work to keep track of them all, I've updated my PKGBUILD to just fetch them recursively.

1 2 Next › Last »