Date: Fri, 16 Jun 2017 07:13:46 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-ports-bugs@FreeBSD.org Subject: [Bug 220030] devel/bison failing to build on 12.0 in jail or under poudriere Message-ID: <bug-220030-13@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D220030 Bug ID: 220030 Summary: devel/bison failing to build on 12.0 in jail or under poudriere Product: Ports & Packages Version: Latest Hardware: Any OS: Any Status: New Severity: Affects Only Me Priority: --- Component: Individual Port(s) Assignee: sunpoet@FreeBSD.org Reporter: dave@ci.com.au Flags: maintainer-feedback?(sunpoet@FreeBSD.org) Assignee: sunpoet@FreeBSD.org Created attachment 183518 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=3D183518&action= =3Dedit Logging of bison build going mad The build of bison-3.0.4,1 goes into a runaway state when being built under poudriere or just in a jail running 12.0 . The host of the jail is running FreeBSD 12.0-CURRENT (LOCAL) #3 r308389 . Builds of bison-3.0.4,1 on the same host in a 11.1-RELEASE jail build ok. The build appears to hang at the point where the logging displays... Making all in . It does consume resources. Eventually poudriere kills the build becuase of= no output to stdout. I tried doing the same build jon a jail with using poudriere. This showed the same symptoms. I hacked the Makefile that had been created in /usr/ports/devel/bison/work/bison-3.0.4 to get some idea of what was going = on. I modified: ($(am__cd) $$subdir && $(MAKE) $(AM_MAKEFLAGS) $$local_target) to: ($(am__cd) $$subdir && $(MAKE) -d d $(AM_MAKEFLAGS) $$local_target) This debugging reveals that the build is looping around trying to refind the same things over and over again. See the attached file for evidence of this. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-220030-13>