Deutsch English Français Italiano |
<877cbs11p7.fsf@nosuchdomain.example.com> View for Bookmarking (what is this?) Look up another Usenet article |
Path: ...!2.eu.feeder.erje.net!feeder.erje.net!eternal-september.org!feeder3.eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail From: Keith Thompson <Keith.S.Thompson+u@gmail.com> Newsgroups: comp.unix.programmer Subject: Re: Long filenames in DOS/Windows and Unix/Linux Date: Tue, 03 Sep 2024 21:29:24 -0700 Organization: None to speak of Lines: 25 Message-ID: <877cbs11p7.fsf@nosuchdomain.example.com> 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> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Injection-Date: Wed, 04 Sep 2024 06:29:29 +0200 (CEST) Injection-Info: dont-email.me; posting-host="0c8cc2609bc8d9fbbbb3d106ce45f413"; logging-data="3897102"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1+HGZYr+XAsrHryPWCiSsun" User-Agent: Gnus/5.13 (Gnus v5.13) Cancel-Lock: sha1:kHeyLWZZKkpnO5s2AoRggvqb63A= sha1:5CuMGNog9Nf+4QVEJy4k3sQaSG0= Bytes: 2621 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. >> >> $ 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". -- Keith Thompson (The_Other_Keith) Keith.S.Thompson+u@gmail.com void Void(void) { Void(); } /* The recursive call of the void */