From: voidlinux-github@inbox.vuxu.org
To: ml@inbox.vuxu.org
Subject: Re: [RFC] chromium: update to 80.0.3987.87.
Date: Sun, 09 Feb 2020 01:38:19 +0100 [thread overview]
Message-ID: <20200209003819.Zp_ObJa6v2s6HvUg5pNmsywyEC2giWPtIo_sfghCrbI@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-18955@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1515 bytes --]
New comment by pbui on void-packages repository
https://github.com/void-linux/void-packages/pull/18955#issuecomment-583791737
Comment:
The i686 build fails with the following error:
```
FAILED: chrome
clang++ -Wl,--version-script=../../build/linux/chrome.map -fPIC -Wl,-z,noexecstack -Wl,-z,relro -Wl,-z,now -Wl,-z,defs -Wl,--as-needed -fuse-ld=gold -B/usr/bin/ld.gold -m32 -Wl,-O2 -Wl,--gc-sections -rdynamic -pie -Wl,--disable-new-dtags -L/usr/lib -pthread -o "./chrome" -Wl,--start-group @"./chrome.rsp" -Wl,--end-group -latomic -ldl -lpthread -lrt -lX11 -lX11-xcb -lxcb -lXcomposite -lXcursor -lXdamage -lXext -lXfixes -lXi -lXrender -lXtst -lgmodule-2.0 -lglib-2.0 -lgobject-2.0 -lgthread-2.0 -lsmime3 -lnss3 -lnssutil3 -lplds4 -lplc4 -lnspr4 -lcups -lfontconfig -ldbus-1 -levent -lXss -lresolv -lgio-2.0 -lpng16 -lz -lwebpdemux -lwebpmux -lwebp -lharfbuzz-subset -lharfbuzz -ljpeg -lexpat -ldrm -lXrandr -lm -lopus -lavcodec -lavformat -lavutil -lre2 -lpci -lasound -lpulse -lsnappy -latk-1.0 -latk-bridge-2.0 -lpangocairo-1.0 -lpango-1.0 -lcairo -lxml2 -latspi -lFLAC -lgtk-3 -lgdk-3 -lcairo-gobject -lgdk_pixbuf-2.0 -lxslt
terminate called after throwing an instance of 'std::bad_alloc'
what(): std::bad_alloc
clang-9: error: unable to execute command: Aborted
clang-9: error: linker command failed due to signal (use -v to see invocation)
ninja: build stopped: subcommand failed.
```
I'm not sure how to resolve this... Perhaps we should consider dropping i686 support for chromium.
next parent reply other threads:[~2020-02-09 0:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-18955@inbox.vuxu.org>
2020-02-09 0:38 ` voidlinux-github [this message]
2020-02-10 14:18 ` voidlinux-github
2020-02-14 11:56 ` voidlinux-github
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200209003819.Zp_ObJa6v2s6HvUg5pNmsywyEC2giWPtIo_sfghCrbI@z \
--to=voidlinux-github@inbox.vuxu.org \
--cc=ml@inbox.vuxu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).