[Bug 199905] PCH bustage when building with GCC on -CURRENT kernel (fatal error: had to relocate PCH)

bugzilla-noreply at freebsd.org bugzilla-noreply at freebsd.org
Sun May 3 23:02:53 UTC 2015


https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=199905

            Bug ID: 199905
           Summary: PCH bustage when building with GCC on -CURRENT kernel
                    (fatal error: had to relocate PCH)
           Product: Ports & Packages
           Version: Latest
          Hardware: Any
                OS: Any
            Status: New
          Severity: Affects Only Me
          Priority: ---
         Component: Individual Port(s)
          Assignee: freebsd-ports-bugs at FreeBSD.org
          Reporter: jbeich at FreeBSD.org
                CC: amdmi3 at FreeBSD.org, feld at FreeBSD.org,
                    koalative at gmail.com, lightside at gmx.com,
                    portmgr at FreeBSD.org

pkg-fallout reports a number of broken ports with Host OSVERSION >= 1100066 due
to changes in 11.0-CURRENT kernel [1] that the package cluster hosts various
-RELEASE jails on. The issue can be worked around by disabling PCH [2] in the
affected ports. Maintainers of the broken ports are CC'd.

http://beefy1.isc.freebsd.org/data/93i386-default/385145/logs/assaultcube-1.2.0.2_3.log
http://beefy1.isc.freebsd.org/data/93i386-default/385145/logs/codeblocks-13.12_4.log
http://beefy1.isc.freebsd.org/data/93i386-default/385145/logs/evolvotron-0.6.3_2.log
http://beefy1.isc.freebsd.org/data/93i386-default/385145/logs/fracplanet-0.4.0_8.log
http://beefy1.isc.freebsd.org/data/93i386-default/385145/logs/last.fm-1.5.4.26862_5.log
http://beefy1.isc.freebsd.org/data/93i386-default/385145/logs/leocad-0.80.3_2.log
http://beefy1.isc.freebsd.org/data/93i386-default/385145/logs/murmur-1.2.8_1.log
http://beefy1.isc.freebsd.org/data/93i386-default/385145/logs/sigil-0.6.0_5.log

See also:
http://thread.gmane.org/gmane.os.freebsd.devel.cvs/523979 [1]
https://secure.freshbsd.org/search?project=freebsd-ports&q=PCH [2]

-- 
You are receiving this mail because:
You are the assignee for the bug.


More information about the freebsd-ports-bugs mailing list