Bug 434421 – gprolog failed massrebuild attempt for GCC 4.3

Bug 434421 - gprolog failed massrebuild attempt for GCC 4.3

Summary:	gprolog failed massrebuild attempt for GCC 4.3

Status:	CLOSED NEXTRELEASE

Aliases:	None

Product:	Fedora
Classification:	Fedora
Component:	gprolog (Show other bugs)
Sub Component:
Version:	9
Hardware:	All Linux

Priority	medium Severity medium
Target Milestone:	---
Target Release:	---
Assigned To:	Jochen Schmitt
QA Contact:	Fedora Extras Quality Assurance
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:	gcc43errors
	Show dependency tree / graph

Reported:	2008-02-22 11:22 EST by Jesse Keating
Modified:	2013-01-09 22:12 EST (History)
CC List:	1 user (show)

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2008-06-15 16:36:37 EDT
Type:	---
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Groups: None (edit)

Description Jesse Keating 2008-02-22 11:22:21 EST

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=444644
Exit code was 1, check the build.log for the failed buildArch task.

Comment 1 Tyler Owen 2008-02-23 21:32:56 EST

Error compiling x86_64

Comment 2 Jochen Schmitt 2008-02-25 10:54:48 EST

I have forwarded the issue to the upstream author, but he has asked for an
x86_64 system on which he can reproduced this issue.

Comment 3 Bug Zapper 2008-05-14 01:32:46 EDT

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 4 Jochen Schmitt 2008-06-15 16:36:37 EDT

This bug may be closed, becouse it's a dupe of #440945

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