make includes for 3.3 failes with sigsegv in libssl/crypto

[Adrian Knoth <adi_(_at_)_drcomp_(_dot_)_erfurt_(_dot_)_thur_(_dot_)_de>]

Hi,

as mentioned some days ago by the_13_(_at_)_mail_(_dot_)_ru I faced exactly the same
problems on two different systems when upgrading from 3.2 to 3.3.

Nick Holland claimed hardware-responsibility, but that's not true,
at least one of both systems is running since 3.2-upgrade:

adi_(_at_)_gta:~$ w
 3:02PM  up 143 days, 14:20, 2 users, load averages: 2.35, 1.62, 1.12

Both systems failed on "make includes" with the following lines:

===> crypto
cat /usr/src/lib/libssl/crypto/../src/crypto/objects/obj_mac.num > obj_mac.num.tmp
/usr/bin/perl /usr/src/lib/libssl/crypto/../src/crypto/objects/objects.pl /usr/src/lib/libssl/crypto/../src/crypto/objects/objects.txt obj_mac.num.tmp obj_mac.h*** Signal 11

The error is sig11 for perl, and it is true for every perl-command:

root_(_at_)_trabsoft:/usr/src/include$ perl -v
Segmentation fault (core dumped)

root_(_at_)_trabsoft:/usr/src/include$ ls -l /usr/bin/perl5.6.1
-rwxr-xr-x  2 root  wheel  16384 Oct 20 18:41 /usr/bin/perl5.6.1

This perl was generated by "make build" in an openbsd-3.1-environment
during update to openbsd-3.2. This is the same on both systems.
(both machines were installed under 2.7 and continously updated to 3.2)

I've copied /usr/bin/perl5.6.0 to /usr/bin/perl and everything works
well, now.

I draw the following sketch:

When a system was updated from 3.1 to 3.2, /usr/bin/perl got broken and
that's why the migration to 3.3 fails.

Solution is to test whether perl produces sigsegv and if so using perl5.6.0
or any other working binary instead.

-- 
mail: adi_(_at_)_thur_(_dot_)_de  	http://adi.thur.de	PGP: v2-key via keyserver

Q: Was ist ne Sibling-Beziehung?    (Peter Koellner in Bezug auf Proxies)
A: Schweinkram ist hier off-topic.             (Erik Heinz in thur.misc)