search for: cument

...ssue. > With CONFIG_RELOCATABLE=Y (only change to the kernel) the installer > bow boots OK, > > But meanwhile, is there some other thing I can do, like moving the > > kernel elsewhere in the image? > Stupid idea, of course. I should have dropped an eye on > /usr/src/linux/Documentation/x86/boot.txt > I hardly understand anything there, but i guess this has something > to do with the EFI handover protocol? > > The sparse mentions of "relocatable" (about modules) are > also hardly understandable by me. > > Anyway Slackware-current (or next, if...

...RELOCATABLE=Y to confirm the issue. With CONFIG_RELOCATABLE=Y (only change to the kernel) the installer bow boots OK, > But meanwhile, is there some other thing I can do, like moving the > kernel elsewhere in the image? Stupid idea, of course. I should have dropped an eye on /usr/src/linux/Documentation/x86/boot.txt I hardly understand anything there, but i guess this has something to do with the EFI handover protocol? The sparse mentions of "relocatable" (about modules) are also hardly understandable by me. Anyway Slackware-current (or next, if you prefer) has CONFIG_RELOCATABLE=...

Hi all, I have requested tests of this USB installer: http://slint.fr/testing/slint64-14.1_syslinux.6.03.img in both BIOS and UEFI modes. A test in UEFI mode: http://www.linuxquestions.org/questions/slackware-14/%5Bann%5D-syslinux-6-03-has-been-released-4175521209/#post5270515 leaded to this message: "Cannot relocate kernel, bailing out" That leaded me to this post in the ML:

..... 10.. 20. > FAIL: Clang Tools :: clang-tidy/run-clang-tidy.cpp (17057 of 64198) > ******************** TEST 'Clang Tools :: > clang-tidy/run-clang-tidy.cpp' FAILED ******************** > Script: > -- > : 'RUN: at line 1';   /usr/bin/python > /home/nnelson/Documents/llvm-project/llvm/utils/release/rc4/llvm.src/tools/clang/tools/extra/test/../test/../clang-tidy/tool/run-clang-tidy.py > --help > : 'RUN: at line 2';   rm -rf > /home/nnelson/Documents/llvm-project/llvm/utils/release/rc4/Phase3/Release+Asserts/llvmCore-9.0.0-rc4.obj/tools/clang/...

Thanks! I'll get this posted on the web site. The "Performing Test ... failed to compile" failures from cmake are not interesting. But could you look in the log file and try to see what were the tests that failed in the "check-all" step? On Thu, Sep 12, 2019 at 4:39 PM Neil Nelson via llvm-dev <llvm-dev at lists.llvm.org> wrote: > > Xubuntu/Ubuntu 19.04,