• Status Assigned
  • Percent Complete
    0%
  • Task Type Feature Request
  • Category Packages
  • Assigned To No-one
  • Operating System pentium4
  • Severity Low
  • Priority Very Low
  • Reported Version
  • Due in Version Undecided
  • Due Date Undecided
  • Votes
  • Private
Attached to Project: Arch Linux 32
Opened by Average Linux Fan - 10.09.2022
Last edited by Andreas Baumann - 30.10.2022
Admin
Andreas Baumann commented on 15.09.2022 04:56

Just copying patches from other distros will not be enough.
I'm checking patches from VoidLinux, Slackware, T2SDE, etc. regularly for 32-bit
things.
Last time chromium compiled but didn't run because of seccomp sandboxing (which
is still pending for 32-bit - at least last time I checked it was).

Average Linux Fan commented on 19.09.2022 13:23

i think that seccomp sandboxing is because of sse3 dependency on chromium 87…

Average Linux Fan commented on 22.09.2022 14:39

```
=⇒ Starting build()… make: Entering directory '/build/chromium/src/chromium-launcher-8'
cc -o chromium -DLAUNCHER_VERSION=\"v8\" -DCHROMIUM_NAME=\"chromium\" -DCHROMIUM_BINARY=\"/usr/lib/chromium/chromium\" -DCHROMIUM_VENDOR="\"Arch Linux 32\"" -march=pentium4 -mtune=generic -O2 -pipe -fno-plt -fexceptions -Wp,-D_FORTIFY_SOURCE=2 -Wformat -Werror=format-security -fstack-clash-protection -g -ffile-prefix-map=/build/chromium/src=/usr/src/debug -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/sysprof-4 -pthread -Wl,-O1,–sort-common,–as-needed,-z,relro,-z,now launcher.c -lglib-2.0
make: Leaving directory '/build/chromium/src/chromium-launcher-8'
ERROR at BUILD.gn:1625:1: Assertion failed.
assert(
^—– 'target_cpu=x86' is not supported for 'target_os=linux'. Consider omitting 'target_cpu' (default) or using 'target_cpu=x64' instead.
See
BUILD.gn:1626:5:

  is_valid_x86_target || target_cpu != "x86" || v8_target_cpu == "arm",
  ^-------------------------------------------------------------------

This is where it was set.
```

https://github.com/void-linux/void-packages/blob/master/srcpkgs/chromium/patches/reenable-linux-i686-builds.patch

this patch should fix this thing

Admin
Andreas Baumann commented on 24.10.2022 18:13

Ok, this is a good patch. I have to remove the sandbox patch (it's completely
outdated).. currently building.. [10000/51974] :-)

Admin
Andreas Baumann commented on 24.10.2022 18:27

Now failing in: (after 2 hours)

[11892/51974] ACTION //chrome/browser:resource_prefetch_predictor_proto_gen(//build/toolchain/linux/unbund
le:default)
FAILED: gen/chrome/browser/predictors/resource_prefetch_predictor.pb.h gen/chrome/browser/predictors/resou
rce_prefetch_predictor.pb.cc pyproto/chrome/browser/predictors/resource_prefetch_predictor_pb2.py 
python3 ../../tools/protoc_wrapper/protoc_wrapper.py resource_prefetch_predictor.proto --protoc ./protoc -
-proto-in-dir ../../chrome/browser/predictors --cc-out-dir gen/chrome/browser/predictors --py-out-dir pyproto/chrome/browser/predictors
Protoc has returned non-zero status: -11

That one is new.. :-)

Average Linux Fan commented on 26.10.2022 04:51

chromium based browsers work with –no-sandbox flag..

Admin
Andreas Baumann commented on 26.10.2022 05:00

That's not helping me much when building chromium and hitting the error above. :-) The build had the sandbox 32-bit seccomp patch disabled (because it has to be redone).
Still, the build failed in a (to me) unknown way..

Average Linux Fan commented on 27.10.2022 11:43

is due to some sse3 stuff?? sse3 > chromium v86…

that means a patch has to be written..

Admin
Andreas Baumann commented on 30.10.2022 07:05

I don't think this is a SSE-thingy:
gen/base/tracing/protos/chrome_track_event.descriptor
this is some generator (in
Python) failing on some things it is missing..

Average Linux Fan commented on 18.11.2022 13:31

i think its related with protobuf… try with protobuf..

Admin
Andreas Baumann commented on 18.11.2022 14:18

good point. didn't think about that. :-) protobuf is currently not building on 32-bit (see separate bug report)..
..so that could also fix building chromium..

Average Linux Fan commented on 09.03.2023 07:44

sorry for replying too late, recently i have been inactive due to school so right now one option left is to get chromium working with nix as they still have i686 chromium.

Admin
Andreas Baumann commented on 10.03.2023 07:03
Admin
Andreas Baumann commented on 10.03.2023 07:45

protobuf is fixed in the mean time, I'll try a rebuild..

Admin
Andreas Baumann commented on 10.03.2023 09:15

no, same issue with:

FAILED: gen/chrome/browser/predictors/resource_prefetch_predictor.pb.h gen/chrome/browser/predictors/resource_prefetch_predictor.pb.cc pyproto/chrome/browser/predictors/resource_prefetch_predictor_pb2.py 
python3 ../../tools/protoc_wrapper/protoc_wrapper.py resource_prefetch_predictor.proto --protoc ./protoc --proto-in-dir ../../chrome/browser/predictors --cc-out-dir gen/chrome/browser/predictors --py-out-dir pyproto/chrome/browser/predictors
Protoc has returned non-zero status: -11
Average Linux Fan commented on 13.03.2023 07:53

pb2.py …. seems like some python2 stuff going on

Admin
Andreas Baumann commented on 13.03.2023 07:58

Hopefully not, Python2 is officially dead. :-)

Admin
Andreas Baumann commented on 13.03.2023 07:59

There is some protobuf problem here when generating the predictor API interface. Maybe
predictors can be disabled?

Average Linux Fan commented on 13.03.2023 17:22

that can be tried

Loading...

Available keyboard shortcuts

Tasklist

Task Details

Task Editing