Path: ...!weretis.net!feeder8.news.weretis.net!eternal-september.org!feeder3.eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail
From: Nuno Silva <nunojsilva@invalid.invalid>
Newsgroups: comp.unix.programmer
Subject: Re: Long filenames in DOS/Windows and Unix/Linux
Date: Wed, 04 Sep 2024 10:16:54 +0100
Organization: A noiseless patient Spider
Lines: 37
Message-ID: <vb98i6$3pdv5$1@dont-email.me>
References: <9e7a4bd1-bfbb-4df7-af1a-27ca9625e50bn@googlegroups.com>
	<ubg6o7$3jrsn$1@news.xmission.com> <ubg853$2ssj8$1@dont-email.me>
	<ubg8a8$2t20l$1@dont-email.me> <vaubbo$1d324$1@news.xmission.com>
	<vauknd$uvji$1@dont-email.me> <20240903084440.0000663d@gmail.com>
	<20240903103327.395@kylheku.com> <20240903113937.000008a3@gmail.com>
	<20240903130000.933@kylheku.com> <20240903132547.00000656@gmail.com>
	<87seug1iyj.fsf@nosuchdomain.example.com>
	<20240903155649.659@kylheku.com>
	<87jzfs1f6p.fsf@nosuchdomain.example.com>
	<vb87o7$3h6uk$2@dont-email.me>
	<87frqg1da2.fsf@nosuchdomain.example.com>
	<vb8aci$3hhg4$1@dont-email.me>
	<877cbs11p7.fsf@nosuchdomain.example.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 8bit
Injection-Date: Wed, 04 Sep 2024 11:16:54 +0200 (CEST)
Injection-Info: dont-email.me; posting-host="bf3903c93f73533d3efb0e0124570cd3";
	logging-data="3979237"; mail-complaints-to="abuse@eternal-september.org";	posting-account="U2FsdGVkX19cMusLBm3sDO/q2woNyVYX"
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.5 (gnu/linux)
Cancel-Lock: sha1:J0fnIdH+xYSsDRFE3iCfXSc+j5o=
Bytes: 3028

On 2024-09-04, Keith Thompson wrote:

> Lawrence D'Oliveiro <ldo@nz.invalid> writes:
>> On Tue, 03 Sep 2024 17:19:17 -0700, Keith Thompson wrote:
>>> Lawrence D'Oliveiro <ldo@nz.invalid> writes:
>>>> I have some Makefiles with spaces in the dependency names, of the form:
>>>>
>>>>     target\ name\ with\ space : source\ name\ with\ space
>>> 
>>> I'd be interested in knowing how you do that.
>>>
[I tried to restore the newlines at the appropriate places here, I hope
I got these right:]
>>> $ cat Makefile
>>> foo\ bar: foo\ bar.c
>>> $ make
>>> cc     foo bar.c   -o foo bar
>>> cc: fatal error: input file ‘foo’ is the same as output file
>>> compilation terminated.
>>
>> The Makefiles in question are not using the default build rules for C 
>> code: they are building other things, with explicit use of the "$<" and 
>> "$@" variable substitutions.
>
> I'd still be interested in seeing an example.  In a quick experiment,
> I wasn't able to get GNU Make to recognize the existence of a file named
> "foo bar".

But, in your output, what is having trouble is the compiler invocation,
not make itself processing the files (although that then *is* a problem
with make's implicit rules and their ability to handle spaces).

Or do you mean there is also a problem with detecting the presence or
absence of files with spaces in their names?

-- 
Nuno Silva