[Bug 221029] AMD Ryzen: strange compilation failures using poudriere or plain buildkernel/buildworld

bugzilla-noreply at freebsd.org bugzilla-noreply at freebsd.org
Tue Aug 1 00:31:34 UTC 2017


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

--- Comment #36 from Don Lewis <truckman at FreeBSD.org> ---
I finally had a chance to do another poudriere run.  I saw three failures:

  * gnucash - guild segmentation fault

  * go - entersyscall inconsistent 0xc4207acea8 [0xc4207ac000,0xc4207ae000]

  * thunderbird - some clang segmentation faults plus:

cc -fno-strict-aliasing -O2 -pipe -fstack-protector -fno-strict-aliasing
-DNDEBUG -D_GLIBCXX_USE_C99 -D_GLIBCXX_USE_C99_MATH_TR1
-D_DECLARE_C99_LDBL_MATH -DLIBICONV_PLUG -isystem /usr/local/include -fPIC
-DPSUTIL_VERSION=311 -I/usr/local/include/python2.7 -c psutil/_psutil_bsd.c -o
build/temp.freebsd-12.0-CURRENT-amd64-2.7/psutil/_psutil_bsd.o
psutil/_psutil_bsd.c:958:39: error: no member named 'xt_tp' in 'struct xtcpcb'
        tp = &((struct xtcpcb *)xig)->xt_tp;
              ~~~~~~~~~~~~~~~~~~~~~~  ^
psutil/_psutil_bsd.c:959:13: warning: incompatible pointer types assigning to
'struct inpcb *' from 'struct xinpcb *' [-Wincompatible-pointer-types]
        inp = &((struct xtcpcb *)xig)->xt_inp;
            ^ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
psutil/_psutil_bsd.c:960:39: error: no member named 'xt_socket' in 'struct
xtcpc
b'
        so = &((struct xtcpcb *)xig)->xt_socket;
              ~~~~~~~~~~~~~~~~~~~~~~  ^
psutil/_psutil_bsd.c:969:33: error: incomplete definition of type 'struct
inpcb'
                    AF_INET, inp->inp_lport, &inp->inp_laddr,
                             ~~~^
/usr/include/netinet/in_pcb.h:65:22: note: forward declaration of 'struct
inpcb' LIST_HEAD(inpcbhead, inpcb);

[SNIP]

All three ports built sucessfully when I retried them.

No rename errors, though I had inadvertently disabled tmpfs for this run.

I'm running 12.0-CURRENT #53 r321732M with my pending sharedpage patch.

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


More information about the freebsd-bugs mailing list