Building memflow-native from development fails with memflowup

[GanbaruTobi]

This is the result from memflowup interactive and installing memflow-native with the development option, like showing in the docs at https://memflow.io/quick_start/

[GanbaruTobi]

Using stable also doesnt work:

[danielnehrig]

There are also issues on CI with building
locally for me on 1.76 i can build latest native main just fine maybe try upgrading for the mean time while stuff is fixed
or revert back to an older commit of the repo

[GanbaruTobi]

Locally i run rustc with 1.76.0 if thats what you are referring to. memflow seems to hardcode to 1.74.0 in its cargo.toml, but memflowup is not and thats what I am using.

[ko1N]

Thanks for the heads up! I reverted to the older procfs version to fix this. However we are waiting for m4b/goblin#386 to properly re-release memflow-native and fix it properly in memflowup. Additionally memflow-pcileech needs to be fixed in memflowup, too.

[ko1N]

I worked on the new memflowup release in the last couple weeks specifically for binary builds. If you wanna give it a shot, we already have release artifacts for memflow-native added. We still wait for the goblin merge to provide a proper crates.io release.

To give it a shot:

# install the current git version of memflowup:
cargo install --git https://github.com/memflow/memflowup

# query available artifacts of memflow-native:
memflowup --skip-version-check registry ls native

# pull the latest
memflowup --skip-version-check pull native

# alternatively install from source:
memflowup --skip-version-check build https://github.com/memflow/memflow-native

Let me know if this works for you. Once we have some more testing done we are fully releasing the new memflowup and then you can omit the --skip-version-check flag.

Hope this helps :)

[GanbaruTobi]

pull the latest

memflowup --skip-version-check pull native

On Linux:

On Windows:

Building from source worked on both systems