Date: Mon, 29 Aug 2016 07:30:52 -0700 From: Craig Rodrigues <rodrigc@freebsd.org> To: Dimitry Andric <dim@freebsd.org> Cc: "jenkins-admin@freebsd.org" <jenkins-admin@freebsd.org>, "freebsd-testing@freebsd.org" <freebsd-testing@freebsd.org> Subject: Re: Jenkins build is still unstable: FreeBSD_HEAD #564 Message-ID: <CAG=rPVdtos0CGZxySOA9RL0b%2BYqdF6z8D5=voC%2BmxzO5bYAk9g@mail.gmail.com> In-Reply-To: <8058052E-A09A-403E-828A-74B51ED4BBF4@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>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi, I can't check offhand, since I don't keep the VM around during the build. I'm also not at my FreeBSD machine right now. If you happen to have a fully built FreeBSD HEAD tree available, you can reproduce the layout of the VM by doing something like this: mkdir -p /tmp/foobar make installworld DESTDIR=/tmp/foobar make installkernel DESTDIR=/tmp/foobar make distribution DESTDIR=/tmp/foobar -- Craig On Mon, Aug 29, 2016 at 7:02 AM, Dimitry Andric <dim@freebsd.org> wrote: > Do you have an /usr/include/c++/v1 directory? And is there a file called > "sstream" in it? > > If it is there, I think the problem is due to the -I/usr/include option in > the command line for the test program. If you remove that, I think the > compilation will work correctly. > > -Dimitry > > > On 29 Aug 2016, at 14:55, Craig Rodrigues <rodrigc@freebsd.org> wrote: > > > > 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 properly? > > -- > > Craig > > > > > > On Mon, Aug 29, 2016 at 4:13 AM, Dimitry Andric <dim@freebsd.org> wrote: > > 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=/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 > error message appears to indicate it is getting its headers from > /usr/include instead. > > > > I can't look on the actual test system, but my guess would be that > either the --sysroot flag is incorrect, or the libc++ headers are not > correctly 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> > wrote: > > >> > > >> 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> wrote: > > >> See <https://jenkins.FreeBSD.org/job/FreeBSD_HEAD/564/>; > > >> > > >> > > > > > > > > >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAG=rPVdtos0CGZxySOA9RL0b%2BYqdF6z8D5=voC%2BmxzO5bYAk9g>