Displaying 5 results from an estimated 5 matches for "cumentation".
2014 Nov 17
2
Syslinux 6.03, kernel not relocatable.
...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 you p...
2014 Nov 17
0
Syslinux 6.03, kernel not relocatable.
...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=Y so...
2014 Nov 16
3
Syslinux 6.03, kernel not 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:
2019 Sep 13
2
[9.0.0 Release] Release Candidate 4 is here
It may be that the 'not' operator is not being found under bash at
: 'RUN: at line 12'; not
Perhaps this is would be better as the more commonly seen '!'.
Neil Nelson
On 9/13/19 12:12 PM, Neil Nelson via llvm-dev wrote:
>
> Toward the end of testing.9.0.0-rc4.log.
>
> Testing: 0 .. 10.. 20.
> FAIL: Clang Tools :: clang-tidy/run-clang-tidy.cpp (17057 of
2019 Sep 13
2
[9.0.0 Release] Release Candidate 4 is here
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,