This is the mail archive of the
libstdc++@gcc.gnu.org
mailing list for the libstdc++ project.
Re: Compiling w/o gcc?
Benjamin Kosnik wrote:
>> I'm having fairly good success working without g++. I've
> 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.
Oh, absolutely. I am documenting things as I go along.
I've got a goodly-sized notebook going. :)
> 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.
Agreed. I'm just wanting to get things working at the moment.
I figure we can edit some to brings things into an acceptable
state.
One issue I've discovered is that our vedor's parser chokes on
some of the template code in basic_string.h. Because the
template declaration specifies _Alloc as a parameter (typedef'd
to allocator_type in the class) and _Alloc also exists as a
member of std::allocator<>, the parser gets confused at the
declaration of _Alloc_hider, thinking that the "const _Alloc &"
parameter in the ctor is an access to the (private)
std::allocator::_Alloc since the template is instantiated with
_Alloc=std::allocator<>.
I believe this is a bug in the parser and I'm going to notify the
vendor. In the meantime, adding more #ifdef's (yep, they'll be
cleaned up) and changing _Alloc to allocator_type solved the
problem. I'm sure I'll run into more of these.
> You're flying pretty blind right here, but assuming the vendor runtime
> and header files work, well then. Your library should work too.
Good. I am flying blind, but I'm pretty used to it at this point.
>> Am I being extremely naive? Probably. But what the heck, I'm
>> learning a whole lot! :)
>
> Aaah well. Glad you're having fun.
Always.
-Dave
--
"Some little people have music in them, but Fats, he was all music,
and you know how big he was." -- James P. Johnson