This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: [PATH][Ada][=> MINGW32 Please] Fix multilib handling of gnat.dg when RUNTESTFLAGS is used
On Fri, 2009-03-27 at 14:03 +0100, Paolo Bonzini wrote:
> > If I'm not mistaken this patch still needs mingw32 maintainer ok since
> > there was an objection by Ralf on the behaviour of LN_S - but the two
> > mingw32 testers I could find reported success with LN_S so far - and
> > Arnaud ok.
>
> Yeah, and I actually agreed with Ralf. But given the testing results I
> think I will overrule the Windows port maintainers. :-)
Kai was one of the tester, the other one was on IRC.
Ralf, do you have for sure a mingw32 system meeting GCC version
requirement and where LN_S does not behave as the patch needs? Some
questions and notes below.
Thanks in advance,
Laurent
=====
autoconf 2.59 has:
<<
echo >conf$$.file
if ln -s conf$$.file conf$$ 2>/dev/null; then
# We could just check for DJGPP; but this test a) works b) is more
generic
# and c) will remain valid once DJGPP supports symlinks (DJGPP 2.04).
if test -f conf$$.exe; then
# Don't use ln at all; we don't have any links
as_ln_s='cp -p'
else
as_ln_s='ln -s'
fi
elif ln conf$$.file conf$$ 2>/dev/null; then
as_ln_s=ln
else
as_ln_s='cp -p'
fi
rm -f conf$$ conf$$.exe conf$$.file
>>
Is mingw "ln -s" really creating this magic "conf$$.exe" file? If not it
looks like "ln -s" will be used, no? I guess as you mentioned this can
vary with the mingw version, in the current gcc/doc/install.texi we
mention:
<<
GCC will build with and support only MinGW runtime 3.12 and later.
Earlier versions of headers are incompatible with the new default
semantics of @code{extern inline} in @code{-std=c99} and
@code{-std=gnu99} modes.
>>
Do you know since what version "ln" behave as we want? Is by any chance
3.12 ok?
====