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] [day] [month] [year] [list]
Message-ID: <CAK7LNARi=SVL_b-FhbGtxDmyBgRFtxWrk+F98cmabRWZBHzTUQ@mail.gmail.com>
Date: Sun, 10 Nov 2024 06:53:55 +0900
From: Masahiro Yamada <masahiroy@...nel.org>
To: Matt Fleming <matt@...dmodwrite.com>
Cc: nicolas@...sle.eu, benh@...ian.org, justinstitt@...gle.com, 
	linux-kbuild@...r.kernel.org, linux-kernel@...r.kernel.org, 
	llvm@...ts.linux.dev, morbo@...gle.com, nathan@...nel.org, 
	ndesaulniers@...gle.com, re@...z.net, kernel-team@...udflare.com
Subject: Re: [PATCH 2/3] kbuild: deb-pkg: add pkg.linux-upstream.nokernelheaders
 build profile

On Thu, Nov 7, 2024 at 4:18 AM Matt Fleming <matt@...dmodwrite.com> wrote:
>
>
> Hey there,
>
> Can you explain how this change works a bit more? This reads like it's now
> impossible to build the debian linux-headers package with clang? At Cloudflare,
> we're using a custom build of gcc, not the gcc-x86-64-linux-gnu package, and
> with this change we can no longer build linux-headers.

You need to install the gcc-x86-64-linux-gnu package.
This is available on both Debian and Ubuntu.

Adding the prefix is required to reliably produce the correct
linux-headers package.

For example, when building a linux-headers package for i386 on amd64,
userspace tools must be recompiled with 'i686-linux-gnu-gcc'.


> What's the solution for those of us that want to build the linux-headers deb
> package but can't install gcc-*-linux-gnu?

DPKG_FLAGS=-d

will skip the build dependency check, but 'x86_64-linux-gnu-gcc'
is still required.

If only clang is available on your system, you need a workaround,
e.g.

 ln -s clang ~/bin/x86_64-linux-gnu-gcc

Anyway, you need to find a solution.

-- 
Best Regards
Masahiro Yamada

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ