Skip to content

Conversation

@jsoo1
Copy link
Collaborator

@jsoo1 jsoo1 commented Jun 16, 2023

With accompanying nixos vm test.

jsoo1 and others added 29 commits June 16, 2023 13:20
It fails to apply
USE_OPTIMIZE_FOR_ARCHITECTURE was removed without commit in a prior
commit. This is because it was removed upstream:

arangodb/arangodb@cc860c3

This is unfortunate - now /proc/cpuinfo is read unconditionally for
feature detection.

Some other means of feature detection will have to be found.
It seems that gcc11 - though reportedly supported - introduced some
constraint that arangodb fails to compile with.
Avoid non-deterministic builds of ArangoDB proper. Note that this
provides 0 guarantees about the vendored libraries doing anything
similar.
If -DTARGET_ARCHITECTURE is supplied arango's cmake configuration will
not use /proc/cpuinfo for feature detection. However, `generic` and
`none` options both fail when building the vendored v8.

This workaround provides some defaults, but warns if no override is
provided.
As far as I can tell, this can cause compile failures when building
the vendored abseil_cpp if choosing a target arch that does not
support sse. This might be possible to determine programmatically, but
it is more flexible to let the user decide.
For which no reliable default target architecture is provided upstream.
@jsoo1 jsoo1 force-pushed the jsoo1/main/upgradable-postgres branch 4 times, most recently from 6b18874 to 1490c15 Compare July 14, 2023 23:50
With accompanying nixos vm test.
@jsoo1 jsoo1 force-pushed the jsoo1/main/upgradable-postgres branch from 1490c15 to 8bbd2e6 Compare July 14, 2023 23:55
@jsoo1 jsoo1 force-pushed the main branch 2 times, most recently from 6580daa to d83f082 Compare December 26, 2023 18:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.