From: Lada Trimasova <Lada.Trimasova@synopsys.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 2/2] host-m4: fix build when -std=gnu99 and inline functions are used
Date: Thu, 25 Feb 2016 12:58:05 +0000 [thread overview]
Message-ID: <1456405085.2312.2.camel@synopsys.com> (raw)
In-Reply-To: <20160225135436.18a8385c@free-electrons.com>
Hi Thomas,
I used CentOS 5.7, gcc 4.9.2, glibc 2.5.
Regards,
Lada
On Thu, 2016-02-25 at 13:54 +0100, Thomas Petazzoni wrote:
Dear Lada Trimasova,
On Thu, 25 Feb 2016 14:37:10 +0300, Lada Trimasova wrote:
A lot of the glibc header files use extern inline, which causes
GCC to emit a symbol for each extern inline functions and it causes
functions multiple definition error when "-std=gnu99" is used.
To fix this problem it's necessary to use "-fgnu89-inline" option which
tells GCC to use the traditional GNU semantics for inline functions when
in C99 mode.
I'm using gcc 5.x on my laptop, which I believe defaults to -std=gnu99,
and host-m4 builds fine for me. Could you describe more precisely in
which cases host-m4 doesn't build for you?
diff --git a/package/m4/m4.mk b/package/m4/m4.mk
index 9b5d2d1..2644bb1 100644
--- a/package/m4/m4.mk
+++ b/package/m4/m4.mk
@@ -10,5 +10,6 @@ M4_SITE = $(BR2_GNU_MIRROR)/m4
M4_LICENSE = GPLv3+
M4_LICENSE_FILES = COPYING
HOST_M4_CONF_OPTS = --disable-static
+HOST_M4_MAKE_OPTS = CFLAGS="-fgnu89-inline"
I think it's cleaner to pass this in the configure script environment,
i.e:
HOST_M4_CONF_ENV = \
CFLAGS="$(HOST_CFLAGS) -fgnu89-inline"
(Same comments for the host-tar patch).
Thanks,
Thomas
next prev parent reply other threads:[~2016-02-25 12:58 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-25 11:37 [Buildroot] [PATCH 0/2] fix-build-when-std-gnu99-and-inline-functions-are-used Lada Trimasova
2016-02-25 11:37 ` [Buildroot] [PATCH 1/2] host-tar: fix build when -std=gnu99 and inline functions are used Lada Trimasova
2016-02-25 11:37 ` [Buildroot] [PATCH 2/2] host-m4: " Lada Trimasova
2016-02-25 12:54 ` Thomas Petazzoni
2016-02-25 12:58 ` Lada Trimasova [this message]
2016-02-25 13:26 ` Thomas Petazzoni
2016-02-25 15:33 ` Alexey Brodkin
2016-02-25 22:13 ` Arnout Vandecappelle
2016-02-26 7:20 ` Alexey Brodkin
2016-02-26 8:19 ` Thomas Petazzoni
2016-02-26 9:40 ` Alexey Brodkin
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=1456405085.2312.2.camel@synopsys.com \
--to=lada.trimasova@synopsys.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 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.