Re: Help compiling 4.3.0

2 msg	Linking problem gcj and c++
2 msg	Error building gcc/g++ 4.1.1 on AIX 5.2
6 msg	Optimizing constructors/destructors for embedde...

Help compiling 4.3.0
\ Lee Rhodes (25 Jun 2007)
. \ Brian Dessent (25 Jun 2007)
. . \ Tim Prince (25 Jun 2007)
. . . \ Lee Rhodes (25 Jun 2007)
. . . . \ Brian Dessent (25 Jun 2007)
. . . . . \ Lee Rhodes (25 Jun 2007)
. . . . . . \ Brian Dessent (25 Jun 2007)
. \ Timothy C Prince (25 Jun 2007)

2 msg	GCC with __asm__ generic temporary register query
5 msg	Does GCC assign any type to enums that can be s...
1 msg	Macros for function definitions/calls
8 msg	typedef conflict in GCC and JAVA
1 msg	does gcc 2.95.3 support softfloat ?
17 msg	Help compiling gcc 4.2.0
2 msg	Fwd: Locale problem / debugging libstdc++
2 msg	arm-elf make check fixincludes failures
1 msg	reordering of passes
3 msg	From what versions of binutils, gcc, and glibc ...
4 msg	Help configuring gcc
12 msg	constructors/destructors compiled twice
4 msg	Problem building 4.2.0 on Solaris 10 (SPARC)
2 msg	building/installing GCC and crtx.o's confusion
1 msg	mul instruction
1 msg	GCC 4.2.0: optimisation appears to break C++ co...

Subject:	Re: Help compiling 4.3.0
Group:	Gcc-help
From:	Timothy C Prince
Date:	25 Jun 2007

-----Original Message-----
From: "Lee Rhodes" <lee>
To: <gcc-help>, <brian>
Date: Mon, 25 Jun 2007 11:24:08 -0700
Subject: Help compiling 4.3.0

I didn't build with libgomp (openMP) or libmudflap (bounds checking for
c), and I am wondering if I should have, but I am not sure of the
consequences.

1. Does the absense of libmudflap prevent optional bounds checking in C++?
2. Does the absense of libgomp prevent thread programming?

If I need to rebuild using these libraries, where do I get them?
I couldn't find them in cygwin setup.

________________________________
You don't need any C++ or libgomp components from cygwin to include these libraries in your new build.
I think about everyone has disabled mudflap for cygwin, as it seems to work poorly.
libgomp isn't enabled by default, as it is for linux. I supposed that was on account of the fairly high error rate, yet I thought it worked often enough to be worth testing. Leaving it out doesn't disable explicit threading, simply prevents the -fopenmp option from working. Configure option --enable-threads takes care of enabling an explicit threading library.

Tim Prince