search for: l338

Displaying 3 results from an estimated 3 matches for "l338".

Did you mean: 338
2023 Jan 23
7
[Bug 3527] New: ssh-copy-id broken for dropbear
...keys, and I can ssh to remote without password prompt afterwards. It's possible this dropbear switch bug was added by someone who uses system, that runs a modified version of dropbear, perhaps router of some sort. 1: https://github.com/openssh/openssh-portable/blob/master/contrib/ssh-copy-id#L338 -- Your, Stephan -- You are receiving this mail because: You are watching the assignee of the bug.
2019 Oct 29
2
RFC: LLVM Build System Future Direction
...lative 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...
2019 Oct 29
11
RFC: LLVM Build System Future Direction
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