From: Thomas Mueller <thomas@chaschperli.ch>
To: ceph-devel@vger.kernel.org
Subject: Re: compiler warnings on centos5
Date: Fri, 6 Aug 2010 12:00:57 +0000 (UTC) [thread overview]
Message-ID: <i3gthp$56v$2@dough.gmane.org> (raw)
In-Reply-To: AANLkTi=uegGEfjXw_DpfshdArsjQjk=sOv8DJ0-TF5be@mail.gmail.com
Am Thu, 05 Aug 2010 10:02:15 -0700 schrieb Gregory Farnum:
> Thomas:
> We're certainly interested in keeping the Ceph compile warning-free.
> However, these errors are pretty annoying to work around and are bogus
> enough to not be present in newer versions of gcc (it's the compiler,
> not the system). Can you upgrade your compiler? -Greg
>
I found out that Centos5 actually provides a gcc44 and gcc44-c++ package.
Compiling with those doesn't show the wanrings.
symlinking g++44 and gcc44 to /usr/local/(gcc|g++) works.
calling configure with the custom paths for gcc and g++ doesn't:
CC=/usr/bin/gcc44 CXX=/usr/bin/g++44 ./configure --prefix=/usr
...
checking for atomic_ops.h... yes
checking for dirent.h that defines DIR... yes
checking for library containing opendir... none required
checking for ANSI C header files... (cached) yes
checking for sys/wait.h that is POSIX.1 compatible... yes
checking boost/spirit.hpp usability... no
checking boost/spirit.hpp presence... no
checking for boost/spirit.hpp... no
configure: error: Sorry you need to install the Boost spirit parser
library (libboost-dev on debian)
- Thomas
next prev parent reply other threads:[~2010-08-06 12:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-05 9:49 compiler warnings on centos5 Thomas Mueller
2010-08-05 17:02 ` Gregory Farnum
2010-08-06 12:00 ` Thomas Mueller [this message]
2010-08-06 16:25 ` Gregory Farnum
2010-08-07 10:54 ` Thomas Mueller
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='i3gthp$56v$2@dough.gmane.org' \
--to=thomas@chaschperli.ch \
--cc=ceph-devel@vger.kernel.org \
/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.