Date:	Wed, 17 Nov 1999 09:32:23 +0200 (IST)
From:	Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender:	eliz AT is
To:	Tom Johnson <tjohnson AT digitalfurnace DOT com>
cc:	djgpp AT delorie DOT com
Subject:	Re: Question on bit fields in gnu c
In-Reply-To:	<000001bf3049$672224e0$1101a8c0@DOMAINDF>
Message-ID:	<Pine.SUN.3.91.991117093211.16288P-100000@is>
MIME-Version:	1.0
Reply-To:	djgpp AT delorie DOT com
X-Mailing-List:	djgpp AT delorie DOT com
X-Unsubscribes-To:	listserv AT delorie DOT com

On Tue, 16 Nov 1999, Tom Johnson wrote:

> Alas, I don't have access to the comp.os.... newsgroup from here

You don't need it.  djgpp AT delorie DOT com is an email gateway to the
comp.os.msdos.djgpp news group; everything you send to
djgpp AT delorie DOT com gets automatically posted to the news group, and
every post to the news group gets reflected to subscribers to the
mailing list.

>    In the RTL documentation for DJGPP, there is a mention of a "command line
> option" of "BITS_BIG_ENDIAN".

Where did you see BITS_BIG_ENDIAN being mentioned?  I just searched
all the libc.info file (that's what I understand you meant by ``RTL
documentation'') and didn't find anything.

I can find --endian switch in the docs of the `objdump' utility--is
this what you meant?  This only affects disassembly of code done by
`objdump', so I don't think it will help you.

> I **really** need this for some embedded
> devlopment, since I would rather not have to reverse the declarations of
> several hundred bit field structures.

I really don't understand what is your problem and how you want to
solve it by controlling the endiannes.  Please elaborate.

- Raw text -