Translation Source string Target string
Beyond Linux From Scratch 11.3/introduction_important_building-notes — Portuguese (Brazil)
<userinput>yes '' | ./blfs-yes-test1</userinput>
<userinput>yes '' | ./blfs-yes-test1</userinput>
Beyond Linux From Scratch 11.3/introduction_important_building-notes — English
Notice this results in passing just the press of the <keycap>Enter</keycap> key to the script. This is useful for times when the default answer to the prompt is sufficient. This syntax is used in the <xref linkend="net-tools-automate-example"/> instructions to accept all the defaults to the many prompts during the configuration step. You may now remove the test script, if desired.
Notice this results in passing just the press of the <keycap>Enter</keycap> key to the script. This is useful for times when the default answer to the prompt is sufficient. This syntax is used in the <xref linkend="net-tools-automate-example"/> instructions to accept all the defaults to the many prompts during the configuration step. You may now remove the test script, if desired.
Beyond Linux From Scratch 11.3/introduction_important_building-notes — French
Notice this results in passing just the press of the <keycap>Enter</keycap> key to the script. This is useful for times when the default answer to the prompt is sufficient. This syntax is used in the <xref linkend="net-tools-automate-example"/> instructions to accept all the defaults to the many prompts during the configuration step. You may now remove the test script, if desired.
Remarquez que cela aboutit à ne passer au script que l'appui sur la touche <keycap>Entrée</keycap>. C'est utile parfois quand la réponse par défaut à l'invite est suffisante. Cette syntaxe est utilisée dans les instructions de <xref linkend="net-tools-automate-example"/> pour accepter tous les réglages par défaut à toutes les invites lors de l'étape de configuration. Vous pouvez maintenant supprimer le script de test si vous le désirez.
Beyond Linux From Scratch 11.3/introduction_important_building-notes — Portuguese (Brazil)
Notice this results in passing just the press of the <keycap>Enter</keycap> key to the script. This is useful for times when the default answer to the prompt is sufficient. This syntax is used in the <xref linkend="net-tools-automate-example"/> instructions to accept all the defaults to the many prompts during the configuration step. You may now remove the test script, if desired.
Perceba que isso resulta na passagem apenas do pressionamento da tecla <keycap>Enter</keycap> para o script. Isso é útil para ocasiões quando a resposta padrão para a solicitação for suficiente. Essa sintaxe é usada nas instruções do <xref linkend="net-tools-automate-example"/> para aceitar todos os padrões para as muitas solicitações durante a etapa de configuração. Você possivelmente agora remova o script de teste, se desejado.
Beyond Linux From Scratch 11.3/introduction_important_building-notes — English
File Redirection to Automate Output
File Redirection to Automate Output
Beyond Linux From Scratch 11.3/introduction_important_building-notes — French
File Redirection to Automate Output
Redirection de fichiers pour automatiser la sortie
Beyond Linux From Scratch 11.3/introduction_important_building-notes — Portuguese (Brazil)
File Redirection to Automate Output
Redirecionamento de Arquivo para Automatizar a Saída Gerada
Beyond Linux From Scratch 11.3/introduction_important_building-notes — English
In order to automate the building of some packages, especially those that require you to read a license agreement one page at a time, requires using a method that avoids having to press a key to display each page. Redirecting the output to a file can be used in these instances to assist with the automation. The previous section on this page touched on creating log files of the build output. The redirection method shown there used the <command>tee</command> command to redirect output to a file while also displaying the output to the screen. Here, the output will only be sent to a file.
In order to automate the building of some packages, especially those that require you to read a license agreement one page at a time, requires using a method that avoids having to press a key to display each page. Redirecting the output to a file can be used in these instances to assist with the automation. The previous section on this page touched on creating log files of the build output. The redirection method shown there used the <command>tee</command> command to redirect output to a file while also displaying the output to the screen. Here, the output will only be sent to a file.
Beyond Linux From Scratch 11.3/introduction_important_building-notes — French
In order to automate the building of some packages, especially those that require you to read a license agreement one page at a time, requires using a method that avoids having to press a key to display each page. Redirecting the output to a file can be used in these instances to assist with the automation. The previous section on this page touched on creating log files of the build output. The redirection method shown there used the <command>tee</command> command to redirect output to a file while also displaying the output to the screen. Here, the output will only be sent to a file.
Pour automatiser la construction de certains paquets, surtout ceux qui vous demandent de lire un accord de licence page après page, il faut utiliser une méthode qui évite de devoir appuyer sur une touche pour afficher chaque page. On peut utiliser la redirection de sortie vers un fichier dans ce cas-là pour vous aider à automatiser. La section précédente de cette page a visé à créer des fichiers journaux de la sortie de la construction. La méthode de redirection qui y est décrite utilisait la commande <command>tee</command> pour rediriger la sortie tout en affichant aussi la sortie à l'écran. Ici on ne verra la sortie que dans un fichier.
Beyond Linux From Scratch 11.3/introduction_important_building-notes — Portuguese (Brazil)
In order to automate the building of some packages, especially those that require you to read a license agreement one page at a time, requires using a method that avoids having to press a key to display each page. Redirecting the output to a file can be used in these instances to assist with the automation. The previous section on this page touched on creating log files of the build output. The redirection method shown there used the <command>tee</command> command to redirect output to a file while also displaying the output to the screen. Here, the output will only be sent to a file.
Para a finalidade de automatizar a construção de alguns pacotes, especialmente aqueles que exigem que você leia um acordo de licença em uma página por vez, exige-se usar um método que evite ter que pressionar uma tecla para exibir cada página. Redirecionar a saída gerada para um arquivo pode ser usado nessas instâncias para auxiliar com a automação. A seção anterior nesta página tocou na criação de arquivos de registro da saída gerada da construção. O método de redirecionamento mostrado lá usou o comando <command>tee</command> para redirecionar a saída gerada para um arquivo enquanto também exibia a saída gerada na tela. Aqui, a saída gerada somente será enviada para um arquivo.
Beyond Linux From Scratch 11.3/introduction_important_building-notes — English
Again, the easiest way to demonstrate the technique is to show an example. First, issue the command:
Again, the easiest way to demonstrate the technique is to show an example. First, issue the command:
Beyond Linux From Scratch 11.3/introduction_important_building-notes — French
Again, the easiest way to demonstrate the technique is to show an example. First, issue the command:
De nouveau, la manière la plus facile de montrer la technique est de présenter un exemple. Lancez d'abord la commande&nbsp;:
Beyond Linux From Scratch 11.3/introduction_important_building-notes — Portuguese (Brazil)
Again, the easiest way to demonstrate the technique is to show an example. First, issue the command:
Novamente, a maneira mais fácil para demonstrar a técnica é de mostrar um exemplo. Primeiro, emita o comando:
Beyond Linux From Scratch 11.3/introduction_important_building-notes — English
<userinput>ls -l /usr/bin | more</userinput>
<userinput>ls -l /usr/bin | more</userinput>
Beyond Linux From Scratch 11.3/introduction_important_building-notes — French
<userinput>ls -l /usr/bin | more</userinput>
<userinput>ls -l /usr/bin | more</userinput>
Beyond Linux From Scratch 11.3/introduction_important_building-notes — Portuguese (Brazil)
<userinput>ls -l /usr/bin | more</userinput>
<userinput>ls -l /usr/bin | more</userinput>
Beyond Linux From Scratch 11.3/introduction_important_building-notes — English
Of course, you'll be required to view the output one page at a time because the <command>more</command> filter was used. Now try the same command, but this time redirect the output to a file. The special file <filename>/dev/null</filename> can be used instead of the filename shown, but you will have no log file to examine:
Of course, you'll be required to view the output one page at a time because the <command>more</command> filter was used. Now try the same command, but this time redirect the output to a file. The special file <filename>/dev/null</filename> can be used instead of the filename shown, but you will have no log file to examine:
Beyond Linux From Scratch 11.3/introduction_important_building-notes — French
Of course, you'll be required to view the output one page at a time because the <command>more</command> filter was used. Now try the same command, but this time redirect the output to a file. The special file <filename>/dev/null</filename> can be used instead of the filename shown, but you will have no log file to examine:
Bien entendu, vous devrez voir la sortie page par page car on a utilisé le filtre <command>more</command>. Essayez maintenant la même commande, mais en redirigeant cette fois la sortie vers un fichier. Le fichier spécial <filename>/dev/null</filename> peut être utilisé à la place du fichier indiqué, mais vous n'aurez pas de fichier journal à examiner&nbsp;:
Beyond Linux From Scratch 11.3/introduction_important_building-notes — Portuguese (Brazil)
Of course, you'll be required to view the output one page at a time because the <command>more</command> filter was used. Now try the same command, but this time redirect the output to a file. The special file <filename>/dev/null</filename> can be used instead of the filename shown, but you will have no log file to examine:
Certamente, você será exigido(a) a visualizar a saída gerada uma página por vez, pois o filtro <command>more</command> foi usado. Agora tente o mesmo comando, porém, dessa vez, redirecione a saída gerada para um arquivo. O arquivo especial <filename>/dev/null</filename> pode ser usado em vez do nome de arquivo mostrado, porém você não terá arquivo de registro para examinar:
Beyond Linux From Scratch 11.3/introduction_important_building-notes — English
<userinput>ls -l /usr/bin | more &gt; redirect_test.log 2&gt;&amp;1</userinput>
<userinput>ls -l /usr/bin | more &gt; redirect_test.log 2&gt;&amp;1</userinput>
Beyond Linux From Scratch 11.3/introduction_important_building-notes — French
<userinput>ls -l /usr/bin | more &gt; redirect_test.log 2&gt;&amp;1</userinput>
<userinput>ls -l /usr/bin | more &gt; redirect_test.log 2&gt;&amp;1</userinput>
Beyond Linux From Scratch 11.3/introduction_important_building-notes — Portuguese (Brazil)
<userinput>ls -l /usr/bin | more &gt; redirect_test.log 2&gt;&amp;1</userinput>
<userinput>ls -l /usr/bin | more &gt; redirect_test.log 2&gt;&amp;1</userinput>
Beyond Linux From Scratch 11.3/introduction_important_building-notes — English
Notice that this time the command immediately returned to the shell prompt without having to page through the output. You may now remove the log file.
Notice that this time the command immediately returned to the shell prompt without having to page through the output. You may now remove the log file.
Beyond Linux From Scratch 11.3/introduction_important_building-notes — French
Notice that this time the command immediately returned to the shell prompt without having to page through the output. You may now remove the log file.
Vous remarquerez que cette fois, la commande est immédiatement revenue à l'invite du shell sans devoir parcourir la sortie page par page. Vous pouvez maintenant supprimer le fichier journal.
Beyond Linux From Scratch 11.3/introduction_important_building-notes — Portuguese (Brazil)
Notice that this time the command immediately returned to the shell prompt without having to page through the output. You may now remove the log file.
Perceba que, dessa vez, o comando imediatamente retornou ao prompt do shell sem ter que paginar ao longo da saída gerada. Você agora possivelmente remova o arquivo de registro.
Beyond Linux From Scratch 11.3/introduction_important_building-notes — English
The last example will use the <command>yes</command> command in combination with output redirection to bypass having to page through the output and then provide a <keycap>y</keycap> to a prompt. This technique could be used in instances when otherwise you would have to page through the output of a file (such as a license agreement) and then answer the question of <quote>do you accept the above?</quote>. For this example, another short <application>Bash</application> script is required:
The last example will use the <command>yes</command> command in combination with output redirection to bypass having to page through the output and then provide a <keycap>y</keycap> to a prompt. This technique could be used in instances when otherwise you would have to page through the output of a file (such as a license agreement) and then answer the question of <quote>do you accept the above?</quote>. For this example, another short <application>Bash</application> script is required:
Beyond Linux From Scratch 11.3/introduction_important_building-notes — French
The last example will use the <command>yes</command> command in combination with output redirection to bypass having to page through the output and then provide a <keycap>y</keycap> to a prompt. This technique could be used in instances when otherwise you would have to page through the output of a file (such as a license agreement) and then answer the question of <quote>do you accept the above?</quote>. For this example, another short <application>Bash</application> script is required:
Le dernier exemple utilisera la commande <command>yes</command> associée à la redirection de sortie pour éviter de naviguer page par page dans la sortie, puis de fournir un <keycap>y</keycap> à l'invite. Cette technique peut être utilisée dans les cas où vous devriez, sans elle, naviguer page par page dans la sortie d'un fichier (tel qu'un accord de licence), puis répondre à la question <quote>Acceptez-vous ce qui précède&nbsp;?</quote>. Pour cet exemple, on a besoin d'un autre petit script <application>Bash</application>&nbsp;:
Beyond Linux From Scratch 11.3/introduction_important_building-notes — Portuguese (Brazil)
The last example will use the <command>yes</command> command in combination with output redirection to bypass having to page through the output and then provide a <keycap>y</keycap> to a prompt. This technique could be used in instances when otherwise you would have to page through the output of a file (such as a license agreement) and then answer the question of <quote>do you accept the above?</quote>. For this example, another short <application>Bash</application> script is required:
O último exemplo usará o comando <command>yes</command> em combinação com o redirecionamento da saída gerada para desviar-se de ter que paginar ao longo da saída gerada e, então, fornecerá um <keycap>y</keycap> para uma solicitação. Essa técnica poderia ser usada em instâncias quando, de outra maneira, você teria que paginar ao longo da saída gerada de um arquivo (como um acordo de licença) e, então, responder à pergunta de <quote>você aceita o acima?</quote>. Para esse exemplo, outro script curto do <application>Bash</application> é exigido:
Beyond Linux From Scratch 11.3/introduction_important_building-notes — English
<userinput>cat &gt; blfs-yes-test2 &lt;&lt; "EOF"
<literal>#!/bin/bash

ls -l /usr/bin | more

echo -n -e "\n\nDid you enjoy reading this? (y,n) "

read A_STRING

if test "$A_STRING" = "y"; then A_STRING="You entered the 'y' key"
else A_STRING="You did NOT enter the 'y' key"
fi

echo -e "\n\n$A_STRING\n\n"</literal>
EOF
chmod 755 blfs-yes-test2</userinput>
<userinput>cat &gt; blfs-yes-test2 &lt;&lt; "EOF"
<literal>#!/bin/bash

ls -l /usr/bin | more

echo -n -e "\n\nDid you enjoy reading this? (y,n) "

read A_STRING

if test "$A_STRING" = "y"; then A_STRING="You entered the 'y' key"
else A_STRING="You did NOT enter the 'y' key"
fi

echo -e "\n\n$A_STRING\n\n"</literal>
EOF
chmod 755 blfs-yes-test2</userinput>
Beyond Linux From Scratch 11.3/introduction_important_building-notes — French
<userinput>cat &gt; blfs-yes-test2 &lt;&lt; "EOF"
<literal>#!/bin/bash

ls -l /usr/bin | more

echo -n -e "\n\nDid you enjoy reading this? (y,n) "

read A_STRING

if test "$A_STRING" = "y"; then A_STRING="You entered the 'y' key"
else A_STRING="You did NOT enter the 'y' key"
fi

echo -e "\n\n$A_STRING\n\n"</literal>
EOF
chmod 755 blfs-yes-test2</userinput>
<userinput>cat &gt; blfs-yes-test2 &lt;&lt; "EOF"
<literal>#!/bin/bash

ls -l /usr/bin | more

echo -n -e "\n\nDid you enjoy reading this? (y,n) "

read A_STRING

if test "$A_STRING" = "y"; then A_STRING="You entered the 'y' key"
else A_STRING="You did NOT enter the 'y' key"
fi

echo -e "\n\n$A_STRING\n\n"</literal>
EOF
chmod 755 blfs-yes-test2</userinput>
Beyond Linux From Scratch 11.3/introduction_important_building-notes — Portuguese (Brazil)
<userinput>cat &gt; blfs-yes-test2 &lt;&lt; "EOF"
<literal>#!/bin/bash

ls -l /usr/bin | more

echo -n -e "\n\nDid you enjoy reading this? (y,n) "

read A_STRING

if test "$A_STRING" = "y"; then A_STRING="You entered the 'y' key"
else A_STRING="You did NOT enter the 'y' key"
fi

echo -e "\n\n$A_STRING\n\n"</literal>
EOF
chmod 755 blfs-yes-test2</userinput>
<userinput>cat &gt; blfs-yes-test2 &lt;&lt; "EOF"
<literal>#!/bin/bash

ls -l /usr/bin | more

echo -n -e "\n\nVocê curtiu ler isso? (y,n) "

read A_STRING

if test "$A_STRING" = "y"; then A_STRING="Você informou a tecla 'y'"
else A_STRING="Você NÃO informou a tecla 'y'"
fi

echo -e "\n\n$A_STRING\n\n"</literal>
EOF
chmod 755 blfs-yes-test2</userinput>
Beyond Linux From Scratch 11.3/introduction_important_building-notes — English
This script can be used to simulate a program that requires you to read a license agreement, then respond appropriately to accept the agreement before the program will install anything. First, run the script without any automation techniques by issuing <command>./blfs-yes-test2</command>.
This script can be used to simulate a program that requires you to read a license agreement, then respond appropriately to accept the agreement before the program will install anything. First, run the script without any automation techniques by issuing <command>./blfs-yes-test2</command>.
Beyond Linux From Scratch 11.3/introduction_important_building-notes — French
This script can be used to simulate a program that requires you to read a license agreement, then respond appropriately to accept the agreement before the program will install anything. First, run the script without any automation techniques by issuing <command>./blfs-yes-test2</command>.
On peut utiliser ce script pour simuler un programme qui demande que vous lisiez un accord de licence et que vous acceptiez le contrat avant que le programme n'installe quoique ce soit. Lancez d'abord le script sans techniques d'automatisation en exécutant <command>./blfs-yes-test2</command>.
Beyond Linux From Scratch 11.3/introduction_important_building-notes — Portuguese (Brazil)
This script can be used to simulate a program that requires you to read a license agreement, then respond appropriately to accept the agreement before the program will install anything. First, run the script without any automation techniques by issuing <command>./blfs-yes-test2</command>.
Esse script pode ser usado para simular um aplicativo que exige que você leia um acordo de licença, então responda apropriadamente que aceita o acordo antes do aplicativo instalar qualquer coisa. Primeiro, execute o script sem quaisquer técnicas de automação emitindo <command>./blfs-yes-test2</command>.
Beyond Linux From Scratch 11.3/introduction_important_building-notes — English
Now issue the following command which uses two automation techniques, making it suitable for use in an automated build script:
Now issue the following command which uses two automation techniques, making it suitable for use in an automated build script:
Beyond Linux From Scratch 11.3/introduction_important_building-notes — French
Now issue the following command which uses two automation techniques, making it suitable for use in an automated build script:
Maintenant lancez la commande suivante qui utilise deux techniques d'automatisation, rendant l'utilisation convenable dans un script de construction automatisé&nbsp;:
Beyond Linux From Scratch 11.3/introduction_important_building-notes — Portuguese (Brazil)
Now issue the following command which uses two automation techniques, making it suitable for use in an automated build script:
Agora emita o seguinte comando que usa duas técnicas de automação, tornando-o adequado para uso em um script automatizado de construção:
Beyond Linux From Scratch 11.3/introduction_important_building-notes — English
<userinput>yes | ./blfs-yes-test2 &gt; blfs-yes-test2.log 2&gt;&amp;1</userinput>
<userinput>yes | ./blfs-yes-test2 &gt; blfs-yes-test2.log 2&gt;&amp;1</userinput>
Beyond Linux From Scratch 11.3/introduction_important_building-notes — French
<userinput>yes | ./blfs-yes-test2 &gt; blfs-yes-test2.log 2&gt;&amp;1</userinput>
<userinput>yes | ./blfs-yes-test2 &gt; blfs-yes-test2.log 2&gt;&amp;1</userinput>
Beyond Linux From Scratch 11.3/introduction_important_building-notes — Portuguese (Brazil)
<userinput>yes | ./blfs-yes-test2 &gt; blfs-yes-test2.log 2&gt;&amp;1</userinput>
<userinput>yes | ./blfs-yes-test2 &gt; blfs-yes-test2.log 2&gt;&amp;1</userinput>
Beyond Linux From Scratch 11.3/introduction_important_building-notes — English
If desired, issue <command>tail blfs-yes-test2.log</command> to see the end of the paged output, and confirmation that <keycap>y</keycap> was passed through to the script. Once satisfied that it works as it should, you may remove the script and log file.
If desired, issue <command>tail blfs-yes-test2.log</command> to see the end of the paged output, and confirmation that <keycap>y</keycap> was passed through to the script. Once satisfied that it works as it should, you may remove the script and log file.
Beyond Linux From Scratch 11.3/introduction_important_building-notes — French
If desired, issue <command>tail blfs-yes-test2.log</command> to see the end of the paged output, and confirmation that <keycap>y</keycap> was passed through to the script. Once satisfied that it works as it should, you may remove the script and log file.
Si vous le désirez, lancez <command>tail blfs-yes-test2.log</command> pour voir la fin de la sortie paginée et la confirmation que <keycap>y</keycap> a été passé au script. Une fois que cela marche comme cela devrait, vous pouvez supprimer le script et le fichier journal.
Beyond Linux From Scratch 11.3/introduction_important_building-notes — Portuguese (Brazil)
If desired, issue <command>tail blfs-yes-test2.log</command> to see the end of the paged output, and confirmation that <keycap>y</keycap> was passed through to the script. Once satisfied that it works as it should, you may remove the script and log file.
Se desejado, emita <command>tail blfs-yes-test2.log</command> para ver o final da saída gerada paginada e a confirmação de que <keycap>y</keycap> foi passada ao longo para o script. Tão logo satisfeito que ele funciona como deveria, você possivelmente remova o script e o arquivo de registro.
Beyond Linux From Scratch 11.3/introduction_important_building-notes — English
Finally, keep in mind that there are many ways to automate and/or script the build commands. There is not a single <quote>correct</quote> way to do it. Your imagination is the only limit.
Finally, keep in mind that there are many ways to automate and/or script the build commands. There is not a single <quote>correct</quote> way to do it. Your imagination is the only limit.
Beyond Linux From Scratch 11.3/introduction_important_building-notes — French
Finally, keep in mind that there are many ways to automate and/or script the build commands. There is not a single <quote>correct</quote> way to do it. Your imagination is the only limit.
Enfin, gardez à l'esprit qu'il y a de nombreux moyens d'automatiser ou de scripter les commandes de construction. Il n'y a pas <quote>une seule</quote> manière de procéder. Votre imagination est la seule limite.
Beyond Linux From Scratch 11.3/introduction_important_building-notes — Portuguese (Brazil)
Finally, keep in mind that there are many ways to automate and/or script the build commands. There is not a single <quote>correct</quote> way to do it. Your imagination is the only limit.
Finalmente, tenha em mente que existem muitas maneiras de automatizar e (ou) roteirizar os comandos de construção. Não existe maneira única <quote>correta</quote> para fazê-lo. Sua imaginação é o único limite.
Beyond Linux From Scratch 11.3/introduction_important_building-notes — English
Dependencies
Dependencies
Beyond Linux From Scratch 11.3/introduction_important_building-notes — French
Dependencies
Dépendances
Beyond Linux From Scratch 11.3/introduction_important_building-notes — Portuguese (Brazil)
Dependencies
Dependências
Beyond Linux From Scratch 11.3/introduction_important_building-notes — English
For each package described, BLFS lists the known dependencies. These are listed under several headings, whose meaning is as follows:
For each package described, BLFS lists the known dependencies. These are listed under several headings, whose meaning is as follows:
Beyond Linux From Scratch 11.3/introduction_important_building-notes — French
For each package described, BLFS lists the known dependencies. These are listed under several headings, whose meaning is as follows:
Pour chaque paquet décrit, BLFS liste les dépendances connues. Elles sont listées sous plusieurs en-têtes, dont la signification est la suivante&nbsp;:
Beyond Linux From Scratch 11.3/introduction_important_building-notes — Portuguese (Brazil)
For each package described, BLFS lists the known dependencies. These are listed under several headings, whose meaning is as follows:
Para cada pacote descrito, o BLFS lista as dependências conhecidas. Essas são listadas sob vários títulos, cujo significado é como segue:
Beyond Linux From Scratch 11.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.
<emphasis>Required</emphasis> means that the target package cannot be correctly built without the dependency having first been installed.
Beyond Linux From Scratch 11.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.
<emphasis>Requis</emphasis> signifie que le paquet cible ne peut pas se construire correctement sans avoir d'abord installé la dépendance.
Beyond Linux From Scratch 11.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.
<emphasis>Exigida</emphasis> significa que o pacote alvo não consegue ser corretamente construído sem a dependência tendo primeiro sido instalada.
Beyond Linux From Scratch 11.3/introduction_important_building-notes — English
<emphasis>Recommended</emphasis> means that BLFS strongly suggests this package is installed first 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. Some changes or workarounds may be required if these packages are not installed.
<emphasis>Recommended</emphasis> means that BLFS strongly suggests this package is installed first 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. Some changes or workarounds may be required if these packages are not installed.
Beyond Linux From Scratch 11.3/introduction_important_building-notes — French
<emphasis>Recommended</emphasis> means that BLFS strongly suggests this package is installed first 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. Some changes or workarounds may be required if these packages are not installed.
<emphasis>Recommandées</emphasis> signifie que BLFS suggère fortement d'installer préalablement ce paquet 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. Des modifications ou contournements peuvent être requis si ces paquets ne sont pas installés.
Beyond Linux From Scratch 11.3/introduction_important_building-notes — Portuguese (Brazil)
<emphasis>Recommended</emphasis> means that BLFS strongly suggests this package is installed first 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. Some changes or workarounds may be required if these packages are not installed.
<emphasis>Recomendada</emphasis> significa que o BLFS enfaticamente sugere que esse pacote seja instalado primeiro para uma construção limpa e livre de problemas; que não teria problemas seja durante o processo de construção, seja em tempo de execução. As instruções no livro assumem que esses pacotes estejam instalados. Algumas mudanças ou gambiarras possivelmente sejam exigidas se esses pacotes não estiverem instalados.
Beyond Linux From Scratch 11.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.
<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.
Beyond Linux From Scratch 11.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.
<emphasis>Facultatives</emphasis> signifie que ce paquet pourrait être installé pour ajouter des fonctions. BLFS décrira souvent la dépendance pour expliquer la fonctionnalité supplémentaire résultante.
Beyond Linux From Scratch 11.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.
<emphasis>Opcional</emphasis> significa que esse pacote poderia estar instalado para funcionalidade adicionada. Frequentemente o BLFS descreverá a dependência para explicar a funcionalidade adicionada que resultará.
Beyond Linux From Scratch 11.3/introduction_important_building-notes — English
Using the Most Current Package Sources
Using the Most Current Package Sources
Beyond Linux From Scratch 11.3/introduction_important_building-notes — French
Using the Most Current Package Sources
Utilisation de paquets sources les plus récents
Beyond Linux From Scratch 11.3/introduction_important_building-notes — Portuguese (Brazil)
Using the Most Current Package Sources
Usando os Fontes Mais Atuais de Pacote
Beyond Linux From Scratch 11.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 11.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 11.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 11.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 11.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 11.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 11.3/introduction_important_building-notes — English
Stripping One More Time
Stripping One More Time
Beyond Linux From Scratch 11.3/introduction_important_building-notes — French
Stripping One More Time
Nettoyage une fois de plus
Beyond Linux From Scratch 11.3/introduction_important_building-notes — Portuguese (Brazil)
Stripping One More Time
Despojando Mais Uma Vez
Beyond Linux From Scratch 11.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 11.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 11.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 11.3/introduction_important_building-notes — English
Stripping while Installing a Package
Stripping while Installing a Package
Beyond Linux From Scratch 11.3/introduction_important_building-notes — French
Stripping while Installing a Package
Nettoyage à l'installation d'un paquet
Beyond Linux From Scratch 11.3/introduction_important_building-notes — Portuguese (Brazil)
Stripping while Installing a Package
Despojando enquanto se Instala um Pacote
Beyond Linux From Scratch 11.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 11.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 11.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 11.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 11.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 11.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 11.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 11.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 11.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 11.3/introduction_important_building-notes — English
The packages using the meson build system can accept <parameter>-Dstrip=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>-Dstrip=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 11.3/introduction_important_building-notes — French
The packages using the meson build system can accept <parameter>-Dstrip=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>-Dstrip=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 11.3/introduction_important_building-notes — Portuguese (Brazil)
The packages using the meson build system can accept <parameter>-Dstrip=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 "Meson" conseguem aceitar <parameter>-Dstrip=true</parameter> ao executar <command>meson</command>. Se esqueceu de adicionar essa opção executando o <command>meson</command>, [então] você também consegue executar <command>meson install --strip</command> em vez de <command>ninja install</command>.
Beyond Linux From Scratch 11.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 11.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 11.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 11.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 11.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 11.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 11.3/introduction_important_building-notes — English
Stripping Installed Executables
Stripping Installed Executables
Beyond Linux From Scratch 11.3/introduction_important_building-notes — French
Stripping Installed Executables
Nettoyer les exécutables installés
Beyond Linux From Scratch 11.3/introduction_important_building-notes — Portuguese (Brazil)
Stripping Installed Executables
Despojando Executáveis Instalados