The initial failure: https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=peripatus&dt=2017-05-23%2019%3A17%3A42
I then recompiled perl, and got: borg.lerctr.org /home/pgbuildfarm $ cd /home/pgbuildfarm/bin/latest && ./run_branches.pl --run-all --config=/home/pgbuildfarm/conf/build-farm.conf Socket.c: loadable library and perl binaries are mismatched (got handshake key 0xd200080, needed 0xdf00080) borg.lerctr.org /home/pgbuildfarm/bin/latest $ force rebuilding and installing perl and all p5-* ports fixed that. -- Larry Rosenman http://www.lerctr.org/~ler Phone: +1 214-642-9640 E-Mail: l...@lerctr.org US Mail: 17716 Limpia Crk, Round Rock, TX 78664-7281 On 5/24/17, 4:05 AM, "Konstantin Belousov" <kostik...@gmail.com> wrote: On Tue, May 23, 2017 at 04:46:14PM -0500, Larry Rosenman wrote: > My PostgreSQL buildfarm animal BROKE with this change until I force rebuilt > lang/perl5.24 > and all my p5-* ports. So what was the symptoms and the error, exactly ? A lot of efforts were spent to ensure that _consistent_ set of old binaries and libraries would run without issues on the new system. I mean that if you have binaries and libraries built on pre-ino64 system, which do not reference any libraries built on post ino64, except system libraries (like libc/libthr etc), everything should work. This feature was the main cause of long delay finishing ino64. > > emulators/qemu-user-static also won???t compile (sbruno@ is on this one). This is a separate issue. > > Poudriere did *NOT* force a fuill rebuild even though freebsd-version *WAS* bumped. > > Is there a hazard for others here? > > Or more info needed in /usr/{src,ports}/UPDATING? > > > -- > Larry Rosenman http://www.lerctr.org/~ler > Phone: +1 214-642-9640 E-Mail: l...@lerctr.org > US Mail: 17716 Limpia Crk, Round Rock, TX 78664-7281 > > > > _______________________________________________ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
