cross compling openssh-3.5p1 for ppc

Damien Miller djm at
Wed Jan 14 19:32:39 EST 2004

On Wed, 2004-01-14 at 04:30, John Zavgren wrote:
> Greetings:
> ------------ BACKGROUND --------------------------
> I am using the Monta Vista development kit on an Intel RedHat Linux 
> platform... the target is PPC_405.
> The configure utility that comes with the openssh-3.5p1 code will not 
> support cross compilation. It gives an error message about not being able 
> to test its results and then exits before it creates a Makefile. To get 
> around this bug, I edited the configure shell script so that whenever it 
> performs the cross compilation test it now prints a warning message and 
> continues.
> This is how I generated my Makefile.
> I obtained and built the latest zlib and openssl code, as per the 
> directions that came with openssh-3.5p1. I set the Library and Include 
> paths in the Makefile to refer these packages, and I verified (by 
> temporarily renaming the old packages so that references to them would 
> fail.) that the openssh-3.5p1 actually refers to the new packages.
> ------------ THE PROBLEM -----------------------------
> The openssh-3.5p1 code will create all object files successfully. But, when 
> it tries to create program executables, it fails with the following error 
> message:
> [root at sparky openssh-3.5p1]# ppc_405-ld -o ssh ssh.o sshconnect.o 
> sshconnect1.o sshconnect2.o sshtty.o readconf.o clientloop.o -L. 
> -Lopenbsd-compat/ -L ../../lib  -lssh -lopenbsd-compat -lutil -lz 
> -lnsl  -lcrypto -lcrypt
> ppc_405-ld: warning: cannot find entry symbol _start; defaulting to 100028a0
> /mnt/hardhat//devkit/ppc/405/bin//../target/lib/ undefined 
> reference to `atexit'

That looks very much like a broken build environment to me - either your
linker, crt0 or libc is messed up (or a combination).


More information about the openssh-unix-dev mailing list