[Bug 214456] lang/gcc6: -r424540: FreeBSD's WITH_DEBUG= and full bootstrap are incompatible and the build stops

[bugzilla-noreply at freebsd.org]

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

            Bug ID: 214456
           Summary: lang/gcc6: -r424540: FreeBSD's WITH_DEBUG= and full
                    bootstrap are incompatible and the build stops
           Product: Ports & Packages
           Version: Latest
          Hardware: Any
                OS: Any
            Status: New
          Severity: Affects Only Me
          Priority: ---
         Component: Individual Port(s)
          Assignee: gerald at FreeBSD.org
          Reporter: markmi at dsl-only.net
             Flags: maintainer-feedback?(gerald at FreeBSD.org)
          Assignee: gerald at FreeBSD.org

[This likely applies to some other lang/gcc* examples.]

On powerpc (head -r308247, so 12-CURRENT) I tried to build lang/gcc6 and it
failed at the comparison step (stage 3 vs. 2).

Looking at the mismatched .o's via objdump -x -d : stage 3 had built with debug
information present but stage 2 had not.

The /etc/make.conf had:

WITH_DEBUG=
WITH_DEBUG_FILES=

So to have a build with WITH_DEBUG= in use I had to turn off the full bootstrap
option.

Another way would be to not have WITH_DEBUG= but still have the full bootstrap.

But having both at the same time is broken.


Supporting notes:

I do not build the JAVA stuff so for powerpc64 I enable building lang/gcc6:

# svnlite diff /usr/ports/lang/gcc6
Index: /usr/ports/lang/gcc6/Makefile
===================================================================
--- /usr/ports/lang/gcc6/Makefile       (revision 424540)
+++ /usr/ports/lang/gcc6/Makefile       (working copy)
@@ -13,7 +13,7 @@
 LICENSE=       GPLv3 GPLv3RLE
 LICENSE_COMB=  multi

-BROKEN_powerpc64=      Does not build
+#BROKEN_powerpc64=     Does not build

 LIB_DEPENDS=   libgmp.so:math/gmp \
                libmpfr.so:math/mpfr \

I experiment with the broken/problematical clang 3.8.0 for targeting powerpc64
and powerpc and report specific problems to llvm for what blocks FreeBSD from
being able to use clang as a system compiler for those TARGET_ARCH's. For
example I use a modified kernel signal handling that includes a so-called "red
zone" on the stack to deal with clang's powerpc ABI stack-handling violations
in the code that it generates. (It allows me to find other issues without
waiting for the ABI fix.)

So my powerpc and powerpc64 contexts are not currently normal but are more like
what clang-based powerpc and powerpc64 environments would be like if/when clang
is sufficient for direct use by FreeBSD. (Workarounds and avoiding specific
issues being involved.)

An implication is that direct replication of what I've done would be odd: a
system-clang based build of lang/gcc6.

But I doubt that clang vs. gcc as the host compiler matters for the WITH_DEBUG=
build properties.

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