From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] nasm: Fix compilation with GCC 8
Date: Thu, 24 May 2018 23:03:29 +0200 [thread overview]
Message-ID: <87bmd4davy.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20180505023428.32414-1-casantos@datacom.ind.br> (Carlos Santos's message of "Fri, 4 May 2018 23:34:28 -0300")
>>>>> "Carlos" == Carlos Santos <casantos@datacom.ind.br> writes:
> host-nasm fails to compile with GCC 8:
> In file included from ./include/nasm.h:46,
> from asm/nasm.c:47:
> ./include/nasmlib.h:194:1: error: ?pure? attribute on function returning ?void? [-Werror=attributes]
> void pure_func seg_init(void);
> ^~~~
> Pull a patch from upstream that removes the stale declaration of
> seg_init, which was eliminated a long time ago.
> Signed-off-by: Carlos Santos <casantos@datacom.ind.br>
Committed to 2018.02.x, thanks.
--
Bye, Peter Korsgaard
prev parent reply other threads:[~2018-05-24 21:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-05 2:34 [Buildroot] [PATCH] nasm: Fix compilation with GCC 8 Carlos Santos
2018-05-05 9:21 ` Peter Korsgaard
2018-05-24 21:03 ` Peter Korsgaard [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=87bmd4davy.fsf@dell.be.48ers.dk \
--to=peter@korsgaard.com \
--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