On Thu, 12 Jun 2008 09:17:36 +0100, Dave wrote:

> AGT wrote:
>> On Wed, 11 Jun 2008 11:07:18 -0500, Dave Uhring wrote:
>>
>>> I forgot to mention.... A few months back mplayer's configure script
>>> added something which pukes using #!/bin/sh. Change the she-bang to
>>> #!/usr/bin/bash. The penguins usually symlink /bin/bash to /bin/sh; after
>>> all, they're the same, aren't they?
>>
>> Oscar found a configure hack for this. I just change the configure script
>> s/sh/bash/ as Ive run into it before.
> Better might be to fix the script so it does not need bash and try to
> get the developers to use it.

Yeah right. Talking sense to Penguinites. Pull the other one mate : >

> The problem with accepting the GNUism is that GNU tools keep changing. I
> can think of a couple of occasions recently where specific older
> versions of gcc are needed to compile bits of software.

Been down that road YEARS ago. Nothing new. Esp. when it comes to c++
Talk about mangleing

> Sometimes I think the gnu tools are useful, but on others I think the
> poor stability of them causes more problems than it solves.

Stability issues I dont encounter much.
This latest gcc though is a candidate for BAD software engineering where
running a 64 bit make test results in ~99% failure but gcc -m64
compiles 64 bit code like openssl just fine even at -O4
That was mpfr I think...

Sometimes gtools are needed to compile GNU stuff. The alternative is
to fix the code and submit the changes to the 'developers' who
usually ignore you : > That means every week or so when a new
"improved" version comes out you go through the same thing again.
Maybe you get ignored because the code changes so MUCH that
submitting diffs are pointless : /

Or just use Blastwave and be done with it.