https://sourceware.org/bugzilla/show_bug.cgi?id=31527
--- Comment #8 from Simon Cook <simon.cook at embecosm dot com> --- The definition is there (I have the header file), this was a linking issue (and to confirm we are using the same tools to build). I've looked through the Makefile/config.status files for my build, and what seems to be going on is you're able to build GDB because you're building against the python in that environment, and that requires pulling in the shlwapi library: S["PYTHON_LIBS"]="-lpython3.11 -lversion -lshlwapi -lpathcch -lbcrypt -lm -Wl,--stack,2000000" If I configure GDB without python support, then like gas and binutils the __imp_PathIsNetworkPathA symbol is not found. In order to resolve the link issue, I think there are a couple of solutions. 1. Always link anything using libbfd against shlwapi - that feels a bit intrusive for one small change? 2. Implement an alternative to using PathIsNetworkPathA. From its description, I think it might be possible to substitute that call for something like `is_network_path = strncmp(filename, "//", 2) == 0 || strncmp(filename, "\\\\", 2) == 0` since I think that's the behaviour we actually care about. Any thoughts? -- You are receiving this mail because: You are on the CC list for the bug.
