Changeset e097438 for chapter05/toolchaintechnotes.xml
- Timestamp:
- 09/05/2004 11:18:43 AM (20 years ago)
- Branches:
- 6.0
- Children:
- 752f4e5
- Parents:
- a9e0b22
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
chapter05/toolchaintechnotes.xml
ra9e0b22 re097438 40 40 needed by a program, prepares the program to run, and then runs it. 41 41 The name of the dynamic linker will usually be 42 <filename >ld-linux.so.2</filename>. On platforms that are less43 prevalent, the name might be <filename >ld.so.1</filename>, and newer44 64 bit platforms might be named something else entirely. The name of42 <filename class="libraryfile">ld-linux.so.2</filename>. On platforms that are less 43 prevalent, the name might be <filename class="libraryfile">ld.so.1</filename>, 44 and newer 64 bit platforms might be named something else entirely. The name of 45 45 the platform's dynamic linker can be determined by looking in the 46 46 <filename class="directory">/lib</filename> directory on the host … … 87 87 linker is its library search order. Detailed information can be 88 88 obtained from <command>ld</command> by passing it the 89 <parameter>--verbose</parameter> flag. For example, an < command>ld90 --verbose | grep SEARCH</ command> will illustrate the current search89 <parameter>--verbose</parameter> flag. For example, an <userinput>ld 90 --verbose | grep SEARCH</userinput> will illustrate the current search 91 91 paths and their order. It shows which files are linked by 92 92 <command>ld</command> by compiling a dummy program and passing the … … 120 120 considerations for building Glibc are the compiler, binary tools, and 121 121 kernel headers. The compiler is generally not an issue since Glibc 122 will always use the <command>gcc</command> found in a PATH directory. 122 will always use the <command>gcc</command> found in a 123 <envar>PATH</envar> directory. 123 124 The binary tools and kernel headers can be a bit more complicated. 124 125 Therefore, take no risks and use the available configure switches to
Note:
See TracChangeset
for help on using the changeset viewer.