gl-yziquel

Results 67 comments of gl-yziquel

Build failed: 'numeric_limits' is not a member of 'std'

Proposed a PR for this: https://github.com/annoviko/pyclustering/pull/699 "This works on my computer".

Unclear how to build gvm itself

Stating that ./autogen.sh && make install does the trick would be welcome. it's otherwise not as much confusing as it is not quite straightforward.

Unclear how to build gvm itself

Hmmhh... no. This is precisely the point: the INSTALL file says to to something like autogen.sh, configure, make, make install. which is broken. binscripts/gvm-installer works. So the INSTALL file and...

Unclear how to build gvm itself

@ankitcharolia I'll attempt to give it a shot when go stuff gets back on top of my todo pile.

Virtualised cargo fails with a "No such device" error n°19 likely because of MAP_SHARED mmap call on qemu + virtiofsd with --cache=never.

Confirmation. I did an `strace -f cargo build`. And, after some hunting... ```console [pid 43835] mmap(NULL, 48973144, PROT_READ, MAP_SHARED, 9, 0 [pid 43835] ) = -1 ENODEV (No such device)...

Virtualised cargo fails with a "No such device" error n°19 likely because of MAP_SHARED mmap call on qemu + virtiofsd with --cache=never.

> Thank you for the report. Really appreciate the effort! > > The error came from rustc the compiler. I'm tracing it here in strace -f: ```console [pid 43793] execve("/home/mini-me/.rustup/toolchains/stable-x86_64-unknown-linux-gnu/bin/rustc",...

Virtualised cargo fails with a "No such device" error n°19 likely because of MAP_SHARED mmap call on qemu + virtiofsd with --cache=never.

> We need someone familiar with this part to determine if it is safe and better to use `MAP_PRIVATE`. From what I understood, MAP_PRIVATE has some corner cases that make...

Virtualised cargo fails with a "No such device" error n°19 likely because of MAP_SHARED mmap call on qemu + virtiofsd with --cache=never.

> > From what I understood, MAP_PRIVATE has some corner cases that make it unsafe > > I implemented Miri's `mmap` support so I'd like to think I know a...

Virtualised cargo fails with a "No such device" error n°19 likely because of MAP_SHARED mmap call on qemu + virtiofsd with --cache=never.

> Ah. Whatever that IRC discussion was is not about the Rust concept of unsafety. In Rust, the way we use `memmap2` is UB if the mapping is updated. So...

Virtualised cargo fails with a "No such device" error n°19 likely because of MAP_SHARED mmap call on qemu + virtiofsd with --cache=never.

So, roughly, we can safely assume that MAP_SHARED will misbehave, and unsafely assume MAP_PRIVATE will behave. Great.