Re: [RFC] chromium: update to 80.0.3987.87.

Re: [RFC] chromium: update to 80.0.3987.87.

[voidlinux-github]

[-- Attachment #1: Type: text/plain, Size: 236 bytes --]

New comment by mar1n3r0 on void-packages repository

https://github.com/void-linux/void-packages/pull/18955#issuecomment-584144003

Comment:
It makes sense. The i686 architecture was officially declared EOL in the end of 2017 for Arch.

Re: [RFC] chromium: update to 80.0.3987.87.

[voidlinux-github]

[-- Attachment #1: Type: text/plain, Size: 294 bytes --]

New comment by Hoshpak on void-packages repository

https://github.com/void-linux/void-packages/pull/18955#issuecomment-586258095

Comment:
I agree. We probably won't remove the architecture anytime soon however that doesn't mean that we have to have every packages built for it at all costs. 

Re: [PR PATCH] [Merged]: [RFC] chromium: update to 80.0.3987.116.

[Hoshpak]

[-- Attachment #1: Type: text/plain, Size: 411 bytes --]

There's a merged pull request on the void-packages repository

[RFC] chromium: update to 80.0.3987.116.
https://github.com/void-linux/void-packages/pull/18955

Description:
[ci skip]

- Builds for x86_64, x86_64-musl

- Fails for i686 (std::bad_alloc), mark as broken

- Remove jumbo_build option as upstream has deprecated it:

    https://chromium.googlesource.com/chromium/src/+/master/docs/jumbo.md

Re: [RFC] chromium: update to 80.0.3987.87.

[voidlinux-github]

[-- 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.