>> [ On Friday, November 10, 2000 at 08:46:08 (-0700), Tim Rightnour wrote: ]
>> > Subject: Re: CVS commit: basesrc
>> >
>> > While I do agree with you on that point.. It does seem like there should be a
>> > way to determine the endianess of the machine you are attempting to build for.
>>
>> [ little program deleted ]
>
>Unfortunately, Tim is trying to determine the endianness of the _target_
>platform and not the host platform (this is in a cross-compile environment).

	is it possible for us to put a fake entry (like "*endian*"), which
	includes endian indication, into pwd.db?
	- if there's an entry, password database lookup should convert endian
	  as necessary.
	- if there's no entry (= pwd_mkdb is old and library is new),
	  too bad, it will be just like we are now.
	- if pwd_mkdb is newer, fake entry should be harmless.
	if we can do this, we could gradually migrate to bi-endian password
	database lookup.

itojun