Mailinglist Archive: opensuse-buildservice (262 mails)
| < Previous | Next > |
Re: [opensuse-buildservice] Does osc modify gcc build flags?
- From: Dave Plater <dave.plater@xxxxxxxxxxx>
- Date: Wed, 12 Aug 2009 13:51:29 +0200
- Message-id: <4A82ACC1.4090802@xxxxxxxxxxx>
On 08/12/2009 11:09 AM, Dominique Leuenberger wrote:
uninitialized" errors in the log but with osc build the errors are in
the log. This is using the same package and spec file.
Regards
Dave P
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse-buildservice+help@xxxxxxxxxxxx
When I use rpmbuild to build the package, I don't get any "is usedAre you refering to the initial checking of the result after the build wasI've used -O2 -Wall -Wextra and I still can't get the uninitializedOn 8/12/2009 at 11:05, Dave Plater <dave.plater@xxxxxxxxxxx> wrote:
variables to come up locally. Rpmbuild uses those switches by default,
it's still only osc which throws the "is used uninitialized" warning.
There must be something that osc does that plain rpmbuild doesn't.
Regards
Dave P
successful? Yes, there are many more checks run afterwards, called
brp-checks and rpmlint.
Most of them are heuristic analysis of the built rpms and the compiler
output. (especially the 'initialized variables' are just collected from the
compiler log and raised as warnings so they are not just missed in the huge
build logs.
Dominique
uninitialized" errors in the log but with osc build the errors are in
the log. This is using the same package and spec file.
Regards
Dave P
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse-buildservice+help@xxxxxxxxxxxx
| < Previous | Next > |