actually, here's a decent summary of the current state of things (including CI):
https://linuxplumbersconf.org/event/4/contributions/521/attachments/355/586/LPC-2019-toolchains-ClangBuiltLinux.pdf On Thu, Sep 12, 2019 at 9:44 AM enh <[email protected]> wrote: > > On Thu, Sep 12, 2019 at 8:57 AM Denys Nykula <[email protected]> wrote: > > > > > throw symlinks all over the place if you like > > > > Contrarily, I make fewer symlinks. > > > > > (And they've > > > apprently rewritten the documentation in rust, which I was unaware was an > > > option?) > > > > RST is ReStructured Text. Sort of like Markdown. Has tooling for tables of > > contents and interlinks, generates PDFs and HTML. > > > > > > Mkroot is useful. Regarding allnoconfig, where should I read about > > > > kconfig CLI > > > > helpers if they exist? > > > > > > make help (in toybox or in linux), and there's something under the > > > Documentation > > > directory in the kernel but they keep moving the files there. > > > > > > https://www.kernel.org/doc/Documentation/kbuild/kconfig.txt > > > > Config creation I have seen in docs, config updating and deletion too, but > > what > > about config read and analysis? Like for userland, Portage can find the > > missing > > flags on which the present manually specified flags depend, and generates a > > config including those flags, bailing out if there are || options but saving > > time in the majority of simple cases. So that fewer of those missing flags > > ever have to appear in the miniconfig, as config inflator could derive them. > > > > > I also have my own compressed version of the config files: > > > > > > http://landley.net/aboriginal/FAQ.html#dev_miniconfig > > > > Yep that's from where I learned about the allnoconfig. > > > > > Which I tried to submit upstream multiple times back when I still engaged > > > with > > > linux-kernel: > > > > > > https://lwn.net/Articles/161086/ > > > > Todo read. Probably you answered my above question there but I'm offline > > at the moment of writing this, sending later. > > > > > > #!/bin/sh > > > > # $ kwhy ACPI_WMI > > > > # DELL_WMI > > > > # IDEAPAD_LAPTOP > > > > # ... > > > > find /src/linux/ -name Kconfig -not -path '*scripts*tests*' -exec perl > > > > -0pe 's/\ > > > > nconfig (.+)(\n[ \t]+.*)*\n[ \t]+depends > > > > on.*[^!\w\n]('$1')[^!\w].*/\n$1\n/g;s/( > > > > ^|\n)[^A-Z\n].*/\n/g;s/\s+/\n/g;s/^\n//' {} + > > > > > > See you and raise you: > > > > > > https://github.com/landley/aboriginal/blob/master/more/miniconfig.sh > > > > I have a miniconfig. Some of its items, now leaves, I once manually > > selected to > > make other items visible. While those items are no longer needed, these > > leaves > > remain in miniconfig. I'm asking if a CLI helper could tell me what items > > outside > > miniconfig depended on the remaining leaves inside miniconfig. Since I > > haven't > > found such a helper, I prototyped mine but it's obviously a stopgap. > > > > > > Build continues, just prints distracting warnings at the beginning. > > > > Wrote this > > > > down when trying to build as much as possible with LLVM and note all > > > > that > > > > might have been going wrong. > > > > > > There's more or less annual bursts of interest in that > > > > Looks annual to publishers who report on releases, not following the issues > > and > > everyday development much. Kernel releases more often. LLVM 9 has all the > > compiler extensions and binutils flags required by the kernels released > > earlier > > this year, so its Clang now builds the kernel without GNU binutils which > > reports from previous years were all about. > > yeah, as of this year Android no longer uses GNU binutils for kernels > or userspace, and we're switching the NDK over to the llvm > replacements now. (the NDK might still require us to implement a few > extra flags here and there, since we have a lot less control over what > NDK users are up to than we do in the platform build.) > > > > >>> if ! sed -n -e '/^# Generated by .*libtool/q0;4q1' "${f}"; then > > > >>> continue; fi > > > >> > > > >> Ok, so you need the exitcode extension to q, and never previously > > > >> mentioned it > > > >> on this list. Right, easy enough to add... > > > > > > > > Haven't mentioned because it's not a bottleneck and is in my own todo > > > > list. > > > > > > Just added it, and a couple other things while I was in the area. > > > > > > (The largest part of the patch was the error checking for q123 having > > > something > > > other than digits after it.) > > > > Great! > > > > > > /portage/eclass/epatch.eclass: > > > > # Generate some useful debug info ... > > > > ${patch_cmd} --dry-run -f < "${PATCH_TARGET}" 2>&1 > > > > > > > > Gentoo duplicated this in another place, adding two more options to > > > > imitate > > > > the same dry run behavior in case of a mismatch, dropped support for > > > > standard > > > > patch and required GNU everywhere. This seems dirty and I'm in favor of > > > > letting extra options other than -f remain broken. > > > > > > I wonder what funtoo does? > > > > Copies ebuilds with a delay and puts chief architect name on commits? > > > > > And I am riffing on names which means I am sleep deprived > > > > Sorry. > > _______________________________________________ > > Toybox mailing list > > [email protected] > > http://lists.landley.net/listinfo.cgi/toybox-landley.net _______________________________________________ Toybox mailing list [email protected] http://lists.landley.net/listinfo.cgi/toybox-landley.net
