Date: Thu, 22 Dec 2011 20:48:48 +0400 From: Ruslan Mahmatkhanov <cvs-src@yandex.ru> To: Kevin Oberman <kob6558@gmail.com> Cc: perryh@pluto.rain.com, Martin Matuska <mm@freebsd.org>, freebsd-ports@freebsd.org, leslie@eskk.nu Subject: Re: Stop in /usr/ports/multimedia/x264 Message-ID: <4EF35F70.5070606@yandex.ru> In-Reply-To: <CAN6yY1viu8vxkmOQQEUKk%2BvzM7vGJ8--tsw8hbYfCyBbPyYNpQ@mail.gmail.com> References: <4EF1E3EF.9000405@eskk.nu> <CAN6yY1tOrhyng1o5%2Bo5ko3cEoT2MLqCUF=L47Gesv%2BNnDdrhFw@mail.gmail.com> <4ef30e7b.gG6UGw%2BkkNWpdv07%perryh@pluto.rain.com> <4EF2F920.8060007@FreeBSD.org> <CAN6yY1viu8vxkmOQQEUKk%2BvzM7vGJ8--tsw8hbYfCyBbPyYNpQ@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Kevin Oberman wrote on 22.12.2011 20:38: > The only thing I can think of is that the failing system is the > oldest, running 8.2 while the others were running 9.0-RC2 and > 9.0-Beta3. Yes, all is worked just fine (before the bash fix commit) there on 10.0-CURRENT i386. I saw that configure warnings too, but it still was built successfully. May be bash only needed on some older FreeBSD versions like 8.2, that didn't had all that improvements for /bin/sh, that were merged in 9 and 10, so maybe it is the reason why it builded fine on this systems w/o any additional fixes. -- Regards, Ruslan Tinderboxing kills... the drives.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4EF35F70.5070606>