Bug 434007 - brutus-keyring failed massrebuild attempt for GCC 4.3
Summary: brutus-keyring failed massrebuild attempt for GCC 4.3
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: brutus-keyring
Version: 9
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Brian Pepple
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: gcc43errors
TreeView+ depends on / blocked
 
Reported: 2008-02-22 12:54 UTC by Jesse Keating
Modified: 2013-01-10 02:48 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2008-09-06 00:27:23 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Jesse Keating 2008-02-22 12:54:59 UTC
This is an automatically filed bug for a failed rebuild attempt for GCC 4.3.

http://fedoraproject.org/wiki/JesseKeating/gcc43MassRebuildProposal

Please verify why this build failed and fix it.
http://koji.fedoraproject.org/koji/taskinfo?taskID=436880
Exit code was 1, check the build.log for the failed buildArch task.

Comment 1 Jon Stanley 2008-02-23 19:22:13 UTC
cc1: warnings being treated as errors
main.c: In function 'main':
main.c:443: error: the address of 'ev' will always evaluate as 'true'
main.c:453: error: the address of 'ev' will always evaluate as 'true'
main.c:459: error: the address of 'ev' will always evaluate as 'true'
main.c:465: error: the address of 'ev' will always evaluate as 'true'
main.c:471: error: the address of 'ev' will always evaluate as 'true'
main.c:479: error: the address of 'ev' will always evaluate as 'true'
main.c:508: error: the address of 'ev' will always evaluate as 'true'
main.c:517: error: the address of 'ev' will always evaluate as 'true'
main.c:523: error: the address of 'ev' will always evaluate as 'true'
main.c:529: error: the address of 'ev' will always evaluate as 'true'
main.c:535: error: the address of 'ev' will always evaluate as 'true'
main.c:543: error: the address of 'ev' will always evaluate as 'true'
main.c:548: error: the address of 'ev' will always evaluate as 'true'
make[4]: *** [main.o] Error 1
make[4]: Leaving directory `/builddir/build/BUILD/brutus-keyring-0.9.0/src'
make[3]: *** [all-recursive] Error 1
make[3]: Leaving directory `/builddir/build/BUILD/brutus-keyring-0.9.0/src'
make[2]: *** [all] Error 2
make[2]: Leaving directory `/builddir/build/BUILD/brutus-keyring-0.9.0/src'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/builddir/build/BUILD/brutus-keyring-0.9.0'
make: *** [all] Error 2
error: Bad exit status from /var/tmp/rpm-tmp.42915 (%build)


Comment 2 Jules Colding 2008-02-25 08:00:06 UTC
I strongly believe that all of these warnings are fixed upstream (svn trunk).

Comment 3 Brian Pepple 2008-02-25 15:30:22 UTC
(In reply to comment #2)
> I strongly believe that all of these warnings are fixed upstream (svn trunk).

I'm out of town on vacation, and once I'm back I'll grab the latest trunk.

Comment 4 Jules Colding 2008-02-25 17:02:38 UTC
OK, please yell at me if it still misbehaves :-)


Comment 5 Bug Zapper 2008-05-14 05:22:53 UTC
Changing version to '9' as part of upcoming Fedora 9 GA.
More information and reason for this action is here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 6 FTBFS 2008-09-05 16:10:17 UTC
This package has Failed to Build From Source for many months.  Per
http://fedoraproject.org/wiki/FTBFS, this package is now proposed for
removal from the distribution.  Please address this FTBFS bug
immediately, or this package will be removed from the distribution
within the next few weeks.

Thank you for your continued contributions to Fedora, and your
commitment to ensuring Fedora packages remain buildable from source
code.

Comment 7 Jules Colding 2008-09-05 17:58:46 UTC
brutus-keyring is at 0.9.30 so this copy is ancient. Please, please update from upstream?

Thanks,
  jules

Comment 8 Jules Colding 2008-09-05 18:27:07 UTC
There are also fresh rawhide RPMs here:

http://www.42tools.com/sites/default/files/downloads/dist/brutus-keyring/Rawhide/

Thanks,
  jules


Note You need to log in before you can comment on or make changes to this bug.