Hi there,
I'm sorry, I didn't receive your previous mails about this bug.
FWIW, your patch appears to enable -latomic only for mips, mipsel, m68k.
Some guidance here: it is always correct to link using libatomic on any
glibc architecture. It is non-glibc architectures that may not have
libatomic
Hi,
> In other words, it seems that there may be another better solution.
>
> Step 1. check specific platform really requires -latomic in configure.ac
> Step 2. apply -latomic in Makefile.am (like as your proposed patch does)
>
I've attached patch to fix this issue.
It seems that it's ok for mi
On Tue, 12 Jan 2016 20:39:17 -0800 Steve Langasek
wrote:
> In Ubuntu, we've fixed this slightly differently than with the proposed
> patch, by instead providing -latomic in the upstream Makefile.am. This
> seems a little closer to upstreamable for this (upstream) bug, although
> there will be
`GRN_ATOMIC_ADD_EX'
Message-Id: <20160114001118.a6bce642dc7566c94405a...@clear-code.com>
X-Mailer: Sylpheed 3.5.0 (GTK+ 2.24.29; x86_64-unknown-linux-gnu)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Currently, I'm requesting access to porterbox to
Package: groonga
Version: 5.1.1-1
Followup-For: Bug #770243
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu xenial ubuntu-patch
Hello,
I can confirm that the reason for the build failure on other architectures
is that the software is not linking against libatomic, which is required fo
On Fri, 27 Feb 2015 16:39:44 + Dejan Latinovic
wrote:
>
>
> Hi,
>
> I had tested these changes.
>
> +# elif defined(__ATOMIC_SEQ_CST) /* GCC atomic builtins */
> +# define GRN_ATOMIC_ADD_EX(p,i,r) \
> + (r = __atomic_fetch_add(p, i, __ATOMIC_SEQ_CST))
>
> It solves issue:
> > ../../lib/.libs
Hi,
I had tested these changes.
+# elif defined(__ATOMIC_SEQ_CST) /* GCC atomic builtins */
+# define GRN_ATOMIC_ADD_EX(p,i,r) \
+ (r = __atomic_fetch_add(p, i, __ATOMIC_SEQ_CST))
It solves issue:
> ../../lib/.libs/libgroonga.so: undefined reference to `GRN_ATOMIC_ADD_EX'
Functions __ato
Hi,
Thank you for your patch.
It may work, but I don't know whether all test pass or not.
In the upstream version, it use __atomic_fetch_add to solve issue instead.
+# elif defined(__ATOMIC_SEQ_CST) /* GCC atomic builtins */
+# define GRN_ATOMIC_ADD_EX(p,i,r) \
+ (r = __atomic_fetch_add(p, i,
On Mon, 15 Dec 2014 15:03:44 +0900 HAYASHI Kentaro
wrote:
>
> Hi,
>
> At least, armhf platform will be supported in Groonga 4.0.8 or later.
> As I could use porterbox on ipa, it was confirmed that FTBFS issue is solved
> on testing or unstable.
> (Sadly, I can't build Groonga on wheezy yet.)
>
>
Hi,
At least, armhf platform will be supported in Groonga 4.0.8 or later.
As I could use porterbox on ipa, it was confirmed that FTBFS issue is solved on
testing or unstable.
(Sadly, I can't build Groonga on wheezy yet.)
I'm working on updating Groonga on unstable, but it needs some work to be
Control: severity -1 important
On 2014-11-20 09:14:28, Nobuhiro Iwamatsu wrote:
> Source: groonga
> Version: 4.0.6.1-2
> Severity: serious
> Tags: jessie sid
> Justification: FTBFS on arm64, armel, armhf, mips and other
>
> Dear Maintainer,
>
> groonga FTBFS on arm64, armel, armhf, mips and othe
Source: groonga
Version: 4.0.6.1-2
Severity: serious
Tags: jessie sid
Justification: FTBFS on arm64, armel, armhf, mips and other
Dear Maintainer,
groonga FTBFS on arm64, armel, armhf, mips and other.
arm64:
https://buildd.debian.org/status/fetch.php?pkg=groonga&arch=arm64&ver=4.0.6.1-2&stamp=1
12 matches
Mail list logo
