GCC 3.0

[Phil Edwards]

On Tue, Oct 03, 2000 at 01:05:40PM -0400, David Edelsohn wrote:
> >>>>> Joe Buck writes:
> 
> Joe> It seems that most of the problems are associated with the wide characters
> Joe> and locales.  Perhaps have some #ifdef that takes that out on platforms
> Joe> where it doesn't work yet?  We can then test everything else.
> 
> Joe> Or am I missing something?
> 
> 	Shared libraries.
> 	Thread support.
> 	Atomicity.
> 	ctype.

The library does have some --enable/disable flags to help in porting these
kinds of things.  Essentially:  for a new host, disable them all and just
make certain that the library will build.  Then re-enable them one at
a time.  For the points above, we have --disable-shared, --disable-threads,
and --disable-wchar.

Working with glibc 2.2 still presents problems due to the #inclusion of
at least one header that doesn't exist everywhere, or exists but doesn't
define the things which glibc assumes it does.


> 	Bad interaction with vendor headers (_POSIX_SOURCE, _XOPEN_SOURCE, ...)

The library also has a generic --enable-cxx-flags which can pass around
arbitrary compiler flags.  There are serious caveats when using this method,
but it occasionally helps.

Phil

-- 
pedwards at disaster dot jaj dot com  |  pme at sources dot redhat dot com
devphil at several other less interesting addresses in various dot domains
The gods do not protect fools.  Fools are protected by more capable fools.