Re: Patches for Mingw/MSYS

[heromyth]

Ralf Wildenhues wrote:
> * heromyth wrote on Fri, Jun 17, 2005 at 10:53:59AM CEST:
>
> > Bob Friesenhahn wrote:
> >
> > > On Thu, 16 Jun 2005, Peter Ekberg wrote:
> >
> > In fact, there are two development environment in MSYS Tools of Mingw.
> > One is MINGW, and another is MSYS.
>
>
> Is it possible to have both installed in parallel on the same system,
> so we can test both?  How?
>
> Do you have a config.guess which outputs something containing `msys' in
> the name?  Please show.  Please also show `config.guess --version'.

The more information about Mingw/Msys, maybe you can see here:

    http://www.mingw.org/MinGWiki/index.php/MsysBuildEnvironment
    http://www.mingw.org/MinGWiki/index.php/Build%20MSYS

About config.guess and config.sub, it has nothing about their version.
In config.guess, it just contains these:

    i*:MSYS*:*)
        echo ${UNAME_MACHINE}-pc-msys
        exit 0 ;;

In config.sub, it contains more like these:

        msys)
                basic_machine=i386-pc
                os=-msys
                ;;

In fact, these modifitations that have been done just replace all CYGWIN 
   whith MSYS. That's because of CYGWIN=MSYS.

> > This patch should be done, I think, maybe before more tests have done.
> > There are tow EXE file, if there is no this patch. One is real EXE file
> > existed in subdirctory .libs, and another is just a shell script file
> > which EXTname is EXE and just can be run in Shell(I think the EXE is
> > redundant ).
> >
> > During the tests of automake CVS, I make a test running this:
> >         VERBOSE=yes make check TESTS="nobase.test"
> > If no this patch, this test can't pass. After failed, I run this cmd:
> > 	./libtool --tag=CC   --mode=link gcc  -g -O2   -o sub/base.exe 
> > 	source.o
> >
> > in testSubDir, and I get a file named base(notice no .exe) in
> > testSubDir/sub and another file named base.exe in testSubDir/sub/.libs.
> >
> > Now I run the same command again. This time I also get two file: both
> > are named base.exe. The one in testSubDir/sub is still just a script
> > file. The original base disappears.
> >
> > And run the command again. The result is same to the first running.
> >
> > And run again, the result is same to the second running.
> >
> > And run again, the result just repeat the first tow runnings.
> >         ............
> >
> > If I patch it, this phenomena disappears. Just get base in
> > testSubDir/sub and base.exe in testSubDir/sub/.libs
>
>
> I'm sorry, but I cannot understand most of the above quoted stuff
> precisely.  It would be easier if you could just cut and paste what you
> enter and what is printed.  Programs like `screen' and `script' can help
> with this (but I don't know about their availability for mingw/msys).
>
> Regards,
> Ralf

I just want to say that I get different named executive file when I run 
the same command:

   ./libtool --tag=CC   --mode=link gcc  -g -O2   -o sub/base.exe source.o

Hope these can be helpful:

$ cd savannah/dist-automake/tests/testSubDir
$ ls sub/bas*
sub/base.dat  sub/base.exe  sub/base.h  sub/base.sh

$ ./libtool --tag=CC   --mode=link gcc  -g -O2   -o sub/base.exe source.o
libtool: link: gcc -g -O2 -o sub/.libs/base.exe source.o
libtool: link: creating sub/base.exe

$ ls sub/bas*
sub/base  sub/base.dat  sub/base.h  sub/base.sh

$ ./libtool --tag=CC   --mode=link gcc  -g -O2   -o sub/base.exe source.o
libtool: link: gcc -g -O2 -o sub/.libs/base.exe source.o
libtool: link: creating sub/base.exe

$ ls sub/bas*
sub/base.dat  sub/base.exe  sub/base.h  sub/base.sh

$ ./libtool --tag=CC   --mode=link gcc  -g -O2   -o sub/base.exe source.o
libtool: link: gcc -g -O2 -o sub/.libs/base.exe source.o
libtool: link: creating sub/base.exe

$ ls sub/bas*
sub/base  sub/base.dat  sub/base.h  sub/base.sh