Created attachment 183518 [details] 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.
I have been told by my superior that this problem may be an issue caused by the jail & host O/S being pre-64-bit inode and the automake that would be being used inside the jail being post-64bit inode. I will upgrade the O/S on the host and update the jails where the build is going mad and see if the problem I am seeing continues to occur.
Upgrading the host O/S and refershing the jail to the same version as the host O/S has fixed the build problem I was seeing.