diff options
author | Richard Henderson <rth@redhat.com> | 1999-05-03 11:29:06 +0400 |
---|---|---|
committer | Richard Henderson <rth@redhat.com> | 1999-05-03 11:29:06 +0400 |
commit | a3acbf46947e52ff596461a4cf6f539884c9dbbd (patch) | |
tree | ef93cefb82fdb4d8f2639e166e277474d9b2acab /include/aout/ar.h |
19990502 sourceware importbinu_ss_19990502
Diffstat (limited to 'include/aout/ar.h')
-rw-r--r-- | include/aout/ar.h | 36 |
1 files changed, 36 insertions, 0 deletions
diff --git a/include/aout/ar.h b/include/aout/ar.h new file mode 100644 index 000000000..7b5dcdabd --- /dev/null +++ b/include/aout/ar.h @@ -0,0 +1,36 @@ +/* archive file definition for GNU software */ + +/* So far this is correct for BSDish archives. Don't forget that + files must begin on an even byte boundary. */ + +#ifndef __GNU_AR_H__ +#define __GNU_AR_H__ + +/* Note that the usual '\n' in magic strings may translate to different + characters, as allowed by ANSI. '\012' has a fixed value, and remains + compatible with existing BSDish archives. */ + +#define ARMAG "!<arch>\012" /* For COFF and a.out archives */ +#define ARMAGB "!<bout>\012" /* For b.out archives */ +#define SARMAG 8 +#define ARFMAG "`\012" + +/* The ar_date field of the armap (__.SYMDEF) member of an archive + must be greater than the modified date of the entire file, or + BSD-derived linkers complain. We originally write the ar_date with + this offset from the real file's mod-time. After finishing the + file, we rewrite ar_date if it's not still greater than the mod date. */ + +#define ARMAP_TIME_OFFSET 60 + +struct ar_hdr { + char ar_name[16]; /* name of this member */ + char ar_date[12]; /* file mtime */ + char ar_uid[6]; /* owner uid; printed as decimal */ + char ar_gid[6]; /* owner gid; printed as decimal */ + char ar_mode[8]; /* file mode, printed as octal */ + char ar_size[10]; /* file size, printed as decimal */ + char ar_fmag[2]; /* should contain ARFMAG */ +}; + +#endif /* __GNU_AR_H__ */ |