GNU bug report logs -
#53857
telegram-desktop: fails to build
Previous Next
To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 53857 in the body.
You can then email your comments to 53857 AT debbugs.gnu.org in the normal way.
Toggle the display of automated, internal messages from the tracker.
Report forwarded
to
bug-guix <at> gnu.org
:
bug#53857
; Package
guix
.
(Mon, 07 Feb 2022 18:33:01 GMT)
Full text and
rfc822 format available.
Acknowledgement sent
to
Christopher Howard <christopher <at> librehacker.com>
:
New bug report received and forwarded. Copy sent to
bug-guix <at> gnu.org
.
(Mon, 07 Feb 2022 18:33:01 GMT)
Full text and
rfc822 format available.
Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):
[Message part 1 (text/plain, inline)]
telegram-desktop-2.9.3 fails to build:
```
building /gnu/store/h9f9gm6n3jkxw6mwh050xkmabviim496-telegram-desktop-2.9.3.drv...
33% [################################################# ]builder for `/gnu/store/h9f9gm6n3jkxw6mwh050xkmabviim496-telegram-desktop-2.9.3.drv' failed with exit code 1
build of /gnu/store/h9f9gm6n3jkxw6mwh050xkmabviim496-telegram-desktop-2.9.3.drv failed
View build log at '/var/log/guix/drvs/h9/f9gm6n3jkxw6mwh050xkmabviim496-telegram-desktop-2.9.3.drv.bz2'.
guix package: error: build of `/gnu/store/h9f9gm6n3jkxw6mwh050xkmabviim496-telegram-desktop-2.9.3.drv' failed
```
The first error I see in the build log is pasted below.
```
[ 26%] Building CXX object Telegram/lib_ui/CMakeFiles/lib_ui.dir/ui/gl/gl_window.cpp.o
cd /tmp/guix-build-telegram-desktop-2.9.3.drv-0/build/Telegram/lib_ui && /gnu/store/069aq2v993kpc41yabp5b6vm4wb9jkhg-gcc-10.3.0/bin/c++ -DDESKTOP_APP_DISABLE_CRASH_REPORTS -DDESKTOP_APP_DISABLE_WEBKITGTK -DDESKTOP_APP_USE_PACKAGED -DQT_CORE_LIB -DQT_DBUS_LIB -DQT_GUI_LIB -DQT_NETWORK_LIB -DQT_NO_CAST_FROM_BYTEARRAY -DQT_NO_DEBUG -DQT_NO_KEYWORDS -DQT_WAYLANDCLIENT_LIB -DQT_WIDGETS_LIB -DQT_XKBCOMMON_SUPPORT_LIB -I/tmp/guix-build-telegram-desktop-2.9.3.drv-0/build/Telegram/lib_ui/lib_ui_autogen/include -I/tmp/guix-build-telegram-desktop-2.9.3.drv-0/build/Telegram/lib_ui/gen -I/tmp/guix-build-telegram-desktop-2.9.3.drv-0/source/Telegram/lib_ui -I/tmp/guix-build-telegram-desktop-2.9.3.drv-0/source/Telegram/lib_ui/emoji_suggestions -I/tmp/guix-build-telegram-desktop-2.9.3.drv-0/source/Telegram/lib_waylandshells -I/tmp/guix-build-telegram-desktop-2.9.3.drv-0/source/Telegram/lib_base -I/tmp/guix-build-telegram-desktop-2.9.3.drv-0/source/Telegram/lib_rpl -I/tmp/guix-build-telegram-desktop-2.9.3.drv-0/source/Telegram/lib_crl -isystem /gnu/store/v8yw01fvwdm95jvqa82sylw6qznmh2mi-qtbase-5.15.2/include/qt5/QtCore/5.15.2 -isystem /gnu/store/v8yw01fvwdm95jvqa82sylw6qznmh2mi-qtbase-5.15.2/include/qt5/QtCore/5.15.2/QtCore -isystem /gnu/store/v8yw01fvwdm95jvqa82sylw6qznmh2mi-qtbase-5.15.2/include/qt5/QtGui/5.15.2 -isystem /gnu/store/v8yw01fvwdm95jvqa82sylw6qznmh2mi-qtbase-5.15.2/include/qt5/QtGui/5.15.2/QtGui -isystem /gnu/store/v8yw01fvwdm95jvqa82sylw6qznmh2mi-qtbase-5.15.2/include/qt5/QtXkbCommonSupport/5.15.2 -isystem /gnu/store/v8yw01fvwdm95jvqa82sylw6qznmh2mi-qtbase-5.15.2/include/qt5/QtXkbCommonSupport/5.15.2/QtXkbCommonSupport -isystem /gnu/store/pkr31373nm8hfg65ms46nb2plwwr3k5y-qtwayland-5.15.2/include/qt5/QtWaylandClient/5.15.2 -isystem /gnu/store/pkr31373nm8hfg65ms46nb2plwwr3k5y-qtwayland-5.15.2/include/qt5/QtWaylandClient/5.15.2/QtWaylandClient -isystem /gnu/store/v8yw01fvwdm95jvqa82sylw6qznmh2mi-qtbase-5.15.2/include/qt5 -isystem /gnu/store/v8yw01fvwdm95jvqa82sylw6qznmh2mi-qtbase-5.15.2/include/qt5/QtCore -isystem /gnu/store/v8yw01fvwdm95jvqa82sylw6qznmh2mi-qtbase-5.15.2/lib/qt5/mkspecs/linux-g++ -isystem /gnu/store/v8yw01fvwdm95jvqa82sylw6qznmh2mi-qtbase-5.15.2/include/qt5/QtGui -isystem /gnu/store/v8yw01fvwdm95jvqa82sylw6qznmh2mi-qtbase-5.15.2/include/qt5/QtWidgets -isystem /gnu/store/v8yw01fvwdm95jvqa82sylw6qznmh2mi-qtbase-5.15.2/include/qt5/QtNetwork -isystem /gnu/store/v8yw01fvwdm95jvqa82sylw6qznmh2mi-qtbase-5.15.2/include/qt5/QtDBus -isystem /gnu/store/v8yw01fvwdm95jvqa82sylw6qznmh2mi-qtbase-5.15.2/include/qt5/QtXkbCommonSupport -isystem /gnu/store/pkr31373nm8hfg65ms46nb2plwwr3k5y-qtwayland-5.15.2/include/qt5 -isystem /gnu/store/pkr31373nm8hfg65ms46nb2plwwr3k5y-qtwayland-5.15.2/include/qt5/QtWaylandClient -isystem /gnu/store/2fn1hdvpd7ixkya41z4jvcjp169y3460-kwayland-5.70.0/include/KF5/KWayland/Client -isystem /gnu/store/2fn1hdvpd7ixkya41z4jvcjp169y3460-kwayland-5.70.0/include/KF5 -isystem /gnu/store/84bvs9y0arsimxd2ay26a57xkqw7nsqm-glib-2.70.2/include/gio-unix-2.0 -isystem /gnu/store/84bvs9y0arsimxd2ay26a57xkqw7nsqm-glib-2.70.2/include/glib-2.0 -isystem /gnu/store/84bvs9y0arsimxd2ay26a57xkqw7nsqm-glib-2.70.2/lib/glib-2.0/include -isystem /gnu/store/a76pcinhq6v3v1cc6sq68p2y5z9wfpl6-gtk+-3.24.30/include/gtk-3.0 -isystem /gnu/store/5583c2za2jsn9g6az79rnksgvigwnsk7-util-linux-2.37.2-lib/include/libmount -isystem /gnu/store/5583c2za2jsn9g6az79rnksgvigwnsk7-util-linux-2.37.2-lib/include/blkid -isystem /gnu/store/62vbcpssly0ks874zhhx5saq0zdbbwq2-pango-1.48.10/include/pango-1.0 -isystem /gnu/store/xphvz607v2ridl2m51yyq1788izpvc5l-libcloudproviders-minimal-0.3.1/include/cloudproviders -isystem /gnu/store/ak70pk2hjks17cx7zjdmdmzpcpiy9gpi-freetype-2.10.4/include/freetype2 -isystem /gnu/store/v5x6f3dml69pmn4pfkl51j6y03v6rlsg-fribidi-1.0.9/include/fribidi -isystem /gnu/store/a91v7dy7xn25z9ks5bar66yjari9ddc1-cairo-1.16.0/include/cairo -isystem /gnu/store/nasw4ijnavd2sm5dnpr6185cwf6pc71g-at-spi2-atk-2.38.0/include/at-spi2-atk/2.0 -isystem /gnu/store/8d6hggn9j6xfbnba8643wphh6800pn2l-atk-2.36.0/include/atk-1.0 -isystem /gnu/store/zkl2vfmlifcyxphidx5nbv177qs9ziaz-harfbuzz-2.8.2/include/harfbuzz -isystem /gnu/store/ikghb2zrjjl5944gxqkls89rrbd1qn24-libdrm-2.4.107/include/libdrm -isystem /gnu/store/46ydzcrnv2b9l4fiyxz1qz6paviwgm1f-gdk-pixbuf-2.42.4/include/gdk-pixbuf-2.0 -isystem /gnu/store/p7iq81hxxyk9zy7a9dngbf16zm8d4klx-libpng-1.6.37/include/libpng16 -isystem /gnu/store/j8x167zaka2h6pxk7wiq5zkg67hzf8a2-pixman-0.40.0/include/pixman-1 -isystem /gnu/store/bbf7fkizk6kwgfi6c7p0likhnpg344yk-at-spi2-core-2.40.0/include/at-spi-2.0 -isystem /gnu/store/39rwjffd2gw7lq35mxxa8lxwfmqsbmjh-dbus-1.12.20/include/dbus-1.0 -isystem /gnu/store/39rwjffd2gw7lq35mxxa8lxwfmqsbmjh-dbus-1.12.20/lib/dbus-1.0/include -isystem /gnu/store/6fw36kigrd2cfbh3waf0mlyaji54q0s0-glibmm-2.64.5/include/giomm-2.4 -isystem /gnu/store/6fw36kigrd2cfbh3waf0mlyaji54q0s0-glibmm-2.64.5/lib/giomm-2.4/include -isystem /gnu/store/6fw36kigrd2cfbh3waf0mlyaji54q0s0-glibmm-2.64.5/include/glibmm-2.4 -isystem /gnu/store/6fw36kigrd2cfbh3waf0mlyaji54q0s0-glibmm-2.64.5/lib/glibmm-2.4/include -isystem /gnu/store/iad8jg1fm7jsq0pqj547f3n5s2jn9rp0-libsigc++-2.9.3/include/sigc++-2.0 -isystem /gnu/store/iad8jg1fm7jsq0pqj547f3n5s2jn9rp0-libsigc++-2.9.3/lib/sigc++-2.0/include -O2 -g -DNDEBUG -fPIC -fno-strict-aliasing -pipe -Wall -W -Wno-unused-parameter -Wno-switch -Wno-missing-field-initializers -Wno-sign-compare -Wno-maybe-uninitialized -pthread -std=gnu++17 -Winvalid-pch -include /tmp/guix-build-telegram-desktop-2.9.3.drv-0/build/Telegram/lib_ui/CMakeFiles/lib_ui.dir/cmake_pch.hxx -MD -MT Telegram/lib_ui/CMakeFiles/lib_ui.dir/ui/gl/gl_window.cpp.o -MF CMakeFiles/lib_ui.dir/ui/gl/gl_window.cpp.o.d -o CMakeFiles/lib_ui.dir/ui/gl/gl_window.cpp.o -c /tmp/guix-build-telegram-desktop-2.9.3.drv-0/source/Telegram/lib_ui/ui/gl/gl_window.cpp
{standard input}: Assembler messages:
{standard input}:1918775: Warning: end of file not at end of a line; newline inserted
{standard input}: Error: open CFI at the end of file; missing .cfi_endproc directive
c++: fatal error: Killed signal terminated program cc1plus
compilation terminated.
make[2]: *** [Telegram/CMakeFiles/td_scheme.dir/build.make:79: Telegram/CMakeFiles/td_scheme.dir/gen/scheme.cpp.o] Error 1
make[2]: Leaving directory '/tmp/guix-build-telegram-desktop-2.9.3.drv-0/build'
make[1]: *** [CMakeFiles/Makefile2:1618: Telegram/CMakeFiles/td_scheme.dir/all] Error 2
make[1]: *** Waiting for unfinished jobs....
```
I will attached the build log. Here is my system information:
```
christopher <at> theoden ~$ guix describe
Generation 31 Feb 04 2022 09:30:14 (current)
guix 8391a99
repository URL: https://git.savannah.gnu.org/git/guix.git
branch: master
commit: 8391a99d089322a39cbacb1e6dc2979d8b2ef7c9
christopher <at> theoden ~$ neofetch --stdout
christopher <at> theoden
-------------------
OS: Guix System x86_64
Host: OptiPlex 9020 00
Kernel: 5.15.12-gnu
Uptime: 34 days, 18 hours, 48 mins
Packages: 92 (guix-system), 149 (guix-user)
Shell: bash 5.1.8
Resolution: 1920x1080
DE: GNOME
Theme: Adwaita [GTK2/3]
Icons: Adwaita [GTK2/3]
Terminal: .gnome-terminal
CPU: Intel i5-4570 (4) @ 3.600GHz
GPU: Intel HD Graphics
GPU: AMD ATI Radeon HD 8490 / R5 235X OEM
Memory: 3470MiB / 7869MiB
```
--
馃摏 Christopher Howard
馃殌 gemini://gem.librehacker.com
馃寪 https://portal.mozz.us/gemini/gem.librehacker.com
讘专讗砖讬转 讘专讗 讗诇讛讬诐 讗转 讛砖诪讬诐 讜讗转 讛讗专抓
[f9gm6n3jkxw6mwh050xkmabviim496-telegram-desktop-2.9.3.drv.bz2 (application/octet-stream, attachment)]
Information forwarded
to
bug-guix <at> gnu.org
:
bug#53857
; Package
guix
.
(Tue, 08 Feb 2022 07:16:02 GMT)
Full text and
rfc822 format available.
Message #8 received at 53857 <at> debbugs.gnu.org (full text, mbox):
Hi Christopher,
Am Montag, dem 07.02.2022 um 09:32 -0900 schrieb Christopher Howard:
> {standard input}:1918775: Warning: end of file not at end of a line;
> newline inserted
> {standard input}: Error: open CFI at the end of file; missing
> .cfi_endproc directive
> c++: fatal error: Killed signal terminated program cc1plus
> compilation terminated.
> make[2]: *** [Telegram/CMakeFiles/td_scheme.dir/build.make:79:
> Telegram/CMakeFiles/td_scheme.dir/gen/scheme.cpp.o] Error 1
> make[2]: Leaving directory '/tmp/guix-build-telegram-desktop-2.9.3.drv-
> 0/build'
> make[1]: *** [CMakeFiles/Makefile2:1618:
> Telegram/CMakeFiles/td_scheme.dir/all] Error 2
> make[1]: *** Waiting for unfinished jobs....
> ```
According to [1], this happens when GCC runs out of memory. You could
try decreasing parallelism to see how that goes, but I'd hazard a guess
that telegram-desktop is too large for measly 12 gigs of RAM+swap.
> I will attached the build log. Here is my system information:
>
> ```
> christopher <at> theoden ~$ guix describe
> Generation 31聽聽聽Feb 04 2022 09:30:14聽聽聽聽(current)
> 聽 guix 8391a99
> 聽聽聽 repository URL: https://git.savannah.gnu.org/git/guix.git
> 聽聽聽 branch: master
> 聽聽聽 commit: 8391a99d089322a39cbacb1e6dc2979d8b2ef7c9
Note that the last build of telegram-desktop succeeded in the
evaluation of commit 11590bff50fe0244e66c11d995aa5301c8965959 [2],
which admittedly is newer than February 4th, but the recipe hasn't
changed in between as far as I'm aware. I therefore don't think that
the package itself is broken.
Cheers
[1] https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67571
[2] https://ci.guix.gnu.org/build/467392/log/raw
Information forwarded
to
bug-guix <at> gnu.org
:
bug#53857
; Package
guix
.
(Wed, 09 Feb 2022 20:19:02 GMT)
Full text and
rfc822 format available.
Message #11 received at 53857 <at> debbugs.gnu.org (full text, mbox):
Hi, when I try to build with `guix build -M 1 -c 1 telegram-desktop` I seem to be getting the same error. I can believe what you say about the ram, as I've run into that problem before with other packages, though it seems frustrating I can't use some kind of command line option or something to tell the linker/compiler/assembler to use less ram. Seems strange that any package should need more than a GB or two of ram to build (*end rant*).
One thing though: using the above command-line options, I see that the last message in the build log is:
```
error: in phase 'build': uncaught exception:
%exception #<&invoke-error program: "make" arguments: ("-j" "4") exit-status: 2 term-signal: #f stop-signal: #f>
phase `build' failed after 254.0 seconds
command "make" "-j" "4" failed with status 2
```
Isn't using -M 1 in the guix build options supposed to translate to "make -j 1", or do I misunderstand?
Christopher Howard
Information forwarded
to
bug-guix <at> gnu.org
:
bug#53857
; Package
guix
.
(Thu, 10 Feb 2022 07:03:01 GMT)
Full text and
rfc822 format available.
Message #14 received at 53857 <at> debbugs.gnu.org (full text, mbox):
Am Mittwoch, dem 09.02.2022 um 11:18 -0900 schrieb Christopher Howard:
> Hi, when I try to build with `guix build -M 1 -c 1 telegram-desktop`
> I seem to be getting the same error. I can believe what you say about
> the ram, as I've run into that problem before with other packages,
> though it seems frustrating I can't use some kind of command line
> option or something to tell the linker/compiler/assembler to use less
> ram. Seems strange that any package should need more than a GB or two
> of ram to build (*end rant*).
>
> One thing though: using the above command-line options, I see that
> the last message in the build log is:
>
> ```
> error: in phase 'build': uncaught exception:
> %exception #<&invoke-error program: "make" arguments: ("-j" "4")
> exit-status: 2 term-signal: #f stop-signal: #f>
> phase `build' failed after 254.0 seconds
> command "make" "-j" "4" failed with status 2
> ```
>
> Isn't using -M 1 in the guix build options supposed to translate to
> "make -j 1", or do I misunderstand?
-M 1 tells *guix* how many jobs it should use in parallel. What you're
aiming fore is probably -c 1.
Information forwarded
to
bug-guix <at> gnu.org
:
bug#53857
; Package
guix
.
(Thu, 10 Feb 2022 07:07:01 GMT)
Full text and
rfc822 format available.
Message #17 received at 53857 <at> debbugs.gnu.org (full text, mbox):
As mentioned, I used -c 1 as well. Is something wrong in the package that Make still tries to use -j 4?
Information forwarded
to
bug-guix <at> gnu.org
:
bug#53857
; Package
guix
.
(Wed, 06 Jul 2022 07:24:02 GMT)
Full text and
rfc822 format available.
Message #20 received at 53857 <at> debbugs.gnu.org (full text, mbox):
I got the same error, solved by using a swap partition.
Information forwarded
to
bug-guix <at> gnu.org
:
bug#53857
; Package
guix
.
(Wed, 06 Jul 2022 07:56:02 GMT)
Full text and
rfc822 format available.
Message #23 received at 53857 <at> debbugs.gnu.org (full text, mbox):
If you got a 4G ram like mine, try allocating a swap around 10-15GB, though in proper settings of the compiling task, it is unlikely to hit the 10 GB ceiling. (And it may vary depending on different machines)
Information forwarded
to
bug-guix <at> gnu.org
:
bug#53857
; Package
guix
.
(Sun, 23 Oct 2022 11:42:01 GMT)
Full text and
rfc822 format available.
Message #26 received at 53857 <at> debbugs.gnu.org (full text, mbox):
Am Montag, dem 07.02.2022 um 09:32 -0900 schrieb Christopher Howard:
> telegram-desktop-2.9.3 fails to build:
Telegram was "recently" updated and is now getting proper substitutes
as far as I'm aware.
Does the problem persist?
Reply sent
to
Liliana Marie Prikler <liliana.prikler <at> gmail.com>
:
You have taken responsibility.
(Mon, 24 Oct 2022 18:31:02 GMT)
Full text and
rfc822 format available.
Notification sent
to
Christopher Howard <christopher <at> librehacker.com>
:
bug acknowledged by developer.
(Mon, 24 Oct 2022 18:31:02 GMT)
Full text and
rfc822 format available.
Message #31 received at 53857-done <at> debbugs.gnu.org (full text, mbox):
Am Montag, dem 24.10.2022 um 09:13 -0800 schrieb Christopher Howard:
> I am able to install it normally using the most recent Guix commit.
>
> On Sun, Oct 23, 2022 at 01:41:41PM +0200, Liliana Marie Prikler
> wrote:
> > Telegram was "recently" updated and is now getting proper
> > substitutes as far as I'm aware.
> >
> > Does the problem persist?
Good to know. Closing
bug archived.
Request was from
Debbugs Internal Request <help-debbugs <at> gnu.org>
to
internal_control <at> debbugs.gnu.org
.
(Tue, 22 Nov 2022 12:24:04 GMT)
Full text and
rfc822 format available.
This bug report was last modified 1 year and 148 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.