>  > Thanks Frederick and Brendan for your comments, they were very
>>  helpful. Points about tech-pkg well taken. Hopefully this is more
>>  on-topic:
>
>Actually, no. It's clearly a package issue, and not a problem with
>mac68k. ;-)

dang, I'll get the hang of it, but since you answered :-)

>The thing is, the second file would usually be accessed as
>
>	#include <machine/endian.h>

meaning there is a typo? Or something more complex?


>"machine/endian.h" is a
>hard-link to "mac68k/endian.h".

Yes this is correct on my installation.

>The real question is, how did
>"HAVE_ENDIAN_H" get defined when you have no "/usr/include/endian.h"?

Indeed. I do have endian.h in /usr/include/mac68k, so it's simple 
enough for me to make the fix it would seem, but I'm not sure if I 
would somehow break something else. Does this sort of discrepancy 
creep in often to pkgsrc? (Clearly a question for the tech-pkg list, 
I guess; I'll head on over there).

>On my system, 1.4.3/mac68k, configure says "checking for endian.h...
>no". Do you have CFLAGS or CPPFLAGS set to something strange?

in ../../security/openssh/work/openssh-2.5.1p2/Makefile, neither 
CFLAGS nor CPPFLAGS looks funny, and elsewhere there is certainly no 
def of HAVE_ENDIAN_H that I can see, and I have changed nothing since 
I downloaded pkgsrc, except make and install openssl (and its 
assorted dependencies, which were all done automatically).


Stefan Jeglinski