Package Details: lagrange 1.17.6-1

Git Clone URL: https://aur.archlinux.org/lagrange.git (read-only, click to copy)
Package Base: lagrange
Description: Beautiful Gemini Client
Upstream URL: https://git.skyjake.fi/skyjake/lagrange
Licenses: BSD
Submitter: Roshless
Maintainer: Roshless
Last Packager: Roshless
Votes: 37
Popularity: 0.094921
First Submitted: 2020-10-10 19:45 (UTC)
Last Updated: 2024-01-16 13:31 (UTC)

Pinned Comments

Roshless commented on 2020-11-04 08:20 (UTC) (edited on 2022-08-23 13:45 (UTC) by Roshless)

Instead of flagging this package out of date please send patches to repo using mailing list linked in index.md.

Tutorial: https://git-send-email.io/

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 7 Next › Last »

dmerejkowsky commented on 2021-05-13 16:01 (UTC)

Patch for 1.4.1-1 has been sent and compiles fine here :)

dmerejkowsky commented on 2021-05-09 19:14 (UTC) (edited on 2021-05-09 19:14 (UTC) by dmerejkowsky)

aaronfischer: we're on the right track - the bug should be fixed in the text Lagrange release after 1.4.0.

Note that the workaround described below should still work :)

aaronfischer commented on 2021-05-09 19:06 (UTC)

Can you please apply this fix to the package? https://github.com/skyjake/lagrange/issues/270

dmerejkowsky commented on 2021-05-08 11:33 (UTC)

The error persists with a clean build of 1.4.0-1

Indeed, we went from

"cc1: all warnings being treated as errors"

to

"cc1: some warnings being treated as errors"

To be continued ...

autumnontape commented on 2021-05-08 05:12 (UTC)

The error persists with a clean build of 1.4.0-1 with the default CFLAGS. It seems gcc treats this as an error even without -Werror.

dmerejkowsky commented on 2021-05-04 11:10 (UTC) (edited on 2021-05-04 11:14 (UTC) by dmerejkowsky)

That's expected. The PKGBUILD has been fixed to add the appropriate flags, but the upstream source code does not use it yet. You should wait for version 1.3.5 or something - or use the workaround described below.

autumnontape commented on 2021-05-04 06:49 (UTC)

I still get the same error when building 1.3.4-3 with the default CFLAGS in /etc/makepkg.conf. It shouldn't make a difference in this case, but it was a clean build.

dmerejkowsky commented on 2021-05-03 14:43 (UTC)

Good news: the_Foundation can now be built without -Werror.

I've send a patch to set TFDN_ENABLE_WERROR=OFF so the issue should be fixed in the next lagrange release

xanc commented on 2021-05-02 11:43 (UTC)

I get this error:

[code] [ 1%] Building C object lib/the_Foundation/CMakeFiles/the_Foundation.dir/src/the_foundation.c.o cc1: error: ‘-Wformat-security’ ignored without ‘-Wformat’ [-Werror=format-security] cc1: all warnings being treated as errors make[2]: [lib/the_Foundation/CMakeFiles/the_Foundation.dir/build.make:76: lib/the_Foundation/CMakeFiles/the_Foundation.dir/src/the_foundation.c.o] Error 1 make[2]: Leaving directory '/home/xan/aur/gemini-lagrange/lagrange/src/build' make[1]: [CMakeFiles/Makefile2:126: lib/the_Foundation/CMakeFiles/the_Foundation.dir/all] Error 2 make[1]: Leaving directory '/home/xan/aur/gemini-lagrange/lagrange/src/build' make: *** [Makefile:136: all] Error 2 make: Leaving directory '/home/xan/aur/gemini-lagrange/lagrange/src/build' ==> ERROR: Ha ocorregut una fallada a build(). Es cancel·la...

[/code]

dmerejkowsky commented on 2021-04-29 14:02 (UTC) (edited on 2021-04-29 14:06 (UTC) by dmerejkowsky)

Good news! The bug in the_Foundation is being fixed upstream.

https://codeberg.org/skyjake/the_Foundation/issues/6

I'll update the pkgbuild when the fix is available, and I'll take care of the CMAKE_BUILD_TYPE issue then.

As a workaround, you can build the package this way:

rm -fr src/build/

makepkg \
  CFLAGS="-march=x86-64 -mtune=generic -O2 -pipe -fno-plt -fexceptions \
  -Wp,-D_FORTIFY_SOURCE=2,-D_GLIBCXX_ASSERTIONS \
   -fstack-clash-protection -fcf-protection" \
   -f

« First ‹ Previous 1 2 3 4 5 6 7 Next › Last »