mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Harith George <mail2hgg@gmail.com>
To: Arnd Bergmann <arnd@arndb.de>,
	Yuntao Liu <liuyuntao12@huawei.com>,
	Linus Walleij <linus.walleij@linaro.org>,
	Russell King <rmk+kernel@armlinux.org.uk>,
	Ard Biesheuvel <ardb@kernel.org>,
	harith.g@alifsemi.com
Cc: linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [build fail] v6.11-rc2 from "ARM: 9404/1: arm32: enable HAVE_LD_DEAD_CODE_DATA_ELIMINATION"
Date: Wed, 7 Aug 2024 16:51:34 +0530	[thread overview]
Message-ID: <0c725174-d67d-47f2-bd4b-29af8b8d6b1c@gmail.com> (raw)
In-Reply-To: <acc20caa-79b1-4174-98e5-97a651012685@app.fastmail.com>



On 07-08-2024 15:40, Arnd Bergmann wrote:
> Obviously 'ld' should not segfault, so there is at least one bug
> there, possibly also a kernel bug that triggered this. Can you
> try with newer binutils? This should hopefully either solve your
> problem or produce a more useful error message if there is still a
> kernel problem.
> 
> Any of the binary toolchains below should work in general,
> the latest one is the gcc-14.2/binutils-2.43 version I uploaded
> to kernel.org the other day.

So, I tested with 3 more gcc builds.

gcc14.2 (x86_64-gcc-14.2.0-nolibc-arm-linux-gnueabi.tar.xz) and gcc9.5 
(x86_64-gcc-9.5.0-nolibc-arm-linux-gnueabi.tar.xz) from 
https://mirrors.edge.kernel.org/pub/tools/crosstool/index.html
works and in both these ld does not segfault and build completes.

But gcc9.3 (armv7-eabihf--musl--stable-2020.08-1.tar.bz2) from 
(https://toolchains.bootlin.com/releases_armv7-eabihf.html) resulted in 
the same LD segfault below.

+ arm-buildroot-linux-musleabihf-ld -EL -z noexecstack --no-undefined -X 
--pic-veneer -z norelro --build-id=sha1 --orphan-handling=warn 
--script=./arch/arm/kernel/vmlinux.lds --strip-debug -o .tmp_vmlinux1 
--whole-archive vmlinux.a init/version-timestamp.o --no-whole-archive 
--start-group arch/arm/lib/lib.a lib/lib.a --end-group 
.tmp_vmlinux0.kallsyms.o
scripts/link-vmlinux.sh: line 49: 3802905 Segmentation fault      ${ld} 
${ldflags} -o ${output} ${wl}--whole-archive ${objs} 
${wl}--no-whole-archive ${wl}--start-group ${libs} ${wl}--end-group 
${kallsymso} ${btf_vmlinux_bin_o} ${ldlibs}
make[2]: *** [scripts/Makefile.vmlinux:34: vmlinux] Error 139
make[1]: *** [/home/amol/hgg/mainline/linux/Makefile:1156: vmlinux] Error 2


Thanks,
Warm Regards,
Harith


      reply	other threads:[~2024-08-07 11:21 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-07  5:12 Harith George
2024-08-07  6:42 ` liuyuntao (F)
2024-08-07  9:49 ` liuyuntao (F)
2024-08-07 11:51   ` Harith George
2024-08-07 15:22     ` liuyuntao (F)
2024-08-07 15:36       ` Harith George
2024-08-07 15:41         ` Arnd Bergmann
2024-08-07 15:47           ` liuyuntao (F)
2024-08-07 15:48           ` Harith George
2024-08-08  8:43             ` liuyuntao (F)
2024-08-08  8:31           ` liuyuntao (F)
2024-08-07 10:10 ` Arnd Bergmann
2024-08-07 11:21   ` Harith George [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=0c725174-d67d-47f2-bd4b-29af8b8d6b1c@gmail.com \
    --to=mail2hgg@gmail.com \
    --cc=ardb@kernel.org \
    --cc=arnd@arndb.de \
    --cc=harith.g@alifsemi.com \
    --cc=linus.walleij@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=liuyuntao12@huawei.com \
    --cc=rmk+kernel@armlinux.org.uk \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®