For backend C++ with standards compliant STL, I need gcc3. The STL in RH's gcc 2.96.x doesn't seem to be entirely complete. Namely we've had compile time errors using some bitset features.
Ok, so I can compile with gcc3. Now the bad part is that I can't compile the Xerces-C++ v1.5.2 sample programs (DOMPrint, etc.). The library builds fine but then I get a ton of unresolved symbols. I can compile it cleanly with gcc 2.96.x but then of course my C++ STL breaks. Basically this chicken & egg situation is preventing me from porting our app to Linux (or maybe any UNIX variant). I see they released gcc v3.0.2 not too long ago. Any plans to definitely go with gcc v3.x in RHL 8.x? Anyone else in my situation too? Thanks, Tuan On Tue, 20 Nov 2001, E Neigma wrote: > On Monday 19 November 2001 15:27, you wrote: > > On Sun, 18 Nov 2001 22:14:57 -0800 (PST) > > Rudy Ordaz <[EMAIL PROTECTED]> wrote: > > > > > When I installed RH 7.2 I decided to install gcc3 > > > instead of the RH specific gcc (2.96??). > > > > You really should have 2.9x. I don't think 3 compiles everything correctly > > (e.g. the kernel). > > > > I think the kernel's okay (I've seen patches for it), but from what some RH > folk have said pre-ENigma, the will be problems in C++ programs. > > Bugs aside, those problems would be fixed by recompiling everything. > > > > _______________________________________________ > enigma-list mailing list > [EMAIL PROTECTED] > https://listman.redhat.com/mailman/listinfo/enigma-list > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
