Say, did you look at the port recently? :-)
I have added bash as a build dependency and use it for the configure script.
There are two ways I can solve this in general:
1.) add bash as a build dependency and use it for configure (I have
chosen this for now, already committed)
2.) patch configure
On 22 December 2011 09:32, Martin Matuska m...@freebsd.org wrote:
Say, did you look at the port recently? :-)
I have added bash as a build dependency and use it for the configure script.
There are two ways I can solve this in general:
1.) add bash as a build dependency and use it for
On Thu, Dec 22, 2011 at 1:32 AM, Martin Matuska m...@freebsd.org wrote:
Say, did you look at the port recently? :-)
I have added bash as a build dependency and use it for the configure script.
There are two ways I can solve this in general:
1.) add bash as a build dependency and use it for
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
On 22 Dec 2011 16:49, Ruslan Mahmatkhanov cvs-...@yandex.ru wrote:
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
Chris Rees wrote on 22.12.2011 22:12:
On 22 Dec 2011 16:49, Ruslan Mahmatkhanov cvs-...@yandex.ru wrote:
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,
On 22 Dec 2011 18:20, Ruslan Mahmatkhanov cvs-...@yandex.ru wrote:
Chris Rees wrote on 22.12.2011 22:12:
On 22 Dec 2011 16:49, Ruslan Mahmatkhanov cvs-...@yandex.ru wrote:
Kevin Oberman wrote on 22.12.2011 20:38:
The only thing I can think of is that the failing system is the
oldest,
On Thu, Dec 22, 2011 at 10:57 AM, Chris Rees utis...@gmail.com wrote:
On 22 Dec 2011 18:20, Ruslan Mahmatkhanov cvs-...@yandex.ru wrote:
Chris Rees wrote on 22.12.2011 22:12:
On 22 Dec 2011 16:49, Ruslan Mahmatkhanov cvs-...@yandex.ru wrote:
Kevin Oberman wrote on 22.12.2011 20:38:
The
is reported only once
x264.c:250: error: for each function it appears in.)
gmake: *** [x264.o] Fel 1
gmake: *** Inväntar oavslutade jobb...
*** Error code 1
Stop in /usr/ports/multimedia/x264.
*** Error code 1
Stop in /usr/ports/multimedia/x264.
=== make failed for multimedia/x264
=== Aborting update
in this function)
x264.c:250: error: (Each undeclared identifier is reported only once
x264.c:250: error: for each function it appears in.)
gmake: *** [x264.o] Fel 1
gmake: *** Inväntar oavslutade jobb...
*** Error code 1
Stop in /usr/ports/multimedia/x264.
*** Error code 1
Stop in /usr
Stop in /usr/ports/multimedia/x264.
*** Error code 1
Stop in /usr/ports/multimedia/x264.
=== make failed for multimedia/x264
=== Aborting update
I get this error on only a single system. My other two built the x264
port without any problems.
I see the following errors during the configure
Kevin Oberman kob6...@gmail.com wrote:
I see the following errors during the configure stage:
=== Configuring for x264-0.119.2113
[[: not found
That sure looks as if the configure script needs to be run with bash.
files/patch-configure does this:
-#!/bin/bash
+#!/bin/sh
which presumes
On Thu, Dec 22, 2011 at 3:03 AM, per...@pluto.rain.com wrote:
Kevin Oberman kob6...@gmail.com wrote:
I see the following errors during the configure stage:
=== Configuring for x264-0.119.2113
[[: not found
That sure looks as if the configure script needs to be run with bash.
On Thu, Dec 22, 2011 at 3:03 AM, per...@pluto.rain.com wrote:
Kevin Oberman kob6...@gmail.com wrote:
I see the following errors during the configure stage:
=== Configuring for x264-0.119.2113
[[: not found
That sure looks as if the configure script needs to be run with bash.
(first use in this
function)
x264.c:250: error: (Each undeclared identifier is reported only once
x264.c:250: error: for each function it appears in.)
gmake: *** [x264.o] Fel 1
gmake: *** Inväntar oavslutade jobb...
*** Error code 1
Stop in /usr/ports/multimedia/x264.
*** Error code 1
Stop in /usr
15 matches
Mail list logo
