Farid Zaripov wrote:
[...]
Fix #2 -- Your /stdcxx-4.2.2/build file:
I renamed the /stdcxx-4.2.2/build file that came with the svn download, to
/stdcxx-4.2.1/build_faridz, because the presence of the build FILE was
preventing the GNUmakefile from creating the /stdcxx-4.2.2/build/ DIRECTORY.
Farid Zaripov wrote:
Although it probably shouldn't be called liblibstd, should it?
What's with the duplicate lib part?
I think you should know, that the library file located in lib subdirectory ;)
I suppose that there missed '/' after the first 'lib':
/stdcxx-4.2.2/build/lib/libstd.a
Steve Petrie, P.Eng. wrote:
[...]
I use the following MSYS console shell command, to compile the
test_stdcxx_1.cpp program:
g++.exe -I./include -nostdinc++ -nostdinc -nostdlib -c -o test_stdcxx_1.o
test_stdcxx_1.cpp
You also need -I./include/ansi. Its also a good idea to avoid
using the g++
On Sun, Apr 26, 2009 at 11:28 PM, Peter Lee peter.lee@gmail.com wrote:
Hello guys,
I would like to know where/how the information about, which projects are
based on STDXX, can be gained.
Regards
P
We don't have such a list. I would certainly be interested in finding out
what projects
Sun C++ 5.1 is ages old. IIRC, the first version of Sun C++ after
5.0 that an old version of the library was ported to (2.2?) with
some success was 5.2 or perhaps even later. The problem is unlikely
to be in stdcxx but rather in the compiler itself.
If you must stay with this old compiler then
On 04/07/2010 09:29 AM, Bailey, Kendall wrote:
Ah, perhaps it's my mistake. CC -V reports a version of 5.10, not 5.1. I
must have left off the zero. I haven't used Sun C++ for ages, so I didn't realize my mistake until
you pointed it out.
Actually, you state
if (__errtmp !=
