[bug #63516] `include` of absolute path prepends path with `./`

Update of bug #63516 (project make): Status:None => Fixed Assigned to:None => psmith Open/Closed:Open => Closed Fixed Release:

[bug #63516] `include` of absolute path prepends path with `./`

Follow-up Comment #9, bug #63516 (project make): > The file name "d:foo" means on Windows "the file 'foo' in the directory that is current on drive 'd' Yep, I don't know much about Windows but I do know that much! :) > So in my opinion we should treat such file names as absolute, because

[bug #63516] `include` of absolute path prepends path with `./`

Follow-up Comment #8, bug #63516 (project make): The file name "d:foo" means on Windows "the file 'foo' in the directory that is current on drive 'd'. Yes, windows programs can have a separate current directory on each drive. You can see that if you do the following dance: C:\> cd foobar

[bug #63516] `include` of absolute path prepends path with `./`

Follow-up Comment #7, bug #63516 (project make): Thanks for the patch but there's no need to spend more time on this; as I said I have a fix. During this time of year I've got a lot going on so it takes me a bit longer to finish things. But Eli I was curious about your comment that we should

[bug #63516] `include` of absolute path prepends path with `./`

Follow-up Comment #6, bug #63516 (project make): [comment #5 comment #5:] > Thanks for the patch. > > I have three comments: > > (1) The test under "WINDOWS32" should allow a backslash after the colon as well as a forward slash. Sounds right. > > (2) Do we want Make to consider

[bug #63516] `include` of absolute path prepends path with `./`

Follow-up Comment #5, bug #63516 (project make): Thanks for the patch. I have three comments: (1) The test under "WINDOWS32" should allow a backslash after the colon as well as a forward slash. (2) Do we want Make to consider "drive-relative" file names, as in "d:foo/bar", relative or

Re: [bug #63516] `include` of absolute path prepends path with `./`

On Thu, Dec 15, 2022 at 4:17 PM anonymous wrote: > > Follow-up Comment #4, bug #63516 (project make): > > I've attached my fix in case it's helpful. Also attached is a small fix to > `bootstrap.bat` that I had to make to get it to build with `tcc`. > > (file #54105, file #54106) Regarding this

[bug #63516] `include` of absolute path prepends path with `./`

Follow-up Comment #4, bug #63516 (project make): I've attached my fix in case it's helpful. Also attached is a small fix to `bootstrap.bat` that I had to make to get it to build with `tcc`. (file #54105, file #54106) ___ Additional Item

[bug #63516] `include` of absolute path prepends path with `./`

Follow-up Comment #3, bug #63516 (project make): Yes, that's it. I have a fix and will put in up a patch shortly. ___ Reply to this item at: ___

[bug #63516] `include` of absolute path prepends path with `./`

Follow-up Comment #2, bug #63516 (project make): Line 376 in `src/read.c` may be the culprit: if (ebuf.fp == NULL && deps->error == ENOENT && (flags & RM_INCLUDED) && *filename != '/' && include_directories) Looks like it's trying to determine whether the path is absolute in a way

[bug #63516] `include` of absolute path prepends path with `./`

Follow-up Comment #1, bug #63516 (project make): `make` was installed with `scoop`. ___ Reply to this item at: ___ Message sent via Savannah

[bug #63516] `include` of absolute path prepends path with `./`

URL: Summary: `include` of absolute path prepends path with `./` Project: make Submitter: None Submitted: Mon 12 Dec 2022 10:17:30 PM UTC Severity: 3 - Normal