I have just noticed that when running the multiboot2 build with "configure
CC=clang" instead of going with the default gcc, clang10 will not recognize the
"-Wa,-adhlns=$(@:.o=.lst)" argument and abort.
Ist clang support for the multiboot2 example kernel important? If so, I could
either comment out those parameter additions, or guard them with a check for
adhlns support and an AM_CONDITIONAL in configure.ac.
Am 15. Mai 2020 05:43:46 MESZ schrieb Hans Ulrich Niedermann
:
>Generate one listing file *.lst per object file *.o.
>
>This allows easy examination of the generated machine code,
>making the example kernel more educational.
>
>Signed-off-by: Hans Ulrich Niedermann
>
>diff --git a/.gitignore b/.gitignore
>index e27a3e0e2..7a035c267 100644
>--- a/.gitignore
>+++ b/.gitignore
>@@ -30,6 +30,7 @@ Makefile
> /stamp-h1
>
> # Generated by "make"
>+*.lst
> *.o
>
> /doc/*.S.texi
>diff --git a/doc/Makefile.am b/doc/Makefile.am
>index cb290a0cb..cc07ceec8 100644
>--- a/doc/Makefile.am
>+++ b/doc/Makefile.am
>@@ -1,3 +1,4 @@
>+CLEANFILES =
> info_TEXINFOS = multiboot.texi
> arch_sources = boot_i386.S boot_mips.S
>multiboot_TEXINFOS = boot_i386.S.texi boot_mips.S.texi kernel.c.texi
>multiboot2.h.texi
>@@ -17,6 +18,10 @@ kernel_CFLAGS = $(kernel_cflags) -fno-builtin
>-nostdinc -O -g -Wall \
> -imacros $(top_builddir)/config.h
>kernel_LDFLAGS = -nostdlib -Wl,-N -Wl,-Ttext -Wl,8010
>-Wl,--build-id=none
>
>+CLEANFILES += *.lst
>+kernel_CCASFLAGS += -Wa,-adhlns=$(@:.o=.lst)
>+kernel_CFLAGS+= -Wa,-adhlns=$(@:.o=.lst)
>+
> EXTRA_DIST = $(man_MANS) $(noinst_SCRIPTS) \
> $(arch_sources) $(multiboot_TEXINFOS)
>
>--
>2.26.2
>
>
>___
>Grub-devel mailing list
>Grub-devel@gnu.org
>https://lists.gnu.org/mailman/listinfo/grub-devel
___
Grub-devel mailing list
Grub-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/grub-devel
