This is the mail archive of the
mailing list for the libstdc++ project.
Re: Couldn't build libstdc++ (configure fails)
- To: libstdc++ at sources dot redhat dot com
- Subject: Re: Couldn't build libstdc++ (configure fails)
- From: Loren James Rittle <rittle at latour dot rsch dot comm dot mot dot com>
- Date: Fri, 1 Dec 2000 04:11:34 -0600 (CST)
- CC: loreti at pd dot infn dot it
- References: <Pine.LNX.email@example.com>
- Reply-to: rittle at rsch dot comm dot mot dot com
In article <Pine.LNX.firstname.lastname@example.org>,
Maurizio Loreti <email@example.com> writes:
[Since I know little of Linux... - all Linux-specific stuff removed.]
> In this moment I am performing a "make -k check", and I got:
> - build failures in 20_util/auto_ptr.cc, 23_containers/map_operators.cc,
> - run failures in 27_io/filebuf_members.cc
"No problem": you have as good a build as anyone else does. Those are
all known problems.
> However, I hope the previous info will be usefull to you; I may send the
> files in .../testsuite/, if you need them.
I suspect that there is no need for you to send a full testsuite
report since you are using the same platform as the primary developers
of libstdc++-v3. ;-)
In general (these are my own rules based on past observation):
- Don't send all files from the testsuite directory.
- If you get a new port working or a port's status changes, then send
exactly one file after a build and 'make check' of libstdc++-v3.
Namely, testsuite/*-mkcheck.txt (if you have more than one that
matches that pattern, send the one with the latest date encoded into