Date: Mon, 29 Aug 2016 11:02:07 -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: <67E84707-3267-49F3-8DB6-13CBD05B1690@gmail.com> In-Reply-To: <31f11ba3-ca29-0f85-f1c1-6a3cd467bb57@FreeBSD.org> 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>
index | next in thread | previous in thread | raw e-mail
[-- Attachment #1 --] > 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. Thanks, -Ngie [-- Attachment #2 --] -----BEGIN PGP SIGNATURE----- Comment: GPGTools - https://gpgtools.org iQIcBAEBCgAGBQJXxHigAAoJEPWDqSZpMIYV8HQQAKwMZZ4aIQoeRE7hN33rmE3R Cp5N7NSfqleb+LIInTnfBUQSBenU4pqQmNHJxYBexPTR9WgeYYXaO0kxXNnJ1H5g x731TPWUr1KzhIz0B5BOcLpAcB72DfKho7XeHJDeEH/dOiuIMu1WRA83d8BvU0Ej LVO3BzVhSMmnJNav3FI6TSAL7kczOgiEPJLhYBDjY6k5lFDjURx+ZoA7WK9i/aUR Jjy/nAlY69COU5ffOe7RBQLdYFh2DiSu5LxSqOjXCniuLvFa32m23m8Go8khsPE/ eqOt9RuYDxTLQQ4DSceZ7wmtxOjjs/bd3BaCh6Hj4crnr/J81ISACOiO2a1zxLrz YCzNYYsR5wFDU3gUynN+CWUpap3Dyi9wkGYnnoX/lwcYmy89rvzdrimfkg/9qPFX pdYd24/piUtUxIVnLvPzZ82/imH2HjKWu/0zDZ8HMBCxfr7sjMj1RaRbWbF3ImUr 26k3cUEpI5Uc9/FxPRgC8M/ruI4LL2dRk18qLc/np8qykhY5FMrYRQ2gT5wzYjdt ZklgiXzZzEuQYSWHFXq/SSfWYOhh52UbiR0jQadLIL31sx241OkWkp19iA9Y4BIO 2fgdGcnq9zPZftrH0lVQb5usynD9CQDEIAHfaEcaMlhunQ5gEk066y2B/pec6uWD l2t3vplp4D1gfI8ytWzI =hOu3 -----END PGP SIGNATURE-----home | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?67E84707-3267-49F3-8DB6-13CBD05B1690>