All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Andrew Randrianasulu <randrianasulu@gmail.com>,
	lkml <linux-kernel@vger.kernel.org>
Cc: Thomas Gleixner <tglx@linutronix.de>,
	Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>,
	Dave Hansen <dave.hansen@linux.intel.com>,
	x86@kernel.org, "H. Peter Anvin" <hpa@zytor.com>,
	Michael Kelley <mikelley@microsoft.com>
Subject: Re: Build failure in 6.5-rcX ?
Date: Wed, 16 Aug 2023 10:27:49 +0700	[thread overview]
Message-ID: <ZNxCNRzvDN87_MIf@debian.me> (raw)
In-Reply-To: <CA+rFky5xK35402EGQ-6VqxT-arR7SWLAcp2PyB1xK9ZGRqhs2A@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1914 bytes --]

On Fri, Aug 11, 2023 at 11:39:06PM +0300, Andrew Randrianasulu wrote:
> I was trying to crosscompile linux git
> 
> 9106536c1aa37bcf60202ad93bb8b94bcd29f3f0
> 
> Unfortunately I got this error:
> 
> ====
> bash-5.1$ make ARCH=x86_64 CROSS_COMPILE=x86_64-unknown-linux-gnu-
>   CALL    scripts/checksyscalls.sh
>   DESCEND objtool
>   INSTALL libsubcmd_headers
>   CHK     kernel/kheaders_data.tar.xz
>   UPD     include/generated/utsversion.h
>   CC      init/version-timestamp.o
>   LD      .tmp_vmlinux.kallsyms1
> arch/x86/kernel/irq.o: In function `__common_interrupt':
> irq.c:(.text+0x1727): undefined reference to `irq_regs'
> irq.c:(.text+0x172f): undefined reference to `irq_regs'
> irq.c:(.text+0x179a): undefined reference to `irq_regs'
> arch/x86/kernel/irq.o: In function `__sysvec_x86_platform_ipi':
> irq.c:(.text+0x1897): undefined reference to `irq_regs'
> irq.c:(.text+0x189f): undefined reference to `irq_regs'
> arch/x86/kernel/irq.o:irq.c:(.text+0x194a): more undefined references
> to `irq_regs' follow
> make[2]: *** [scripts/Makefile.vmlinux:36: vmlinux] Ошибка 1
> make[1]: *** [/dev/shm/linux-2.6/Makefile:1250: vmlinux] Ошибка 2
> make: *** [Makefile:234: __sub-make] Ошибка 2
> 
> ====
> 
> config attached.
> 
> I use binutils 2.25.1 and gcc 7.5.0 targeting x86_64-unknown-linux-gnu-
> 
> so my compile line was
> 
>  make ARCH=x86_64 CROSS_COMPILE=x86_64-unknown-linux-gnu- -j8
> 
> after adding crosscompiler into PATH
> 
> I tried to rebuild with make clean, but issue still here.
> 

What system are you running your kernel builds?

And in the future, please run make with V=1. Also, try prepending it with
LC_ALL=en_US.UTF-8 to set compilation messages to English instead of your
language, as people here can understand what's going wrong.

Thanks.

-- 
An old man doll... just what I always wanted! - Clara

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]

  parent reply	other threads:[~2023-08-16  3:29 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-11 20:39 Build failure in 6.5-rcX ? Andrew Randrianasulu
2023-08-11 23:16 ` Randy Dunlap
     [not found]   ` <CA+rFky49=Cj1MaQszHuyYMnuNA0UTBNoVNN4xfjHWujzfkKO8g@mail.gmail.com>
2023-08-12  0:03     ` Randy Dunlap
2023-08-12  0:02       ` Andrew Randrianasulu
2023-08-16  3:27 ` Bagas Sanjaya [this message]
2023-08-16  3:25   ` Andrew Randrianasulu

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=ZNxCNRzvDN87_MIf@debian.me \
    --to=bagasdotme@gmail.com \
    --cc=bp@alien8.de \
    --cc=dave.hansen@linux.intel.com \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mikelley@microsoft.com \
    --cc=mingo@redhat.com \
    --cc=randrianasulu@gmail.com \
    --cc=tglx@linutronix.de \
    --cc=x86@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.