[gentoo-dev] testing software: reporting compiler warnings?

[gentoo-dev] testing software: reporting compiler warnings?

[Gerold Strobel]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi

I'm using the ~x86 portage tree and emerge every new package as soon as it is 
available.
Some times is watch gcc work and occasionally see some compiler warnings 
(unused variables, missing function definitions,...)

- From my own little experience in C and C++ I know that a warning can turn into 
a full blown error sometimes.

Would it be of any use to report the warnings to the developers or will they 
ignore it as they may have ignored them when compiling the software 
themselves?

How should I report the warnings? Via bugs.gentoo.org or directly to the 
software developers?

Is there an easy way to collect all warnings in a file when doing an 'emerge 
- -u world'?

- -- 



~~~~~~~~~~~~~~~

Gerold Strobel
~~~~~~~~~~~~~~~
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (GNU/Linux)

iD8DBQE/3ITQeiAAHmcDbIERAhwDAKDf+nGcDp9DAIkW7VIbXdntwx14pgCfdwAR
H71e1xZev/QzxFSYamwu4YI=
=aq1L
-----END PGP SIGNATURE-----


--
gentoo-dev@gentoo.org mailing list

Re: [gentoo-dev] testing software: reporting compiler warnings?

[Paul de Vrieze]

[-- Attachment #1: signed data --]
[-- Type: text/plain, Size: 1144 bytes --]

On Sunday 14 December 2003 16:42, Gerold Strobel wrote:
> From my own little experience in C and C++ I know that a warning can turn
> into a full blown error sometimes.

That depends very much on the nature of the cause, but it is true that in 
general warnings should be avoided. However many are caused by various 
compiler changes, so originally correct code may cause warnings.

> Would it be of any use to report the warnings to the developers or will
> they ignore it as they may have ignored them when compiling the software
> themselves?

I think that depends on the developers. However there are very many different 
compiler/glibc/arch/other dependency combinations so there is a good chance 
that what compiled clean for the developers doesn't for you. In that case 
they might want to see the warnings.

> How should I report the warnings? Via bugs.gentoo.org or directly to the
> software developers?

Well, I don't think that many ebuild developers are even a bit interested in 
compiler warnings. 

Paul

-- 
Paul de Vrieze
Gentoo Developer
Mail: pauldv@gentoo.org
Homepage: http://www.devrieze.net

[-- Attachment #2: signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

Re: [gentoo-dev] testing software: reporting compiler warnings?

[John Nilsson]

[-- Attachment #1: Type: text/plain, Size: 201 bytes --]

On 12/14/03 16:42:08, Gerold Strobel wrote:

> How should I report the warnings? Via bugs.gentoo.org or directly to
> the
> software developers?

Send a patch to fix the warnings upstream.
/John

[-- Attachment #2: Type: application/pgp-signature, Size: 481 bytes --]

Re: [gentoo-dev] testing software: reporting compiler warnings?

[Renat Golubchyk]

Hi!

On Sunday 14 December 2003 16:42, Gerold Strobel wrote:
>
> Is there an easy way to collect all warnings in a file when doing an
> 'emerge -u world'?

Set PORT_LOGDIR in your make.conf and the output of emerge will be logged.


Cheers,
Renat


--
gentoo-dev@gentoo.org mailing list

Re: [gentoo-dev] testing software: reporting compiler warnings?

[Aron Griffis]

[-- Attachment #1: Type: text/plain, Size: 635 bytes --]

Gerold Strobel wrote:	[Sun Dec 14 2003, 10:42:08AM EST]
> How should I report the warnings? Via bugs.gentoo.org or directly to
> the software developers?

Please be careful when reporting directly to software developers.  Keep
your CFLAGS to a minimum since upstream developers don't like getting
reports from Gentoo users who are over-optimizing.

When reporting warnings as a bug to upstream developers, it's far better
to include a patch since most are easily fixable.

Aron

-- 
Aron Griffis
Gentoo Linux Developer (alpha / ia64 / ruby / vim)
Key fingerprint = E3B6 8734 C2D6 B5E5 AE76  FB3A 26B1 C5E3 2010 4EB0


[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]