Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Niklas Cassel via buildroot <buildroot@buildroot.org>
To: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
Cc: "damien.lemoal@opensource.wdc.com"
	<damien.lemoal@opensource.wdc.com>,
	"alistair@alistair23.me" <alistair@alistair23.me>,
	"geert@linux-m68k.org" <geert@linux-m68k.org>,
	"buildroot@buildroot.org" <buildroot@buildroot.org>,
	"romain.naour@smile.fr" <romain.naour@smile.fr>,
	"yann.morin.1998@free.fr" <yann.morin.1998@free.fr>
Subject: Re: [Buildroot] [PATCH v2 0/2] fix elf2flt on m68k, xtensa, riscv
Date: Tue, 17 Jan 2023 15:45:28 +0000	[thread overview]
Message-ID: <Y8bCl2PFW+amUUqB@x1-carbon> (raw)
In-Reply-To: <20220923224039.31d67d9c@windsurf>

On Fri, Sep 23, 2022 at 10:40:39PM +0200, Thomas Petazzoni wrote:
> Hello Niklas,
> 
> On Thu, 11 Aug 2022 11:40:47 +0200
> Niklas Cassel via buildroot <buildroot@buildroot.org> wrote:
> 
> > Niklas Cassel (2):
> >   package/elf2flt: remove broken patch
> >   package/elf2flt: fix fatal error regression on m68k, xtensa, riscv64
> 
> I am sorry to report that on Buildroot 2022.08, which has those
> patches, the following defconfig still fails to build:
> 
> BR2_m68k=y
> BR2_m68k_cf5208=y
> BR2_KERNEL_HEADERS_5_4=y
> BR2_TOOLCHAIN_BUILDROOT_LOCALE=y
> BR2_PTHREAD_DEBUG=y
> BR2_BINUTILS_VERSION_2_39_X=y
> BR2_BINUTILS_GPROFNG=y
> BR2_GCC_VERSION_12_X=y
> BR2_TOOLCHAIN_BUILDROOT_CXX=y
> BR2_TOOLCHAIN_BUILDROOT_FORTRAN=y
> BR2_GCC_ENABLE_OPENMP=y
> BR2_PACKAGE_HOST_GDB=y
> BR2_PACKAGE_HOST_GDB_TUI=y
> BR2_PACKAGE_HOST_GDB_PYTHON3=y
> BR2_GDB_VERSION_12=y
> BR2_INIT_NONE=y
> # BR2_PACKAGE_BUSYBOX is not set
> BR2_PACKAGE_GDB=y
> # BR2_TARGET_ROOTFS_TAR is not set
> 
> It fails with:
> 
> /home/thomas/buildroot/outputs/m68k-coldfire-uclibc-bleeding-edge/host/m68k-buildroot-uclinux-uclibc/bin/elf2flt: ERROR: text=0x3c826 overlaps data=0x256e0 ?
> 
> while building gdb for the target.


Hello Thomas,

I decided to (finally) cross this one off from my TODO list.

Submitted a fix here:
https://patchwork.ozlabs.org/project/buildroot/patch/20230117153503.2075602-1-niklas.cassel@wdc.com/


Kind regards,
Niklas
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

      reply	other threads:[~2023-01-17 15:52 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-11  9:40 [Buildroot] [PATCH v2 0/2] fix elf2flt on m68k, xtensa, riscv Niklas Cassel via buildroot
2022-08-11  9:40 ` [Buildroot] [PATCH v2 1/2] package/elf2flt: remove broken patch Niklas Cassel via buildroot
2022-08-11  9:40 ` [Buildroot] [PATCH v2 2/2] package/elf2flt: fix fatal error regression on m68k, xtensa, riscv64 Niklas Cassel via buildroot
2022-08-11 20:30   ` Thomas Petazzoni via buildroot
2022-08-12  0:02     ` Max Filippov
2022-09-15  7:21   ` Peter Korsgaard
2022-09-15 11:18     ` Niklas Cassel via buildroot
2022-09-15 14:01       ` Peter Korsgaard
2022-08-11 20:28 ` [Buildroot] [PATCH v2 0/2] fix elf2flt on m68k, xtensa, riscv Thomas Petazzoni via buildroot
2022-09-23 20:40 ` Thomas Petazzoni via buildroot
2023-01-17 15:45   ` Niklas Cassel via buildroot [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=Y8bCl2PFW+amUUqB@x1-carbon \
    --to=buildroot@buildroot.org \
    --cc=Niklas.Cassel@wdc.com \
    --cc=alistair@alistair23.me \
    --cc=damien.lemoal@opensource.wdc.com \
    --cc=geert@linux-m68k.org \
    --cc=romain.naour@smile.fr \
    --cc=thomas.petazzoni@bootlin.com \
    --cc=yann.morin.1998@free.fr \
    /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