This is the mail archive of the libstdc++@sourceware.cygnus.com mailing list for the libstdc++ project.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
> Yes I need to use v3. I've written code that makes use of many > iostreams features that have just been put into the new libstdc++ and > it won't make any sense for me to go back and change them all to hacks > just so I can get it to work with an old library. Be forwarned that iostreams is not in any way, shape, or form ready for production code. I too wish that it was, but the simple truth is that it is not. You may want to get your build of v-3 straightened out, then run some simple test cases by the library before you start off on this noble endeavor. > Also ... out of curiosity I ran make check on my newly built library > ... unlike the pass/fail ratio on the web page (45/2 or something?) > practically all my tests failed! It built and installed fine on my > RH6.0/Intel install. I built gcc-2.95 with egcs-1.1.2 and I built the > library with gcc-2.95. What did I do wrong? As Martin suggests, in the build directory, "make check" generates a "testsuite" directory. Inside that you'll see three files (which may look something like this): -rw-rw-r-- 1 bkoz bkoz 3088 Aug 12 19:36 990812-mkcheck.txt -rw-rw-r-- 1 bkoz bkoz 1269 Aug 12 19:25 990812-mkcheckfiles.txt -rw-rw-r-- 1 bkoz bkoz 198 Aug 12 19:32 990812-mkchecklog.txt the first == results the second == what files to run tests on the third == what went wrong The suggestion is to look at the third file, and see if you can fix it yourself. If not, post to the list. -benjamin
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |