From: Matt Benjamin <mbenjamin@redhat.com>
To: Willem Jan Withagen <wjw@digiware.nl>
Cc: Ceph Development <ceph-devel@vger.kernel.org>
Subject: Re: Has rgw recently switched to deque usuage??
Date: Sat, 20 Feb 2016 19:13:35 -0500 (EST) [thread overview]
Message-ID: <1135436239.44164632.1456013615024.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <56C8E590.7090609@digiware.nl>
Hi Willem,
That's good news, but massive header re-ordering sounds suspicious. Likely, there are just missing unix headers.
Matt
----- Original Message -----
> From: "Willem Jan Withagen" <wjw@digiware.nl>
> To: "Matt Benjamin" <mbenjamin@redhat.com>
> Cc: "Ceph Development" <ceph-devel@vger.kernel.org>
> Sent: Saturday, February 20, 2016 5:15:44 PM
> Subject: Re: Has rgw recently switched to deque usuage??
>
> On 20-2-2016 22:33, Matt Benjamin wrote:
> > Hi Willem,
> >
> > A number of new features have merged, sure, and they make use of new
> > primitives. I haven't compiled with clang recently, mainly due to
> > issues linking with gcc-compiled leveldb and rocksdb on Linux
> > platforms. For now, maybe you can send more specific info.
> >
> > (I'll be able to try-build on FreeBSD at some point, probably, but
> > not in the next day or so due to travel.)
>
> Hi Matt,
>
> It turns out to be all about the order of includes and that Clang not
> always sees eye to eye with GCC.
> Right now I'm sort of reordering a lot includes rados/rgw headers in the
> rgw/*cc files.
> Probably too much reordering but first I want it to get it to compile.
> :) After that lets see what was really needed.
>
> Save travels,
> --WjW
>
> > Matt
> >
> > ----- Original Message -----
> >> From: "Willem Jan Withagen" <wjw@digiware.nl> To: "Ceph
> >> Development" <ceph-devel@vger.kernel.org> Sent: Saturday, February
> >> 20, 2016 9:41:45 AM Subject: Has rgw recently switched to deque
> >> usuage??
> >>
> >> Hi,
> >>
> >> With the last rebase I'm getting compilation errors on rgw stuff.
> >> So I was wondering if deque usuage got included recently, or that
> >> I'm running into a case where Clang doesn't like the way some code
> >> is used. And GCC just compiles fine...
> >>
> >> Any answer would be appriciated
> >>
> >> --WjW -- To unsubscribe from this list: send the line "unsubscribe
> >> ceph-devel" in the body of a message to majordomo@vger.kernel.org
> >> More majordomo info at http://vger.kernel.org/majordomo-info.html
> >>
> >
>
>
--
--
Matt Benjamin
Red Hat, Inc.
315 West Huron Street, Suite 140A
Ann Arbor, Michigan 48103
http://www.redhat.com/en/technologies/storage
tel. 734-707-0660
fax. 734-769-8938
cel. 734-216-5309
next prev parent reply other threads:[~2016-02-21 0:13 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-20 14:41 Has rgw recently switched to deque usuage?? Willem Jan Withagen
2016-02-20 21:33 ` Matt Benjamin
2016-02-20 22:15 ` Willem Jan Withagen
2016-02-21 0:13 ` Matt Benjamin [this message]
2016-02-21 0:49 ` Willem Jan Withagen
2016-02-21 10:46 ` Willem Jan Withagen
2016-02-21 11:00 ` Matt Benjamin
2016-02-21 13:18 ` Willem Jan Withagen
2016-02-22 15:12 ` RGW include modifications to compile with Clang Willem Jan Withagen
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=1135436239.44164632.1456013615024.JavaMail.zimbra@redhat.com \
--to=mbenjamin@redhat.com \
--cc=ceph-devel@vger.kernel.org \
--cc=wjw@digiware.nl \
/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