From owner-freebsd-current Tue Sep 8 13:33:04 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA08346 for freebsd-current-outgoing; Tue, 8 Sep 1998 13:33:04 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from austin.polstra.com (austin.polstra.com [206.213.73.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA08341 for ; Tue, 8 Sep 1998 13:33:02 -0700 (PDT) (envelope-from jdp@austin.polstra.com) Received: from austin.polstra.com (jdp@localhost) by austin.polstra.com (8.8.8/8.8.8) with ESMTP id NAA14899; Tue, 8 Sep 1998 13:32:26 -0700 (PDT) (envelope-from jdp) Message-Id: <199809082032.NAA14899@austin.polstra.com> To: rnordier@nordier.com Subject: Re: ELF: No values for section flags defined In-Reply-To: <199809081806.UAA20067@ceia.nordier.com> References: <199809081806.UAA20067@ceia.nordier.com> Organization: Polstra & Co., Seattle, WA Cc: current@FreeBSD.ORG Date: Tue, 08 Sep 1998 13:32:26 -0700 From: John Polstra Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <199809081806.UAA20067@ceia.nordier.com>, Robert Nordier wrote: > There appear to be no values for sh_flags defined in > , specifically: > > #define SHF_WRITE 0x1 > #define SHF_ALLOC 0x2 > #define SHF_EXECINSTR 0x4 > #define SHF_MASKPROC 0xf0000000 > > Is there some deep reason for this omission (since pretty much > everything else seems to be there)? Nope, that's a bug. Thanks for the report! I'll add those flags in right away. John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Self-knowledge is always bad news." -- John Barth To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message