From: Waldemar Brodkorb <wbx@openadk.org>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] pcre: fix compile error for m68k coldfire
Date: Fri, 19 Aug 2016 23:24:56 +0200 [thread overview]
Message-ID: <20160819212456.GY22524@waldemar-brodkorb.de> (raw)
In-Reply-To: <20160819231348.2127118e@free-electrons.com>
Hi Thomas,
Thomas Petazzoni wrote,
> So we have several options here:
>
> 1/ Mark pcre as not available for BR2_BINFMT_FLAT_SEP_DATA. But pcre
> has gazillions of reverse dependencies, and I expect the issue of
> -msep-data to show up on many many packages, as soon as they have a
> fairly large binary size.
>
> 2/ Actually fix up the problem, but I'm not sure it's even doable.
>
> 3/ Decide that we don't support BR2_BINFMT_FLAT_SEP_DATA at all on
> m68k. On master, BR2_BINFMT_FLAT_ONE was not available for m68k due
> to kernel issues, but they have been resolved, and
> BR2_BINFMT_FLAT_ONE is now enabled on m68k in the next branch. So I
> would suggest to also enable BR2_BINFMT_FLAT_ONE on m68k in master,
> disallow the selection of BR2_BINFMT_FLAT_SEP_DATA. If in the
> future someone is interested by -msep-data on m68k, this person can
> always restart the work and see how to fix the issues.
I vote for 3)
thanks for the nice summary,
Waldemar
next prev parent reply other threads:[~2016-08-19 21:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-18 6:25 [Buildroot] [PATCH] pcre: fix compile error for m68k coldfire Waldemar Brodkorb
2016-08-19 21:13 ` Thomas Petazzoni
2016-08-19 21:24 ` Waldemar Brodkorb [this message]
2016-08-22 15:30 ` Peter Korsgaard
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=20160819212456.GY22524@waldemar-brodkorb.de \
--to=wbx@openadk.org \
--cc=buildroot@busybox.net \
/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