[Bug 212868] devel/binutils 2.27 broken for powerpc64 (and powerpc?)

[bugzilla-noreply at freebsd.org]

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

            Bug ID: 212868
           Summary: devel/binutils 2.27 broken for powerpc64 (and
                    powerpc?)
           Product: Ports & Packages
           Version: Latest
          Hardware: Any
                OS: Any
            Status: New
          Severity: Affects Only Me
          Priority: ---
         Component: Individual Port(s)
          Assignee: bapt at FreeBSD.org
          Reporter: markmi at dsl-only.net
          Assignee: bapt at FreeBSD.org
             Flags: maintainer-feedback?(bapt at FreeBSD.org)

This mostly is copying list reports into bugzilla.

[I wonder if the various(?) binutil port(s) that are 2.27 based now and can
target powerpc64/powerpc should be marked broken for powerpc64/powerpc until
this is figured out. Any ports that are only for targeting powerpc64 or powerpc
probably should not be at 2.27 at this point.]



The below forward from freebsd-pcc's list confirms that binutils 2.27 not
working for powerpc64 (& powerpc?) contexts.

Note: Krzysztof Parzyszek is one of the two people that have recently been
working on updating clang/llvm for fixing some of the issues that block FreeBSD
from using clang for powerpc and powerpc64 for buildworld and buildkernel.

===
Mark Millard
markmi at dsl-only.net

On 2016-Sep-20, at 11:19 AM, Krzysztof Parzyszek <kristof at swissmail.org>
wrote:

I've had similar problems after building gcc-4.8.  After reverting back to
binutils 2.25 and rebuilding, it worked fine.

-Krzysztof

On 9/9/2016 11:32 AM, Bill Sorenson wrote:
Everything I've built with the new binutils using either GCC 4.9, 5.4 or
6.2 instantly dumps when run. This is on an Xserve G5. Is this just me or
is there something genuinely broken here?

Thanks,
Bill

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