From: Alexander Dahl <post@lespocky.de>
To: Roland Hieber <rhi@pengutronix.de>
Cc: Alexander Dahl <post@lespocky.de>, ptxdist@pengutronix.de
Subject: Re: [ptxdist] [PATCH 2/2] m4: make it build with ICECC again
Date: Fri, 26 Apr 2019 21:08:55 +0200 [thread overview]
Message-ID: <20190426190855.iuw6bpc7faj5lwqd@falbala.home.lespocky.de> (raw)
In-Reply-To: <20190426184253.ex43p36lh577v2yo@pengutronix.de>
[-- Attachment #1.1: Type: text/plain, Size: 2327 bytes --]
Hei hei,
I brought this up on IRC yesterday, I just tried to compile DistroKit
master on Debian 10 (buster) on an amd64 host, with some Debian 9
(stretch) icecc nodes on the local net.
On Fri, Apr 26, 2019 at 08:42:53PM +0200, Roland Hieber wrote:
> On Fri, Apr 26, 2019 at 07:49:44PM +0200, Roland Hieber wrote:
> > Signed-off-by: Roland Hieber <rohieb@rohieb.name>
> > ---
> > ...nt-warnings-when-building-with-ICECC.patch | 39 +++++++++++++++++++
> > patches/m4-1.4.18/series | 3 +-
> > 2 files changed, 41 insertions(+), 1 deletion(-)
> > create mode 100644 patches/m4-1.4.18/0002-HACK-prevent-warnings-when-building-with-ICECC.patch
> >
> > diff --git a/patches/m4-1.4.18/0002-HACK-prevent-warnings-when-building-with-ICECC.patch b/patches/m4-1.4.18/0002-HACK-prevent-warnings-when-building-with-ICECC.patch
> > new file mode 100644
> > index 000000000..979106910
> > --- /dev/null
> > +++ b/patches/m4-1.4.18/0002-HACK-prevent-warnings-when-building-with-ICECC.patch
> > @@ -0,0 +1,39 @@
> > +From: Roland Hieber <rohieb@rohieb.name>
> > +Date: Fri, 26 Apr 2019 19:11:19 +0200
> > +Subject: [PATCH] HACK: prevent warnings when building with ICECC
> > +
> > +If ICECC is enabled, -fdirectives-only is apparently always used, which
> > +leads to errors like
> > +
> > + verify.h:161:31: error: __COUNTER__ expanded inside directive with -fdirectives-only
>
> Strange, I see the same issue with glib too, and libtasn1, and
> host-gettext, and gdbserver. All of them seem to have forked the same
> verify.h... :) But I don't think patching all of them is the right way
> to approach this.
I only saw the issue with host-m4.
> Debian testing/unstable, ptxdist master, ICECC 1.2.0, host-gcc 8.2.0,
> but I also saw this with an old host-gcc 5.4.0, so I guess it's
> independent of the host compiler version.
Could the difference be in the icecc version on the host? Debian 9 has
ICECC 1.0.1 and does not fail. Debian 10 has ICECC 1.2.0 and fails.
Greets
Alex
--
/"\ ASCII RIBBON | »With the first link, the chain is forged. The first
\ / CAMPAIGN | speech censured, the first thought forbidden, the
X AGAINST | first freedom denied, chains us all irrevocably.«
/ \ HTML MAIL | (Jean-Luc Picard, quoting Judge Aaron Satie)
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
[-- Attachment #2: Type: text/plain, Size: 91 bytes --]
_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de
next prev parent reply other threads:[~2019-04-26 19:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-26 17:49 [ptxdist] [PATCH 1/2] m4: re-export patches with git-ptx-patches Roland Hieber
2019-04-26 17:49 ` [ptxdist] [PATCH 2/2] m4: make it build with ICECC again Roland Hieber
2019-04-26 18:42 ` Roland Hieber
2019-04-26 19:08 ` Alexander Dahl [this message]
2019-04-26 19:16 ` Roland Hieber
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=20190426190855.iuw6bpc7faj5lwqd@falbala.home.lespocky.de \
--to=post@lespocky.de \
--cc=ptxdist@pengutronix.de \
--cc=rhi@pengutronix.de \
/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