Bug 434394 - lilypond failed massrebuild attempt for GCC 4.3
Summary: lilypond failed massrebuild attempt for GCC 4.3
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: lilypond
Version: 9
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Gwyn Ciesla
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
: 440826 (view as bug list)
Depends On: 449273
Blocks: gcc43errors
TreeView+ depends on / blocked
 
Reported: 2008-02-22 16:08 UTC by Jesse Keating
Modified: 2013-01-10 03:10 UTC (History)
4 users (show)

Fixed In Version: rawhide
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2008-09-08 18:39:55 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Jesse Keating 2008-02-22 16:08:25 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=443752
Exit code was 1, check the build.log for the failed buildArch task.

Comment 1 Jon Stanley 2008-03-01 20:13:44 UTC
scratch build 482723

Comment 2 Jon Stanley 2008-03-01 21:33:44 UTC
                 from file-name.cc:10:
./include/std-vector.hh:260: error: 'string' was not declared in this scope
./include/std-vector.hh:260: error: template argument 1 is invalid
./include/std-vector.hh:260: error: template argument 2 is invalid
./include/std-vector.hh:260: error: invalid type in declaration before '(' token
./include/std-vector.hh:260: error: 'string' was not declared in this scope
./include/std-vector.hh:260: error: expected primary-expression before 'char'
./include/std-vector.hh:260: error: initializer expression list treated as
compound expression


Comment 3 Christopher Aillon 2008-04-19 05:05:46 UTC
Above is fixed in CVS.  However, a new error:

http://koji.fedoraproject.org/koji/taskinfo?taskID=573260

MFINPUTS=. mftrace --encoding ./out/feta11.enc --no-afm -I . -I ./out/
--formats=pfa,pfb,svg feta11
mftrace 1.2.14
Font `feta11'...
Warning: no extra font information for this font.
Consider writing a XX_guess_font_info() routine.
Using encoding file: `/builddir/build/BUILD/lilypond-2.10.33/mf/out/feta11.enc'
Running Metafont...
warning: mf: command exited with value 32512 (ignored) 
Metafont failed.  Excerpt from the log file: 
*****
Traceback (most recent call last):
  File "/usr/bin/mftrace", line 1412, in <module>
    main()
  File "/usr/bin/mftrace", line 1408, in main
    do_file (filename)
  File "/usr/bin/mftrace", line 1382, in do_file
    base = gen_pixel_font (basename, metric, options.magnification)
  File "/usr/bin/mftrace", line 928, in gen_pixel_font
    start = m.start (0)
AttributeError: 'NoneType' object has no attribute 'start'


Comment 4 Bug Zapper 2008-05-14 05:31:44 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 5 Hans Ulrich Niedermann 2008-06-01 14:54:28 UTC
This looks like a bug in metafont to me. I have filed it at
https://bugzilla.redhat.com/show_bug.cgi?id=449273


Comment 6 Gwyn Ciesla 2008-08-27 14:58:35 UTC
*** Bug 440826 has been marked as a duplicate of this bug. ***

Comment 7 FTBFS 2008-09-05 16:13:02 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 8 Gwyn Ciesla 2008-09-05 16:19:24 UTC
Requested assistance on fedora-devel.  I am working on this currently.

Comment 9 Gwyn Ciesla 2008-09-08 18:39:12 UTC
Fixed.
http://koji.fedoraproject.org/koji/buildinfo?buildID=62194


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