URL:
http://savannah.gnu.org/bugs/?34818
Summary: PATH_SEPARATOR_CHAR broken for windows when
cross-compiled
Project: make
Submitted by: sezero
Submitted on: Mon 14 Nov 2011 11:04:23 AM GMT
Severity: 3 - Normal
Follow-up Comment #2, bug #34818 (project make):
A slightly cleaner implementation might have PATH_SEPARATOR_CHAR
defined in the various target-specific config.h files on systems
that don't support autoconf, ...
Autoconf _is_ the problem here, because its PATH_SEP detection is
not
Follow-up Comment #3, bug #34818 (project make):
Maybe I don't understand the context. For typical Windows, VMS, OS2, etc.
builds GNU make doesn't run autotools (as I understand it). It has predefined
config.h variations for those targets and you copy the right one over to
config.h before you
Follow-up Comment #4, bug #34818 (project make):
... For typical Windows, VMS, OS2, etc. builds GNU make doesn't
run autotools (as I understand it).
Well, _need_ not run autotools, if one is lazy or especially when
building on the native OS itself, provided that he has his own
build scripts or
Follow-up Comment #5, bug #34818 (project make):
Gotcha. I didn't realize people were using autotools with Windows targets.
Cross-compiling for a Windows target sounds funky to me but I definitely see
the attraction there :-).
___
Reply
Follow-up Comment #6, bug #34818 (project make):
Cross-compiling for a Windows target sounds funky
to me but I definitely see the attraction there :-)
Yep :)
I, for one, compile 95% of times on linux rather than
on windows or djgpp.
___
