i'm having problems with OpenGL (JOGL) on mandrake 10.  i'm led to believe
that it's a pain-in-the-a$$ c++ issue.

apparently there are quite a few different binary formats produced by the
gcc 3.x family.  here's an exerpt from
http://gcc.gnu.org/onlinedocs/libstdc++/abi.html showing the application
binary interface versions for gcc (g++)

    * gcc-3.1.0: GLIBCPP_3.1, CXXABI_1
    * gcc-3.1.1: GLIBCPP_3.1, CXXABI_1
    * gcc-3.2.0: GLIBCPP_3.2, CXXABI_1.2
    * gcc-3.2.1: GLIBCPP_3.2.1, CXXABI_1.2
    * gcc-3.2.2: GLIBCPP_3.2.2, CXXABI_1.2
    * gcc-3.2.3: GLIBCPP_3.2.2, CXXABI_1.2
    * gcc-3.3.0: GLIBCPP_3.2.2, CXXABI_1.2.1
    * gcc-3.3.1: GLIBCPP_3.2.3, CXXABI_1.2.1
    * gcc-3.3.2: GLIBCPP_3.2.3, CXXABI_1.2.1
    * gcc-3.3.3: GLIBCPP_3.2.3, CXXABI_1.2.1
    * gcc-3.4.0: GLIBCXX_3.4, CXXABI_1.3
    * gcc-3.4.1: GLIBCXX_3.4.1, CXXABI_1.3

And, don't forget gcc 2.95!

Now, here is the list of requirements from the 1.4.2 release notes:
*  Requirements:
          o i586 compatible system
          o glibc-2.2.5 or newer
          o kernel 2.4.18 or newer
          o XFree 4.2 or newer
          o libstdc++ from gcc-3.2 or newer
               (only needed for the gcc-3.2 Java build)
          o Mozilla 1.0 or newer
              built with gcc-2.95 or gcc-3.2 depending on
              which Java build you use (needed only for the Java Plug-In)

I think this should be corrected to specify exactly which gcc should be
used with blackdown.  From the matrix above, it seems clear that it would
be safest to use only the compiler that blackdown was built with.  This
also implies that all the code that uses CXX will need to have been built
with this compiler.  So if i'm deploying a VRML/HTML site using Xj3D, i'll
need to make sure that the user:

  1) has windows
or
  2) has a linux system built with gcc-2.95 or gcc-3.2.0
        (i'm guessing 3.2.0 is the correct version of 3.2?)

is what i'm saying true?  it seems a bit far-fetched...
i'm building a new linux box tomorrow with gcc-2.95 -- back to the future.


jack


----------------------------------------------------------------------
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to