Search Criteria
Package Details: phrase-cli 2.34.1-1
Package Actions
Git Clone URL: | https://aur.archlinux.org/phrase-cli.git (read-only, click to copy) |
---|---|
Package Base: | phrase-cli |
Description: | Phrase CLI tool |
Upstream URL: | https://phrase.com/cli |
Licenses: | MIT |
Submitter: | lautat |
Maintainer: | lautat |
Last Packager: | lautat |
Votes: | 4 |
Popularity: | 0.000536 |
First Submitted: | 2021-08-24 13:03 (UTC) |
Last Updated: | 2024-11-27 17:04 (UTC) |
Dependencies (1)
- go (go-gitAUR, gcc-go-gitAUR, gcc-go-snapshotAUR, go-sylixosAUR, gcc-go) (make)
Latest Comments
1 2 Next › Last »
lautat commented on 2024-02-12 18:50 (UTC)
The build should now work with
lto
option enabled. It is now usingcgo
, and that seemed to be the way that some go apps were built in official repositories. Thanks for reporting the issue!lautat commented on 2024-02-12 18:28 (UTC)
When the
OPTIONS
array containslto
, makepkg will appendLTOFLAGS
toLDFLAGS
. In addition to/etc/makepkg.conf
, the array could be declared in your home folder, either~/.makepkg.conf
or~/.config/pacman/makepkg.conf
.Adding quotes around
LDFLAGS
seems to fix the build, but I guess that could break ifLDFLAGS
may contain quotes. I'll try to check what options could be used to pass flags to the linker.gouvinb commented on 2024-02-12 16:00 (UTC)
I usually use
aur/yay 12.2.0-1
, but I get the same error withaur/paru 2.0.1-1
.I see that my
/etc/makepkg.conf
file contains a line withLTOFLAGS="-flto=auto"
, I have no idea where this could be coming from.I'll investigate on my side too.
lautat commented on 2024-02-12 15:19 (UTC)
Thanks! I found the reason why the issue happens. I guess you have enabled
lto
option in makepkg configuration (or maybe the package manager you seem to be using has enabled it). Withlto
enabled, I get the same error. If you disable it temporarily (add an "!" before the option), you should be able to build the package.man 5 makepkg.conf
has more information on the configuration.I think this PKGBUILD should work with
lto
enabled, so I'll try to check how the issue could be fixed. Maybe the variable just needs quotes or something similar.gouvinb commented on 2024-02-12 14:40 (UTC) (edited on 2024-02-12 14:40 (UTC) by gouvinb)
Hi!
I cloned the repository to display the
_LDFLAGS
variable at build time, here's what I got:_LDFLAGS=-X github.com/phrase/phrase-cli/cmd.PHRASE_CLIENT_VERSION=2.22.0 -extldflags -Wl,-O1,--sort-common,--as-needed,-z,relro,-z,now -flto=auto
Checking my environment, I don't have any
LDFLAGS
variable set and I useextra/go 2:1.22.0-1
.lautat commented on 2024-02-12 11:43 (UTC)
Hello @gouvinb!
Thanks for reporting the issue. However, I'm struggling to reproduce it. I just tried rebuilding the package and it works for me. In case it matters, I'm using
go-2:1.22.0-1
from the official extra repo. Based on the log, I suspect that the error could be related toLDFLAGS
environment variable. I tried some values for the variable, but none of them resulted in build errors.Could you share more details of your makepkg configuration, at least the
LDFLAGS
variable? That could help me to reproduce an fix the issue. You could also try to temporarily modify your config to remove the key or set it back to the default value, and see if that fixes the build.gouvinb commented on 2024-02-12 10:01 (UTC) (edited on 2024-02-12 10:04 (UTC) by gouvinb)
I cannot build the
2.22.0-1
version.Log...
lautat commented on 2021-08-24 13:11 (UTC)
The upstream project has been renamed so I created a new package and the latest version is available here: https://aur.archlinux.org/packages/phrase-cli/. I will now request this package to be merged to the new one.
saveman71 commented on 2018-08-23 16:08 (UTC)
Thanks a bunch for the ultra-fast update!
lautat commented on 2018-08-23 10:47 (UTC)
Latest version, 1.9.1, still warns about outdated version when invoked: "Please consider updating the PhraseApp CLI client (1.9.0 < 1.9.1)". This seems to be a bug in 1.9.1. There is no need to worry about it.
1 2 Next › Last »