On Wednesday 15 April 2009 07:06:09 Ralf Wildenhues wrote:
> > > Not all packages follow GNU Coding Standards, therefore,
> > > DESTDIR is not properly supported in a surprisingly large
> > > number of packages.
> >
> > We already enforce a level of GNUism on packages that use
> > autoconf/automake
>> This requirement is reflected in the SunOS man page, (from
>> SunOS 5.5.4, IIRC)
>
> Hmmm, "SunOS 5.5.4"? There's no such version.
It's actually 5.5.1; I wasn't able to access the machine until
I came back to work today, after the Easter break, and was quoting
from a failing memory :-( Perha
On Sunday 16 April 2006 7:36 pm, Stepan Kasal wrote:
> Second, let me remind me that we are currently in a freeze; I believe
> that this type of changes should be put off after 2.60, unless it is
> supported by a real-world problem report.
I wasn't suggesting that you should immediadely rush to ch
On Sunday 16 April 2006 1:41 pm, Andreas Schwab wrote:
> Is there any evidence that there exists a sed implementation that does
> not support the semicolon as command separator? Note that the thread
> you quote above is _not_ about semicolons being unsupported, but rather
> about missing ones. Au
On Wednesday 12 April 2006 8:47 pm, Stepan Kasal wrote:
> On Wed, Apr 12, 2006 at 08:45:04PM +0200, Ralf Wildenhues wrote:
> > here's a patch that I think does more or less what Bruno's patch
> > intends to do, against current CVS.
>
> I worked on the same issue. We both use the same pattern
>
BRM wrote:
> (I am limited to the version numbers below because MSYS won't
> compile & pass certain important tests for a newer autoconf, so
> I can't build a newer automake. Any how...)
Eh??? Frode reported here:
http://sourceforge.net/mailarchive/message.php?msg_id=13962147
that the current re
BRM wrote:
> I´ve been playing around with it a bit today, mostly
> MSYS, and have thus far only had one issue with it -
> cl won´t compile the program because of bad parameters
> being passed to it (since MSYS uses // instead of /).
> (Not sure if that´s an issue for you guys, mingw-msys,
> or the
Howard Chu wrote, quoting BRM:
>> I´m taking a look at Msys/MingW now. Its worked best
>> so far - though a script is failing. I got it to run
>> by running the VC build environment (e.g. vcvars.bat)
>> and then running the msys environment (msys.bat) to
>> enter into the msys shell.
>>
>> Thanks f
Stepan Kasal wrote:
> I think that the parametr to compile should look like
>some/path/main.c
> which becomes cfile, and then cofile is assigned as...
Just guessing, but with cl.exe being Bill's C compiler, it
probably doesn't understand `some/path/main.c' as a path name;
(it will
