linux-kernel - Re: headers_install builds break on a lot of targets?

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:   Wed, 3 Jun 2020 19:59:32 +0200
From:   Arnd Bergmann <arnd@...db.de>
To:     Rich Felker <dalias@...c.org>
Cc:     Rob Landley <rob@...dley.net>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
        David Woodhouse <dwmw2@...radead.org>,
        Masahiro Yamada <yamada.masahiro@...ionext.com>
Subject: Re: headers_install builds break on a lot of targets?

On Wed, Jun 3, 2020 at 7:04 PM Rich Felker <dalias@...c.org> wrote:
> On Wed, Jun 03, 2020 at 08:49:54AM -0500, Rob Landley wrote:
> >     make ARCH=$i distclean defconfig headers_install \
> >
> > On the bright side, the resulting fruitbasket.tar.xz is 1.5 megabytes. The
> > downside is I have no idea how broken the resulting header files are after this
> > error-fest:
> >
> > alpha
> > arc
> > gcc: error: unrecognized command line option ‘-mmedium-calls’
> > gcc: error: unrecognized command line option ‘-mno-sdata’; did you mean
> > ‘-fno-stats’?
> > gcc: error: unrecognized command line option ‘-mmedium-calls’
> > gcc: error: unrecognized command line option ‘-mno-sdata’; did you mean
> > ‘-fno-stats’?
> > [...]
>
> Uhg. Surely there should be some fix for whatever mistaken dep is
> behind this? Headers shouldn't actually depend on any config/compiler
> output, should they??

The first one of the two comes from "make defconfig", which definitely needs
a working $TARGET compiler, but isn't actually needed before
"make headers_install" as I just checked.

> Or is that machinery somehow involved in
> generating the syscall lists and similar?

The syscall list for ARC is still not generated (that's on my todo list), but
something does call it even for "make headers_install".

What it does is to set Makefile variables such as

CC_VERSION_TEXT = $(shell $(CC) --version 2>/dev/null | head -n 1)
and trying out all kinds of gcc options that may or may not be supported
such as  "$(call cc-option,-fno-tree-loop-im)".

Setting CC=: avoids this, like

make -s CC=: ARCH=$i headers_install  INSTALL_HDR_PATH="$PWD/fruitbasket/$i"

      Arnd