On 21/07/2020 22:02, Keith Marshall wrote: > but make fails: > > CPPFLAGS=-I/mingw/include make > ... > CXXLD gdb.exe > make[3]: Entering directory '/.../gdb-9.2-mingw32-cross-native/gdb' > python//.deps/py-arch.Po:1: *** multiple target patterns. Stop. > make[3]: Leaving directory '/.../gdb-9.2-mingw32-cross-native/gdb' > make[2]: *** [Makefile:1651: all] Error 2 > make[2]: Leaving directory '/.../gdb-9.2-mingw32-cross-native/gdb' > make[1]: *** [Makefile:9571: all-gdb] Error 2 > make[1]: Leaving directory '/.../gdb-9.2-mingw32-cross-native' > make: *** [Makefile:859: all] Error 2 > > What does this mean? I decided to sleep on it, and the penny dropped: by using paths output by the Windows python.exe, with the C: drive prefix in place, and mapped into the Linux file system through a symbolic link called 'C:', make was writing dependency files with extraneous colons in path names, which it then interpreted as (invalid) separators, when it re-read the rules. > How do I fix it? I've kludged around it for now, by manually replacing all instances of 'C:/' with an alternative symlink name, in the generated dependency files, then rerunning make from the point of failure. I'll need to give some more thought to how my win-python script maps path names for header files, and library references; I'm guessing that the 'C:' should be preserved in the 'exec-prefix'. -- Regards, Keith. Public key available from keys.gnupg.net Key fingerprint: C19E C018 1547 DE50 E1D4 8F53 C0AD 36C6 347E 5A3F -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 833 bytes Desc: OpenPGP digital signature URL: <https://lists.osdn.me/mailman/archives/mingw-users/attachments/20200722/f3f41b84/attachment.sig>
Fork