actually, it's less (was RE: build more-or-less successful)

["Edwards, Phil" <pedwards@ball.com>]

+ | This was using CVS source from Sunday afternoon (about 
+ | twenty hours ago).
+ | All was well but for one problem towards the end; the file
+ | src/limitsMEMBERS.cc doesn't get copied into the build directory.
+ 
+ hum... I don't think we need to copy that file into the build
+ directory.  Does it cause the build to fail on your system?

Yep.  There's a break in the transcript I attached, where make dies because
it doesn't know how to create limitsMEMBERS.cc.  After copying the file the
build can pick back up.

As it happens, something is still missing.  All is installed fine, but there
are missing symbols when a link as attempted that uses the library.  With
the same EGCS snapshot (19990502) using v3 and -static, I get

/home/pedwards/3/lib/libstdc++.a(stringMAIN.o): In function
`allocator<char>::allocator(void)':
/home/pedwards/b/src/../../libstdc++/bits/basic_string.h(.void
basic_string<char, char_traits<char>, allocator<char>
>::gnu.linkonce.t._S_copy_chars<__normal_iterator<char const *,
basic_string<char, char_traits<char>, allocator<char> > > >(char *,
__normal_iterator<char const *, basic_string<char, char_traits<char>,
allocator<char> > >, __normal_iterator<char const *, basic_string<char,
char_traits<char>, allocator<char> > >)+0x22): undefined reference to `bool
operator!=<char const *, char const *, basic_string<char, char_traits<char>,
allocator<char> > >(__normal_iterator<char const *, basic_string<char,
char_traits<char>, allocator<char> > > const &, __normal_iterator<char const
*, basic_string<char, char_traits<char>, allocator<char> > > const &)'
collect2: ld returned 1 exit status

(The /home/pedwards/b/src/../../libstdc++/ thing is a bit disturbing and
uninformative, since neither of those directories exist now.  The usual
build-path-in-the-binary thing, I guess.)

Without -static, a different error appears (not included here because I
think it may be this specific system; I didn't look closely).  Using v2
works fine in any case.  After I finish some "real job" work I'm going to
dive into the template parameter mess o' errors and poke around some more.


Phil