Date: Fri, 15 Mar 1996 13:59:32 -0800 From: John Polstra <jdp@polstra.com> To: freebsd-current@freebsd.org Subject: Elfkit release 1.1 is now available Message-ID: <199603152159.NAA02221@austin.polstra.com>
next in thread | raw e-mail | index | archive | help
Elfkit version 1.1 is now available. This version includes many
enhancements to the dynamic linker. It also contains some changes to
the language tools, making it much easier to build programs for ELF.
For full details on what has changed since the last release, see:
ftp://ftp.polstra.com/pub/FreeBSD/elfkit/NEWS
This is probably the last release based on FreeBSD-2.1.0. We plan to
track FreeBSD-current in the future.
WHAT IS ELFKIT?
Elfkit is a collection of tools for compiling and executing ELF
programs under FreeBSD-2.1.0-RELEASE and later. It consists of:
* Patches for gcc-2.7.2, to make it support ELF under FreeBSD.
* Patches for binutils-2.6, to make it support ELF under FreeBSD.
* Patches for libc from FreeBSD-2.1.0-RELEASE, to support building it
as an ELF shared library.
* An ELF dynamic linker.
* A user-level test program that can invoke the dynamic linker to
load and execute ELF programs under FreeBSD.
(The user-level test program is probably superfluous, now that the FreeBSD
kernel can directly load and execute ELF executables.)
WHAT CAN I DO WITH IT?
You can compile and link arbitrary programs, as long as they use only
libc. (The other libraries aren't converted yet.) The output of the
linker is a standard, dynamically-linked ELF executable. You can also
build ELF shared libraries.
WHO SHOULD USE ELFKIT?
The current release of elfkit is intended for people who want to
help develop ELF support under FreeBSD. If you simply want to run
ELF programs, and don't want to learn anything else about it, come
back in a few months.
WHAT IS THE STATUS OF ELFKIT?
Elfkit is a work-in-progress, not a finished product. If you use
it, you should be prepared to deal with some disruption when new
releases come out. For example, the installation procedure and
the directory structure could change in future releases. Of course,
I intend to stabilize such things as soon as is practical. But
it's not practical yet -- we're still too early in the development
cycle.
WHERE CAN I GET IT?
ftp://ftp.polstra.com/pub/FreeBSD/elfkit/elfkit-1.1.tar.gz
WHAT ELSE WILL I NEED?
* gcc-2.7.2.tar.gz, from any GNU site.
* binutils-2.6.tar.gz, from any GNU site.
* The sources for libc, from FreeBSD-2.1.0-RELEASE.
* The /usr/include tree from FreeBSD-2.1.0-RELEASE.
If at all possible, you should get your "libc" and "include" sources
from one of the FreeBSD mirror sites, or from the FreeBSD-2.1.0
CD-ROM. If that's absolutely impossible for you, you can get them
from:
ftp://ftp.polstra.com/pub/FreeBSD/elfkit/libc-2.1.0.tar.gz
ftp://ftp.polstra.com/pub/FreeBSD/elfkit/include-2.1.0.tar.gz
Please try to avoid getting the "libc" and "include" sources from
ftp.polstra.com. Its network connection is only a 56K frame relay
link.
WHERE DO I SEND BUG REPORTS AND COMMENTS?
elfkit-bugs@polstra.com
HOW CAN I HELP?
Help is welcome, especially in the areas of library conversion and
testing. At this time, only libc has been converted to support ELF.
Eventually, all the other libraries will have to be converted as well.
Libc is by far the most difficult; I expect that most of the other
libraries will simply need to be recompiled using the elfkit tools, and
tested. This sounds easy, but nevertheless is it work that somebody is
going to have to spend time doing.
As more ELF libraries become available, there will be an increasing
need for testing -- i.e., building larger and larger parts of the
FreeBSD system as ELF executables, and trying them out.
Send mail to elfkit-bugs@polstra.com if you'd like to help.
--
John Polstra jdp@polstra.com
John D. Polstra & Co., Inc. Seattle, Washington USA
"Self-knowledge is always bad news." -- John Barth
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199603152159.NAA02221>