On Sat, Feb 07, 2004 at 07:13:41PM +0100, Georg Baum spake thusly:
> A short summary: you need to install stlport somewhere. Then you invoke
> configure with
>
> ./configure $YOUR_USUAL_OPTIONS --with-extra-inc=/usr/include/stlport
> CXXFLAGS="-DCXX_GLOBAL_CSTD -ftemplate-depth-30 -nostdinc++"
Am Sonntag, 8. Februar 2004 08:51 schrieb Sivan Toledo:
> I'll try the stlport solution. If you have any idea about the linking
> problem, let me know.
I have only one guess: This could be a name mangling problem. Are you sure
that g++ is used for linking and not gcc?
Georg
Hi George, thanks for the tip, I'll try it out.
The problem with gcc3 is that I get link errors at the end, which I
think are bugs in gcc. I looked at the sources and couldn't figure out
why it was generating these references. I'm attaching them below. This
happened with both 3.3.1, which is th
Am Samstag, 7. Februar 2004 15:07 schrieb Angus Leeming:
> Sivan Toledo wrote:
> > I am using 2.95 since I was not able to compile Qt with 3.3.
> >
> There are a number of threads on this ml about the steps that they
> needed to take to get the compiler and STLPort's library working
> happily to
Sivan Toledo wrote:
> A few more details on the crash with the qt-x11+gcc-2.95.3+cygwin
> build that I reported a few days ago.
>
> I traced (with the help of my wife) the crash to the call to
> std:getline in support/filetools.C, and I was able to duplicate the
> crash with a very short program.
A few more details on the crash with the qt-x11+gcc-2.95.3+cygwin build
that I reported a few days ago.
I traced (with the help of my wife) the crash to the call to std:getline
in support/filetools.C, and I was able to duplicate the crash with a
very short program. This happens with gcc-2.95.3
