This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: PING [4.1 regression, patch] build i686-pc-mingw32
> Is that actually true, though? Doesn't GNU ld try to locate files
> relative to its invoked path?
Sometimes, for sysroots and ldscripts. I wouldn't expect MinGW (or
any native linker) to use this feature. GCC usually passes ld
whatever path specifications it needs.
> Since we know that mingw uses GNU ld couldn't we prewire this action
> into configure by default and avoid the need for this kind of
> system-specific behavior in the makefile?
A thought occurs to me... we *know* how to build build-system
executables, like gen*.exe. Why can't we have small C programs that
know where as/ld are, know how to exec them portably (libiberty), etc?
That gives us the functionality of symlinks even on platforms like
MinGW that support neither symlinks nor shell scripts, without the
nasty side effects of using cp or symlinks.
Heck, it can even search $PATH for us.