Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 30 Aug 2016 01:52:47 +0800
From:      Li-Wen Hsu <lwhsu@FreeBSD.org>
To:        Bryan Drewery <bdrewery@FreeBSD.org>
Cc:        Dimitry Andric <dim@FreeBSD.org>, Craig Rodrigues <rodrigc@freebsd.org>, "jenkins-admin@freebsd.org" <jenkins-admin@freebsd.org>, "freebsd-testing@freebsd.org" <freebsd-testing@freebsd.org>, jmmv@FreeBSD.org
Subject:   Re: Jenkins build is still unstable: FreeBSD_HEAD #564
Message-ID:  <20160829175247.GA10263@FreeBSD.cs.nctu.edu.tw>
In-Reply-To: <4b8980f0-1a90-40d7-45b3-9569b321d1c6@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>

next in thread | previous in thread | raw e-mail | index | archive | help

--PNTmBPCT7hxwcZjr
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

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.

On Mon, Aug 29, 2016 at 10:31:26 -0700, Bryan Drewery wrote:
> This thread is hard to follow. The changes I made shouldn't break
> anything since it's just now acting like an external compiler.
>=20
> Where is the error so I can debug it?
>=20
> On 8/29/2016 9:50 AM, Dimitry Andric wrote:
> > Yes, I've also seen the --sysroot options being added recently.  I'm re=
asonably sure that this is the cause of the error.  Bryan did most of the r=
estructuring for external toolchains, which also adds the --sysroot option.
> >=20
> > Is there an usr/include/c++/v1 under the --sysroot?
> >=20
> > -Dimitry
> >=20
> >> On 29 Aug 2016, at 18:39, Li-Wen Hsu <lwhsu@FreeBSD.org> wrote:
> >>
> >> Dimitry, are you talking about case lib.atf.libatf-c++.atf_c++_test.in=
clude ?
> >>
> >> I happen to have a r304986 VM here:
> >>
> >> https://people.freebsd.org/~lwhsu/tmp/disk-test.img.xz
> >>
> >> (it starts kyua test in /etc/rc.local, just use ctrl-c to interrupt it)
> >>
> >> And there is a /usr/include/c++/v1 directory with sstream in it.
> >>
> >>
> >> BTW, I am not sure removing -I/usr/include is the right solution,  I
> >> think this case is checking for "normal" compiling would work, not
> >> during buildworld.  When this case was passing, it uses following
> >> command:
> >>
> >> c++ -O2 -pipe -DHAVE_CONFIG_H -I/usr/include -Wall -Werror -o test.o -=
c test.cpp
> >>
> >> and now it uses:
> >>
> >> c++ -target x86_64-unknown-freebsd12.0 --sysroot=3D/usr/obj/usr/src/tm=
p -B/usr/obj/usr/src/tmp/usr/bin -O2 -pipe -DHAVE_CONFIG_H -I/usr/include -=
Wall -Werror -o test.o -c test.cpp
> >>
> >> This changed between r304555 and r304698.
> >>
> >>
> >> Also, does anyone know where is "-I/usr/include" coming from?  Is this
> >> one?
> >> https://svnweb.freebsd.org/base/head/contrib/atf/atf-c%2B%2B/detail/te=
st_helpers.cpp?view=3Dmarkup#l56
> >>
> >>
> >> Li-Wen
> >>
> >> On Mon, Aug 29, 2016 at 16:02:42 +0200, Dimitry Andric wrote:
> >>> Do you have an /usr/include/c++/v1 directory?  And is there a file ca=
lled "sstream" in it?
> >>>
> >>> If it is there, I think the problem is due to the -I/usr/include opti=
on in the command line for the test program.  If you remove that, I think t=
he compilation will work correctly.
> >>>
> >>> -Dimitry
> >>>
> >>>> On 29 Aug 2016, at 14:55, Craig Rodrigues <rodrigc@freebsd.org> wrot=
e:
> >>>>
> >>>> Dimitry,
> >>>>
> >>>> During the Jenkins job, I use installworld/installkernel to build a =
fully bootable bhyve virtual machine.
> >>>> After the virtual machine boots, ssh into it, and do:
> >>>>
> >>>> cd /usr/tests
> >>>> kyua test
> >>>> kyua report --verbose
> >>>>
> >>>>
> >>>> So I am suspecting that maybe something didn't get installed properl=
y?
> >>>> --
> >>>> Craig
> >>>>
> >>>>
> >>>> On Mon, Aug 29, 2016 at 4:13 AM, Dimitry Andric <dim@freebsd.org> wr=
ote:
> >>>> I just found the separate "test results" link in Jenkins.  As far as=
 I can see, one of those failing tests is run as:
> >>>>
> >>>> c++ -target x86_64-unknown-freebsd12.0 --sysroot=3D/builds/workspace=
/FreeBSD_HEAD/obj/builds/workspace/FreeBSD_HEAD/src/tmp -B/builds/workspace=
/FreeBSD_HEAD/obj/builds/workspace/FreeBSD_HEAD/src/tmp/usr/bin -O2 -pipe -=
DHAVE_CONFIG_H -I/usr/include -Wall -Werror -o test.o -c test.cpp
> >>>>
> >>>> So are the libc++ headers installed in the /builds/workspace/FreeBSD=
_HEAD/obj/builds/workspace/FreeBSD_HEAD/src/tmp sysroot?  The compiler erro=
r message appears to indicate it is getting its headers from /usr/include i=
nstead.
> >>>>
> >>>> I can't look on the actual test system, but my guess would be that e=
ither the --sysroot flag is incorrect, or the libc++ headers are not correc=
tly installed on the target system.
> >>>>
> >>>> -Dimitry
> >>>>
> >>>>> On 29 Aug 2016, at 12:56, Dimitry Andric <dim@FreeBSD.org> wrote:
> >>>>>
> >>>>> Hi Craig,
> >>>>>
> >>>>> I find it very hard to parse these extremely verbose logs.  Can you=
 point out the location and contents of the exact error you are seeing?
> >>>>>
> >>>>> -Dimitry
> >>>>>
> >>>>>> On 29 Aug 2016, at 08:59, Craig Rodrigues <rodrigc@FreeBSD.org> wr=
ote:
> >>>>>>
> >>>>>> Dimitry,
> >>>>>>
> >>>>>> Can you take a look at this?
> >>>>>> I'm not sure why, but after recent changes, one of the tests is
> >>>>>> complaining that the C++ header <sstream> is missing.
> >>>>>>
> >>>>>> --
> >>>>>> Craig
> >>>>>>
> >>>>>>
> >>>>>> On Sun, Aug 28, 2016 at 11:11 PM, <jenkins-admin@freebsd.org> wrot=
e:
> >>>>>> See <https://jenkins.FreeBSD.org/job/FreeBSD_HEAD/564/>;
> >>>>>>
> >>>>>>
> >>>>>
> >>>>
> >>>>
> >>>
> >>
> >>
> >>
> >> --
> >> Li-Wen Hsu <lwhsu@FreeBSD.org>
> >> https://lwhsu.org
> >=20
>=20
>=20
> --=20
> Regards,
> Bryan Drewery
>=20




--=20
Li-Wen Hsu <lwhsu@FreeBSD.org>
https://lwhsu.org

--PNTmBPCT7hxwcZjr
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQJ8BAEBCgBmBQJXxHZtXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w
ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQxMDdENTNGNjUyMTUzMzVCNzA5NDNGODQ2
NzI3RTc3Qzg4NjJCNjU2AAoJEGcn53yIYrZWXw8QAIMZ0zrW6FgKiJTTj3pOx7ij
+TtUeRUDKNkfVp/jlJiCsh5/qzfnpS2HekiiR+ApGDy+jXPZl2wwdgM8Uz9q7c+f
LdsdOenu55lTSzlM+3mYIVjVPC77KGS45J8zVI4+bsEPEyBbNLCB9JJMjyoP3hJ2
k/SJIrzno/59z3HMAznIBwWCgIyTFOaE5+Kg5U13CZH9ABSc8uXI9DQ7CdxQzLWG
59ulF0ugM383r+F2s/48wI9vJhqz4kXSUvPuP/RyuGJaRdJfF3i+jlDM0fSWUflh
Zh2XnoaEhpFm3BXsCX5bdnaJo+Tv/XNKkF8XkbdhNR/thtnF98HJ3gOBazWodpUe
4Zir5g1WzcZRM5HUMmZ4G0gN4o+e2CK29cp1FrXEAx0R2VNHRmy4dCy84nkPic2U
vwbJnPhgDUYWzaiCJDImSwUNVTSCjPFrTur4rtyamo3lT1e687m1J3aisXj+NXhc
KnbGURaLTAse8S2uxMXYxKrbTU7f585z5muNCqAGC6ooHjA4h6h6CWL4nlnvCSIW
dtAWJdb/VLMgAz0zJD2pR7vH7cNlxY3K34RfMWsy8W4QzdeEEtF9a7ZgEQjGUrlJ
4bpl3eLD3TaKgFbUOs+2ljdteqARgnRKudrj066NFcZfGY8T1S/wvsKI7EkNIcJZ
ekYtqOSJCvJ2HHCowCnd
=YJmY
-----END PGP SIGNATURE-----

--PNTmBPCT7hxwcZjr--



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20160829175247.GA10263>