openssh unix dev - Oct 2005 - Error when cross configuring openssh 4.2p1

I see that lots of improvements have happened in cross configure support 
compared to version 3.8p1 but a couple of problems remain

1) The check that openpty does not reacquire controlling terminal (line 1326 
in configure.ac)  does not have a default value - I ran the test on my target 
and checked it was OK but I'm not sure what is the best default for others.

2) The etc_default_login check at line 2973 in configure.ac attempts to define 
a default behaviour but configure still fails unless you specify  
--disable-etc-default-login

I suspect at least the former is dependent on what target you are building 
for, I'm building on a Suse 9.3 system for a armv5b-softfloat-linux target.

openssh at baker-net.org.uk wrote:
> I see that lots of improvements have happened in cross configure support 
> compared to version 3.8p1 but a couple of problems remain
> 
> 1) The check that openpty does not reacquire controlling terminal (line
1326
> in configure.ac)  does not have a default value - I ran the test on my
target
> and checked it was OK but I'm not sure what is the best default for
others.
> 
> 2) The etc_default_login check at line 2973 in configure.ac attempts to
define
> a default behaviour but configure still fails unless you specify  
> --disable-etc-default-login
> 
> I suspect at least the former is dependent on what target you are building 
> for, I'm building on a Suse 9.3 system for a armv5b-softfloat-linux
target.
There's a patch for this here: 
http://bugzilla.mindrot.org/show_bug.cgi?id=1097

I'm pretty sure it addresses #1, not sure about #2.

If you can confirm that it works OK then we can apply it too.

-- 
Darren Tucker (dtucker at zip.com.au)
GPG key 8FF4FA69 / D9A3 86E9 7EEE AF4B B2D4  37C9 C982 80C7 8FF4 FA69
     Good judgement comes with experience. Unfortunately, the experience
usually comes from bad judgement.