This is the mail archive of the
gcc-help@gcc.gnu.org
mailing list for the GCC project.
Re: How to enable the long long IOSTREAM-OPs (gcc-3.0.1, Unixware 7.0.1)
- To: "Schlick, Jochen" <schlick at comsoft dot de>
- Subject: Re: How to enable the long long IOSTREAM-OPs (gcc-3.0.1, Unixware 7.0.1)
- From: Phil Edwards <pedwards at disaster dot jaj dot com>
- Date: Mon, 1 Oct 2001 11:55:26 -0400
- Cc: gcc-help at gcc dot gnu dot org, libstdc++ at gcc dot gnu dot org
- References: <3BB8460A.543AB5DC@comsoft.de>
On Mon, Oct 01, 2001 at 12:31:38PM +0200, Schlick, Jochen wrote:
> Is it possible to enable (or get to work) the
> iostream operators for long long under Unixware 7.0.1
>
> I tried to use the _GLIBCPP_USE_LONG_LONG define but this
> produces only coredumps.
>
> //////////////testprog.cpp//////////////////////////////////////
> #define _GLIBCPP_USE_LONG_LONG
This isn't the way it works. A bunch of tests are run from the 'configure'
script. The results of those tests determine whether _GLIBCPP_USE_LONG_LONG
is defined or not. If it isn't defined when the library is built, then
you can't use them. Defining it later, in user code, won't work.
The 'long long' extensions are on by default. The next step is to determine
why the configure tests turned them off. If you have your build directory
around, look in the libstdc++-v3 subdirectory for a file named config.log.
Phil
--
"You have to wonder what kind of life you have when your list of personal
rules begins with, '#3: No drowning in your own mucus,' and '#4: Don't
ask what happened to rules 1 and 2.'"