If gcc-3.4.6 is selected (gcc-config), acroread fails with: /opt/Adobe/Reader9/Reader/intellinux/bin/acroread: /usr/lib/gcc/i686-pc-linux-gnu/3.4.6/libstdc++.so.6: version `GLIBCXX_3.4.5' not found (required by /opt/Adobe/Reader9/Reader/intellinux/bin/acroread) /opt/Adobe/Reader9/Reader/intellinux/bin/acroread: /usr/lib/gcc/i686-pc-linux-gnu/3.4.6/libstdc++.so.6: version `CXXABI_1.3.1' not found (required by /opt/Adobe/Reader9/Reader/intellinux/bin/acroread) /opt/Adobe/Reader9/Reader/intellinux/bin/acroread: /usr/lib/gcc/i686-pc-linux-gnu/3.4.6/libstdc++.so.6: version `CXXABI_1.3.1' not found (required by /opt/Adobe/Reader9/Reader/intellinux/lib/libAGM.so) /opt/Adobe/Reader9/Reader/intellinux/bin/acroread: /usr/lib/gcc/i686-pc-linux-gnu/3.4.6/libstdc++.so.6: version `CXXABI_1.3.1' not found (required by /opt/Adobe/Reader9/Reader/intellinux/lib/libCoolType.so) This can be fixed by: LD_PRELOAD=/usr/lib/gcc/i686-pc-linux-gnu/4.1.2/libstdc++.so acroread or adjusting the script /opt/bin/acroread accordingly. Since acroread is not only used as standalone application but also as browser plugin, this hack spreads. Do you consider this a bug or is gcc-3.4 abandoned? It's still used on hardened AFAIK (although this acroread version might not be supported there). Reproducible: Always Steps to Reproduce:
(In reply to comment #0) > If gcc-3.4.6 is selected (gcc-config), acroread fails with: > /opt/Adobe/Reader9/Reader/intellinux/bin/acroread: > /usr/lib/gcc/i686-pc-linux-gnu/3.4.6/libstdc++.so.6: version `GLIBCXX_3.4.5' > not found (required by /opt/Adobe/Reader9/Reader/intellinux/bin/acroread) > /opt/Adobe/Reader9/Reader/intellinux/bin/acroread: > /usr/lib/gcc/i686-pc-linux-gnu/3.4.6/libstdc++.so.6: version `CXXABI_1.3.1' not > found (required by /opt/Adobe/Reader9/Reader/intellinux/bin/acroread) > /opt/Adobe/Reader9/Reader/intellinux/bin/acroread: > /usr/lib/gcc/i686-pc-linux-gnu/3.4.6/libstdc++.so.6: version `CXXABI_1.3.1' not > found (required by /opt/Adobe/Reader9/Reader/intellinux/lib/libAGM.so) > /opt/Adobe/Reader9/Reader/intellinux/bin/acroread: > /usr/lib/gcc/i686-pc-linux-gnu/3.4.6/libstdc++.so.6: version `CXXABI_1.3.1' not > found (required by /opt/Adobe/Reader9/Reader/intellinux/lib/libCoolType.so) > > This can be fixed by: > LD_PRELOAD=/usr/lib/gcc/i686-pc-linux-gnu/4.1.2/libstdc++.so acroread > or adjusting the script /opt/bin/acroread accordingly. > > Since acroread is not only used as standalone application but also as browser > plugin, this hack spreads. > > Do you consider this a bug or is gcc-3.4 abandoned? > It's still used on hardened AFAIK (although this acroread version might not be > supported there). > > Reproducible: Always > > Steps to Reproduce: > I ve just met this trouble. I try to solve it by replacing LD_PRELOAD value in /opt/bin/acroread but it doesn't work. Can you explain in detail the way to solve it Thnaks
Created attachment 200373 [details, diff] LD_PRELOAD patch for /opt/bin/acroread
You can try the patch above: patch /opt/bin/acroread < acroread.patch
Since we're now up to gcc 4.3 I'd consider this bug invalid. Use that patch if you really have to use gcc 3 :)
We are not up to gcc 4.x. According to /usr/portage/profiles/hardened/package.mask: # Hardened versions of gcc-4.0* through gcc-4.2* are not available. =sys-devel/gcc-4.0* =sys-devel/gcc-4.1* =sys-devel/gcc-4.2* # Mask non-hardened+non-testing gcc-4.3.x releases. =sys-devel/gcc-4.3.2* So please fix acroread or test and mark stable gcc 4.x for x86 and amd64.
(In reply to comment #3) > You can try the patch above: patch /opt/bin/acroread < acroread.patch Provided patch does not work [for me]: thoughtpad bin # patch acroread < acroread.patch patching file acroread Hunk #1 succeeded at 558 (offset -66 lines). thoughtpad ~ $ acroread ERROR: Cannot find installation directory. app-text/acroread 9.1.3 CHOST="i686-pc-linux-gnu" CFLAGS="-O2 -march=i686 -pipe" gcc (GCC) 3.4.6 (Gentoo 3.4.6-r2 p1.6, ssp-3.4.6-1.0, pie-8.7.10)
(In reply to comment #6) > (In reply to comment #3) > > You can try the patch above: patch /opt/bin/acroread < acroread.patch > > Provided patch does not work [for me]: Oops. My own mistake. Please disregard or delete my previous post above... I got mixed up in real files versus symlinks...
