All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sven Joachim <svenjoac@gmx.de>
To: "David F." <df7729@gmail.com>
Cc: Linux Kbuild mailing list <linux-kbuild@vger.kernel.org>
Subject: Re: Building x64 kernel on i686 broken in 6.12.
Date: Fri, 20 Jun 2025 08:37:01 +0200	[thread overview]
Message-ID: <87a562apgy.fsf@turtle.gmx.de> (raw)
In-Reply-To: <CAGRSmLuJmg38_Rai+3vDFHQUedFynNdo8ORjkKwS9w=V8qU_dA@mail.gmail.com> (David F.'s message of "Thu, 19 Jun 2025 21:14:13 -0700")

On 2025-06-19 21:14 -0700, David F. wrote:

> I'm resending this since no response.   It appears something was
> changed to address ARM64 and it broke building x64 on i686 which I've
> done for a very long time.
>
> Resending:
>
>
> I always build both the i686 and x64 kernel on my VM which has changed
> through the years from debian (several distros) to now devuan-chimaera
> (couple years now). Last build was 6.6.x but now jumping to 6.12.x. I
> can build the 686 version however, it won't build the x64 version and
> gives me a dependency issue.
>
> At first it was gcc-x86-64-linux-gnu, libssl-dev
>
> I first updated libssl-dev, then the gcc-x86-64-linux-gnu with apt-get install
>
> It now just says it doesn't like libssl-dev but it's installed and up to date.

You need to install libssl-dev for both the host and the build
architecture, so install libssl-dev:amd64.

Alternatively, if you do not need the linux-headers package, use the
pkg.linux-upstream.nokernelheaders build profile, like so:

$ DEB_BUILD_PROFILES=pkg.linux-upstream.nokernelheaders make [...] bindeb-pkg

See commit e2c318225ac1 ("kbuild: deb-pkg: add
pkg.linux-upstream.nokernelheaders build profile").

Cheers,
       Sven

      reply	other threads:[~2025-06-20  6:37 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-20  4:14 Building x64 kernel on i686 broken in 6.12 David F.
2025-06-20  6:37 ` Sven Joachim [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87a562apgy.fsf@turtle.gmx.de \
    --to=svenjoac@gmx.de \
    --cc=df7729@gmail.com \
    --cc=linux-kbuild@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.