mathieu <[EMAIL PROTECTED]> writes: > I am running a linux debian stable, let say I install g++3.4, if I > build an executable using this particular I should be garantee that > the binary use a quite old GLIBC API, right ?
There are 2 separate issues: 1. GLIBC API 2. GLIBCXX API The article I referred you to deals only with "issue 1". So far, your users have only hit the "issue 2". I am guessing that as soon as you fix it (by using g++-3.4 to build), your users will start hitting "issue 1" (which can *not* solved by installing any version of gcc). > As a side note, since solution #1 seems to be used internally in > solution #2 (apgc is shipped with some kind of old glibc) Apgcc did not include any old version of glibc last I looked, only cross-compiler does that. Solution #1 is the simplest in terms of what one has to do, provided one has an extra machine laying around [1], and is conceptually simplest to understand. > do you have > any further documentation on how to do that. apgcc is not part of > debian... Huh? Couldn't you just follow instructions on the autopackage pages? Probably start here: http://autopackage.org/download-tools.html > I might eventually try solution #3 as support for cross compilation > seems to be a lot easier when using cmake (http://cmake.org), I'll try > to reproduce what was done there. It is just as trivial to use cross-compiler from "regular" make: instead of "CXX = g++" or "CXX = /usr/local/gcc-3.4/bin/g++", you just do "CXX = /usr/crosstool/gcc-3.4-glibc-2.2/i386-.../bin/i386-..g++" Cheers, [1] Our ancient RedHat-6.2 machine died recently. So we now build on a VMWare RedHat-6.2 image, running "inside" Fedora 7. Despite virtualization overhead, this is still 2 times faster than what the old hardware could do. -- In order to understand recursion you must first understand recursion. Remove /-nsp/ for email. _______________________________________________ help-gplusplus mailing list help-gplusplus@gnu.org http://lists.gnu.org/mailman/listinfo/help-gplusplus
