Date: Mon, 29 Aug 2016 11:04:50 -0700 From: "Ngie Cooper (yaneurabeya)" <yaneurabeya@gmail.com> To: Bryan Drewery <bdrewery@FreeBSD.org> Cc: Li-Wen Hsu <lwhsu@FreeBSD.org>, "jenkins-admin@freebsd.org" <jenkins-admin@freebsd.org>, "freebsd-testing@freebsd.org" <freebsd-testing@freebsd.org>, Dimitry Andric <dim@FreeBSD.org> Subject: Re: Jenkins build is still unstable: FreeBSD_HEAD #564 Message-ID: <B014DD06-4BB2-4503-8908-C78EFEE0FCA2@gmail.com> In-Reply-To: <67E84707-3267-49F3-8DB6-13CBD05B1690@gmail.com> References: <1491374121.44.1472440150670.JavaMail.jenkins@jenkins-9.freebsd.org> <166099893.51.1472451061454.JavaMail.jenkins@jenkins-9.freebsd.org> <CAG=rPVdZp171Egp=OHWDc3qCgcJDE3HQ0rv-j=i%2BO1LHcfH%2BJQ@mail.gmail.com> <CFA236ED-7DE0-4BE1-B944-52284E2FB6E0@FreeBSD.org> <6E443BB8-0269-4812-A2F4-40AA303E69C6@FreeBSD.org> <CAG=rPVdfgoF0mts-edHATUaefD7YuGtNu5ZTJOa8efUn2W4QuA@mail.gmail.com> <8058052E-A09A-403E-828A-74B51ED4BBF4@FreeBSD.org> <20160829163911.GA51650@FreeBSD.cs.nctu.edu.tw> <E73154DF-6A88-457D-B1FF-6B7F7610C37F@FreeBSD.org> <4b8980f0-1a90-40d7-45b3-9569b321d1c6@FreeBSD.org> <20160829175247.GA10263@FreeBSD.cs.nctu.edu.tw> <CAA41D00-2451-42EC-B9FD-3E31F42F9CF6@gmail.com> <31f11ba3-ca29-0f85-f1c1-6a3cd467bb57@FreeBSD.org> <67E84707-3267-49F3-8DB6-13CBD05B1690@gmail.com>
index | next in thread | previous in thread | raw e-mail
[-- Attachment #1 --] > On Aug 29, 2016, at 11:02, Ngie Cooper (yaneurabeya) <yaneurabeya@gmail.com> wrote: > >> >> On Aug 29, 2016, at 11:00, Bryan Drewery <bdrewery@FreeBSD.org> wrote: >> >> On 8/29/2016 10:58 AM, Ngie Cooper (yaneurabeya) wrote: >>> (-bdrewery) >>> >>>> On Aug 29, 2016, at 10:52, Li-Wen Hsu <lwhsu@FreeBSD.org> wrote: >>>> >>>> I guess the quickest way is boot that VM, cd to >>>> /usr/tests/lib/atf/libatf-c++ and run `kyua test atf_c++_test` >>>> However I am not sure this provides enough information because stuff >>>> under /usr/tests/lib/atf/libatf-c++ are all binary files. >>>> >>>> FWIW, I would like to know, should these -target, --sysroot and -B flages be >>>> given when compiling a normal program in a normal time? In this test >>>> case, kyua just wanted to compile test.cpp which includes sstream, it's >>>> not during buildworld/buildkernel time, so files under /usr/obj >>>> should not be used. >>> >>> I’m actively working on this right now. If I can’t resolve it soon, I’ll file a bug, mark it as an expected failure, and we can work on fixing the issue with a bit more leisure. >>> >>> It’s not a cross-compiler problem — something changed recently (likely in clang/libc++) that’s causing this problem, and it might just be an existing bug that was triggered by that change.. >>> >> >> What changed recently is that buildworld now always uses --sysroot for >> Clang, and --sysroot,-isystem,-B,-L for GCC. > > Ok. I’m not fully convinced that that’s the problem yet. Will drill down into the issue in the next half hour and will post a bug with my findings. Oh wait. Damn… I see the --sysroot line in the compilation output from the test. Crap… that’s not going to work. Thanks, -Ngie [-- Attachment #2 --] -----BEGIN PGP SIGNATURE----- Comment: GPGTools - https://gpgtools.org iQIcBAEBCgAGBQJXxHlCAAoJEPWDqSZpMIYVN54P/0acdi9gHzvI+oWlVBGnnojg J+a9TrlC8+Du9qgCnvqWg4zirlPhfYsOklVOnDAQdz0LVH0NxdhyPGIrF6d6/6sP uKWG6CySiMbvKdJM0fDA6mx7IYBAjyXLx79berEnpgvIndA1F9iGkYhIFfLD0eUp qUXrgqau1bhQI3xh+kNdT6Z1DaHA6Oovcc38KW6X8hyHO/Tx7zzCZaQLcD+9F6BJ Z7zRHQRnSqNIxWA+ROOdADJEYbn0i898fTwPSMAnRwBecpokGod7OqY804aF0GdR zR6lv66J4TmL8h7xX2zXpP8/AtuxDuL9oB1vX28fpoooJ3IJ/zpgMJRGVlwkcS7b mucWHfwkJLUl9x/K5Hx7YOarxC66XFoIgmaLZS/SRtrKg3UlZiAih52n3N26vsvx 21sikPBQBXzwhtS+ThJR7U5+TCAJ0a9dKQyUZGcVByGVSzhny76h04v24/KFwbtd ZjBvbW/+CepKRRdcTkY4eHvsML9kWOU2z7mrPqvR1VrnzRGZPK/UYGZMeM5G8bO9 St5qLe/H6uvnEdzto/TrIX6Qy6zVAuU94NCRACAWIGNQ7Vv5qOVGaH7LErYE3pgF vwwDpqgHNmXnrQgIj9REOqZ75vddJre3JNbJgizJ69ofploF44MS9S47Gn1cZyzw LpKUMaUjDvttF54Fc5pG =WaJp -----END PGP SIGNATURE-----help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?B014DD06-4BB2-4503-8908-C78EFEE0FCA2>