[bug #63315] Test failures with 4.4 on OpenBSD

Follow-up Comment #7, bug #63315 (project make): I also hit this on illumos, and just reached the same conclusion - that the memory containing the function name in the hash table entry becomes unmapped when testapi.so is unloaded and loaded again. I'll apply the patch, thanks!

[bug #63359] patsubst messes up functions in replacement

Update of bug #63359 (project make): Status:None => Not A Bug Open/Closed:Open => Closed Component Version: SCM => 4.4

[bug #63359] patsubst messes up functions in replacement

URL: Summary: patsubst messes up functions in replacement Project: make Submitter: bertsky Submitted: Sun 13 Nov 2022 05:30:38 PM UTC Severity: 3 - Normal Item

[bug #63359] patsubst messes up functions in replacement

Follow-up Comment #2, bug #63359 (project make): Duh, that was stupid of me to think! Sorry to bother you, and thanks for the explanation, anyway! > Instead, you want to apply the function to the `$(FOO)` variable, like this: Yes, but I wanted to avoid that because the pattern … $(notdir

[bug #63307] make 4.4 passes ignored SIGPIPE on to children

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

[bug #63315] loadapi test / user-defined function reload SEGV failures

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

[bug #63352] nested conditional wrongly reports extraneous endif

Update of bug #63352 (project make): Status:None => Duplicate Open/Closed:Open => Closed ___ Follow-up Comment #1: Duplicate post for

[bug #63359] patsubst messes up functions in replacement

Follow-up Comment #3, bug #63359 (project make): It's not clear to me what you're trying to do: I think we have a bit of an XY problem. But if what you want is get the containing pathname without a trailing slash, then you can do this: $(patsubst %/,%,$(dir $(FOO))) A bit annoying but it does

[bug #63359] patsubst messes up functions in replacement

Follow-up Comment #4, bug #63359 (project make): Yes, I am doing that now, plus the outer $(notdir ...). Yes, I must admit the Github experience spoiled me in that regard, but I shall go ML first next time I get lost in make-space so bad I get to believe it's an actual bug (as if that was so

[bug #63351] nested conditional wrongly reports extraneous endif

Update of bug #63351 (project make): Status:None => Duplicate Open/Closed:Open => Closed ___ Follow-up Comment #1: Duplicate of bug

[bug #63352] nested conditional wrongly reports extraneous endif

Update of bug #63352 (project make): Status: Duplicate => None Open/Closed: Closed => Open ___ Follow-up Comment #2: Oh it looks like this

[bug #63352] nested conditional wrongly reports extraneous endif

Update of bug #63352 (project make): Status:None => Not A Bug Open/Closed:Open => Closed ___ Follow-up Comment #3: This is not a bug in

Re: [PATCH 1/2] Fix duplicated __strchrnul() declaration error on OS/2 kLIBC

On Wed, 2022-11-09 at 22:45 +0900, KO Myung-Hun wrote: > OS/2 kLIBC has __strchrnul(). But HAVE___STRCHRNUL is undefined. > 'static' declarion of __strchrnul() causes an error with gcc4 because > OS/2 kLIBC declares __strchrnul() as public. I assume kLIBC is a libc implementation for OS/2? I'm

[bug #63333] Keep running w/o output sync on temp file failure.

Update of bug #6 (project make): Status:None => Fixed Open/Closed:Open => Closed Component Version: SCM => 4.4 Fixed Release:

[bug #63315] Test failures with 4.4 on OpenBSD

Follow-up Comment #8, bug #63315 (project make): Me too, on OmniOS. Presumably Linux will map the shared object back into the same address as before, or has that just been luck? It's definitely not the case on all operating systems. Please consider changing the title of this bug so it's easier

[bug #63315] loadapi test / user-defined function reload SEGV failures

Update of bug #63315 (project make): Operating System:None => POSIX-Based Summary: Test failures with 4.4 on OpenBSD => loadapi test / user-defined function reload SEGV failures ___