summaryrefslogtreecommitdiffstats
path: root/usr.bin/elf2aout
Commit message (Collapse)AuthorAgeFilesLines
* Start the dreaded NOFOO -> NO_FOO conversion.ru2004-12-211-1/+1
| | | | OK'ed by: core
* For variables that are only checked with defined(), don't provideru2004-10-241-1/+1
| | | | any fake value.
* Back out the totally unapproved backout of my commits.obrien2003-03-292-2/+1
|
* Back out the removal (here too) of the "custom" version ofru2003-02-192-1/+2
| | | | | | | | | <sys/endian.h>. It is needed to cross-build sparc64 on RELENG_4 and to build sparc64 on say 5.0-DP1 (on systems without <sys/endian.h>). This will be revisited when we create RELENG_5. Spotted by: make universe
* Use the offical sys/endian.h rather than reaching way over into anotherobrien2002-12-302-2/+1
| | | | binary's directory to use a private header.
* Adjust path to crunchide.obrien2002-12-301-3/+3
|
* Set NO_WERROR to ignore the following warning which is emitted onbde2002-07-111-0/+1
| | | | | | | | | | | alphas: .../elf2aout.c:130: warning: cast increases required alignment of target type The warning is about casting ((char *)e + phoff) to a struct pointer, where e is aligned but phoff might be garbage, so I think the warning should be emitted on most machines (even on i386's, alignment checking might be on) and the correct fix would involve validation phoff before using it.
* Make it work for a different endianness binary.ru2002-05-252-47/+31
| | | | | | (This version is still limited to ELF64.) Reviewed by: jake
* Bootstrap elf2aout(1) for sparc64; used to build sys/boot/sparc64/boot1.ru2002-05-201-1/+29
|
* Kill the stray #include line.ru2002-05-201-1/+0
|
* s/u_int/u_int32_t/ru2002-05-201-8/+9
|
* Get byte swapping primitives from sys/endian.h now that they are exportedjake2002-05-171-5/+1
| | | | to userland. This makes elf2aout work as a cross tool.
* Add a Makefile for this.jake2002-04-221-0/+6
|
* Utility to create a.out [kernels] from an ELF one.obrien2002-03-281-0/+156
This is needed on sparc64 (and maybe all OpenFirmware based machines) as most [all?] OpenBoot PROM's require either an a.out or FCode boot image. Submitted by: jake
OpenPOWER on IntegriCloud