Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] package/berkeleydb: fix build error with gcc8
Date: Thu, 21 Jun 2018 14:16:30 +0200	[thread overview]
Message-ID: <20180621141630.44b90e93@windsurf> (raw)
In-Reply-To: <20180620195804.9594-1-bernd.kuhls@t-online.de>

Hello,

On Wed, 20 Jun 2018 21:58:04 +0200, Bernd Kuhls wrote:
> Fixes
> 
> ../src/dbinc/atomic.h:179:19: error: definition of 'int __atomic_compare_exchange(db_atomic_t*,
>  atomic_value_t, atomic_value_t)' ambiguates built-in declaration 'bool
>  __atomic_compare_exchange(unsigned int, volatile void*, void*, void*, int, int)'
>  static inline int __atomic_compare_exchange(
>                    ^~~~~~~~~~~~~~~~~~~~~~~~~
> 
> To reproduce the build error use this defconfig
> 
> BR2_GCC_VERSION_8_X=y
> BR2_TOOLCHAIN_BUILDROOT_CXX=y
> BR2_PACKAGE_BERKELEYDB=y
> BR2_PACKAGE_BERKELEYDB_COMPAT185=y
> BR2_PACKAGE_BERKELEYDB_TOOLS=y
> 
> Please note that to trigger the error BR2_TOOLCHAIN_BUILDROOT_CXX=y
> is needed although berkeleydb does not depend on c++.
> 
> Signed-off-by: Bernd Kuhls <bernd.kuhls@t-online.de>

Isn't this one a duplicate of
https://patchwork.ozlabs.org/patch/909328/?

Thomas
-- 
Thomas Petazzoni, CTO, Bootlin (formerly Free Electrons)
Embedded Linux and Kernel engineering
https://bootlin.com

  parent reply	other threads:[~2018-06-21 12:16 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-20 19:58 [Buildroot] [PATCH 1/1] package/berkeleydb: fix build error with gcc8 Bernd Kuhls
2018-06-20 21:25 ` Peter Korsgaard
2018-06-21 12:16 ` Thomas Petazzoni [this message]
2018-06-21 19:03   ` Bernd Kuhls

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=20180621141630.44b90e93@windsurf \
    --to=thomas.petazzoni@bootlin.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