Re: gcc -mno-cygwin STL support for setup.exe?

2002-01-18 Thread Jan Nieuwenhuizen

Christopher Faylor [EMAIL PROTECTED] writes:

 The biggest issue with relying on libstdc++.a for for setup.exe is that it
 requires this library to be built for cross-compilation.  I have no idea how
 to do that.

What am I missing?

19:37:40 fred@appel:~$ locate libstdc++.a | grep x-

/home/cygwin/cygwin-1.3.3/linux-x-cygwin/usr/lib/gcc-lib/i686-pc-cygwin/2.95.3-5/libstdc++.a
/home/cygwin/cygwin-1.3.3/linux-x-cygwin/usr/lib/libstdc++.a.2.10.0

/home/cygwin/cygwin-1.3.6/linux-x-cygwin/usr/lib/gcc-lib/i686-pc-cygwin/2.95.3-5/libstdc++.a
/home/cygwin/cygwin-1.3.6/linux-x-cygwin/usr/lib/libstdc++.a.2.10.0

This x-compiles fine here

#include iostream
#include string
int
main ()
{
string s = Hello world;
cout  s  endl;
return 0;
}

Greetings,
Jan.

-- 
Jan Nieuwenhuizen [EMAIL PROTECTED] | GNU LilyPond - The music typesetter
http://www.xs4all.nl/~jantien   | http://www.lilypond.org




Re: gcc -mno-cygwin STL support for setup.exe?

2002-01-18 Thread Christopher Faylor

On Fri, Jan 18, 2002 at 01:59:57PM -0500, Jason Tishler wrote:
 The biggest issue with relying on libstdc++.a for for setup.exe is that it
 requires this library to be built for cross-compilation.  I have no idea how
 to do that.

I don't know either -- this is why I'm asking for help.

I think that was clear.  What I'm trying to say is that it may not be possible to use
functions from libstdc++.a.

In gcc 3.x, this will include things like new() and delete().

cgf



Re: gcc -mno-cygwin STL support for setup.exe?

2002-01-18 Thread Christopher Faylor

On Sat, Jan 19, 2002 at 03:57:24PM +1100, Danny Smith wrote:
For what its worth, 3.1 libsupc++.a  and libstdc++.a build natively with
mingw. (libsupc++.a contains the eh and new/delete stuff that is currently
in libgcc.a for mingw). Locale class support is missing (as it is with
cygwin/newlib), but C-locale works for me. Wide char support is missing,
because of deficiencies in C-runtime. If you want wide char with
-mno-cygwin, you'll need an auxiliary library -- like mingw's [incomplete]
libisocext.a -- to supply  C wide char support.  Iostreams work for char.
 In 3.1 -mno-cygwin needs the mingw32/bits headers.  Also, there may be
differences in the way the C_runtime functions are promoted into namespace
std. 

Hmm.  I haven't been able to build libstdc++ v3 for cygwin for a while.  Maybe
it's just a cross build error.

cgf