From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Waldemar Brodkorb <wbx@openadk.org>
Cc: Giulio Benetti <giulio.benetti@benettiengineering.com>,
buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH] package/libpcap: fix m68k-cf compile issue
Date: Wed, 14 Aug 2024 21:13:42 +0200 [thread overview]
Message-ID: <20240814211342.393203ce@windsurf> (raw)
In-Reply-To: <ZrzwwtPZGEENRwxV@waldemar-brodkorb.de>
On Wed, 14 Aug 2024 20:00:34 +0200
Waldemar Brodkorb <wbx@openadk.org> wrote:
> > Your bug seems somewhat similar to https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104028,
> > for which we already have BR2_TOOLCHAIN_HAS_GCC_BUG_104028 in
> > Buildroot. Not sure it is exactly the same bug.
>
> Okay, sorry. I was just taking the example from
> package/assimp/assimp.mk, which use a similar workaround for m68k.
I think the -mxgot is needed when we are building a large binary (but
I'm not 100% sure). On the other hand, disabling optimization is
clearly a workaround for a bug.
Yes, assimp.mk could use some love to better express the different
gcc/binutils bugs.
Maybe even for the mxgot thing we could do something a bit more generic
perhaps.
Thomas
--
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2024-08-14 19:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-14 13:09 [Buildroot] [PATCH] package/libpcap: fix m68k-cf compile issue Waldemar Brodkorb
2024-08-14 17:57 ` Thomas Petazzoni via buildroot
2024-08-14 18:00 ` Waldemar Brodkorb
2024-08-14 19:13 ` Thomas Petazzoni via buildroot [this message]
2024-09-16 9:26 ` Peter Korsgaard
-- strict thread matches above, loose matches on Subject: below --
2024-08-14 23:52 Waldemar Brodkorb
2024-08-15 7:19 ` Thomas Petazzoni via buildroot
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=20240814211342.393203ce@windsurf \
--to=buildroot@buildroot.org \
--cc=giulio.benetti@benettiengineering.com \
--cc=thomas.petazzoni@bootlin.com \
--cc=wbx@openadk.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.