compiler warnings on centos5

compiler warnings on centos5

[Thomas Mueller]

hi

altough my tests are running ok on centos5  there a lots of compiler 
warnings:

http://chaschperli.ch/testing/viewBuildError.php?type=1&buildid=149

I do not seem them on debian.

this is with ceph.git/unstable.

- Thomas

Re: compiler warnings on centos5

[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

On Thu, Aug 5, 2010 at 2:49 AM, Thomas Mueller <thomas@chaschperli.ch> wrote:
> hi
>
> altough my tests are running ok on centos5  there a lots of compiler
> warnings:
>
> http://chaschperli.ch/testing/viewBuildError.php?type=1&buildid=149
>
> I do not seem them on debian.
>
> this is with ceph.git/unstable.
>
> - Thomas
>
> --
> 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
>
--
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

Re: compiler warnings on centos5

[Thomas Mueller]

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

Re: compiler warnings on centos5

[Gregory Farnum]

On Fri, Aug 6, 2010 at 5:00 AM, Thomas Mueller <thomas@chaschperli.ch> wrote:
> 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)
Looks like a configuration issue since it can't find the Boost header
file. I imagine that by calling them directly you're losing some
include lines or something?

Re: compiler warnings on centos5

[Thomas Mueller]

On 06.08.2010 18:25, Gregory Farnum wrote:
> On Fri, Aug 6, 2010 at 5:00 AM, Thomas Mueller<thomas@chaschperli.ch>  wrote:
>> 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.

I just thought it would work. did not look at the configure output.

>>
>>
>> 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)
> Looks like a configuration issue since it can't find the Boost header
> file. I imagine that by calling them directly you're losing some
> include lines or something?


I think i finally located the problem, in config.log:


configure:20728: g++ -E  conftest.cc
In file included from /usr/include/boost/mpl/apply.hpp:23,
                  from /usr/include/boost/iterator/iterator_facade.hpp:34,
                  from /usr/include/boost/iterator/iterator_adaptor.hpp:15,
                  from /usr/include/boost/iterator_adaptors.hpp:8,
                  from 
/usr/include/boost/spirit/iterator/file_iterator.hpp:55,
                  from /usr/include/boost/spirit/iterator.hpp:21,
                  from /usr/include/boost/spirit.hpp:49,
                  from conftest.cc:30:
/usr/include/boost/mpl/apply_wrap.hpp:81:31: error: missing binary 
operator before token "("
/usr/include/boost/mpl/apply_wrap.hpp:173:31: error: missing binary 
operator before token "("

seems that the version of boost (1.33.1) in Centos5 does not compile 
with gcc 4.4.

- Thomas