| Summary: | #ifdef around memmem() is invalid. | ||
|---|---|---|---|
| Product: | Portable OpenSSH | Reporter: | balu <balu.gajjala> |
| Component: | Miscellaneous | Assignee: | Assigned to nobody <unassigned-bugs> |
| Status: | CLOSED WORKSFORME | ||
| Severity: | enhancement | CC: | bagajjal, dtucker |
| Priority: | P5 | ||
| Version: | 8.2p1 | ||
| Hardware: | Other | ||
| OS: | Windows 10 | ||
|
Description
balu
2020-04-23 05:12:13 AEST
Nope that's deliberate. HAVE_MEMMEM means you have the function, HAVE_DECL_MEMMEM means you have the function declaration. Over in bug#3102 we found a system that had the function but not the declaration. At least I think that's what was going on. I don't have access to the affected system but the HAVE_DECL_MEMMEM change did apparently fix it. Interesting. If there is a system that doesn't have a declaration but has a definition then the issue is specific to that environment? Is it expected behavior? I guess No? (In reply to balu from comment #2) > Interesting. If there is a system that doesn't have a declaration > but has a definition then the issue is specific to that environment? Like I said I think that's what was going on, but it's not 100% clear (the reporter said they did not have HAVE_MEMMEM, but in that case I would have expected the old "#ifndef HAVE_MEMMEM" to have worked). > Is it expected behavior? I guess No? Well I'd expect a platform to have both declaration and implementation but in the case of having implementation only I'd expect it to cause problems in LP64 platforms. There's a lot of weirdness out there. closing resolved bugs as of 8.6p1 release |