Hello;
I'm attempting create a FreeBSD port from an application that was
developed mainly for linux. The original author did use autoconf so
this will make porting easier.
One problem that I'm having trouble solving is that the configure
script fails with the following error:
checking for a BSD
Hey
What i would do is maby take a look inside his configure.ac to figure
out what he is checking for. And maby see why/how to fix it :). Like
look for the macro that checks for that specific feature in the shell
or otherwise.
-Phil
2009/4/30 Joey Mingrone :
> Hello;
>
> I'm attempting create a
On Thu, Apr 30, 2009 at 12:44:48AM -0700, Joey Mingrone wrote:
> checking for a BSD-compatible install... /usr/local/bin/ginstall -c
> checking whether build environment is sane... configure: error: ls -t
> appears to fail. Make sure there is not a broken
> alias in your environment
> configure: e
> On Wednesday 29 April 2009 16:22:08 Andreas Schwab wrote:
> > Mike Frysinger writes:
> > >
> http://www.opengroup.org/onlinepubs/9699919799/utilities/V3_chap02.html#t
> > >rap If the first operand is an unsigned decimal integer, the shell shall
> > > treat all operands as conditions, and shall r
2009/4/30 Ralf Wildenhues :
> Hello Priit,
>
> please keep the mailing list in Cc:, thanks.
Mailer-Daemon answered to the list letter, telling me that
The following address(es) failed:
bug-autoc...@gnu.org
>
> * Priit Pääsukene wrote on Wed, Apr 29, 2009 at 10:39:11AM CEST:
>> > Which Autoconf
Hi;
On Thu, Apr 30, 2009 at 01:50, Philip Herron
wrote:
> What i would do is maby take a look inside his configure.ac to figure
> out what he is checking for. And maby see why/how to fix it :). Like
> look for the macro that checks for that specific feature in the shell
> or otherwise.
>
That's
Hello Joey,
* Joey Mingrone wrote on Thu, Apr 30, 2009 at 09:44:48AM CEST:
>
> checking for a BSD-compatible install... /usr/local/bin/ginstall -c
> checking whether build environment is sane... configure: error: ls -t
> appears to fail. Make sure there is not a broken
> alias in your environmen
On Thu, Apr 30, 2009 at 06:56, Patrick Welche wrote:
> On Thu, Apr 30, 2009 at 12:44:48AM -0700, Joey Mingrone wrote:
>> checking for a BSD-compatible install... /usr/local/bin/ginstall -c
>> checking whether build environment is sane... configure: error: ls -t
>> appears to fail. Make sure there
Hello Ralf;
On Thu, Apr 30, 2009 at 10:35, Ralf Wildenhues wrote:
> Please check whether the files in the package tarball had time stamps in
> the future (relative to the time when you were building). In that case,
> it may be the distributor's system clock that is wrong.
They seem OK. All the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Joey Mingrone on 4/30/2009 12:36 PM:
>> ls -t "$srcdir/configure" conftest.file
>>
>> So, what "ls" is on the system, and is "ls" really /bin/ls or is it an
>> alias? (I'm just paraphrasing the error message ;-) )
>>
>
> Yeah, /bin/ls i
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Joey Mingrone on 4/30/2009 1:07 PM:
> + ls -Lt ./configure conftest.file
> + set X conftest.file [31m./configure[39;49m[m
> + test X conftest.file [31m./configure[39;49m[m = X
> + rm -f conftest.file
> + test X conftest.file [31m./c
Hi Eric;
On Thu, Apr 30, 2009 at 12:23, Eric Blake wrote:
> Your ls version is trying to output colors, even though it is in a
> non-interactive context. Almost like using GNU 'ls --color=always'
> instead of the recommended 'ls --color=auto', except that you said it
> wasn't GNU ls. Are you su
12 matches
Mail list logo
