Source strings

11 Strings 100%
Browse Translate
661 Words 100%
4,377 Characters 100%
This translation is being used as source strings within this component.

Strings status

Strings Words Characters
11 661 4,377
All strings Browse Translate Zen
11 661 4,377
Read-only strings Browse Translate Zen
1 229 1,666
Strings with any failing checks Browse Translate Zen
1 229 1,666
Failing check: Ellipsis Browse Translate Zen

Overview

Project website www.linuxfromscratch.org
Translation process
  • Translations can be made directly.
  • Translation suggestions can be made.
  • Any authenticated user can contribute.
  • The translation uses bilingual files.
Source code repository git@git.linuxfromscratch.org:fr-lfs
Repository branch 12.1
Last remote commit Add pt_BR translation e751a3b16e
Julien Lepiller authored 7 months ago
Weblate repository https://translate.linuxfromscratch.org/git/linux-from-scratch-12-1/index/
File mask blfs/*/introduction/important/la-files.po
Translation file Not available
Last change March 4, 2024, 7:58 a.m.
Last author None
3 weeks ago

String statistics

Strings percent Hosted strings Words percent Hosted words Characters percent Hosted characters
Total 11 661 4,377
Translated 100% 11 100% 661 100% 4,377
Needs editing 0% 0 0% 0 0% 0
Read-only 100% 11 100% 661 100% 4,377
Failing checks 9% 1 34% 229 38% 1,666
Strings with suggestions 0% 0 0% 0 0% 0
Untranslated strings 0% 0 0% 0 0% 0
Last 12 months Previous

Activity in last 12 months

0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 11 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes
Dec Jan Feb Mar Apr May Jun Jul Aug Sep Oct Nov

Quick numbers

661
Hosted words
11
Hosted strings
100%
Translated
0
Contributors
and previous 30 days

Trends of last 30 days

—
Hosted words
+100%
—
Hosted strings
+100%
—
Translated
+100%
—
Contributors
—
User avatar None

Source string added
<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>
9 months ago
User avatar None

Source string added
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.
9 months ago
User avatar None

Source string added
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.
9 months ago
User avatar None

Source string added
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.
9 months ago
User avatar None

Source string added
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.
9 months ago
User avatar None

Source string added
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.
9 months ago
User avatar None

Source string added
In LFS and BLFS, many packages use a 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.
9 months ago
User avatar None

Source string added
Files with a .la extension
9 months ago
User avatar None

Source string added
Library archive (.la) files
9 months ago
User avatar None

Source string added
About Libtool Archive (.la) files
9 months ago
Browse all translation changes