2. Beyond Linux From Scratch 12.3
3. introduction_important_building-notes
4. Search

Filters

• Untranslated strings • state:empty
• Unfinished strings • state:<translated
• Translated strings • state:>=translated
• Strings marked for edit • state:needs-editing
• Strings with suggestions • has:suggestion
• Strings with variants • has:variant
• Strings with screenshots • has:screenshot
• Strings with labels • has:label
• Strings with context • has:context
• Unfinished strings without suggestions • state:<translated AND NOT has:suggestion
• Strings with comments • has:comment
• Strings with any failing checks • has:check
• Approved strings • state:approved
• Strings waiting for review • state:translated

state:>=translated

Position and priority

• Position and priority
• Position
• Priority
• Labels
• Source string
• Target string
• String age
• Last updated
• Number of words
• Number of comments
• Number of failing checks
• Key
• String location

	Translation	Source string	Target string
	Beyond Linux From Scratch 12.3/introduction_important_building-notes — English	<emphasis>Required</emphasis> means that the target package cannot be correctly built without the dependency having first been installed, except if the dependency is said to be <quote>runtime</quote> which means the target package can be built but cannot function without it.	<emphasis>Required</emphasis> means that the target package cannot be correctly built without the dependency having first been installed, except if the dependency is said to be <quote>runtime</quote> which means the target package can be built but cannot function without it.
	Beyond Linux From Scratch 12.3/introduction_important_building-notes — French	<emphasis>Required</emphasis> means that the target package cannot be correctly built without the dependency having first been installed, except if the dependency is said to be <quote>runtime</quote> which means the target package can be built but cannot function without it.	<emphasis>Requis</emphasis> signifie que le paquet cible ne peut pas se construire correctement sans avoir d'abord installé la dépendance, sauf si la dépendance est dite <quote>à l'exécution</quote>, ce qui signifie que le paquet cible peut être construit mais ne peut pas fonctionner sans elle.
	Beyond Linux From Scratch 12.3/introduction_important_building-notes — Portuguese (Brazil)	<emphasis>Required</emphasis> means that the target package cannot be correctly built without the dependency having first been installed, except if the dependency is said to be <quote>runtime</quote> which means the target package can be built but cannot function without it.	<emphasis>Exigida</emphasis> significa que o pacote alvo não pode ser construído corretamente sem que a dependência tenha sido instalada primeiro, exceto se a dependência for considerada de <quote>tempo de execução</quote>, o que significa que o pacote alvo pode ser construído, mas não pode funcionar sem ela.
	Beyond Linux From Scratch 12.3/introduction_important_building-notes — English	Note that a target package can start to <quote>function</quote> in many subtle ways: an installed configuration file can make the init system, cron daemon, or bus daemon to run a program automatically; another package using the target package as a dependency can run a program from the target package in the building system; and the configuration sections in the BLFS book may also run a program from a just installed package. So if you are installing the target package without a <emphasis>Required (runtime)</emphasis> dependency installed, You should install the dependency as soon as possible after the installation of the target package.	Note that a target package can start to <quote>function</quote> in many subtle ways: an installed configuration file can make the init system, cron daemon, or bus daemon to run a program automatically; another package using the target package as a dependency can run a program from the target package in the building system; and the configuration sections in the BLFS book may also run a program from a just installed package. So if you are installing the target package without a <emphasis>Required (runtime)</emphasis> dependency installed, You should install the dependency as soon as possible after the installation of the target package.
	Beyond Linux From Scratch 12.3/introduction_important_building-notes — French	Note that a target package can start to <quote>function</quote> in many subtle ways: an installed configuration file can make the init system, cron daemon, or bus daemon to run a program automatically; another package using the target package as a dependency can run a program from the target package in the building system; and the configuration sections in the BLFS book may also run a program from a just installed package. So if you are installing the target package without a <emphasis>Required (runtime)</emphasis> dependency installed, You should install the dependency as soon as possible after the installation of the target package.	Remarquez qu'un paquet cible peut commencer à <quote>fonctionner</quote> de plusieurs manières subtiles&nbsp;: un fichier de configuration installé peut le faire exécuter au système d'initialisation, au démon cron ou au démon de bus automatiquement. Ou bien un autre paquet qui utilise le paquet cible en dépendance peut exécuter le programme du paquet cible dans son système de construction. Ou encore, les sections de configuration du livre BLFS peuvent également exécuter un problème du paquet tout juste installé. Si vous installez le paquet cible sans un dépendance <emphasis>Requise (à l'exécution)</emphasis>, vous devriez installer la dépendance aussi vite que possible après l'installation du paquet cible.
	Beyond Linux From Scratch 12.3/introduction_important_building-notes — Portuguese (Brazil)	Note that a target package can start to <quote>function</quote> in many subtle ways: an installed configuration file can make the init system, cron daemon, or bus daemon to run a program automatically; another package using the target package as a dependency can run a program from the target package in the building system; and the configuration sections in the BLFS book may also run a program from a just installed package. So if you are installing the target package without a <emphasis>Required (runtime)</emphasis> dependency installed, You should install the dependency as soon as possible after the installation of the target package.	Observe que um pacote alvo pode começar a <quote>funcionar</quote> de muitas maneiras sutis: um arquivo de configuração instalado pode fazer o sistema init, o processo de segundo plano cron ou o processo de segundo plano de barramento executar um aplicativo automaticamente; outro pacote usando o pacote alvo como dependência pode executar um aplicativo oriundo do pacote alvo no sistema de construção; e as seções de configuração no livro BLFS também podem executar um aplicativo a partir de um pacote recém-instalado. Portanto, se estiver instalando o pacote alvo sem uma dependência <emphasis>Exigida (tempo de execução)</emphasis> instalada, você deveria instalar a dependência o mais rápido possível depois da instalação do pacote alvo.
	Beyond Linux From Scratch 12.3/introduction_important_building-notes — English	<emphasis>Recommended</emphasis> means that BLFS strongly suggests this package is installed first (except if said to be <quote>runtime,</quote> see below) for a clean and trouble-free build, that won't have issues either during the build process, or at run-time. The instructions in the book assume these packages are installed. In many cases, if a recommended dependency (not just <quote>runtime</quote>) is not installed, the built package may lack some important functionalities (for example, a video player may be only able to play audio). Sometimes, it's needed to modify the book instructions to disable those important functionalities. In other cases, the build system of the package may build a copy of the dependency (often outdated and sometimes with known security vulnerabilities) shipped in the source tree, or may be downloaded from the Internet during the build process. This increases build time and disk usage. This could potentially cause other problems. If a recommended dependency is said to be <quote>runtime,</quote> it means that BLFS strongly suggests that this dependency is installed before using the package, for getting full functionality.	<emphasis>Recommended</emphasis> means that BLFS strongly suggests this package is installed first (except if said to be <quote>runtime,</quote> see below) for a clean and trouble-free build, that won't have issues either during the build process, or at run-time. The instructions in the book assume these packages are installed. In many cases, if a recommended dependency (not just <quote>runtime</quote>) is not installed, the built package may lack some important functionalities (for example, a video player may be only able to play audio). Sometimes, it's needed to modify the book instructions to disable those important functionalities. In other cases, the build system of the package may build a copy of the dependency (often outdated and sometimes with known security vulnerabilities) shipped in the source tree, or may be downloaded from the Internet during the build process. This increases build time and disk usage. This could potentially cause other problems. If a recommended dependency is said to be <quote>runtime,</quote> it means that BLFS strongly suggests that this dependency is installed before using the package, for getting full functionality.
	Beyond Linux From Scratch 12.3/introduction_important_building-notes — French	<emphasis>Recommended</emphasis> means that BLFS strongly suggests this package is installed first (except if said to be <quote>runtime,</quote> see below) for a clean and trouble-free build, that won't have issues either during the build process, or at run-time. The instructions in the book assume these packages are installed. In many cases, if a recommended dependency (not just <quote>runtime</quote>) is not installed, the built package may lack some important functionalities (for example, a video player may be only able to play audio). Sometimes, it's needed to modify the book instructions to disable those important functionalities. In other cases, the build system of the package may build a copy of the dependency (often outdated and sometimes with known security vulnerabilities) shipped in the source tree, or may be downloaded from the Internet during the build process. This increases build time and disk usage. This could potentially cause other problems. If a recommended dependency is said to be <quote>runtime,</quote> it means that BLFS strongly suggests that this dependency is installed before using the package, for getting full functionality.	<emphasis>Recommandées</emphasis> signifie que BLFS suggère fortement d'installer préalablement ce paquet (sauf si elle est dite <quote>à l'exécution</quote>, voir plus bas) pour une construction propre et sans problème, ni pendant le processus de construction ni au moment de l'exécution. Les instructions dans le livre considèrent que ces paquets sont installés. Dans de nombreux cas, si une dépendance recommandée (sauf les dépendances <quote>à l'exécution</quote>) n'est pas installée, le paquet construit peut ne pas avoir certaines fonctionnalités importantes (par exemple, un lecteur vidéo pourrait ne lire que de l'audio). Parfois, il est nécessaire de modifier les instructions du livre pour désactiver ces fonctionnalités importantes. Dans d'autres cas, le système de construction du paquet peut construire une copie de la dépendance (souvent ancienne, elle peut parfois contenir des vulnérabilités de sécurité connues) embarquée dans l'arborescence des sources ou téléchargée sur l'Internet pendant le processus de construction. Cela augmente le temps de construction et l'utilisation du disque. Cela peut éventuellement causer d'autres problèmes. Si une dépendance recommandée est dite <quote>à l'exécution</quote>, cela signifie que BLFS suggère fortement d'installer cette dépendance avant d'utiliser le paquet, pour avoir toutes les fonctionnalités.
	Beyond Linux From Scratch 12.3/introduction_important_building-notes — Portuguese (Brazil)	<emphasis>Recommended</emphasis> means that BLFS strongly suggests this package is installed first (except if said to be <quote>runtime,</quote> see below) for a clean and trouble-free build, that won't have issues either during the build process, or at run-time. The instructions in the book assume these packages are installed. In many cases, if a recommended dependency (not just <quote>runtime</quote>) is not installed, the built package may lack some important functionalities (for example, a video player may be only able to play audio). Sometimes, it's needed to modify the book instructions to disable those important functionalities. In other cases, the build system of the package may build a copy of the dependency (often outdated and sometimes with known security vulnerabilities) shipped in the source tree, or may be downloaded from the Internet during the build process. This increases build time and disk usage. This could potentially cause other problems. If a recommended dependency is said to be <quote>runtime,</quote> it means that BLFS strongly suggests that this dependency is installed before using the package, for getting full functionality.	<emphasis>Recomendada</emphasis> significa que o BLFS sugere fortemente que esse pacote seja instalado primeiro (exceto se for dito ser <quote>tempo de execução,</quote> veja-se abaixo) para uma construção limpa e sem problemas, que não terá problemas nem durante o processo de construção nem em tempo de execução. As instruções no livro pressupõem que esses pacotes estejam instalados. Em muitos casos, se uma dependência recomendada (não apenas <quote>tempo de execução</quote>) não estiver instalada, o pacote construído pode carecer algumas funcionalidades importantes (por exemplo, um reprodutor de vídeo pode reproduzir somente áudio). Às vezes, é necessário modificar as instruções do livro para desabilitar essas funcionalidades importantes. Em outros casos, o sistema de construção do pacote pode construir uma cópia da dependência (frequentemente desatualizada e às vezes com vulnerabilidades conhecidas de segurança) enviada na árvore do fonte ou pode ser baixada da a partir da Internet durante o processo de construção. Isso aumenta o tempo de construção e o uso do disco. Isso poderia causar outros problemas. Se uma dependência recomendada for <quote>tempo de execução,</quote> isso significa que o BLFS sugere fortemente que essa dependência seja instalada antes de usar o pacote, para obter funcionalidade completa.
	Beyond Linux From Scratch 12.3/introduction_important_building-notes — English	<emphasis>Optional</emphasis> means that this package might be installed for added functionality. Often BLFS will describe the dependency to explain the added functionality that will result. Some optional dependencies are automatically picked up by the target package if the dependency is installed, while others also need additional configuration options to be enabled when the target package is built. Such additional options are often documented in the BLFS book. If an optional dependency is said to be <quote>runtime,</quote> it means you may install the dependency after installing the target package to support some optional features of the target package if you need these features.	<emphasis>Optional</emphasis> means that this package might be installed for added functionality. Often BLFS will describe the dependency to explain the added functionality that will result. Some optional dependencies are automatically picked up by the target package if the dependency is installed, while others also need additional configuration options to be enabled when the target package is built. Such additional options are often documented in the BLFS book. If an optional dependency is said to be <quote>runtime,</quote> it means you may install the dependency after installing the target package to support some optional features of the target package if you need these features.
	Beyond Linux From Scratch 12.3/introduction_important_building-notes — French	<emphasis>Optional</emphasis> means that this package might be installed for added functionality. Often BLFS will describe the dependency to explain the added functionality that will result. Some optional dependencies are automatically picked up by the target package if the dependency is installed, while others also need additional configuration options to be enabled when the target package is built. Such additional options are often documented in the BLFS book. If an optional dependency is said to be <quote>runtime,</quote> it means you may install the dependency after installing the target package to support some optional features of the target package if you need these features.	<emphasis>Facultatives</emphasis> signifie que ce paquet peut être installé pour ajouter une fonctionnalité. Souvent BLFS décrira la dépendance pour expliquer la fonctionnalité ajoutée. Certaines dépendances facultatives peuvent être automatiquement trouvées par le paquet cible si la dépendance est installée, alors que d'autres dépendances facultatives nécessitent des options de configuration supplémentaires pour être activées à la construction du paquet cible. Ces options seront documentées dans le livre BLFS. Si un dépendance facultative est dite <quote>à l'exécution</quote>, cela signifie que vous pouvez installer la dépendance après l'installation du paquet cible pour prendre en charge des fonctionnalités facultatives du paquet cible si vous en avez besoin.
	Beyond Linux From Scratch 12.3/introduction_important_building-notes — Portuguese (Brazil)	<emphasis>Optional</emphasis> means that this package might be installed for added functionality. Often BLFS will describe the dependency to explain the added functionality that will result. Some optional dependencies are automatically picked up by the target package if the dependency is installed, while others also need additional configuration options to be enabled when the target package is built. Such additional options are often documented in the BLFS book. If an optional dependency is said to be <quote>runtime,</quote> it means you may install the dependency after installing the target package to support some optional features of the target package if you need these features.	<emphasis>Opcional</emphasis> significa que esse pacote pode ser instalado para funcionalidade adicional. Frequentemente, o BLFS descreverá a dependência para explicar a funcionalidade adicional que resultará. Algumas dependências opcionais são automaticamente selecionadas pelo pacote alvo se a dependência estiver instalada, enquanto outras também precisam de opções de configuração adicionais para serem habilitadas quando o pacote alvo for construído. Essas opções adicionais frequentemente estão documentadas no livro BLFS. Se uma dependência opcional for dita como <quote>tempo de execução</quote>, significa que você pode instalar a dependência depois de instalar o pacote alvo para suportar alguns recursos opcionais do pacote alvo se precisar desses recursos.
	Beyond Linux From Scratch 12.3/introduction_important_building-notes — English	An optional dependency may be out of BLFS. If you need such an <emphasis>external</emphasis> optional dependency for some features you need, read <xref linkend='beyond'/> for the general hint about installing an out-of-BLFS package.	An optional dependency may be out of BLFS. If you need such an <emphasis>external</emphasis> optional dependency for some features you need, read <xref linkend='beyond'/> for the general hint about installing an out-of-BLFS package.
	Beyond Linux From Scratch 12.3/introduction_important_building-notes — French	An optional dependency may be out of BLFS. If you need such an <emphasis>external</emphasis> optional dependency for some features you need, read <xref linkend='beyond'/> for the general hint about installing an out-of-BLFS package.	Une dépendance facultative peut se trouver en dehors de BLFS. Si vous avez besoin d'une dépendance facultative <emphasis>externe</emphasis> pour des fonctionnalités, consultez <xref linkend='beyond'/> pour trouver l'aide générique sur l'installation des paquets en dehors de BLFS.
	Beyond Linux From Scratch 12.3/introduction_important_building-notes — Portuguese (Brazil)	An optional dependency may be out of BLFS. If you need such an <emphasis>external</emphasis> optional dependency for some features you need, read <xref linkend='beyond'/> for the general hint about installing an out-of-BLFS package.	Uma dependência opcional pode estar fora do BLFS. Se você precisar de uma tal dependência opcional <emphasis>externa</emphasis> para alguns recursos necessários, leia <xref linkend='beyond'/> para as dicas gerais acerca de instalar um pacote fora do BLFS.
	Beyond Linux From Scratch 12.3/introduction_important_building-notes — English	Using the Most Current Package Sources	Using the Most Current Package Sources
	Beyond Linux From Scratch 12.3/introduction_important_building-notes — French	Using the Most Current Package Sources	Utilisation de paquets sources les plus récents
	Beyond Linux From Scratch 12.3/introduction_important_building-notes — Portuguese (Brazil)	Using the Most Current Package Sources	Usando os Fontes Mais Atuais de Pacote
	Beyond Linux From Scratch 12.3/introduction_important_building-notes — English	On occasion you may run into a situation in the book when a package will not build or work properly. Though the Editors attempt to ensure that every package in the book builds and works properly, sometimes a package has been overlooked or was not tested with this particular version of BLFS.	On occasion you may run into a situation in the book when a package will not build or work properly. Though the Editors attempt to ensure that every package in the book builds and works properly, sometimes a package has been overlooked or was not tested with this particular version of BLFS.
	Beyond Linux From Scratch 12.3/introduction_important_building-notes — French	On occasion you may run into a situation in the book when a package will not build or work properly. Though the Editors attempt to ensure that every package in the book builds and works properly, sometimes a package has been overlooked or was not tested with this particular version of BLFS.	Il peut arriver occasionnellement qu'un paquet ne se construise pas ou ne fonctionne pas correctement dans le livre. Bien que les éditeurs tentent de faire en sorte que chaque paquet dans le livre se construise et fonctionne correctement, il arrive parfois qu'un paquet ait été oublié ou n'ait pas été testé avec cette version particulière de BLFS.
	Beyond Linux From Scratch 12.3/introduction_important_building-notes — Portuguese (Brazil)	On occasion you may run into a situation in the book when a package will not build or work properly. Though the Editors attempt to ensure that every package in the book builds and works properly, sometimes a package has been overlooked or was not tested with this particular version of BLFS.	Ocasionalmente você possivelmente se encontre em uma situação no livro onde um pacote não construirá ou não funcionará adequadamente. Apesar dos(as) Editores(as) tentarem garantir que cada pacote no livro construa e funcione adequadamente, ocasionalmente um pacote tenha sido negligenciado ou não foi testado com esta versão particular do BLFS.
	Beyond Linux From Scratch 12.3/introduction_important_building-notes — English	If you discover that a package will not build or work properly, you should see if there is a more current version of the package. Typically this means you go to the maintainer's web site and download the most current tarball and attempt to build the package. If you cannot determine the maintainer's web site by looking at the download URLs, use Google and query the package's name. For example, in the Google search bar type: 'package_name download' (omit the quotes) or something similar. Sometimes typing: 'package_name home page' will result in you finding the maintainer's web site.	If you discover that a package will not build or work properly, you should see if there is a more current version of the package. Typically this means you go to the maintainer's web site and download the most current tarball and attempt to build the package. If you cannot determine the maintainer's web site by looking at the download URLs, use Google and query the package's name. For example, in the Google search bar type: 'package_name download' (omit the quotes) or something similar. Sometimes typing: 'package_name home page' will result in you finding the maintainer's web site.
	Beyond Linux From Scratch 12.3/introduction_important_building-notes — French	If you discover that a package will not build or work properly, you should see if there is a more current version of the package. Typically this means you go to the maintainer's web site and download the most current tarball and attempt to build the package. If you cannot determine the maintainer's web site by looking at the download URLs, use Google and query the package's name. For example, in the Google search bar type: 'package_name download' (omit the quotes) or something similar. Sometimes typing: 'package_name home page' will result in you finding the maintainer's web site.	Si vous découvrez un paquet qui ne se construit pas ou ne fonctionne pas correctement, vous pouvez regarder s'il s'agit de la version la plus récente du paquet. En général, cela signifie que vous devez vous rendre sur le site web du responsable, télécharger l'archive la plus récente et tenter de construire le paquet. Si vous ne pouvez pas déterminer le site web du responsable en regardant l'URL de chargement, utilisez Google et cherchez le nom du paquet. Par exemple, dans la barre de recherche de Google tapez&nbsp;: «&nbsp;nom_du_paquet download&nbsp;» (sans les guillemets) ou quelque chose de similaire. Parfois en tapant&nbsp;: «&nbsp;nom_du_paquet home page&nbsp;» vous trouverez le site web du responsable.
	Beyond Linux From Scratch 12.3/introduction_important_building-notes — Portuguese (Brazil)	If you discover that a package will not build or work properly, you should see if there is a more current version of the package. Typically this means you go to the maintainer's web site and download the most current tarball and attempt to build the package. If you cannot determine the maintainer's web site by looking at the download URLs, use Google and query the package's name. For example, in the Google search bar type: 'package_name download' (omit the quotes) or something similar. Sometimes typing: 'package_name home page' will result in you finding the maintainer's web site.	Se você descobrir que um pacote não construirá ou não funcionará adequadamente, [então] você deveria ver se existe uma versão mais recente do pacote. Tipicamente isso significa você ir ao sítio da web do(a) mantenedor(a) e transferir o tarball mais recente e tentar construir o pacote. Se você não conseguir determinar o sítio da web do(a) mantenedor(a) olhando para os URLs de transferência, [então] use o Google e consulte o nome do pacote. Por exemplo, na barra de pesquisa do Google, digite: 'nome_do_pacote download' (omita as aspas) ou algo semelhante. Ocasionalmente, digitar: 'nome_do_pacote home page' resultará em você encontrar o sítio da web do(a) mantenedor(a).
	Beyond Linux From Scratch 12.3/introduction_important_building-notes — English	Stripping One More Time	Stripping One More Time
	Beyond Linux From Scratch 12.3/introduction_important_building-notes — French	Stripping One More Time	Nettoyage une fois de plus
	Beyond Linux From Scratch 12.3/introduction_important_building-notes — Portuguese (Brazil)	Stripping One More Time	Despojando Mais Uma Vez
	Beyond Linux From Scratch 12.3/introduction_important_building-notes — English	In LFS, stripping of debugging symbols and unneeded symbol table entries was discussed a couple of times. When building BLFS packages, there are generally no special instructions that discuss stripping again. Stripping can be done while installing a package, or afterwards.	In LFS, stripping of debugging symbols and unneeded symbol table entries was discussed a couple of times. When building BLFS packages, there are generally no special instructions that discuss stripping again. Stripping can be done while installing a package, or afterwards.
	Beyond Linux From Scratch 12.3/introduction_important_building-notes — French	In LFS, stripping of debugging symbols and unneeded symbol table entries was discussed a couple of times. When building BLFS packages, there are generally no special instructions that discuss stripping again. Stripping can be done while installing a package, or afterwards.	Dans LFS, le nettoyage des symboles de débogage et des entrées de la table des symboles inutiles a été abordé plusieurs fois. Pour la construction des paquets BLFS, il n'y a généralement pas d'instructions qui abordent de nouveau le nettoyage. Le nettoyage peut avoir lieu après l'installation d'un paquet, ou plus tard.
	Beyond Linux From Scratch 12.3/introduction_important_building-notes — Portuguese (Brazil)	In LFS, stripping of debugging symbols and unneeded symbol table entries was discussed a couple of times. When building BLFS packages, there are generally no special instructions that discuss stripping again. Stripping can be done while installing a package, or afterwards.	No LFS, a remoção de símbolos de depuração e entradas desnecessárias na tabela de símbolos foi discutida algumas vezes. Ao construir pacotes BLFS, geralmente não existem instruções especiais que discutam a remoção novamente. A remoção pode ser feita durante a instalação de um pacote ou posteriormente.
	Beyond Linux From Scratch 12.3/introduction_important_building-notes — English	Stripping while Installing a Package	Stripping while Installing a Package
	Beyond Linux From Scratch 12.3/introduction_important_building-notes — French	Stripping while Installing a Package	Nettoyage à l'installation d'un paquet
	Beyond Linux From Scratch 12.3/introduction_important_building-notes — Portuguese (Brazil)	Stripping while Installing a Package	Despojando enquanto se Instala um Pacote
	Beyond Linux From Scratch 12.3/introduction_important_building-notes — English	There are several ways to strip executables installed by a package. They depend on the build system used (see below <link linkend="buildsystems">the section about build systems</link>), so only some generalities can be listed here:	There are several ways to strip executables installed by a package. They depend on the build system used (see below <link linkend="buildsystems">the section about build systems</link>), so only some generalities can be listed here:
	Beyond Linux From Scratch 12.3/introduction_important_building-notes — French	There are several ways to strip executables installed by a package. They depend on the build system used (see below <link linkend="buildsystems">the section about build systems</link>), so only some generalities can be listed here:	Il y a plusieurs manières de nettoyer les exécutables installés par un paquet. Elles dépendent du système de construction utilisé (voir plus bas <link linkend="buildsystems">la section sur les systèmes de construction</link>), c'est pourquoi nous ne listons que quelques généralités ici&nbsp;:
	Beyond Linux From Scratch 12.3/introduction_important_building-notes — Portuguese (Brazil)	There are several ways to strip executables installed by a package. They depend on the build system used (see below <link linkend="buildsystems">the section about build systems</link>), so only some generalities can be listed here:	Existem várias maneiras de se despojar executáveis instalados por um pacote. Elas dependem do sistema de construção usado (veja-se abaixo <link linkend="buildsystems">a seção acerca de sistemas de construção</link>), de modo que somente algumas generalidades podem ser listadas aqui:
	Beyond Linux From Scratch 12.3/introduction_important_building-notes — English	The following methods using the feature of a building system (autotools, meson, or cmake) will not strip static libraries if any is installed. Fortunately there are not too many static libraries in BLFS, and a static library can always be stripped safely by running <command>strip --strip-unneeded</command> on it manually.	The following methods using the feature of a building system (autotools, meson, or cmake) will not strip static libraries if any is installed. Fortunately there are not too many static libraries in BLFS, and a static library can always be stripped safely by running <command>strip --strip-unneeded</command> on it manually.
	Beyond Linux From Scratch 12.3/introduction_important_building-notes — French	The following methods using the feature of a building system (autotools, meson, or cmake) will not strip static libraries if any is installed. Fortunately there are not too many static libraries in BLFS, and a static library can always be stripped safely by running <command>strip --strip-unneeded</command> on it manually.	Les méthodes suivantes qui utilisent la fonctionnalité d'un système de construction (autotools, meson ou cmake) ne nettoieront pas les bibliothèques statiques si elles sont installées. Heureusement il n'y a pas tant de bibliothèques statiques dans BLFS et une bibliothèque statique peut toujours être nettoyée sans problème en exécutant <command>strip --strip-unneeded</command> dessus manuellement.
	Beyond Linux From Scratch 12.3/introduction_important_building-notes — Portuguese (Brazil)	The following methods using the feature of a building system (autotools, meson, or cmake) will not strip static libraries if any is installed. Fortunately there are not too many static libraries in BLFS, and a static library can always be stripped safely by running <command>strip --strip-unneeded</command> on it manually.	Os métodos a seguir que usam o recurso de um sistema de construção ("autotools", "meson" ou "cmake") não despojarão bibliotecas estáticas, se alguma estiver instalada. Felizmente não existem muitas bibliotecas estáticas no BLFS, e uma biblioteca estática sempre pode ser despojada com segurança executando <command>strip --strip-unneeded</command> nela manualmente.
	Beyond Linux From Scratch 12.3/introduction_important_building-notes — English	The packages using autotools usually have an <parameter>install-strip</parameter> target in their generated <filename>Makefile</filename> files. So installing stripped executables is just a matter of using <command>make install-strip</command> instead of <command>make install</command>.	The packages using autotools usually have an <parameter>install-strip</parameter> target in their generated <filename>Makefile</filename> files. So installing stripped executables is just a matter of using <command>make install-strip</command> instead of <command>make install</command>.
	Beyond Linux From Scratch 12.3/introduction_important_building-notes — French	The packages using autotools usually have an <parameter>install-strip</parameter> target in their generated <filename>Makefile</filename> files. So installing stripped executables is just a matter of using <command>make install-strip</command> instead of <command>make install</command>.	Les paquets qui utilisent les autotools ont habituellement une cible <parameter>install-strip</parameter> dans leur fichier <filename>Makefile</filename> généré. Donc installer des exécutables nettoyer est aussi simple qu'utiliser <command>make install-strip</command> au lieu de <command>make install</command>.
	Beyond Linux From Scratch 12.3/introduction_important_building-notes — Portuguese (Brazil)	The packages using autotools usually have an <parameter>install-strip</parameter> target in their generated <filename>Makefile</filename> files. So installing stripped executables is just a matter of using <command>make install-strip</command> instead of <command>make install</command>.	Os pacotes que usam "Autotools" geralmente tem um alvo <parameter>install-strip</parameter> nos arquivos <filename>Makefile</filename> gerados deles. Portanto, instalar executáveis despojados é apenas uma questão de usar <command>make install-strip</command> em vez de <command>make install</command>.
	Beyond Linux From Scratch 12.3/introduction_important_building-notes — English	The packages using the meson build system can accept <parameter>-D strip=true</parameter> when running <command>meson</command>. If you've forgot to add this option running the <command>meson</command>, you can also run <command>meson install --strip</command> instead of <command>ninja install</command>.	The packages using the meson build system can accept <parameter>-D strip=true</parameter> when running <command>meson</command>. If you've forgot to add this option running the <command>meson</command>, you can also run <command>meson install --strip</command> instead of <command>ninja install</command>.
	Beyond Linux From Scratch 12.3/introduction_important_building-notes — French	The packages using the meson build system can accept <parameter>-D strip=true</parameter> when running <command>meson</command>. If you've forgot to add this option running the <command>meson</command>, you can also run <command>meson install --strip</command> instead of <command>ninja install</command>.	Les paquets qui utilisent le système de construction meson acceptent <parameter>-D strip=true</parameter> au lancement de <command>meson</command>. Si vous avez oublié d'ajouter cette option en lançant <command>meson</command>, vous pouvez aussi lancer <command>meson install --strip</command> au lieu de <command>ninja install</command>.
	Beyond Linux From Scratch 12.3/introduction_important_building-notes — Portuguese (Brazil)	The packages using the meson build system can accept <parameter>-D strip=true</parameter> when running <command>meson</command>. If you've forgot to add this option running the <command>meson</command>, you can also run <command>meson install --strip</command> instead of <command>ninja install</command>.	Os pacotes que usam o sistema de construção do meson conseguem aceitar <parameter>-D strip=true</parameter> ao executar <command>meson</command>. Se tiver esquecido de adicionar essa opção executando o <command>meson</command>, você também consegue executar <command>meson install --strip</command> em vez de <command>ninja install</command>.
	Beyond Linux From Scratch 12.3/introduction_important_building-notes — English	<command>cmake</command> generates <parameter>install/strip</parameter> targets for both the <parameter>Unix Makefiles</parameter> and <parameter>Ninja</parameter> generators (the default is <parameter>Unix Makefiles</parameter> on linux). So just run <command>make install/strip</command> or <command>ninja install/strip</command> instead of the <command>install</command> counterparts.	<command>cmake</command> generates <parameter>install/strip</parameter> targets for both the <parameter>Unix Makefiles</parameter> and <parameter>Ninja</parameter> generators (the default is <parameter>Unix Makefiles</parameter> on linux). So just run <command>make install/strip</command> or <command>ninja install/strip</command> instead of the <command>install</command> counterparts.
	Beyond Linux From Scratch 12.3/introduction_important_building-notes — French	<command>cmake</command> generates <parameter>install/strip</parameter> targets for both the <parameter>Unix Makefiles</parameter> and <parameter>Ninja</parameter> generators (the default is <parameter>Unix Makefiles</parameter> on linux). So just run <command>make install/strip</command> or <command>ninja install/strip</command> instead of the <command>install</command> counterparts.	<command>cmake</command> génère des cibles <parameter>install/strip</parameter> aussi bien pour le générateur de <parameter>Makefiles Unix</parameter> que pour le générateur <parameter>Ninja</parameter> (par défaut c'est le générateur de <parameter>Makefiles Unix</parameter> qui sera utilisé sur linux). Lancez simplement <command>make install/strip</command> ou <command>ninja install/strip</command> au lieu de l'équivalent avec <command>install</command>.
	Beyond Linux From Scratch 12.3/introduction_important_building-notes — Portuguese (Brazil)	<command>cmake</command> generates <parameter>install/strip</parameter> targets for both the <parameter>Unix Makefiles</parameter> and <parameter>Ninja</parameter> generators (the default is <parameter>Unix Makefiles</parameter> on linux). So just run <command>make install/strip</command> or <command>ninja install/strip</command> instead of the <command>install</command> counterparts.	<command>cmake</command> gera alvos <parameter>install/strip</parameter> para ambos os geradores <parameter>Unix Makefiles</parameter> e <parameter>Ninja</parameter> (o padrão é <parameter>Unix Makefiles</parameter> no Linux). Portanto, basta executar <command>make install/strip</command> ou <command>ninja install/strip</command> em vez das contrapartes <command>install</command>.
	Beyond Linux From Scratch 12.3/introduction_important_building-notes — English	Removing (or not generating) debug symbols can also be achieved by removing the <parameter>-g&lt;something&gt;</parameter> options in C/C++ calls. How to do that is very specific for each package. And, it does not remove unneeded symbol table entries. So it will not be explained in detail here. See also below the paragraphs about optimization.	Removing (or not generating) debug symbols can also be achieved by removing the <parameter>-g&lt;something&gt;</parameter> options in C/C++ calls. How to do that is very specific for each package. And, it does not remove unneeded symbol table entries. So it will not be explained in detail here. See also below the paragraphs about optimization.
	Beyond Linux From Scratch 12.3/introduction_important_building-notes — French	Removing (or not generating) debug symbols can also be achieved by removing the <parameter>-g&lt;something&gt;</parameter> options in C/C++ calls. How to do that is very specific for each package. And, it does not remove unneeded symbol table entries. So it will not be explained in detail here. See also below the paragraphs about optimization.	Supprimer (ou éviter de générer) les symboles de débogage peut aussi se faire en supprimant les options <parameter>-g&lt;quelque chose&gt;</parameter> dans les appels au compilateur C/C++. La manière de procéder est spécifique à chaque paquet. En plus, cela ne supprime pas les entrées inutiles de la table des symboles. Nous ne l'expliquons donc pas ici. Voir plus bas les paragraphes sur l'optimisation.
	Beyond Linux From Scratch 12.3/introduction_important_building-notes — Portuguese (Brazil)	Removing (or not generating) debug symbols can also be achieved by removing the <parameter>-g&lt;something&gt;</parameter> options in C/C++ calls. How to do that is very specific for each package. And, it does not remove unneeded symbol table entries. So it will not be explained in detail here. See also below the paragraphs about optimization.	A remoção (ou não geração) de símbolos de depuração também consegue ser obtida removendo-se as opções <parameter>-g&lt;alguma_coisa&gt;</parameter> em chamadas &quot;C/C++&quot;. Como fazer isso é muito específico para cada pacote. E não remove entradas desnecessárias da tabela de símbolos. Portanto, não será explicado em detalhes aqui. Veja-se também abaixo os parágrafos acerca de otimização.
	Beyond Linux From Scratch 12.3/introduction_important_building-notes — English	Stripping Installed Executables	Stripping Installed Executables
	Beyond Linux From Scratch 12.3/introduction_important_building-notes — French	Stripping Installed Executables	Nettoyer les exécutables installés
	Beyond Linux From Scratch 12.3/introduction_important_building-notes — Portuguese (Brazil)	Stripping Installed Executables	Despojando Executáveis Instalados
	Beyond Linux From Scratch 12.3/introduction_important_building-notes — English	The <command>strip</command> utility changes files in place, which may break anything using it if it is loaded in memory. Note that if a file is in use but just removed from the disk (i.e. not overwritten nor modified), this is not a problem since the kernel can use <quote>deleted</quote> files. Look at <filename>/proc/*/maps</filename> and it is likely that you'll see some <emphasis>(deleted)</emphasis> entries. The <command>mv</command> just removes the destination file from the directory but does not touch its content, so that it satisfies the condition for the kernel to use the old (deleted) file. But this approach can detach hard links into duplicated copies, causing a bloat which is obviously unwanted as we are stripping to reduce system size. If two files in a same file system share the same inode number, they are hard links to each other and we should reconstruct the link. The script below is just an example. It should be run as the &root; user:	The <command>strip</command> utility changes files in place, which may break anything using it if it is loaded in memory. Note that if a file is in use but just removed from the disk (i.e. not overwritten nor modified), this is not a problem since the kernel can use <quote>deleted</quote> files. Look at <filename>/proc/*/maps</filename> and it is likely that you'll see some <emphasis>(deleted)</emphasis> entries. The <command>mv</command> just removes the destination file from the directory but does not touch its content, so that it satisfies the condition for the kernel to use the old (deleted) file. But this approach can detach hard links into duplicated copies, causing a bloat which is obviously unwanted as we are stripping to reduce system size. If two files in a same file system share the same inode number, they are hard links to each other and we should reconstruct the link. The script below is just an example. It should be run as the &root; user:
	Beyond Linux From Scratch 12.3/introduction_important_building-notes — French	The <command>strip</command> utility changes files in place, which may break anything using it if it is loaded in memory. Note that if a file is in use but just removed from the disk (i.e. not overwritten nor modified), this is not a problem since the kernel can use <quote>deleted</quote> files. Look at <filename>/proc/*/maps</filename> and it is likely that you'll see some <emphasis>(deleted)</emphasis> entries. The <command>mv</command> just removes the destination file from the directory but does not touch its content, so that it satisfies the condition for the kernel to use the old (deleted) file. But this approach can detach hard links into duplicated copies, causing a bloat which is obviously unwanted as we are stripping to reduce system size. If two files in a same file system share the same inode number, they are hard links to each other and we should reconstruct the link. The script below is just an example. It should be run as the &root; user:	L'utilitaire <command>strip</command> modifie les fichiers en place, ce qui peut casser tout ce qui l'utilise s'il est chargé en mémoire. Remarquez que si un fichier est utilisé mais simplement supprimé du disque (c.-à-d. pas écrasé ou modifié), ce n'est pas un problème car le noyau peut utiliser des fichiers <quote>supprimés</quote>. Regardez dans <filename>/proc/*/maps</filename>, et il est probable que vous verrez des entrées <emphasis>(deleted)</emphasis>. La commande <command>mv</command> supprime seulement le fichier de destination du répertoire mais ne change pas son contenu, donc elle satisfait aux conditions pour que le noyau utilise l'ancien fichier supprimé. Mais cette approche peut détacher des liens en dur et créer des copies dupliquées, causant une plus forte utilisation du disque, ce qui n'est évidemment pas souhaitable quand nous nettoyons pour réduire la taille du système. Si deux fichiers du même système de fichiers partage le même numéro d'inœud, ils sont liés en dur et nous devrions reconstruire le lien. Le script ci-dessous est juste un exemple. Il devrait être lancé en &root;&nbsp;:
	Beyond Linux From Scratch 12.3/introduction_important_building-notes — Portuguese (Brazil)	The <command>strip</command> utility changes files in place, which may break anything using it if it is loaded in memory. Note that if a file is in use but just removed from the disk (i.e. not overwritten nor modified), this is not a problem since the kernel can use <quote>deleted</quote> files. Look at <filename>/proc/*/maps</filename> and it is likely that you'll see some <emphasis>(deleted)</emphasis> entries. The <command>mv</command> just removes the destination file from the directory but does not touch its content, so that it satisfies the condition for the kernel to use the old (deleted) file. But this approach can detach hard links into duplicated copies, causing a bloat which is obviously unwanted as we are stripping to reduce system size. If two files in a same file system share the same inode number, they are hard links to each other and we should reconstruct the link. The script below is just an example. It should be run as the &root; user:	O utilitário <command>strip</command> muda arquivos no local, o que possivelmente quebre alguma coisa que os usem se estiverem carregados na memória. Observe que se um arquivo estiver em uso, mas recém removido do disco (ou seja, não sobrescrito nem modificado), isso não será um problema, pois o núcleo consegue usar arquivos <quote>deletados</quote>. Veja-se <filename>/proc/*/maps</filename> e é provável que você veja algumas entradas <emphasis>(deleted)</emphasis>. O <command>mv</command> apenas remove o arquivo de destino a partir do diretório, mas não toca no conteúdo dele, de modo que satisfaça a condição para o núcleo usar o arquivo antigo (deletado). Porém, essa abordagem pode desanexar links rígidos em cópias duplicadas, causando um inchaço que, obviamente, é indesejado, pois estamos despojando para reduzir o tamanho do sistema. Se dois arquivos em um mesmo sistema de arquivos compartilharem o mesmo número de inode, eles serão links rígidos entre eles e deveríamos reconstruir o link. O conjunto de comandos sequenciais abaixo é apenas um exemplo. Ele deveria ser executado como o(a) usuário(a) &root;:
	Beyond Linux From Scratch 12.3/introduction_important_building-notes — English	<userinput>cat &gt; /usr/sbin/strip-all.sh &lt;&lt; "EOF" <literal>#!/usr/bin/bash if [ $EUID -ne 0 ]; then echo "Need to be root" exit 1 fi last_fs_inode= last_file= { find /usr/lib -type f -name '*.so*' ! -name '*dbg' find /usr/lib -type f -name '*.a' find /usr/{bin,sbin,libexec} -type f } | xargs stat -c '%m %i %n' | sort | while read fs inode file; do if ! readelf -h $file >/dev/null 2>&amp;1; then continue; fi if file $file | grep --quiet --invert-match 'not stripped'; then continue; fi if [ "$fs $inode" = "$last_fs_inode" ]; then ln -f $last_file $file; continue; fi cp --preserve $file ${file}.tmp strip --strip-unneeded ${file}.tmp mv ${file}.tmp $file last_fs_inode="$fs $inode" last_file=$file done</literal> EOF chmod 744 /usr/sbin/strip-all.sh</userinput>	<userinput>cat &gt; /usr/sbin/strip-all.sh &lt;&lt; "EOF" <literal>#!/usr/bin/bash if [ $EUID -ne 0 ]; then echo "Need to be root" exit 1 fi last_fs_inode= last_file= { find /usr/lib -type f -name '*.so*' ! -name '*dbg' find /usr/lib -type f -name '*.a' find /usr/{bin,sbin,libexec} -type f } | xargs stat -c '%m %i %n' | sort | while read fs inode file; do if ! readelf -h $file >/dev/null 2>&amp;1; then continue; fi if file $file | grep --quiet --invert-match 'not stripped'; then continue; fi if [ "$fs $inode" = "$last_fs_inode" ]; then ln -f $last_file $file; continue; fi cp --preserve $file ${file}.tmp strip --strip-unneeded ${file}.tmp mv ${file}.tmp $file last_fs_inode="$fs $inode" last_file=$file done</literal> EOF chmod 744 /usr/sbin/strip-all.sh</userinput>
	Beyond Linux From Scratch 12.3/introduction_important_building-notes — French	<userinput>cat &gt; /usr/sbin/strip-all.sh &lt;&lt; "EOF" <literal>#!/usr/bin/bash if [ $EUID -ne 0 ]; then echo "Need to be root" exit 1 fi last_fs_inode= last_file= { find /usr/lib -type f -name '*.so*' ! -name '*dbg' find /usr/lib -type f -name '*.a' find /usr/{bin,sbin,libexec} -type f } | xargs stat -c '%m %i %n' | sort | while read fs inode file; do if ! readelf -h $file >/dev/null 2>&amp;1; then continue; fi if file $file | grep --quiet --invert-match 'not stripped'; then continue; fi if [ "$fs $inode" = "$last_fs_inode" ]; then ln -f $last_file $file; continue; fi cp --preserve $file ${file}.tmp strip --strip-unneeded ${file}.tmp mv ${file}.tmp $file last_fs_inode="$fs $inode" last_file=$file done</literal> EOF chmod 744 /usr/sbin/strip-all.sh</userinput>	<userinput>cat &gt; /usr/sbin/strip-all.sh &lt;&lt; "EOF" <literal>#!/usr/bin/bash if [ $EUID -ne 0 ]; then echo "Need to be root" exit 1 fi last_fs_inode= last_file= { find /usr/lib -type f -name '*.so*' ! -name '*dbg' find /usr/lib -type f -name '*.a' find /usr/{bin,sbin,libexec} -type f } | xargs stat -c '%m %i %n' | sort | while read fs inode file; do if ! readelf -h $file >/dev/null 2>&amp;1; then continue; fi if file $file | grep --quiet --invert-match 'not stripped'; then continue; fi if [ "$fs $inode" = "$last_fs_inode" ]; then ln -f $last_file $file; continue; fi cp --preserve $file ${file}.tmp strip --strip-unneeded ${file}.tmp mv ${file}.tmp $file last_fs_inode="$fs $inode" last_file=$file done</literal> EOF chmod 744 /usr/sbin/strip-all.sh</userinput>
	Beyond Linux From Scratch 12.3/introduction_important_building-notes — Portuguese (Brazil)	<userinput>cat &gt; /usr/sbin/strip-all.sh &lt;&lt; "EOF" <literal>#!/usr/bin/bash if [ $EUID -ne 0 ]; then echo "Need to be root" exit 1 fi last_fs_inode= last_file= { find /usr/lib -type f -name '*.so*' ! -name '*dbg' find /usr/lib -type f -name '*.a' find /usr/{bin,sbin,libexec} -type f } | xargs stat -c '%m %i %n' | sort | while read fs inode file; do if ! readelf -h $file >/dev/null 2>&amp;1; then continue; fi if file $file | grep --quiet --invert-match 'not stripped'; then continue; fi if [ "$fs $inode" = "$last_fs_inode" ]; then ln -f $last_file $file; continue; fi cp --preserve $file ${file}.tmp strip --strip-unneeded ${file}.tmp mv ${file}.tmp $file last_fs_inode="$fs $inode" last_file=$file done</literal> EOF chmod 744 /usr/sbin/strip-all.sh</userinput>	<userinput>cat &gt; /usr/sbin/strip-all.sh &lt;&lt; "EOF" <literal>#!/usr/bin/bash if [ $EUID -ne 0 ]; then echo "Precisa ser root" exit 1 fi last_fs_inode= last_file= { find /usr/lib -type f -name '*.so*' ! -name '*dbg' find /usr/lib -type f -name '*.a' find /usr/{bin,sbin,libexec} -type f } | xargs stat -c '%m %i %n' | sort | while read fs inode file; do if ! readelf -h $file >/dev/null 2>&amp;1; then continue; fi if file $file | grep --quiet --invert-match 'not stripped'; then continue; fi if [ "$fs $inode" = "$last_fs_inode" ]; then ln -f $last_file $file; continue; fi cp --preserve $file ${file}.tmp strip --strip-unneeded ${file}.tmp mv ${file}.tmp $file last_fs_inode="$fs $inode" last_file=$file done</literal> EOF chmod 744 /usr/sbin/strip-all.sh</userinput>
	Beyond Linux From Scratch 12.3/introduction_important_building-notes — English	If you install programs in other directories such as <filename class="directory">/opt</filename> or <filename class="directory">/usr/local</filename>, you may want to strip the files there too. Just add other directories to scan in the compound list of <command>find</command> commands between the braces.	If you install programs in other directories such as <filename class="directory">/opt</filename> or <filename class="directory">/usr/local</filename>, you may want to strip the files there too. Just add other directories to scan in the compound list of <command>find</command> commands between the braces.
	Beyond Linux From Scratch 12.3/introduction_important_building-notes — French	If you install programs in other directories such as <filename class="directory">/opt</filename> or <filename class="directory">/usr/local</filename>, you may want to strip the files there too. Just add other directories to scan in the compound list of <command>find</command> commands between the braces.	Si vous installez des programmes dans d'autres répertoires tels que <filename class="directory">/opt</filename> ou <filename class="directory">/usr/local</filename>, vous pouvez vouloir nettoyer les fichiers ici aussi. Ajoutez simplement d'autres répertoires à scanner dans la liste des commandes <command>find</command> entre accolades.
	Beyond Linux From Scratch 12.3/introduction_important_building-notes — Portuguese (Brazil)	If you install programs in other directories such as <filename class="directory">/opt</filename> or <filename class="directory">/usr/local</filename>, you may want to strip the files there too. Just add other directories to scan in the compound list of <command>find</command> commands between the braces.	Se você instalar aplicativos em outros diretórios, como <filename class="directory">/opt</filename> ou <filename class="directory">/usr/local</filename>, você possivelmente queira despojar os arquivos lá também . Basta adicionar outros diretórios a escanear na lista composta de comandos <command>find</command> entre chaves.
	Beyond Linux From Scratch 12.3/introduction_important_building-notes — English	For more information on stripping, see <ulink url="https://www.technovelty.org/linux/stripping-shared-libraries.html"/>.	For more information on stripping, see <ulink url="https://www.technovelty.org/linux/stripping-shared-libraries.html"/>.
	Beyond Linux From Scratch 12.3/introduction_important_building-notes — French	For more information on stripping, see <ulink url="https://www.technovelty.org/linux/stripping-shared-libraries.html"/>.	Pour plus d'information sur le nettoyage, regardez <ulink url="https://www.technovelty.org/linux/stripping-shared-libraries.html"/>.
	Beyond Linux From Scratch 12.3/introduction_important_building-notes — Portuguese (Brazil)	For more information on stripping, see <ulink url="https://www.technovelty.org/linux/stripping-shared-libraries.html"/>.	Para mais informações acerca de despojamento, veja-se <ulink url="https://www.technovelty.org/linux/stripping-shared-libraries.html"/>.
	Beyond Linux From Scratch 12.3/introduction_important_building-notes — English	Working with different build systems	Working with different build systems
	Beyond Linux From Scratch 12.3/introduction_important_building-notes — French	Working with different build systems	Travailler avec différents systèmes de construction
	Beyond Linux From Scratch 12.3/introduction_important_building-notes — Portuguese (Brazil)	Working with different build systems	Trabalhando com diferentes sistemas de construção
	Beyond Linux From Scratch 12.3/introduction_important_building-notes — English	There are now three different build systems in common use for converting C or C++ source code into compiled programs or libraries and their details (particularly, finding out about available options and their default values) differ. It may be easiest to understand the issues caused by some choices (typically slow execution or unexpected use of, or omission of, optimizations) by starting with the <envar>CFLAGS</envar>, <envar>CXXFLAGS</envar>, and <envar>LDFLAGS</envar> environment variables. There are also some programs which use Rust.	There are now three different build systems in common use for converting C or C++ source code into compiled programs or libraries and their details (particularly, finding out about available options and their default values) differ. It may be easiest to understand the issues caused by some choices (typically slow execution or unexpected use of, or omission of, optimizations) by starting with the <envar>CFLAGS</envar>, <envar>CXXFLAGS</envar>, and <envar>LDFLAGS</envar> environment variables. There are also some programs which use Rust.
	Beyond Linux From Scratch 12.3/introduction_important_building-notes — French	There are now three different build systems in common use for converting C or C++ source code into compiled programs or libraries and their details (particularly, finding out about available options and their default values) differ. It may be easiest to understand the issues caused by some choices (typically slow execution or unexpected use of, or omission of, optimizations) by starting with the <envar>CFLAGS</envar>, <envar>CXXFLAGS</envar>, and <envar>LDFLAGS</envar> environment variables. There are also some programs which use Rust.	Il y a maintenant trois systèmes de construction différents utilisés régulièrement pour convertir du code source C ou C++ en un programme compilé ou en une bibliothèque et leur fonctionnement (en particulier, comment trouver les options disponibles et leurs valeurs par défaut) est différent. Il peut être plus facile de comprendre les problèmes causés par certains choix (typiquement une exécution lente ou l'utilisation inattendue, ou l'omission, des optimisations en commençant par les variables d'environnement <envar>CFLAGS</envar>, <envar>CXXFLAGS</envar> et <envar>LDFLAGS</envar>. Certains programmes utilisent aussi Rust.
	Beyond Linux From Scratch 12.3/introduction_important_building-notes — Portuguese (Brazil)	There are now three different build systems in common use for converting C or C++ source code into compiled programs or libraries and their details (particularly, finding out about available options and their default values) differ. It may be easiest to understand the issues caused by some choices (typically slow execution or unexpected use of, or omission of, optimizations) by starting with the <envar>CFLAGS</envar>, <envar>CXXFLAGS</envar>, and <envar>LDFLAGS</envar> environment variables. There are also some programs which use Rust.	Existem, agora, três sistemas de construção em uso comum para converter código fonte C ou C++ em aplicativos ou bibliotecas compilados e os detalhes deles (particularmente, descobrir acerca de opções disponíveis e os valores padrão delas) diferem. Possivelmente seja mais fácil entender os problemas causados por algumas escolhas (tipicamente, execução lenta; ou uso inesperado de, ou omissão de, otimizações) iniciando-se com as variáveis de ambiente <envar>CFLAGS</envar>, <envar>CXXFLAGS</envar> e <envar>LDFLAGS</envar>. Também existem alguns aplicativos que usam Rust.
	Beyond Linux From Scratch 12.3/introduction_important_building-notes — English	Most LFS and BLFS builders are probably aware of the basics of <envar>CFLAGS</envar> and <envar>CXXFLAGS</envar> for altering how a program is compiled. Typically, some form of optimization is used by upstream developers (<option>-O2</option> or <option>-O3</option>), sometimes with the creation of debug symbols (<option>-g</option>), as defaults.	Most LFS and BLFS builders are probably aware of the basics of <envar>CFLAGS</envar> and <envar>CXXFLAGS</envar> for altering how a program is compiled. Typically, some form of optimization is used by upstream developers (<option>-O2</option> or <option>-O3</option>), sometimes with the creation of debug symbols (<option>-g</option>), as defaults.
	Beyond Linux From Scratch 12.3/introduction_important_building-notes — French	Most LFS and BLFS builders are probably aware of the basics of <envar>CFLAGS</envar> and <envar>CXXFLAGS</envar> for altering how a program is compiled. Typically, some form of optimization is used by upstream developers (<option>-O2</option> or <option>-O3</option>), sometimes with the creation of debug symbols (<option>-g</option>), as defaults.	La plupart des lecteurs de LFS et de BLFS connaissent probablement déjà les bases de l'utilisation de <envar>CFLAGS</envar> et <envar>CXXFLAGS</envar> pour altérer la compilation d'un programme. En général, certaines formes d'optimisations sont utilisées par les développeurs en amont (<option>-O2</option> ou <option>-O3</option>), parfois avec la création de symboles de débogage (<option>-g</option>) par défaut.
	Beyond Linux From Scratch 12.3/introduction_important_building-notes — Portuguese (Brazil)	Most LFS and BLFS builders are probably aware of the basics of <envar>CFLAGS</envar> and <envar>CXXFLAGS</envar> for altering how a program is compiled. Typically, some form of optimization is used by upstream developers (<option>-O2</option> or <option>-O3</option>), sometimes with the creation of debug symbols (<option>-g</option>), as defaults.	A maioria dos(as) construtores(as) do LFS e do BLFS provavelmente está ciente dos básicos de <envar>CFLAGS</envar> e <envar>CXXFLAGS</envar> para alterar como um aplicativo é compilado. Tipicamente, alguma forma de otimização é usada pelos(as) desenvolvedores(as) de aplicativos (<option>-O2</option> ou <option>-O3</option>), ocasionalmente com a criação de símbolos de depuração (<option>-g</option>), como padrões.
	Beyond Linux From Scratch 12.3/introduction_important_building-notes — English	If there are contradictory flags (e.g. multiple different <option>-O</option> values), the <emphasis>last</emphasis> value will be used. Sometimes this means that flags specified in environment variables will be picked up before values hardcoded in the Makefile, and therefore ignored. For example, where a user specifies <option>-O2</option> and that is followed by <option>-O3</option> the build will use <option>-O3</option>.	If there are contradictory flags (e.g. multiple different <option>-O</option> values), the <emphasis>last</emphasis> value will be used. Sometimes this means that flags specified in environment variables will be picked up before values hardcoded in the Makefile, and therefore ignored. For example, where a user specifies <option>-O2</option> and that is followed by <option>-O3</option> the build will use <option>-O3</option>.
	Beyond Linux From Scratch 12.3/introduction_important_building-notes — French	If there are contradictory flags (e.g. multiple different <option>-O</option> values), the <emphasis>last</emphasis> value will be used. Sometimes this means that flags specified in environment variables will be picked up before values hardcoded in the Makefile, and therefore ignored. For example, where a user specifies <option>-O2</option> and that is followed by <option>-O3</option> the build will use <option>-O3</option>.	S'il y a des drapeaux contradictoires (p. ex. plusieurs valeurs différentes de <option>-O</option>), la <emphasis>dernière</emphasis> valeur sera utilisée. Parfois les drapeaux spécifiés dans les variables d'environnement sont insérés avant les valeurs en dur dans le Makefile, ce qui signifie qu'ils sont ignorés. Par exemple, si un utilisateur spécifie <option>-O2</option>et qu'il est suivi de <option>-O3</option>, la construction utilisera <option>-O3</option>.
	Beyond Linux From Scratch 12.3/introduction_important_building-notes — Portuguese (Brazil)	If there are contradictory flags (e.g. multiple different <option>-O</option> values), the <emphasis>last</emphasis> value will be used. Sometimes this means that flags specified in environment variables will be picked up before values hardcoded in the Makefile, and therefore ignored. For example, where a user specifies <option>-O2</option> and that is followed by <option>-O3</option> the build will use <option>-O3</option>.	Se existirem sinalizadores contraditórios (por exemplo, múltiplos valores <option>-O</option>), o <emphasis>último</emphasis> valor será usado. Ocasionalmente, isso significa que os sinalizadores especificados em variáveis de ambiente serão escolhidos antes dos valores codificados rigidamente no Makefile, e, portanto, ignorados. Por exemplo, onde um(a) usuário(a) especificar <option>-O2</option> e isso for seguido por <option>-O3</option>, a construção usará <option>-O3</option>.
	Beyond Linux From Scratch 12.3/introduction_important_building-notes — English	There are various other things which can be passed in CFLAGS or CXXFLAGS, such as allowing using the instruction set extensions available with a specific microarchitecture (e.g. <option>-march=amdfam10</option> or <option>-march=native</option>), tune the generated code for a specific microarchitecture (e. g. <option>-mtune=tigerlake</option> or <option>-mtune=native</option>, if <option>-mtune=</option> is not used, the microarchitecture from <option>-march=</option> setting will be used), or specifying a specific standard for C or C++ (<option>-std=c++17</option> for example). But one thing which has now come to light is that programmers might include debug assertions in their code, expecting them to be disabled in releases by using <option>-D NDEBUG</option>. Specifically, if <xref linkend="mesa"/> is built with these assertions enabled, some activities such as loading levels of games can take extremely long times, even on high-class video cards.	There are various other things which can be passed in CFLAGS or CXXFLAGS, such as allowing using the instruction set extensions available with a specific microarchitecture (e.g. <option>-march=amdfam10</option> or <option>-march=native</option>), tune the generated code for a specific microarchitecture (e. g. <option>-mtune=tigerlake</option> or <option>-mtune=native</option>, if <option>-mtune=</option> is not used, the microarchitecture from <option>-march=</option> setting will be used), or specifying a specific standard for C or C++ (<option>-std=c++17</option> for example). But one thing which has now come to light is that programmers might include debug assertions in their code, expecting them to be disabled in releases by using <option>-D NDEBUG</option>. Specifically, if <xref linkend="mesa"/> is built with these assertions enabled, some activities such as loading levels of games can take extremely long times, even on high-class video cards.
	Beyond Linux From Scratch 12.3/introduction_important_building-notes — French	There are various other things which can be passed in CFLAGS or CXXFLAGS, such as allowing using the instruction set extensions available with a specific microarchitecture (e.g. <option>-march=amdfam10</option> or <option>-march=native</option>), tune the generated code for a specific microarchitecture (e. g. <option>-mtune=tigerlake</option> or <option>-mtune=native</option>, if <option>-mtune=</option> is not used, the microarchitecture from <option>-march=</option> setting will be used), or specifying a specific standard for C or C++ (<option>-std=c++17</option> for example). But one thing which has now come to light is that programmers might include debug assertions in their code, expecting them to be disabled in releases by using <option>-D NDEBUG</option>. Specifically, if <xref linkend="mesa"/> is built with these assertions enabled, some activities such as loading levels of games can take extremely long times, even on high-class video cards.	On peut passer divers autres drapeaux dans CFLAGS et CXXFLAGS, comme permettre d'utiliser les extensions des jeux d'instruction disponibles pour une microarchitecture spécifique (p. ex. <option>-march=amdfam10</option> ou <option>-march=native</option>), optimiser le code généré pour une microarchitecture donnée (p. ex. <option>-mtune=tigerlake</option> ou <option>-mtune=native</option>, si <option>-mtune=</option> n'est pas utilisé, la microarchitecture du paramètre <option>-march=</option> sera utilisé) ou pour spécifier un standard C ou C++ particulier (<option>-std=c++17</option> par exemple). Mais ce qui commence à apparaître, c'est l'inclusion par les développeurs d'assertions de débogage dans leur code qui sont généralement désactivés dans les versions publiées avec <option>-D NDEBUG</option>. Plus spécifiquement, si <xref linkend="mesa"/> est construit avec ces assertions, certaines activités comme le chargement de niveaux dans les jeux peuvent prendre très longtemps, même sur des cartes vidéo haut de gamme.
	Beyond Linux From Scratch 12.3/introduction_important_building-notes — Portuguese (Brazil)	There are various other things which can be passed in CFLAGS or CXXFLAGS, such as allowing using the instruction set extensions available with a specific microarchitecture (e.g. <option>-march=amdfam10</option> or <option>-march=native</option>), tune the generated code for a specific microarchitecture (e. g. <option>-mtune=tigerlake</option> or <option>-mtune=native</option>, if <option>-mtune=</option> is not used, the microarchitecture from <option>-march=</option> setting will be used), or specifying a specific standard for C or C++ (<option>-std=c++17</option> for example). But one thing which has now come to light is that programmers might include debug assertions in their code, expecting them to be disabled in releases by using <option>-D NDEBUG</option>. Specifically, if <xref linkend="mesa"/> is built with these assertions enabled, some activities such as loading levels of games can take extremely long times, even on high-class video cards.	Existem várias outras coisas que podem ser passadas em CFLAGS ou em CXXFLAGS, tais como permitir-se usar as extensões de conjunto de instruções disponíveis com uma microarquitetura específica (por exemplo, <option>-march=amdfam10</option> ou <option>-march=native</option>) ajustar o código gerado para uma microarquitetura específica (por exemplo, <option>-mtune=tigerlake</option> ou <option>-mtune=native</option>; se <option>-mtune=</option> não for usada, a microarquitetura oriunda da configuração <option>-march=</option> será usada) ou especificar-se um padrão específico para C ou C++ (<option>-std=c++17</option>, por exemplo). Porém, uma coisa que agora veio à tona é que os(as) programadores(as) poderiam incluir asserções de depuração no código deles(as), esperando que sejam desabilitadas em lançamentos usando-se <option>-D NDEBUG</option>. Especificamente, se o <xref linkend="mesa"/> for construído com essas asserções habilitadas, algumas atividades, tais como o carregamento de níveis dos jogos, podem tomar tempos extremamente longos, mesmo em placas de vídeo de alta qualidade.
	Beyond Linux From Scratch 12.3/introduction_important_building-notes — English	Autotools with Make	Autotools with Make
	Beyond Linux From Scratch 12.3/introduction_important_building-notes — French	Autotools with Make	Autotools avec Make
	Beyond Linux From Scratch 12.3/introduction_important_building-notes — Portuguese (Brazil)	Autotools with Make	Autotools com Make
	Beyond Linux From Scratch 12.3/introduction_important_building-notes — English	This combination is often described as <quote>CMMI</quote> (configure, make, make install) and is used here to also cover the few packages which have a configure script that is not generated by autotools.	This combination is often described as <quote>CMMI</quote> (configure, make, make install) and is used here to also cover the few packages which have a configure script that is not generated by autotools.
	Beyond Linux From Scratch 12.3/introduction_important_building-notes — French	This combination is often described as <quote>CMMI</quote> (configure, make, make install) and is used here to also cover the few packages which have a configure script that is not generated by autotools.	Cette combinaison est souvent décrite comme <quote>CMMI</quote> (configure, make, make install) et est utilisée ici pour couvrir aussi certains paquets dont le script configure n'a pas été généré par les autotools.
	Beyond Linux From Scratch 12.3/introduction_important_building-notes — Portuguese (Brazil)	This combination is often described as <quote>CMMI</quote> (configure, make, make install) and is used here to also cover the few packages which have a configure script that is not generated by autotools.	Essa combinação frequentemente é descrita como <quote>CMMI</quote> (configure; make; make install) e é usada aqui também para cobrir os poucos pacotes que tenham um conjunto de comandos sequenciais de configuração que não seja gerado por autotools.
	Beyond Linux From Scratch 12.3/introduction_important_building-notes — English	Sometimes running <command>./configure --help</command> will produce useful options about switches which might be used. At other times, after looking at the output from configure you may need to look at the details of the script to find out what it was actually searching for.	Sometimes running <command>./configure --help</command> will produce useful options about switches which might be used. At other times, after looking at the output from configure you may need to look at the details of the script to find out what it was actually searching for.
	Beyond Linux From Scratch 12.3/introduction_important_building-notes — French	Sometimes running <command>./configure --help</command> will produce useful options about switches which might be used. At other times, after looking at the output from configure you may need to look at the details of the script to find out what it was actually searching for.	Parfois lancer <command>./configure --help</command> affichera les options utiles des paramètres qui peuvent être utilisés. D'autres fois, après avoir regardé la sortie de configure vous pourriez avoir besoin de regarder les détails du script pour comprendre ce qu'il cherchait vraiment.
	Beyond Linux From Scratch 12.3/introduction_important_building-notes — Portuguese (Brazil)	Sometimes running <command>./configure --help</command> will produce useful options about switches which might be used. At other times, after looking at the output from configure you may need to look at the details of the script to find out what it was actually searching for.	Ocasionalmente, executar-se <command>./configure --help</command> produzirá opções úteis acerca de chaves que poderiam ser usadas. Em outras ocasiões, depois de olhar para a saída gerada a partir do configure, você possivelmente precise olhar para os detalhes do script para descobrir pelo que ele estava procurando atualmente.
	Beyond Linux From Scratch 12.3/introduction_important_building-notes — English	Many configure scripts will pick up any CFLAGS or CXXFLAGS from the environment, but CMMI packages vary about how these will be mixed with any flags which would otherwise be used (<emphasis>variously</emphasis>: ignored, used to replace the programmer's suggestion, used before the programmer's suggestion, or used after the programmer's suggestion).	Many configure scripts will pick up any CFLAGS or CXXFLAGS from the environment, but CMMI packages vary about how these will be mixed with any flags which would otherwise be used (<emphasis>variously</emphasis>: ignored, used to replace the programmer's suggestion, used before the programmer's suggestion, or used after the programmer's suggestion).
	Beyond Linux From Scratch 12.3/introduction_important_building-notes — French	Many configure scripts will pick up any CFLAGS or CXXFLAGS from the environment, but CMMI packages vary about how these will be mixed with any flags which would otherwise be used (<emphasis>variously</emphasis>: ignored, used to replace the programmer's suggestion, used before the programmer's suggestion, or used after the programmer's suggestion).	De nombreux scripts configure récupéreront les CFLAGS et CXXFLAGS de l'environnement, mais les paquets CMMI varient dans la manière dont ils seront insérés avec les drapeaux qui sinon seraient utilisés (<emphasis>au choix</emphasis>&nbsp;: ignorés, utilisés à la place de la suggestion des programmeurs, utilisés avant la suggestion des programmeurs ou utilisés après la suggestion des programmeurs).
	Beyond Linux From Scratch 12.3/introduction_important_building-notes — Portuguese (Brazil)	Many configure scripts will pick up any CFLAGS or CXXFLAGS from the environment, but CMMI packages vary about how these will be mixed with any flags which would otherwise be used (<emphasis>variously</emphasis>: ignored, used to replace the programmer's suggestion, used before the programmer's suggestion, or used after the programmer's suggestion).	Muitos scripts de configuração escolherão quaisquer CFLAGS ou CXXFLAGS a partir do ambiente, porém os pacotes CMMI variam acerca do como esses serão misturados com quaisquer sinalizadores que, de outra maneira, seriam usados (<emphasis>variadamente</emphasis>: ignorados; usados para substituir a sugestão do(a) programador(a); usados antes da sugestão do(a) programador(a); ou usados depois da sugestão do(a) programador(a)).
	Beyond Linux From Scratch 12.3/introduction_important_building-notes — English	In most CMMI packages, running <command>make</command> will list each command and run it, interspersed with any warnings. But some packages try to be <quote>silent</quote> and only show which file they are compiling or linking instead of showing the command line. If you need to inspect the command, either because of an error, or just to see what options and flags are being used, adding <option>V=1</option> to the make invocation may help.	In most CMMI packages, running <command>make</command> will list each command and run it, interspersed with any warnings. But some packages try to be <quote>silent</quote> and only show which file they are compiling or linking instead of showing the command line. If you need to inspect the command, either because of an error, or just to see what options and flags are being used, adding <option>V=1</option> to the make invocation may help.
	Beyond Linux From Scratch 12.3/introduction_important_building-notes — French	In most CMMI packages, running <command>make</command> will list each command and run it, interspersed with any warnings. But some packages try to be <quote>silent</quote> and only show which file they are compiling or linking instead of showing the command line. If you need to inspect the command, either because of an error, or just to see what options and flags are being used, adding <option>V=1</option> to the make invocation may help.	Dans la plupart des paquets CMMI, <command>make</command> listera les commandes lancées, séparées par des avertissements éventuels. Mais certains paquets essayent d'être <quote>silencieux</quote> et ne montrent que les fichiers qu'ils compilent ou dont ils éditent les liens au lieu de montrer la ligne de commande. Si vous devez inspecter la commande, soit à cause d'une erreur, ou juste pour voir les options et les drapeaux utilisés, ajouter<option>V=1</option> à l'invocation make peut aider.
	Beyond Linux From Scratch 12.3/introduction_important_building-notes — Portuguese (Brazil)	In most CMMI packages, running <command>make</command> will list each command and run it, interspersed with any warnings. But some packages try to be <quote>silent</quote> and only show which file they are compiling or linking instead of showing the command line. If you need to inspect the command, either because of an error, or just to see what options and flags are being used, adding <option>V=1</option> to the make invocation may help.	Na maioria dos pacotes CMMI, executar-se <command>make</command> listará cada comando e o executará, intercalado com quaisquer avisos. Porém, alguns pacotes tentam ser <quote>silenciosos</quote> e mostram somente qual arquivo eles estão compilando ou vinculando em vez de mostrar a linha de comando. Se você precisar inspecionar o comando, seja por causa de um erro, seja apenas para ver quais opções e sinalizadores estão sendo usados, adicionar <option>V=1</option> à invocação do make possivelmente ajude.
	Beyond Linux From Scratch 12.3/introduction_important_building-notes — English	CMake	CMake
	Beyond Linux From Scratch 12.3/introduction_important_building-notes — French	CMake	CMake
	Beyond Linux From Scratch 12.3/introduction_important_building-notes — Portuguese (Brazil)	CMake	CMake
	Beyond Linux From Scratch 12.3/introduction_important_building-notes — English	CMake works in a very different way, and it has two backends which can be used on BLFS: <command>make</command> and <command>ninja</command>. The default backend is make, but ninja can be faster on large packages with multiple processors. To use ninja, specify <option>-G Ninja</option> in the cmake command. However, there are some packages which create fatal errors in their ninja files but build successfully using the default of Unix Makefiles.	CMake works in a very different way, and it has two backends which can be used on BLFS: <command>make</command> and <command>ninja</command>. The default backend is make, but ninja can be faster on large packages with multiple processors. To use ninja, specify <option>-G Ninja</option> in the cmake command. However, there are some packages which create fatal errors in their ninja files but build successfully using the default of Unix Makefiles.

• 4 / 6
  / 6