This is the mail archive of the
libstdc++@gcc.gnu.org
mailing list for the libstdc++ project.
Re: Compiling w/o gcc?
- To: "David A. Greene" <greened at eecs dot umich dot edu>
- Subject: Re: Compiling w/o gcc?
- From: Benjamin Kosnik <bkoz at redhat dot com>
- Date: Tue, 3 Apr 2001 14:08:44 -0700 (PDT)
- cc: libstdc++ at gcc dot gnu dot org
> I'm having fairly good success working without g++. I've
> had to edit acinclude.m4, some Makefile.am's and so forth as
> well as adding #ifdef __GNUC__'s in some headers.
ok. When you're done, perhaps you'd consider writing up a FAQ entry or
posting some notes for documentation? That would be much appreciated.
> Once concern I have is the interaction with libsupc++. These routines
> are provided by our vendor. Because of the conflict, I've disabled
> building libsupc++ (through an --enable-cxxruntime configure option
> which defaults to libsupc++, similar to the way --enable-cstdio
> works). Obviously this is probably somewhat dangerous. Are there
> any known pitfalls with doing this? It seems to me that as long as
> I have headers that define the necessary bits (I do, from our vendor),
> it should be ok to compile libstdc++ with those and link with the
> vendor's runtime library.
Nice, elegant hack to disable libsupc++, kudos. The #ifdefs in the header
files are less elegant, but perhaps a more acceptable solution can be
created when the sum total of your changes are finished.
You're flying pretty blind right here, but assuming the vendor runtime
and header files work, well then. Your library should work too.
> Am I being extremely naive? Probably. But what the heck, I'm
> learning a whole lot! :)
Aaah well. Glad you're having fun.
-benjamin