[PATCHES] Re: Remarks about the building process

[John Mandereau]

On 2008/11/05 20:57 +0100, Jean-Charles Malahieude wrote:
> Some nitpicks during the building process, on a fresh repository:
> 
> 
> 1- the configure script:
> For a long time now, I always get this:
> 
> configure: WARNING: autoconf <= 2.59 with g++ >= 3.3 gettext test broken.
> configure: WARNING: Trying gcc, cross fingers.
> 
> It does not break anything;  it is just boring since:
> 
> # autoconf --version
> autoconf (GNU Autoconf) 2.61
> 
> # g++ --version
> g++ (GCC) 4.3.0 20080428 (Red Hat 4.3.0-8)
>
> I consider this kind of thing might even become "dangerous":
> as we say in French: " A force de crier au loup..." (after having yelled 
> so often at the wolf...)

It looks like the wolf has been killed, the second attached patch works
for me; is it OK to apply it to master?  I don't know whether autoconf
2.60 gettext/g++ test has been fixed, I assumed it's not for the sake of
safety.


> 2- The make stage:
> 
> I don't report  this kind of warnings:
>   conversion to 'xx' from 'yy' may alter its value
> or
>   part-combine-iterator.cc:22: warning: 'typedef' was ignored in this 
> declaration
> 
> 
> but those ones just bother me, since I am unable to analyze what is 
> going on:

> I truly hope someone understands my questioning.

My zen answer is
http://www.nojhan.net/geekscottes/index.php?strip=7

Quick translation for non-French readers:
— What comes after death do you think?
— I believe you are reincarned in a world where all GNU software
compiles with no warning.
— Would it happen because you've been good or you've been nasty?

See also the other attached patch.

Cheers,
John

fix-lily-cc-warnings.diff
Description: Text Data

configure-gettext-warning-fix.diff
Description: Text Data