public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: 徐持恒 <chhxu@fiberhome.com.cn>
To: <gcc@gcc.gnu.org>
Subject: How to run gcc test suite in pure mingw32 environment?
Date: Mon, 09 Nov 2009 02:26:00 -0000	[thread overview]
Message-ID: <E313AF66D4DE4B17BC6A851056F9690B@WWW06B9403DCD7> (raw)

Hi,

These days, I’m trying to build gcc-4.4.2 + binutils-2.20 + gmp + mpfr in
Msys+MinGW and Cygwin environment.

The builds on both environments are OK, but I cannot run "make check", or
"make check-gcc".

Finally, I found, that, to run test, you must first install guile, autogen,
tck/tk, expect, dejagnu.
In Msys+MinGW and Cygwin environments, these tools are missing or outdated.
I spend a lot of time to have the latest versions of these packages to be
build and installed in Cygwin, with some patchs applied of course.
Sometimes, I even edit configure.ac file, and run "autoreconf" with the
newest version of autoconf, automake, libtool installed. For expect-5.43.0,
it is even necessary for Cygwin to masquerade as a linux host by specifing
"--host=i686-pc-linux", thus the configure script can run without a
complain.

Having all these tools installed, I found, most of the test results of "make
check" is "fail" in Cygwin environment.

I'm very disappointed with this.

I also spend a lot of time, trying to get these packages installed int
Msys+MinGW environment. But this is too difficult for me.

So, I want to ask, how to run gcc test suite in pure Msys+MinGW environment?

Can the Msys+MinGW use the installed tools in Cygwin to let "make check"
possible ?

Althouth the "gcc + binutils + gmp + mpfr" are ported to pure MinGW
environment, many of the dependent tools are very difficult to port to pure
MinGW environment, because they expect a linux environmemt. But I found,
newlib seems to meet their desire very well. Is't it necessary to port
newlib to pure MinGW environment ? This is much like what cygwin does, but
in a much simpler way. Just to make the necessary gnu tools to be build and
installed.

I think the test environment is very significant.

If we have test environment on Windows platform, we can greatly improve the
development process in this platform ,and ensure the quality of gcc and
companion tools on Windows. I noticed that there are also a MinGW-w64
project, if we have that test environment, we can impove it, even accelerate
it.










Chiheng Xu

Embedded OS Group,
Optical Network Product Division,
Fiberhome Telecommunication Technology Co.,Ltd.,
No.5 Dongxin Road of Guanshan Er Road,Hongshan Dist.,Wuhan,Hubei,P.R.China
Tel:    +86 27 59100296
zipcode: 430073
Email:  chhxu@fiberhome.com.cn




             reply	other threads:[~2009-11-09  2:26 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-09  2:26 徐持恒 [this message]
2009-11-09  6:38 ` Dave Korn
2009-11-09  6:43   ` Kai Tietz
2009-11-09  7:13     ` 答复: " 徐持恒
2009-11-09  7:50       ` Kai Tietz
2009-11-09 14:28       ` Dave Korn
2009-11-09 10:52 ` Kai Ruottu
2009-11-09 11:04   ` Kai Tietz
2009-11-10  2:37     ` 答复: " 徐持恒

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=E313AF66D4DE4B17BC6A851056F9690B@WWW06B9403DCD7 \
    --to=chhxu@fiberhome.com.cn \
    --cc=gcc@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).