This is the mail archive of the
libstdc++@gcc.gnu.org
mailing list for the libstdc++ project.
Re: `malloc_alloc' not declared
- From: Loren James Rittle <rittle at latour dot rsch dot comm dot mot dot com>
- To: rqiu at innovance dot com
- Cc: libstdc++ at gcc dot gnu dot org
- Date: Mon, 9 Sep 2002 18:02:14 -0500 (CDT)
- Subject: Re: `malloc_alloc' not declared
- References: <EB38D5AB3238D611A91000306E1CE45F4E22D9@postal.innovance.com>
- Reply-to: rittle at labs dot mot dot com
> Thanks for the reply. What does it mean "Any macro that starts
> with __ is in library implementation space..."?
I am afraid that you will have to read the C and C++ standard text to
fully understand. In summary, all macros that begin with:
_[A-Z] and __ are not for users to play with. I.e. you should not be
defining them...
> I couldn't find
> "malloc_alloc" anywhere in libstdc++-v3, and couldn't find relevant
> information
> in the commentary in libstdc++-v3. Can you give me more details?
It appears that Phil (back from the dead ;-), already answered this.
Next issue: this is a pure guess, but it appears that the OS-installed
headers are conflicting with C++ library names. Someone that knows
about your system or you will need to debug this.
Regards,
Loren