2. Beyond Linux From Scratch 12.3
3. introduction_important_la-files
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_la-files — English	Libtool archive (.la) files	Libtool archive (.la) files
	Beyond Linux From Scratch 12.3/introduction_important_la-files — French	Libtool archive (.la) files	Fichiers d'archive libtool (.la)
	Beyond Linux From Scratch 12.3/introduction_important_la-files — Portuguese (Brazil)	Libtool archive (.la) files	Arquivos de arquivamento do Libtool (.la)
	Beyond Linux From Scratch 12.3/introduction_important_la-files — English	About Libtool Archive (.la) files	About Libtool Archive (.la) files
	Beyond Linux From Scratch 12.3/introduction_important_la-files — French	About Libtool Archive (.la) files	À propos des fichiers d'archive libtool (.la)
	Beyond Linux From Scratch 12.3/introduction_important_la-files — Portuguese (Brazil)	About Libtool Archive (.la) files	Acerca dos arquivos de Arquivamento do Libtool (.la)
	Beyond Linux From Scratch 12.3/introduction_important_la-files — English	Library archive (.la) files	Library archive (.la) files
	Beyond Linux From Scratch 12.3/introduction_important_la-files — French	Library archive (.la) files	Fichiers d'archives de bibliothèques (.la)
	Beyond Linux From Scratch 12.3/introduction_important_la-files — Portuguese (Brazil)	Library archive (.la) files	Arquivos de arquivamento de biblioteca (.la)
	Beyond Linux From Scratch 12.3/introduction_important_la-files — English	Files with a .la extension	Files with a .la extension
	Beyond Linux From Scratch 12.3/introduction_important_la-files — French	Files with a .la extension	Fichiers avec une extension .la
	Beyond Linux From Scratch 12.3/introduction_important_la-files — Portuguese (Brazil)	Files with a .la extension	Arquivos com uma extensão .la
	Beyond Linux From Scratch 12.3/introduction_important_la-files — English	In LFS and BLFS, many packages use an internally shipped libtool copy to build on a variety of Unix platforms. This includes platforms such as AIX, Solaris, IRIX, HP-UX, and Cygwin as well as Linux. The origins of this tool are quite dated. It was intended to manage libraries on systems with less advanced capabilities than a modern Linux system.	In LFS and BLFS, many packages use an internally shipped libtool copy to build on a variety of Unix platforms. This includes platforms such as AIX, Solaris, IRIX, HP-UX, and Cygwin as well as Linux. The origins of this tool are quite dated. It was intended to manage libraries on systems with less advanced capabilities than a modern Linux system.
	Beyond Linux From Scratch 12.3/introduction_important_la-files — French	In LFS and BLFS, many packages use an internally shipped libtool copy to build on a variety of Unix platforms. This includes platforms such as AIX, Solaris, IRIX, HP-UX, and Cygwin as well as Linux. The origins of this tool are quite dated. It was intended to manage libraries on systems with less advanced capabilities than a modern Linux system.	Dans LFS et BLFS, de nombreux paquets utilisent une copie interne de libtool pour se construire sur diverses plateformes Unix. Cela comprend des plateformes comme AIX, Solaris, IRIX, HP-UX et Cygwin, ainsi que Linux. Les origines de cet outil sont assez anciennes. Son objectif premier était de gérer les bibliothèques sur des systèmes aux capacités moins avancées qu'un système Linux moderne.
	Beyond Linux From Scratch 12.3/introduction_important_la-files — Portuguese (Brazil)	In LFS and BLFS, many packages use an internally shipped libtool copy to build on a variety of Unix platforms. This includes platforms such as AIX, Solaris, IRIX, HP-UX, and Cygwin as well as Linux. The origins of this tool are quite dated. It was intended to manage libraries on systems with less advanced capabilities than a modern Linux system.	No LFS e no BLFS, muitos pacotes usam uma cópia da libtool enviada internamente para construir em uma variedade de plataformas Unix. Isso inclui plataformas como AIX, Solaris, IRIX, HP-UX e Cygwin, bem como Linux. As origens dessa ferramenta são bastante antigas. Ela era destinada gerenciar bibliotecas em sistemas com capacidades menos avançadas que um sistema Linux moderno.
	Beyond Linux From Scratch 12.3/introduction_important_la-files — English	On a Linux system, libtool specific files are generally unneeded. Normally libraries are specified in the build process during the link phase. Since a linux system uses the <ulink url="https://en.wikipedia.org/wiki/Executable_and_Linkable_Format"> Executable and Linkable Format (ELF)</ulink> for executables and dynamic libraries, information needed to complete the task is embedded in the files. Both the linker and the program loader can query the appropriate files and properly link or execute the program.	On a Linux system, libtool specific files are generally unneeded. Normally libraries are specified in the build process during the link phase. Since a linux system uses the <ulink url="https://en.wikipedia.org/wiki/Executable_and_Linkable_Format"> Executable and Linkable Format (ELF)</ulink> for executables and dynamic libraries, information needed to complete the task is embedded in the files. Both the linker and the program loader can query the appropriate files and properly link or execute the program.
	Beyond Linux From Scratch 12.3/introduction_important_la-files — French	On a Linux system, libtool specific files are generally unneeded. Normally libraries are specified in the build process during the link phase. Since a linux system uses the <ulink url="https://en.wikipedia.org/wiki/Executable_and_Linkable_Format"> Executable and Linkable Format (ELF)</ulink> for executables and dynamic libraries, information needed to complete the task is embedded in the files. Both the linker and the program loader can query the appropriate files and properly link or execute the program.	Sur un système Linux, les fichiers spécifiques à libtool sont généralement inutiles. En temps normal, les bibliothèques sont spécifiées dans le processus de construction pendant l'édition de liens. Comme un système Linux utilise le <ulink url="https://fr.wikipedia.org/wiki/Executable_and_Linkable_Format">format exécutable et liable (ELF)</ulink> pour les exécutables et les bibliothèques, les informations nécessaires à cette tâche sont incluses dans les fichiers. Aussi bien le chargeur de programme que l'éditeur de liens peuvent demander les fichiers requis, ainsi que charger et exécuter correctement le programme.
	Beyond Linux From Scratch 12.3/introduction_important_la-files — Portuguese (Brazil)	On a Linux system, libtool specific files are generally unneeded. Normally libraries are specified in the build process during the link phase. Since a linux system uses the <ulink url="https://en.wikipedia.org/wiki/Executable_and_Linkable_Format"> Executable and Linkable Format (ELF)</ulink> for executables and dynamic libraries, information needed to complete the task is embedded in the files. Both the linker and the program loader can query the appropriate files and properly link or execute the program.	Em um sistema Linux, os arquivos específicos da "libtool" geralmente são desnecessários. Normalmente as bibliotecas são especificadas no processo de construção durante a fase de ligação. Como um sistema Linux usa o <ulink url="https://en.wikipedia.org/wiki/Executable_and_Linkable_Format">Executable and Linkable Format (ELF)</ulink> para executáveis e bibliotecas dinâmicas, as informações necessárias para concluir a tarefa são embutidas nos arquivos. Tanto o vinculador quanto o carregador de aplicativos podem consultar os arquivos apropriados e vincular ou executar o aplicativo adequadamente.
	Beyond Linux From Scratch 12.3/introduction_important_la-files — English	Static libraries are rarely used in LFS and BLFS. And, nowadays most packages store the information needed for linking against a static library into a .pc file, instead of relying on libtool. A <command>pkg-config --static --libs</command> command will output the sufficient flags for the linker to link against a static library without any libtool magic.	Static libraries are rarely used in LFS and BLFS. And, nowadays most packages store the information needed for linking against a static library into a .pc file, instead of relying on libtool. A <command>pkg-config --static --libs</command> command will output the sufficient flags for the linker to link against a static library without any libtool magic.
	Beyond Linux From Scratch 12.3/introduction_important_la-files — French	Static libraries are rarely used in LFS and BLFS. And, nowadays most packages store the information needed for linking against a static library into a .pc file, instead of relying on libtool. A <command>pkg-config --static --libs</command> command will output the sufficient flags for the linker to link against a static library without any libtool magic.	Le bibliothèques statiques sont rarement utilisées dans LFS et BLFS. De nos jours la plupart des paquets stockent les informations requises pour la liaisons aux bibliothèques statiques dans un fichier .pc, au lieu de s'appuyer sur libtool. La commande <command>pkg-config --static --libs</command> affichera les drapeaux nécessaires à l'éditeur de liens pour se lier à une bibliothèque statique sans la magie de libtool.
	Beyond Linux From Scratch 12.3/introduction_important_la-files — Portuguese (Brazil)	Static libraries are rarely used in LFS and BLFS. And, nowadays most packages store the information needed for linking against a static library into a .pc file, instead of relying on libtool. A <command>pkg-config --static --libs</command> command will output the sufficient flags for the linker to link against a static library without any libtool magic.	Bibliotecas estáticas raramente são usadas no LFS e no BLFS. E hoje em dia a maioria dos pacotes armazena as informações necessárias para vincular a uma biblioteca estática em um arquivo ".pc", em vez de depender da "libtool". Um comando <command>pkg-config --static --libs</command> gerará os sinalizadores suficientes para o vinculador para vincular-se a uma biblioteca estática sem qualquer mágica da "libtool".
	Beyond Linux From Scratch 12.3/introduction_important_la-files — English	The problem is that libtool usually creates one or more text files for package libraries called libtool archives. These small files have a ".la" extension and contain information that is similar to that embedded in the libraries or pkg-config files. When building a package that uses libtool, the process automatically looks for these files. Sometimes a .la file can contains the name or path of a static library used during build but not installed, then the build process will break because the .la file refers to something nonexistent on the system. Similarly, if a package is updated and no longer uses the .la file, then the build process can break with the old .la files.	The problem is that libtool usually creates one or more text files for package libraries called libtool archives. These small files have a ".la" extension and contain information that is similar to that embedded in the libraries or pkg-config files. When building a package that uses libtool, the process automatically looks for these files. Sometimes a .la file can contains the name or path of a static library used during build but not installed, then the build process will break because the .la file refers to something nonexistent on the system. Similarly, if a package is updated and no longer uses the .la file, then the build process can break with the old .la files.
	Beyond Linux From Scratch 12.3/introduction_important_la-files — French	The problem is that libtool usually creates one or more text files for package libraries called libtool archives. These small files have a ".la" extension and contain information that is similar to that embedded in the libraries or pkg-config files. When building a package that uses libtool, the process automatically looks for these files. Sometimes a .la file can contains the name or path of a static library used during build but not installed, then the build process will break because the .la file refers to something nonexistent on the system. Similarly, if a package is updated and no longer uses the .la file, then the build process can break with the old .la files.	Le problème est que libtool crée typiquement un ou plusieurs fichiers texte pour les paquets de bibliothèques appelés archives libtool. Ces petits fichiers ont l'extension «&nbsp;.la&nbsp;» et contiennent des informations identiques à celles incluses dans les bibliothèques ou les fichiers pkg-config. Lors de la construction d'un paquet qui utilise libtool, le processus cherche automatiquement ces fichiers. Parfois un fichier .la peut contenir le nom ou le chemin d'une bibliothèque statique utilisée pendant la construction mais jamais installée, et le processus de construction échoue car le fichier .la se réfère à un objet inexistant sur le système. De même, si un paquet est mis à jour et n'utilise plus de fichier .la, le processus de construction peut échouer à cause de l'ancien fichier .la.
	Beyond Linux From Scratch 12.3/introduction_important_la-files — Portuguese (Brazil)	The problem is that libtool usually creates one or more text files for package libraries called libtool archives. These small files have a ".la" extension and contain information that is similar to that embedded in the libraries or pkg-config files. When building a package that uses libtool, the process automatically looks for these files. Sometimes a .la file can contains the name or path of a static library used during build but not installed, then the build process will break because the .la file refers to something nonexistent on the system. Similarly, if a package is updated and no longer uses the .la file, then the build process can break with the old .la files.	O problema é que a "libtool" geralmente cria um ou mais arquivos de texto para bibliotecas de pacotes, chamados arquivamentos "libtool". Esses pequenos arquivos tem uma extensão ".la" e contém informações semelhantes àquelas embutidas nas bibliotecas ou nos arquivos "pkg-config". Ao construir um pacote que usa "libtool", o processo procura automaticamente por esses arquivos. Às vezes, um arquivo ".la" pode conter o nome ou caminho de uma biblioteca estática usada durante a construção, mas não instalada, então o processo de construção será interrompido porque o arquivo ".la" se refere a algo inexistente no sistema. Da mesma forma, se um pacote for atualizado e não mais usar o arquivo ".la", então o processo de construção poderá quebrar com os arquivos ".la" antigos.
	Beyond Linux From Scratch 12.3/introduction_important_la-files — English	The solution is to remove the .la files. However there is a catch. Some packages, such as <xref linkend='imagemagick'/>, use a libtool function, lt_dlopen, to load libraries as needed during execution and resolve their dependencies at run time. In this case, the .la files should remain.	The solution is to remove the .la files. However there is a catch. Some packages, such as <xref linkend='imagemagick'/>, use a libtool function, lt_dlopen, to load libraries as needed during execution and resolve their dependencies at run time. In this case, the .la files should remain.
	Beyond Linux From Scratch 12.3/introduction_important_la-files — French	The solution is to remove the .la files. However there is a catch. Some packages, such as <xref linkend='imagemagick'/>, use a libtool function, lt_dlopen, to load libraries as needed during execution and resolve their dependencies at run time. In this case, the .la files should remain.	La solution consiste à supprimer les fichiers .la, mais il y a un inconvénient. Certains paquets, comme <xref linkend='imagemagick'/>, utilisent une fonction de libtool, lt_dlopen, pour charger les bibliothèques requises pendant l'exécution et résoudre leurs dépendances à l'exécution. Dans ce cas, les fichiers .la ne doivent pas être supprimés.
	Beyond Linux From Scratch 12.3/introduction_important_la-files — Portuguese (Brazil)	The solution is to remove the .la files. However there is a catch. Some packages, such as <xref linkend='imagemagick'/>, use a libtool function, lt_dlopen, to load libraries as needed during execution and resolve their dependencies at run time. In this case, the .la files should remain.	A solução é a de remover os arquivos .la. No entanto, existe uma pegadinha. Alguns pacotes, tais como o <xref linkend='imagemagick'/>, usam uma função do libtool, lt_dlopen, para carregar bibliotecas conforme necessárias durante a execução e resolver as dependências deles em tempo de execução. Nesse caso, os arquivos .la deveriam permanecer.
	Beyond Linux From Scratch 12.3/introduction_important_la-files — English	The script below, removes all unneeded .la files and saves them in a directory, /var/local/la-files by default, not in the normal library path. It also searches all pkg-config files (.pc) for embedded references to .la files and fixes them to be conventional library references needed when an application or library is built. It can be run as needed to clean up the directories that may be causing problems.	The script below, removes all unneeded .la files and saves them in a directory, /var/local/la-files by default, not in the normal library path. It also searches all pkg-config files (.pc) for embedded references to .la files and fixes them to be conventional library references needed when an application or library is built. It can be run as needed to clean up the directories that may be causing problems.
	Beyond Linux From Scratch 12.3/introduction_important_la-files — French	The script below, removes all unneeded .la files and saves them in a directory, /var/local/la-files by default, not in the normal library path. It also searches all pkg-config files (.pc) for embedded references to .la files and fixes them to be conventional library references needed when an application or library is built. It can be run as needed to clean up the directories that may be causing problems.	Le script ci-dessous supprime tous les fichiers .la inutiles et les sauvegarde dans un répertoire, /var/local/la-files par défaut, qui ne se trouve pas dans le chemin de recherche habituel des bibliothèques. Il recherche également les références à des fichiers .la dans les fichiers pkg-config (.pc) et les transforme en références de bibliothèques conventionnelles qui sont nécessaires lors de la construction d'une application ou d'une bibliothèque. Il peut être lancé au besoin pour nettoyer les répertoires qui causent des problèmes.
	Beyond Linux From Scratch 12.3/introduction_important_la-files — Portuguese (Brazil)	The script below, removes all unneeded .la files and saves them in a directory, /var/local/la-files by default, not in the normal library path. It also searches all pkg-config files (.pc) for embedded references to .la files and fixes them to be conventional library references needed when an application or library is built. It can be run as needed to clean up the directories that may be causing problems.	O script abaixo remove todos os arquivos .la desnecessários e os salva em um diretório, /var/local/la-files, por padrão, não no caminho normal de biblioteca. Ele também procura em todos os arquivos pkg-config (.pc) por referências embutidas a arquivos .la e os corrige para serem referências convencionais de biblioteca necessárias quando uma aplicação ou biblioteca for construída. Ele pode ser executado conforme necessário para limpar os diretórios que possivelmente estejam causando problemas.
	Beyond Linux From Scratch 12.3/introduction_important_la-files — English	<userinput>cat &gt; /usr/sbin/remove-la-files.sh &lt;&lt; "EOF" <literal>#!/bin/bash # /usr/sbin/remove-la-files.sh # Written for Beyond Linux From Scratch # by Bruce Dubbs &lt;bdubbs@&lfs-domainname;&gt; # Make sure we are running with root privs if test "${EUID}" -ne 0; then echo "Error: $(basename ${0}) must be run as the root user! Exiting..." exit 1 fi # Make sure PKG_CONFIG_PATH is set if discarded by sudo source /etc/profile OLD_LA_DIR=/var/local/la-files mkdir -p $OLD_LA_DIR # Only search directories in /opt, but not symlinks to directories OPTDIRS=$(find /opt -mindepth 1 -maxdepth 1 -type d) # Move any found .la files to a directory out of the way find /usr/lib $OPTDIRS -name "*.la" ! -path "/usr/lib/ImageMagick*" \ -exec mv -fv {} $OLD_LA_DIR \; ############### # Fix any .pc files that may have .la references STD_PC_PATH='/usr/lib/pkgconfig /usr/share/pkgconfig /usr/local/lib/pkgconfig /usr/local/share/pkgconfig' # For each directory that can have .pc files for d in $(echo $PKG_CONFIG_PATH | tr : ' ') $STD_PC_PATH; do # For each pc file for pc in $d/*.pc ; do if [ $pc == "$d/*.pc" ]; then continue; fi # Check each word in a line with a .la reference for word in $(grep '\.la' $pc); do if $(echo $word | grep -q '.la$' ); then mkdir -p $d/la-backup cp -fv $pc $d/la-backup basename=$(basename $word ) libref=$(echo $basename|sed -e 's/^lib/-l/' -e 's/\.la$//') # Fix the .pc file sed -i "s:$word:$libref:" $pc fi done done done</literal> EOF chmod +x /usr/sbin/remove-la-files.sh</userinput>	<userinput>cat &gt; /usr/sbin/remove-la-files.sh &lt;&lt; "EOF" <literal>#!/bin/bash # /usr/sbin/remove-la-files.sh # Written for Beyond Linux From Scratch # by Bruce Dubbs &lt;bdubbs@&lfs-domainname;&gt; # Make sure we are running with root privs if test "${EUID}" -ne 0; then echo "Error: $(basename ${0}) must be run as the root user! Exiting..." exit 1 fi # Make sure PKG_CONFIG_PATH is set if discarded by sudo source /etc/profile OLD_LA_DIR=/var/local/la-files mkdir -p $OLD_LA_DIR # Only search directories in /opt, but not symlinks to directories OPTDIRS=$(find /opt -mindepth 1 -maxdepth 1 -type d) # Move any found .la files to a directory out of the way find /usr/lib $OPTDIRS -name "*.la" ! -path "/usr/lib/ImageMagick*" \ -exec mv -fv {} $OLD_LA_DIR \; ############### # Fix any .pc files that may have .la references STD_PC_PATH='/usr/lib/pkgconfig /usr/share/pkgconfig /usr/local/lib/pkgconfig /usr/local/share/pkgconfig' # For each directory that can have .pc files for d in $(echo $PKG_CONFIG_PATH | tr : ' ') $STD_PC_PATH; do # For each pc file for pc in $d/*.pc ; do if [ $pc == "$d/*.pc" ]; then continue; fi # Check each word in a line with a .la reference for word in $(grep '\.la' $pc); do if $(echo $word | grep -q '.la$' ); then mkdir -p $d/la-backup cp -fv $pc $d/la-backup basename=$(basename $word ) libref=$(echo $basename|sed -e 's/^lib/-l/' -e 's/\.la$//') # Fix the .pc file sed -i "s:$word:$libref:" $pc fi done done done</literal> EOF chmod +x /usr/sbin/remove-la-files.sh</userinput>
	Beyond Linux From Scratch 12.3/introduction_important_la-files — French	<userinput>cat &gt; /usr/sbin/remove-la-files.sh &lt;&lt; "EOF" <literal>#!/bin/bash # /usr/sbin/remove-la-files.sh # Written for Beyond Linux From Scratch # by Bruce Dubbs &lt;bdubbs@&lfs-domainname;&gt; # Make sure we are running with root privs if test "${EUID}" -ne 0; then echo "Error: $(basename ${0}) must be run as the root user! Exiting..." exit 1 fi # Make sure PKG_CONFIG_PATH is set if discarded by sudo source /etc/profile OLD_LA_DIR=/var/local/la-files mkdir -p $OLD_LA_DIR # Only search directories in /opt, but not symlinks to directories OPTDIRS=$(find /opt -mindepth 1 -maxdepth 1 -type d) # Move any found .la files to a directory out of the way find /usr/lib $OPTDIRS -name "*.la" ! -path "/usr/lib/ImageMagick*" \ -exec mv -fv {} $OLD_LA_DIR \; ############### # Fix any .pc files that may have .la references STD_PC_PATH='/usr/lib/pkgconfig /usr/share/pkgconfig /usr/local/lib/pkgconfig /usr/local/share/pkgconfig' # For each directory that can have .pc files for d in $(echo $PKG_CONFIG_PATH | tr : ' ') $STD_PC_PATH; do # For each pc file for pc in $d/*.pc ; do if [ $pc == "$d/*.pc" ]; then continue; fi # Check each word in a line with a .la reference for word in $(grep '\.la' $pc); do if $(echo $word | grep -q '.la$' ); then mkdir -p $d/la-backup cp -fv $pc $d/la-backup basename=$(basename $word ) libref=$(echo $basename|sed -e 's/^lib/-l/' -e 's/\.la$//') # Fix the .pc file sed -i "s:$word:$libref:" $pc fi done done done</literal> EOF chmod +x /usr/sbin/remove-la-files.sh</userinput>	<userinput>cat &gt; /usr/sbin/remove-la-files.sh &lt;&lt; "EOF" <literal>#!/bin/bash # /usr/sbin/remove-la-files.sh # Written for Beyond Linux From Scratch # by Bruce Dubbs &lt;bdubbs@&lfs-domainname;&gt; # Make sure we are running with root privs if test "${EUID}" -ne 0; then echo "Error: $(basename ${0}) must be run as the root user! Exiting..." exit 1 fi # Make sure PKG_CONFIG_PATH is set if discarded by sudo source /etc/profile OLD_LA_DIR=/var/local/la-files mkdir -p $OLD_LA_DIR # Only search directories in /opt, but not symlinks to directories OPTDIRS=$(find /opt -mindepth 1 -maxdepth 1 -type d) # Move any found .la files to a directory out of the way find /usr/lib $OPTDIRS -name "*.la" ! -path "/usr/lib/ImageMagick*" \ -exec mv -fv {} $OLD_LA_DIR \; ############### # Fix any .pc files that may have .la references STD_PC_PATH='/usr/lib/pkgconfig /usr/share/pkgconfig /usr/local/lib/pkgconfig /usr/local/share/pkgconfig' # For each directory that can have .pc files for d in $(echo $PKG_CONFIG_PATH | tr : ' ') $STD_PC_PATH; do # For each pc file for pc in $d/*.pc ; do if [ $pc == "$d/*.pc" ]; then continue; fi # Check each word in a line with a .la reference for word in $(grep '\.la' $pc); do if $(echo $word | grep -q '.la$' ); then mkdir -p $d/la-backup cp -fv $pc $d/la-backup basename=$(basename $word ) libref=$(echo $basename|sed -e 's/^lib/-l/' -e 's/\.la$//') # Fix the .pc file sed -i "s:$word:$libref:" $pc fi done done done</literal> EOF chmod +x /usr/sbin/remove-la-files.sh</userinput>
	Beyond Linux From Scratch 12.3/introduction_important_la-files — Portuguese (Brazil)	<userinput>cat &gt; /usr/sbin/remove-la-files.sh &lt;&lt; "EOF" <literal>#!/bin/bash # /usr/sbin/remove-la-files.sh # Written for Beyond Linux From Scratch # by Bruce Dubbs &lt;bdubbs@&lfs-domainname;&gt; # Make sure we are running with root privs if test "${EUID}" -ne 0; then echo "Error: $(basename ${0}) must be run as the root user! Exiting..." exit 1 fi # Make sure PKG_CONFIG_PATH is set if discarded by sudo source /etc/profile OLD_LA_DIR=/var/local/la-files mkdir -p $OLD_LA_DIR # Only search directories in /opt, but not symlinks to directories OPTDIRS=$(find /opt -mindepth 1 -maxdepth 1 -type d) # Move any found .la files to a directory out of the way find /usr/lib $OPTDIRS -name "*.la" ! -path "/usr/lib/ImageMagick*" \ -exec mv -fv {} $OLD_LA_DIR \; ############### # Fix any .pc files that may have .la references STD_PC_PATH='/usr/lib/pkgconfig /usr/share/pkgconfig /usr/local/lib/pkgconfig /usr/local/share/pkgconfig' # For each directory that can have .pc files for d in $(echo $PKG_CONFIG_PATH | tr : ' ') $STD_PC_PATH; do # For each pc file for pc in $d/*.pc ; do if [ $pc == "$d/*.pc" ]; then continue; fi # Check each word in a line with a .la reference for word in $(grep '\.la' $pc); do if $(echo $word | grep -q '.la$' ); then mkdir -p $d/la-backup cp -fv $pc $d/la-backup basename=$(basename $word ) libref=$(echo $basename|sed -e 's/^lib/-l/' -e 's/\.la$//') # Fix the .pc file sed -i "s:$word:$libref:" $pc fi done done done</literal> EOF chmod +x /usr/sbin/remove-la-files.sh</userinput>	<userinput>cat &gt; /usr/sbin/remove-la-files.sh &lt;&lt; "EOF" <literal>#!/bin/bash # /usr/sbin/remove-la-files.sh # Escrito para o Beyond Linux From Scratch # por Bruce Dubbs &lt;bdubbs@&lfs-domainname;&gt; # Certifique-se de que estamos executando com privilégios de "root" if test "${EUID}" -ne 0; then echo "Erro: $(basename ${0}) precisa ser executado como o(a) usuário(a) root! Saindo..." exit 1 fi # Certifique-se de que PKG_CONFIG_PATH esteja definido se descartado pelo "sudo" source /etc/profile OLD_LA_DIR=/var/local/la-files mkdir -p $OLD_LA_DIR # Pesquise somente diretórios em /opt, mas não links simbólicos para diretórios OPTDIRS=$(find /opt -mindepth 1 -maxdepth 1 -type d) # Mova todos os arquivos ".la" encontrados para um diretório fora do caminho find /usr/lib $OPTDIRS -name "*.la" ! -path "/usr/lib/ImageMagick*" \ -exec mv -fv {} $OLD_LA_DIR \; ############### # Corrija quaisquer arquivos ".pc" que possam ter referências ".la" STD_PC_PATH='/usr/lib/pkgconfig /usr/share/pkgconfig /usr/local/lib/pkgconfig /usr/local/share/pkgconfig' # Para cada diretório que pode conter arquivos ".pc" for d in $(echo $PKG_CONFIG_PATH | tr : ' ') $STD_PC_PATH; do # Para cada arquivo "pc" for pc in $d/*.pc ; do if [ $pc == "$d/*.pc" ]; then continue; fi # Verifique cada palavra em uma linha com uma referência ".la" for word in $(grep '\.la' $pc); do if $(echo $word | grep -q '.la$' ); then mkdir -p $d/la-backup cp -fv $pc $d/la-backup basename=$(basename $word ) libref=$(echo $basename|sed -e 's/^lib/-l/' -e 's/\.la$//') # Corrige o arquivo ".pc" sed -i "s:$word:$libref:" $pc fi done done done</literal> EOF chmod +x /usr/sbin/remove-la-files.sh</userinput>