Changeset 1ff0f0c for introduction/important/la-files.xml
- Timestamp:
- 09/28/2022 10:34:01 AM (19 months ago)
- Branches:
- 11.3, 12.0, 12.1, kea, ken/TL2024, ken/inkscape-core-mods, ken/tuningfonts, lazarus, lxqt, plabs/newcss, plabs/python-mods, python3.11, qt5new, rahul/power-profiles-daemon, renodr/vulkan-addition, trunk, xry111/llvm18, xry111/xf86-video-removal
- Children:
- 3d48ae4
- Parents:
- 5fe69261 (diff), 87065037 (diff)
Note: this is a merge changeset, the changes displayed below correspond to the merge itself.
Use the(diff)
links above to see all the changes relative to each parent. - File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
introduction/important/la-files.xml
r5fe69261 r1ff0f0c 25 25 <para> 26 26 27 In LFS we installed a package, libtool, that is used by many packagesto27 In LFS and BLFS, many packages use a internally shipped libtool copy to 28 28 build on a variety of Unix platforms. This includes platforms such as 29 29 AIX, Solaris, IRIX, HP-UX, and Cygwin as well as Linux. The origins of … … 40 40 url="https://en.wikipedia.org/wiki/Executable_and_Linkable_Format"> 41 41 Executable and Linkable Format (ELF)</ulink> for executables and 42 libraries, information needed to complete the task is embedded in the43 files. At run time the program loader can query the appropriate files44 a nd properly load andexecute the program.42 dynamic libraries, information needed to complete the task is embedded 43 in the files. Both the linker and the program loader can query the 44 appropriate files and properly link or execute the program. 45 45 46 46 </para> 47 47 48 48 <para> 49 Static libraries are rarely used in LFS and BLFS. And, nowadays most 50 packages store the information needed for linking against a static 51 library into a .pc file, instead of relying on libtool. 52 A <command>pkg-config --static --libs</command> command will output 53 the sufficient flags for the linker to link against a static library 54 without any libtool magic. 55 </para> 49 56 50 The problem is that libtool usually creates one or more text files for 51 package libraries called libtool archives. These small files have a 52 ".la" extension and contain information that is similar to that embedded 53 in the libraries. When building a package that uses libtool, the 54 process automatically looks for these files. If a package is updated 55 and no longer uses the .la file, then the build process can break. 56 57 <para> 58 The problem is that libtool usually creates one or more text files for 59 package libraries called libtool archives. These small files have a 60 ".la" extension and contain information that is similar to that embedded 61 in the libraries or pkg-config files. When building a package that 62 uses libtool, the process automatically looks for these files. 63 Sometimes a .la file can contains the name or path of a static library 64 used during build but not installed, then the build process will break 65 because the .la file refers to something nonexistent on the system. 66 Similarly, if a package is updated and no longer uses the .la file, 67 then the build process can break with the old .la files. 57 68 </para> 58 69 … … 135 146 done 136 147 done 137 done 148 done</literal> 138 149 139 150 EOF 140 151 141 chmod +x /usr/sbin/remove-la-files.sh</ literal></userinput></screen>152 chmod +x /usr/sbin/remove-la-files.sh</userinput></screen> 142 153 143 154 <para condition="html" role="usernotes">
Note:
See TracChangeset
for help on using the changeset viewer.