os/doc
3
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity

Add some application and filename tags.

Browse source
This commit is contained in:
Marc Fonvieille 2003-08-20 14:02:52 +00:00
parent 77c745bbae
commit e894b1e1a3
Notes: svn2git 2020-12-08 03:00:23 +00:00 
svn path=/head/; revision=17937
1 changed files with 6 additions and 6 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

12
en_US.ISO8859-1/books/handbook/basics/chapter.sgml
View file

@ -1756,10 +1756,10 @@ console none unknown off secure</programlisting>
<para>So, why are there so many different formats?</para>
<para>Back in the dim, dark past, there was simple hardware. This
simple hardware supported a simple, small system. a.out was
simple hardware supported a simple, small system. <filename>a.out</filename> was
completely adequate for the job of representing binaries on this
simple system (a PDP-11). As people ported Unix from this simple
system, they retained the a.out format because it was sufficient
system, they retained the <filename>a.out</filename> format because it was sufficient
for the early ports of Unix to architectures like the Motorola
68k, VAXen, etc.</para>
@ -1805,18 +1805,18 @@ console none unknown off secure</programlisting>
support for building cross compilers, plugging in different
formats at will, etc. Since many people wanted to build cross
compilers targeting FreeBSD, they were out of luck since the
older sources that FreeBSD had for as and ld were not up to the
task. The new gnu tools chain (binutils) does support cross
older sources that FreeBSD had for <application>as</application> and <application>ld</application> were not up to the
task. The new GNU tools chain (<application>binutils</application>) does support cross
compiling, <acronym>ELF</acronym>, shared libraries, C++
extensions, etc. In addition, many vendors are releasing
<acronym>ELF</acronym> binaries, and it is a good thing for
FreeBSD to run them.</para>
<para><acronym>ELF</acronym> is more expressive than a.out and
<para><acronym>ELF</acronym> is more expressive than <filename>a.out</filename> and
allows more extensibility in the base system. The
<acronym>ELF</acronym> tools are better maintained, and offer
cross compilation support, which is important to many people.
<acronym>ELF</acronym> may be a little slower than a.out, but
<acronym>ELF</acronym> may be a little slower than <filename>a.out</filename>, but
trying to measure it can be difficult. There are also numerous
details that are different between the two in how they map
pages, handle init code, etc. None of these are very important,