search for: l346

In data giovedì 25 giugno 2015 14:50:03, Richard W.M. Jones ha scritto: > We had a chat about this on IRC, and I'm not very happy about any > patch that requires a special ./configure flag. I'm not sure where you see any special ./configure flag, other than what is already there (and not used much because makes things cumbersome). > We should find a way > to enable this

...272f962926ab279ac4cf37855dd2008d/src/lib/restrict-access.c#L238-L256 <https://github.com/dovecot/core/blob/863887d4272f962926ab279ac4cf37855dd2008d/src/lib/restrict-access.c#L238-L256> https://github.com/dovecot/core/blob/863887d4272f962926ab279ac4cf37855dd2008d/src/lib/restrict-access.c#L342-L346 <https://github.com/dovecot/core/blob/863887d4272f962926ab279ac4cf37855dd2008d/src/lib/restrict-access.c#L342-L346> doveconf -n: > # 2.3.0.1 (ffd8a29): /opt/local/etc/dovecot/dovecot.conf > # Pigeonhole version 0.5.0.1 (d33dca20) > # OS: Darwin 18.6.0 x86_64 apfs > auth_cache_si...

...more on the parts you consider racy? There are two objections: (1) That we currently have separate shutdown paths in the valgrind/non-valgrind case: https://github.com/libguestfs/libguestfs/blob/master/src/handle.c#L429-L443 https://github.com/libguestfs/libguestfs/blob/master/src/conn-socket.c#L346-L364 We shouldn't have two different paths that developers and non- developers use. (2) This actually causes bugs. The second one is the race. https://bugzilla.redhat.com/show_bug.cgi?id=1023630 https://bugzilla.redhat.com/show_bug.cgi?id=1020216 There's also another race which I don...

...e paths. As long as all the source that is being built is below the toplevel CMake directory, and the build directory itself is within the toplevel CMake project directory, CMake uses relative paths in all build files. (https://github.com/Kitware/CMake/blob/master/Source/cmLocalGenerator.h#L338-L346 contains some mention of this.) This means, my build layout is that I build in llvm-project/llvm/build. In this setup, CMake produces build files with paths e.g. ../tools/clang/. If I use LLVM_ENABLE_PROJECTS for enabling clang/lldb, all clang/lldb source files are referenced by absolute path...

Not all UEFI guests can survive conversion, because of lost bootloader information in UEFI NVRAM. But some guest can cope with this because they have a fallback bootloader and use UEFI Removable Media Boot Behavior. (see https://uefi.org/sites/default/files/resources/UEFI_Spec_2_8_A_Feb14.pdf 3.5.1.1 Removable Media Boot Behavior) to load. If UEFI firmware can't find a bootloader in its

Sorry for the delay in writing this up and sending it out, but I wanted to recap the discussion from the roundtable on October 23rd. The roundtable ran for almost two hours and we discussed at most of the main points in my RFC. Thank you everyone who participated and contributed to the discussion! TL;DR: We should move to CMake 3.15 (RFC incoming). We should make `all` really `all`. We should