--- "Greg A. Woods" <[EMAIL PROTECTED]> wrote:
-8<-
>
> > If we can deal with ":" - fine, if we cannot - no problem.
>
> It might be sensible for GNU Make to try and introduce quoting rules
> that would allow ':' to be used in filenames. However I would hope that
> wouldn't mean that the GNU Co
> "Greg" == Greg A Woods <[EMAIL PROTECTED]> writes:
>> If we can deal with ":" - fine, if we cannot - no problem.
Greg> It might be sensible for GNU Make to try and introduce quoting
Greg> rules that would allow ':' to be used in filenames. However I
Greg> would hope that wouldn't mean tha
[ On Tuesday, May 9, 2000 at 15:40:58 (-0400), Pavel Roskin wrote: ]
> Subject: Re: Possible bug involving ':' in directory names
>
> From GNU Coding Standards (by RMS):
>
> Utilities reading files should not drop NUL characters, or any other
> nonprinting character
Hello, Greg!
> If anyone really and truly believes that it should be possible to
> include any character except perhaps '/' and '\0' in a filename then I
>From GNU Coding Standards (by RMS):
Utilities reading files should not drop NUL characters, or any other
nonprinting characters @emph{inclu
[ On Tuesday, May 9, 2000 at 09:11:02 (-0700), Tom Tromey wrote: ]
> Subject: Re: Possible bug involving ':' in directory names
>
> And once you get past the autoconf problems, you still have to contend
> with make. If a ":" ends up in your Makefile, you are doom
On May 9, 2000, Akim Demaille <[EMAIL PROTECTED]> wrote:
> I'm not surprised you found such problems: the colon is used in many
> places to separate various file names.
Moreover, it's a very important component of `make's syntax. So,
trying to fix it would be hopeless.
--
Alexandre Oliva
> "Akim" == Akim Demaille <[EMAIL PROTECTED]> writes:
> "Keith" == Keith Thompson <[EMAIL PROTECTED]> writes:
Keith> I recently discovered that the generated configure scripts have
Keith> problems when the software is installed in a directory whose
Keith> name contains ':' characters. (I
> "Keith" == Keith Thompson <[EMAIL PROTECTED]> writes:
Keith> I recently discovered that the generated configure scripts have
Keith> problems when the software is installed in a directory whose
Keith> name contains ':' characters. (I was using a timestamp as part
Keith> of the directory nam
This is a rather vague bug report; I don't have a lot of detailed
information on it. It may not even be a bug in autoconf.
The Globus software package (see www.globus.org) uses autoconf to
generate configure scripts. I recently discovered that the generated
configure scripts have problems when
