Summary: | net/boinc-client: configure alternate platform according to ${ARCH} | ||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Product: | Ports & Packages | Reporter: | Älven <alster> | ||||||||||
Component: | Individual Port(s) | Assignee: | Larry Rosenman <ler> | ||||||||||
Status: | Open --- | ||||||||||||
Severity: | Affects Only Me | CC: | ler | ||||||||||
Priority: | --- | Keywords: | easy, feature | ||||||||||
Version: | Latest | Flags: | alster:
maintainer-feedback-
|
||||||||||
Hardware: | amd64 | ||||||||||||
OS: | Any | ||||||||||||
URL: | https://boinc.berkeley.edu/trac/wiki/BuildSystem | ||||||||||||
Attachments: |
|
We also could have it with both platforms enabled: For example, on a x86_64 linux system that supports both 64-bit and 32-bit executables, you might specify --with-boinc-platform=x86_64-pc-linux-gnu and --with-boinc-alt-platform=i686-pc-linux-gnu. Just not sure whether it could be of any use, as even if some BOINC projects still have 32-bit executables, they are very likely to have 64-bit ones too, which perform better. And whether Linuxulator subsystem would be able to run 32 bit Linux executables? What else could we do with it: some kind of platform autodetection? Or manual selection via Makefile flags? This patch is just a simplest working solution, but what could the best one look like? Created attachment 243858 [details]
[PATCH] net/boinc-client: Change alternate platform to x86_64-pc-linux-gnu
Created attachment 243865 [details]
[PATCH] net/boinc-client: Change alternate platform to x86_64-pc-linux-gnu
Comment on attachment 243865 [details]
[PATCH] net/boinc-client: Change alternate platform to x86_64-pc-linux-gnu
Maintainer timeout
Fixed with commit for bug #252273. I have a simple patch for this now. Created attachment 251307 [details]
[PATCH] net/boinc-client: configure alternate platform according to ${ARCH}
|
Created attachment 243618 [details] Trivial patch As most computers with BOINC clients are running on x86_64 nowadays