All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gregory Farnum <gregory.farnum@dreamhost.com>
To: ceph-devel@vger.kernel.org, Laszlo Boszormenyi <gcs@debian.hu>
Subject: Re: building Ceph on various architectures
Date: Sun, 27 Feb 2011 19:42:24 -0800	[thread overview]
Message-ID: <ACE7B038C1A34D9A88CDFFDBABDA2D87@gmail.com> (raw)
In-Reply-To: <E3D560F92CD249D4B2D590A54614CA08@gmail.com>

On Saturday, February 26, 2011 at 11:52 AM, Gregory Farnum wrote:
On Saturday, February 26, 2011 at 11:40 AM, Laszlo Boszormenyi wrote: 
> > On Sat, 2011-02-26 at 10:28 -0800, Gregory Farnum wrote:
> > > This looks like an error that came up (and got fixed) on Ubuntu several months ago:
> > > https://bugs.launchpad.net/ubuntu/+source/ceph/+bug/635388
> >  Yes, it looks similar. But please note two things. The counterpart of
> > #635388 in Ubuntu is #597193 [1] in Debian. It was fixed on the 20th of
> > September, last year. Also, that bugs was:
> > 'AO_fetch_and_sub1_write' was not declared in this scope
> > Compared to this one:
> > 'AO_fetch_and_add_write' was not declared in this scope
> > 
> > I don't say it completely different, but doesn't look the exact same.
> 
> Ah, I didn't notice that -- I'll look into it more closely! 
>  I looked at this a bit more and there's nothing really obvious jumping out at me, but I do have a few observations/questions: 
1) It looks to me like this is the same error of definitions as previously. AO_fetch_and_sub1_write, AO_fetch_and_add_write, etc are in both bugs. (This is to be expected, since the most probable cause of atomic-ops issues are problems with definition chaining.)
2) I notice that this is in the compile output: "Kernel: Linux 2.6.31-rc9 armel (armv5tel)"
Does that mean it's building on an arm v5 machine?
I wonder if maybe there's an issue there -- my knowledge of the ARM architecture is extremely limited (basically just tracking issues like this down) but from what I've read there were some changes which could account for a bug like this. Notably, atomic-ops for arm depends on the "__arm__" preprocessor variable being defined, which I'd expect to be defined for any version but maybe isn't.

So, does anybody out there have more experience with ARM or the atomic-ops package? I can email the atomic-ops people but I'd like to make sure we aren't doing something odd ourselves!
-Greg




  reply	other threads:[~2011-02-28  3:42 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-26 11:41 building Ceph on various architectures Laszlo Boszormenyi
2011-02-26 18:28 ` Gregory Farnum
2011-02-26 19:40   ` Laszlo Boszormenyi
2011-02-26 19:52     ` Gregory Farnum
2011-02-28  3:42       ` Gregory Farnum [this message]
2011-02-28  6:23         ` Laszlo Boszormenyi
2011-03-14 19:03 ` Tommi Virtanen

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=ACE7B038C1A34D9A88CDFFDBABDA2D87@gmail.com \
    --to=gregory.farnum@dreamhost.com \
    --cc=ceph-devel@vger.kernel.org \
    --cc=gcs@debian.hu \
    /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.