diff options
Diffstat (limited to 'doc/gettext/el/gcc-upgrading.xml.po')
| -rw-r--r-- | doc/gettext/el/gcc-upgrading.xml.po | 639 |
1 files changed, 151 insertions, 488 deletions
diff --git a/doc/gettext/el/gcc-upgrading.xml.po b/doc/gettext/el/gcc-upgrading.xml.po index 006108e..8bcced3 100644 --- a/doc/gettext/el/gcc-upgrading.xml.po +++ b/doc/gettext/el/gcc-upgrading.xml.po @@ -1,7 +1,7 @@ msgid "" msgstr "" "Project-Id-Version: PACKAGE VERSION\n" -"POT-Creation-Date: 2011-09-05 14:12+0600\n" +"POT-Creation-Date: 2011-10-28 22:38+0600\n" "PO-Revision-Date: 2010-10-21 23:56+0600\n" "Last-Translator: Automatically generated\n" "Language-Team: none\n" @@ -16,615 +16,278 @@ msgid "Gentoo GCC Upgrade Guide" msgstr "" #: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(author:title):9 -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(author:title):12 msgid "Author" msgstr "" #: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(mail:link):10 -msgid "amne@gentoo.org" +msgid "swift" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(mail):10 -msgid "Wernfried Haas" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(mail:link):13 -msgid "jkt@gentoo.org" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(mail):13 -msgid "Jan Kundrát" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(author:title):15 -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(author:title):18 -msgid "Editor" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(mail:link):16 -msgid "halcy0n" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(mail:link):19 -msgid "nightmorph" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(abstract):22 +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(abstract):13 msgid "This document will guide the user through the process of upgrading GCC." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(version):30 -msgid "23" +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(version):21 +msgid "25" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(date):31 -msgid "2008-07-19" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(title):34 -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(title):80 -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(title):167 -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(title):333 -msgid "Introduction" +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(date):22 +msgid "2011-10-15" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(title):36 -msgid "GCC Upgrading" +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(title):25 +msgid "Quickstart" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(p):39 -msgid "" -"Why should you upgrade? Well, GCC is quite similar to any other package on " -"your system, just a bit more critical. You should upgrade GCC whenever a new " -"version fixes some bug that annoys you, new functionality you need is " -"introduced, or if you want to keep your system up-to-date. If none of the " -"previous cases apply to you, you can safely postpone upgrade as long as your " -"GCC version is supported by Gentoo developers." -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(p):48 -msgid "" -"If you install a new major version of GCC (such as 3.3.6 to 3.4.5), the " -"system will not switch over to use it automatically. You'll have to " -"explicitly request the change because the migration process might require " -"some additional steps. If you decide not to switch, Portage will continue to " -"use older version of your compiler until you change your mind, or remove the " -"old compiler from the system. Non-major gcc upgrades are switched " -"automatically for you (such as 3.4.5 to 3.4.6)." -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(p):58 -msgid "" -"This guide will document the necessary steps required to perform a seamless " -"upgrade of the compiler used by your Gentoo box. A specific section is " -"dedicated to the <uri link=\"#upgrade-3.3-to-3.4\">upgrade from GCC 3.3 to " -"3.4</uri> and issues with <c>libstdc++</c>. A second specific section is for " -"users <uri link=\"#first-install\">first installing</uri> Gentoo using a " -"stage3 tarball, after a new GCC major/minor version has been released." -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(warn):67 -msgid "" -"It should be noted that upgrading from GCC-3.4 (or 3.3) to GCC-4.1 or " -"greater still requires you to follow the <uri link=\"#upgrade-general" -"\">general upgrading instructions</uri>, as GCC-3.4 and GCC-4.1 use slightly " -"different ABIs." -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(title):78 -msgid "General Upgrade Instructions" +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(title):27 +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(title):84 +msgid "Introduction" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(impo):83 +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(p):30 msgid "" -"If you're looking for instructions specific to upgrades from GCC-3.3 to " -"GCC-3.4, please consult the <uri link=\"#upgrade-3.3-to-3.4\">dedicated " -"section</uri>." +"This is about <e>upgrading</e> GCC. Downgrading GCC might have unwanted side " +"effects. Please refer to <uri link=\"#troubleshooting\">Troubleshooting</" +"uri> for some commonly reported issues." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(impo):89 +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(p):36 msgid "" -"If you're looking for instructions specific to upgrades in GCC for new " -"installs, please consult the <uri link=\"#first-install\">dedicated section</" -"uri>." +"The next section gives a quick primer into GCC upgrades (and how easy they " +"are). If you want to read the lengthy reasoning behind GCC upgrades, please " +"continue with <uri link=\"#explanation\">GCC Upgrading Explained</uri>." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(p):95 -msgid "" -"Generally speaking, upgrades to <e>bug fix releases</e>, like from 3.3.5 to " -"3.3.6, should be quite safe -- just emerge new version, switch your system " -"to use it and rebuild the only affected package, <c>libtool</c>. However, " -"some GCC upgrades break binary compatibility; in such cases a rebuild of the " -"affected packages (or even whole toolchain and system) might be required." +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(title):45 +msgid "Short Version" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(p):103 +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(p):48 msgid "" -"When we spoke about the need to switch your compiler to the newer version by " -"hand, we said it won't happen automatically. However, there is one exception " -"-- upgrades to bug fix releases, like from 3.3.5 to 3.3.6 in case you don't " -"use the \"multislot\" feature allowing them to coexist on one system. " -"Multislot is disabled by default as the majority of users won't benefit from " -"it." +"If you are upgrading GCC then you do not need to do anything except switch " +"compiler version and rebuild libtool:" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(pre:caption):111 -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(pre:caption):278 -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(pre:caption):366 -msgid "Upgrading GCC" +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(pre:caption):53 +msgid "Switching GCC version" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(pre):111 +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(pre):53 #, no-wrap msgid "" "\n" -"# <i>emerge -uav gcc</i>\n" +"# <i>emerge -u gcc</i>\n" +"# <i>gcc-config -l</i>\n" +"[1] i686-pc-linux-gnu-4.4.5 *\n" +"[2] i686-pc-linux-gnu-4.5.3\n" "\n" -"<comment>(Please substitute \"i686-pc-linux-gnu-4.1.1\" with the GCC\n" -"version and CHOST settings you've upgraded to:)</comment>\n" -"# <i>gcc-config i686-pc-linux-gnu-4.1.1</i>\n" +"# <i>gcc-config 2</i>\n" "# <i>env-update && source /etc/profile</i>\n" -"\n" -"<comment>If you upgraded from gcc 3 to 4 (e.g. from 3.4.6 to 4.1.1 in this\n" -"example) you will have to run fix_libtool_files.sh manually</comment>\n" -"<comment>(Replace $CHOST with your actual CHOST, found in /etc/make.conf)</comment>\n" -"<comment>(Replace <gcc-version> with your new, updated GCC version)</comment>\n" -"# <i>/usr/share/gcc-data/$CHOST/<gcc-version>/fix_libtool_files.sh 3.4.6</i>\n" -"\n" -"<comment>(Rebuilding libtool)</comment>\n" -"# <i>emerge --oneshot -av libtool</i>\n" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(p):129 -msgid "" -"To be completely safe that your system is in a sane state, you <e>must</e> " -"rebuild the toolchain and then world to make use of the new compiler." -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(pre:caption):134 -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(pre:caption):433 -msgid "Rebuilding system" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(pre):134 -#, no-wrap -msgid "" -"\n" -"# <i>emerge -eav system</i>\n" -"# <i>emerge -eav world</i>\n" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(p):139 -msgid "" -"It is safe to remove the older GCC version at this time. If you feel the " -"need, please issue the following command (as usual, substitute <c>=sys-devel/" -"gcc-3.4*</c> with the version you want to uninstall):" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(pre:caption):145 -msgid "Removing older GCC version" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(pre):145 -#, no-wrap -msgid "" -"\n" -"# <i>emerge -aC =sys-devel/gcc-3.4*</i>\n" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(impo):149 -msgid "" -"Please note that the GCC 4.1 and newer can compile only kernels newer than " -"2.4.34. Don't remove your old GCC version if you want to use an older kernel." -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(impo):154 -msgid "" -"In case you're upgrading from GCC-3.3, you should run <c>emerge --oneshot " -"sys-libs/libstdc++-v3</c> to provide compatibility with older binary C++ " -"applications." -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(title):165 -msgid "Upgrading from GCC-3.3 to 3.4" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(p):170 -msgid "" -"The upgrade from GCC-3.3 to 3.4 is not seamless as the C++ ABI changed " -"between these two versions. There is an issue with the <c>libstdc++</c> " -"library which must be taken care of, as well." -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(title):179 -msgid "The Choices" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(impo):182 -msgid "" -"If you upgrade from gcc 3.4 to 4.1, please consult the <uri link=\"#upgrade-" -"general\">General Update instructions</uri>." -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(impo):187 -msgid "" -"If you're upgrading on a SPARC machine, you will have to take the way of " -"<uri link=\"#upgrade-3.3-to-3.4-emerge-e\">complete system rebuild</uri> due " -"to some internal <uri link=\"http://gcc.gnu.org/gcc-3.4/sparc-abi.html\">ABI " -"changes</uri> in GCC's parameter passing." +"# <i>emerge --oneshot libtool</i>\n" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(p):194 +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(p):64 msgid "" -"If you upgrade from gcc 3.3 to 3.4, you have two possibilities on how to " -"upgrade your system. The <uri link=\"#upgrade-3.3-to-3.4-revdep-rebuild" -"\">first method</uri> is faster and requires use of the <c>revdep-rebuild</" -"c> tool from package <c>gentoolkit</c> while the <uri link=\"#upgrade-3.3-" -"to-3.4-emerge-e\">second one</uri> rebuilds the entire system from scratch " -"so it will make use of new GCC features. It's up to you to decide which of " -"these two ways you will choose. In most cases, the first method is " -"sufficient." +"If you upgrade GCC from a version earlier than 3.4.0 (for the 3.x series) or " +"4.1, you will need to run <c>revdep-rebuild</c> as well:" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(p):205 -msgid "" -"If you upgrade from gcc 3.3 to 4.1, do not use the method based on revdep-" -"rebuild, but do a <uri link=\"#upgrade-3.3-to-3.4-emerge-e\">complete system " -"rebuild</uri>." -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(title):214 -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(pre:caption):242 -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(title):390 -msgid "Using revdep-rebuild" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(p):217 -msgid "" -"This method requires that you first install <c>gentoolkit</c> if you have " -"not already done so. Then we will upgrade GCC and switch to the new " -"compiler. We will also rebuild the <c>libtool</c> package to ensure that " -"toolchain is in healthy state." -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(pre:caption):224 -msgid "Installing gentoolkit and upgrading GCC" +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(pre:caption):69 +msgid "Upgrading from a non-forward compatible GCC version" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(pre):224 +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(pre):69 +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(pre):135 #, no-wrap msgid "" "\n" -"# <i>emerge -an gentoolkit</i>\n" -"# <i>emerge -uav gcc</i>\n" -"<comment>(Please substitute \"i686-pc-linux-gnu-3.4.5\" with the GCC\n" -"version and CHOST settings you've upgraded to:)</comment>\n" -"# <i>gcc-config i686-pc-linux-gnu-3.4.5</i>\n" -"# <i>source /etc/profile</i>\n" -"\n" -"<comment>(Rebuilding libtool)</comment>\n" -"# <i>emerge --oneshot -av libtool</i>\n" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(p):236 -msgid "" -"Now, we want to see which packages that revdep-rebuild will want to rebuild. " -"Then we will tell revdep-rebuild to actually rebuild the packages. This may " -"take some time, so have some patience." -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(pre):242 -#, no-wrap -msgid "" -"\n" -"# <i>revdep-rebuild --library libstdc++.so.5 -- -p -v</i>\n" "# <i>revdep-rebuild --library libstdc++.so.5</i>\n" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(note):247 -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(note):405 -msgid "" -"It is possible that you might have problems with non-existing package " -"versions due to them being outdated or masked. If this is the case, you will " -"want to use the <c>--package-names</c> option to <c>revdep-rebuild</c>. This " -"causes packages to be recompiled based on the package name, rather than the " -"exact name and version." +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(p):73 +msgid "There you go. Enjoy the new compiler!" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(p):255 -msgid "" -"To provide compatibility with older binary C++ applications and any packages " -"that revdep-rebuild might have missed, <c>sys-libs/libstdc++-v3</c> needs to " -"be merged before you unmerge GCC 3.3 from your system." +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(title):82 +msgid "GCC Upgrading Explained" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(pre:caption):261 -msgid "Installing libstdc++-v3 and cleaning up" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(pre):261 -#, no-wrap +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(p):87 msgid "" -"\n" -"# <i>emerge --oneshot sys-libs/libstdc++-v3</i>\n" -"# <i>emerge -aC =sys-devel/gcc-3.3*</i>\n" +"GCC upgrading has always been mystified, with suggestions ranging from \"You " +"do not need to do anything\" up to \"You will need to rebuild your entire " +"system twice\". Most of this FUD comes from the confusion surrounding ABI " +"incompatibility. But first a quick pointer towards <c>libtool</c>." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(title):269 -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(title):416 -msgid "Using emerge -e" +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(title):97 +msgid "libtool and fix_libtool_files.sh" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(p):272 +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(p):100 msgid "" -"This method, while much slower, will rebuild your whole system to ensure " -"that everything has been rebuilt with your new compiler, and therefore " -"safer. At first, you will upgrade GCC and libtool and switch to your new " -"compiler." -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(pre):278 -#, no-wrap -msgid "" -"\n" -"# <i>emerge -uav gcc</i>\n" -"<comment>(Please substitute \"i686-pc-linux-gnu-3.4.5\" with the GCC\n" -"version and CHOST settings you've upgraded to:)</comment>\n" -"# <i>gcc-config i686-pc-linux-gnu-3.4.5</i>\n" -"# <i>source /etc/profile</i>\n" -"\n" -"<comment>If you upgraded from gcc 3 to 4 (e.g. from 3.3.6 to 4.1.1 in this\n" -"example) you will have to run fix_libtool_files.sh manually</comment>\n" -"<comment>(Replace $CHOST with your actual CHOST, found in /etc/make.conf)</comment>\n" -"<comment>(Replace <gcc-version> with your new, updated GCC version)</comment>\n" -"# <i>/usr/share/gcc-data/$CHOST/<gcc-version>/fix_libtool_files.sh 3.3.6</i>\n" -"\n" -"<comment>(Rebuilding libtool)</comment>\n" -"# <i>emerge --oneshot -av libtool</i>\n" +"Earlier installments of GCC on Gentoo required you to run a specific command " +"called <c>fix_libtool_files.sh</c>. Some time ago, the execution of this " +"command has been integrated in the package deployments itself (through the " +"toolchain eclass) so there is no need for users to call this themselves " +"anymore." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(p):295 -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(p):377 +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(p):107 msgid "" -"To provide compatibility with older binary C++ applications, <c>sys-libs/" -"libstdc++-v3</c> needs to be merged onto your system." +"The reason we need to rebuild libtool after the upgrade of gcc versions is " +"because of its main purpose: <e>libtool</e> is a toolset that aggregates " +"platform-specific code in a generic interface, allowing applications to " +"build against shared libraries without needing to deal with the platform " +"specific aspects of shared libraries. To fulfill its function properly, the " +"<c>libtool</c> script uses various library locations that have hardcoded GCC " +"version information in them." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(pre:caption):300 -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(pre:caption):382 -msgid "Installing libstdc++-v3" +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(title):120 +msgid "ABI Changes" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(pre):300 -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(pre):382 -#, no-wrap +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(p):123 msgid "" -"\n" -"# <i>emerge --oneshot sys-libs/libstdc++-v3</i>\n" +"An ABI, or <e>Application Binary Interface</e>, is a set of conventions used " +"by all tools that deal with binary representation of programs, including " +"compilers, assemblers, linkers and language runtime support (source: <uri " +"link=\"http://gcc.gnu.org/onlinedocs/gcc/Compatibility.html\">GCC Binary " +"Compatibility</uri>). When the ABI used for binary applications and " +"libraries is changed, you will risk getting linker errors or malfunctioning " +"programs unless you rebuild all libraries that use C++ code. Yes, C++, since " +"most incompatibilities occur within the C++ ABI. This is also why we use the " +"<c>revdep-rebuild</c> command against the <path>libstdc++.so.5</path> " +"library." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(p):304 -msgid "" -"Now we will go about first rebuilding the system target, then the world " -"target. This will take a very long time, depending on the number of packages " -"that you have installed, as it will rebuild your entire toolchain and " -"supporting system files, followed by every package on your system, including " -"the toolchain. This is necessary to ensure that all packages have been " -"compiled with the new toolchain, including the toolchain itself." +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(pre:caption):135 +msgid "Rebuilding applications linked against libstdc++.so.5" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(pre:caption):313 -msgid "Rebuilding system and world" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(pre):313 -#, no-wrap -msgid "" -"\n" -"# <i>emerge -e system</i>\n" -"# <i>emerge -e world</i>\n" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(p):318 -msgid "It is also safe to remove older GCC versions at this time:" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(pre:caption):322 -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(title):440 -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(pre:caption):448 -msgid "Cleaning up" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(pre):322 -#, no-wrap +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(p):139 msgid "" -"\n" -"# <i>emerge -aC =sys-devel/gcc-3.3*</i>\n" +"So why is this only needed up to GCC 3.4.0/4.1 ? That's because from that " +"version onwards, GCC uses a forward compatible ABI, which removes the need " +"for rebuilding applications and libraries. Of course, guarantees can never " +"be given indefinitely, but when an incompatibility occurs again, we'll " +"definitely document it here ;-) In that case, the version of the " +"<path>libstdc++.so</path> library will probably be increased." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(title):331 -msgid "Upgrading to GCC on a First Install" +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(title):151 +msgid "Rebuilding Everything" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(p):336 +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(p):154 msgid "" -"A GCC upgrade on a system after installation from a stage3 tarball is a " -"simple affair. One advantage users of new installations have is they do not " -"have a plethora of software installed that links against the older version " -"of GCC. The following example is for a GCC-3.3 to 3.4 upgrade. Certain parts " -"will be different if upgrading from other versions of GCC. For example, the " -"library names used for <c>revdep-rebuild</c> below are GCC 3.3 specific, as " -"well as the need to install <c>libstdc++-v3</c>." +"Some people swear that they need to rebuild every single package on their " +"system when a new GCC version is made available. Of course, that doesn't " +"make sense, since there are many applications that are not using GCC for " +"their build and install process anyhow, so they would never be affected by " +"such changes." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(p):346 -msgid "" -"If a user has not made any customizations to their system yet, then there " -"are very few steps to get their system upgraded to a new GCC version. As " -"with the GCC-3.3 to 3.4 upgrade, the user has a couple options. However, " -"unlike the GCC-3.3 to 3.4 upgrade, this one is less complicated as there are " -"fewer differences between the methods. The <uri link=\"#first-install-revdep-" -"rebuild\">first method</uri> is faster and makes use of the <c>revdep-" -"rebuild</c> tool from <c>gentoolkit</c>, similar to the above procedure. " -"Using revdep-rebuild causes only packages which actually link against GCC " -"libraries to be rebuilt, while the <uri link=\"#first-install-emerge-e" -"\">second method</uri> causes your entire new install to be recompiled with " -"the new GCC version and takes much longer. This second method is never " -"required and only documented for completeness." -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(p):361 +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(p):161 msgid "" -"These first steps are common between both methods, and should be completed " -"by everyone." +"That however doesn't mean they are completely incorrect: newer GCC versions " +"often include better support for the processors' instruction set, which " +"might influence the performance of some applications in a positive way. " +"Although it is expected that this improvement is generally only marginally, " +"in some cases (especially CPU intensive applications) this might yield " +"notable improvements." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(pre):366 -#, no-wrap +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(p):169 msgid "" -"\n" -"# <i>emerge -uav gcc</i>\n" -"<comment>(Please substitute \"i686-pc-linux-gnu-3.4.5\" with the GCC\n" -"version and CHOST settings you've upgraded to:)</comment>\n" -"# <i>gcc-config i686-pc-linux-gnu-3.4.5</i>\n" -"# <i>source /etc/profile</i>\n" -"\n" -"<comment>(Rebuilding libtool)</comment>\n" -"# <i>emerge --oneshot -av libtool</i>\n" +"There are also known cases where packages need to be built with the same " +"compiler. Although these packages are usually bumped by Gentoo " +"simultaneously (so that they are always built with the same GCC version) " +"cherry-picking reinstalls on these packages might prove to be troublesome. " +"The various <path>qt-*</path> packages are a nice example on this matter." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(p):393 -msgid "" -"This method requires that you first install <c>gentoolkit</c> if you have " -"not already done so. We will then run <c>revdep-rebuild</c> to actually scan " -"the installed packages for ones we need to rebuild, then rebuild them." -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(pre:caption):399 -msgid "Installing gentoolkit and running revdep-rebuild" +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(title):182 +msgid "Troubleshooting" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(pre):399 -#, no-wrap -msgid "" -"\n" -"# <i>emerge -an gentoolkit</i>\n" -"# <i>revdep-rebuild --library libstdc++.so.5 -- -p -v</i>\n" -"# <i>revdep-rebuild --library libstdc++.so.5</i>\n" +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(title):184 +msgid "libstdc++.so.6: version `GLIBCXX_3.4.15' not found" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(p):419 -msgid "" -"This method, while much slower, will rebuild the system target to ensure " -"that everything has been rebuilt with your new compiler. This is not " -"necessary, but is valid if you are also making changes to CFLAGS or other " -"make.conf variables that will affect the system compile." +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(p):187 +msgid "During updates, you might encounter an error like the following:" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(p):426 -msgid "" -"Since we are performing these actions after an initial installation, we do " -"not need to recompile the <c>world</c> target as we would when doing an " -"upgrade on an already installed system. However, you may choose to perform a " -"world update in place of the system update, to ensure that all packages are " -"updated." +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(pre:caption):191 +msgid "GLIBCXX_x.y.z not found" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(pre):433 +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(pre):191 #, no-wrap msgid "" "\n" -"# <i>emerge -e system</i>\n" +"cmake_bootstrap_28021_test: /usr/lib/gcc/i486-pc-linux-gnu/4.1.2/libstdc++.so.6:\n" +"version `GLIBCXX_3.4.11' not found \n" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(p):443 -msgid "" -"It is also safe to remove older GCC versions at this time. Please substitute " -"<c>YOUR-NEW-GCC-VERSION</c> with the actual version you've upgraded to:" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(pre):448 -#, no-wrap +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(p):196 msgid "" -"\n" -"# <i>emerge -aC \"<sys-devel/gcc-YOUR-NEW-GCC-VERSION\"</i>\n" +"This means that you are trying to build a package with an <e>older</e> GCC " +"version than with which some depending libraries were built. Remember when " +"we told that the C++ ABI if forward-compatible? That is true, but it ensures " +"only that <e>higher</e> (or same) GCC versions can be used when building " +"applications and linking libraries (compared to the GCC version used to " +"build those libraries)." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(title):457 -msgid "Common Pitfalls" +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(title):208 +msgid "Which packages are known to need a rebuild?" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(p):461 +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(p):211 msgid "" -"It's important to disable <c>distcc</c> during upgrade. Mixing compiler " -"versions on your nodes <e>will</e> cause build issues. This is not required " -"for ccache, as the cache objects will be invalidated anyway." +"The following table gives the packages that, <e>if installed</e>, need to be " +"rebuild and why." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(p):467 -msgid "" -"Always use same GCC version for your kernel and additional kernel modules. " -"Once you rebuild your world with new GCC, external modules (like <c>app-" -"emulation/qemu-softmmu</c>) will fail to load. Please rebuild your kernel " -"with the new GCC to fix that." +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(th):218 +msgid "Package" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(p):474 -msgid "" -"If you're upgrading on a SPARC machine, make sure to rerun <c>silo -f</c> " -"after re-emerging world to avoid possible issues." +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(th):219 +msgid "Rebuild needed because ..." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(title):482 -msgid "Frequent Error Messages" +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(ti):222 +msgid "sys-devel/libtool" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(p):485 -msgid "" -"If your system complains about something like <e>libtool: link: `/usr/lib/" -"gcc-lib/i686-pc-linux-gnu/3.3.6/libstdc++.la' is not a valid libtool " -"archive</e>, please run <c>/usr/share/gcc-data/$CHOST/<gcc-version>/" -"fix_libtool_files.sh 3.3.6</c> (substitute \"3.3.6\" with the version " -"numbers from the error message, and $CHOST and <gcc-version> with your " -"actual CHOST and GCC version)." +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(ti):223 +msgid "libtool application has hardcoded paths towards GCC internal libraries" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(p):494 -msgid "" -"If you see <e>error: /usr/bin/gcc-config: line 632: /etc/env.d/gcc/i686-pc-" -"linux-gnu-3.3.5: No such file or directory</e>, then try deleting <path>/etc/" -"env.d/gcc/config-i686-pc-linux-gnu</path> and running <c>gcc-config</c> " -"again, followed by <c>source /etc/profile</c>. Only do this if you do not " -"have any cross-compilers set up, though." +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(ti):229 +msgid "dev-lang/ghc" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(p):502 -msgid "" -"If a package fails during <c>emerge -e system</c> or <c>emerge -e world</c>, " -"you can resume operation with <c>emerge --resume</c>. If a package fails " -"repeatedly, skip it with <c>emerge --resume --skipfirst</c>. Don't run any " -"other instances of emerge in between or you will lose the resume information." +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(ti):230 +msgid "ghc application has hardcoded paths towards GCC internal libraries" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(p):509 -msgid "" -"If you get an error message <e>spec failure: unrecognized spec option</e> " -"while upgrading your compiler, try to switch back to your default compiler, " -"unset the <c>GCC_SPECS</c> variable and upgrade GCC again:" +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(title):241 +msgid "Resources" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(pre:caption):515 -msgid "Restoring primary specs" +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(title):243 +msgid "Gentoo Guides and Resources" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(pre):515 -#, no-wrap +#: ../../gentoo/xml/htdocs/doc/en//gcc-upgrading.xml(li):247 msgid "" -"\n" -"# <i>gcc-config 1</i>\n" -"# <i>source /etc/profile</i>\n" -"# <i>unset GCC_SPECS</i>\n" -"# <i>emerge -uav gcc</i>\n" +"<uri link=\"gcc-upgrading-upto-4.1.xml\">GCC Upgrading up to 4.1</uri>, the " +"previous version of this document" msgstr "" #. Place here names of translator, one per line. Format should be NAME; ROLE; E-MAIL |