Package Details: edencommon 2024.05.27.00-1

Git Clone URL: https://aur.archlinux.org/edencommon.git (read-only, click to copy)
Package Base: edencommon
Description: Shared library for Watchman and Eden projects
Upstream URL: https://github.com/facebookexperimental/edencommon
Licenses: MIT
Provides: libedencommon_os.so, libedencommon_telemetry.so, libedencommon_testharness.so, libedencommon_utils.so
Submitter: carsme
Maintainer: carsme
Last Packager: carsme
Votes: 2
Popularity: 0.001048
First Submitted: 2023-03-11 22:50 (UTC)
Last Updated: 2024-06-01 17:18 (UTC)

Latest Comments

carsme commented on 2024-01-20 16:16 (UTC)

@kusoneko, I think you'll be happy with aurutils long term, but I recognize the struggle of doing the initial migration, I had the same experience. Maybe you'll find something useful or get some inspiration from the custom commands I've written to adapt it to my workflow: carlsmedstad/aurutils-extra.

kusoneko commented on 2024-01-20 06:54 (UTC)

@versusvoid that's a possible issue, I did indeed also change CFLAGS and MAKEFLAGS in my makepkg.conf, not sure why that would prevent it from building (since the change in CFLAGS only tells it to compile bytecode intended for the specific CPU you use rather than for any generic x86_64-compliant CPU, which the former would make the compiled version be slightly more performant as it'd rely on CPU features and extensions that are available rather than be locked to the bare minimum, MAKEFLAGS though I have doubts about raising the -j flag causing issues, unless there's a race condition somewhere in the build setup for either folly or edencommon, both of which would be terrible for facebook in general unless their engineers somehow use only 2 cores to build their shit, not sure what your -w flag is for though, as I don't have it), but that's a possible reason

@carsme I've been spending the past few hours switching from pikaur to aurutils so I can build them all in chroot, so far everything works fine, aside from needing to make my own side scripts to handle some stuff and figuring out how to make it work with -devel packages, the feature is apparently already there but complicated as it's not as straightforward as it just checking in a regular update, instead there's an example script for that, which I'm currently fighting with, but that's besides the point. As the process of doing said switch has been going on, I used the pacman.conf and makepkg.conf with little to no modifications for both as aurutils recommends and after some fighting with it to get it to rebuild and reinstall folly, everything now builds properly. I cannot for sure pinpoint where the problem was, aside from the build of folly I was using. I'm leaning on the CFLAGS change to makepkg.conf being responsible though, despite what I said above, I can't really pinpoint what else could possibly cause this

TLDR: problem solved, current theory = using -march=native in CFLAGS instead of the defaults in makepkg.conf is the likely culprit. Unsure why.

versusvoid commented on 2024-01-19 19:02 (UTC) (edited on 2024-01-19 19:10 (UTC) by versusvoid)

@kusoneko I've been having this problem since November, waiting for a fix

Thinking now about possible differences in environment went to /etc/makepkg.conf where I had changed default

CFLAGS="-march=x86-64 -mtune=generic ...
...
MAKEFLAGS="-j2"

to

CFLAGS="-march=native ...
...
MAKEFLAGS="-j7 -w"

Restored defaults -> it compiles successfully

carsme commented on 2024-01-19 08:45 (UTC)

@kusoneko, I'm afraid I cannot reproduce this, neither on my system or in a chroot. Can you try to build in chroot? If you're building on your system, make sure to clean out any AUR-helper cache, ccache cache, etc.

kusoneko commented on 2024-01-18 19:55 (UTC)

This doesn't build for me at the moment, I have folly 2024.01.15.00-1 successfully built and installed but edencommon 2024.01.15.00-1 fails at 100% with:

/usr/bin/ld: ../libedencommon_utils.so: undefined reference to `folly::f14::detail::F14LinkCheck<(folly::f14::detail::F14IntrinsicsMode)2>::check()'
collect2: error: ld returned 1 exit status

gdiscry commented on 2023-08-28 15:04 (UTC) (edited on 2023-08-28 15:09 (UTC) by gdiscry)

Could you force-disable LTO in the PKGBUILD?

I was trying to build watchman with makechrootpkg (through aurutils) and LTO is enabled by the default configuration in devtools (from what I can tell).

By adding the following line, building watchman works even when LTO is globally enabled in makepkg.conf.

options=('!lto')

I requested a similar change in folly because LTO messes things up when it's enabled in the dependency. So building folly with LTO blocks the build of edencommon and building edencommon with LTO blocks the build of watchman.

carsme commented on 2023-03-17 18:41 (UTC)

@xuanruiqi I also have LTO flags enable as well.

The build log seems to indicate that folly isn't being found. Do you have folly or folly-git installed?

xuanruiqi commented on 2023-03-15 16:23 (UTC)

I can't build this package, do you have any idea why? I do have LTO enabled in my makepkg.conf, but even adding options=(!lto) in the PKGBUILD doesn't help.

Error messages are really long so I uploaded them here: https://pastebin.com/19kf9tFF