This is the mail archive of the
mailing list for the libstdc++ project.
Re: libstdc++v3 portability problems
- To: Robert Lipe <robertl at sco dot com>
- Subject: Re: libstdc++v3 portability problems
- From: Phil Edwards <pedwards at disaster dot jaj dot com>
- Date: Sat, 9 Dec 2000 19:33:08 -0500
- Cc: gcc at gcc dot gnu dot org, libstdc++ at sources dot redhat dot com
- References: <20001208112705.A18615@rjlhome.sco.com> <20001208150204.A14385@disaster.jaj.com> <20001209144318.A6033@rjlhome.sco.com>
On Sat, Dec 09, 2000 at 02:43:18PM -0600, Robert Lipe wrote:
> Lovely. That should reduce the pain. (Or at least trade it for a known
> form of pain. :-)
Known pain is good. Known pain has corresponding known anesthetics. :-)
> Agreed. That should always be our goal as developers. When we succeed,
> it's great. But I have a suspicion that debugging this stuff in the
> field is going to be a patience-trying experience. We could have
> targets now that must have libtool ported to them before the tree will
> bootstrap. Perhaps that's a necessary cost on the road of progress.
I think so... although once the documentation gets cleaned up, I hope to
add some of these problems to the V3 FAQ. (And maybe the faq-o-matic GCC
FAQ, too -- talk about a patience-trying experience. :-)
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.