Re: [SPAM] cross-compilation failing

From: John Zavgren (john_at_zavgren.com)
Date: 10/13/04

  • Next message: C. Linus Hicks: "Re: Password auth turned off in OpenSSH"
    Date: Wed, 13 Oct 2004 12:35:20 -0400
    To: olivier@singla.us
    
    
    

    I wrestled with this problem once. The development machine was an i386
    host (running redhat Linux) and a Power PC platform (running Monta Vista
    Linux).

    After many frustrating days of trying to get cross compilation working,
    I had an epiphany. I NFS mounted the Monta Vista development environment
    and then performed a chroot operation; then the development environment
    became my root partition. From that point forward I could configure,
    compile, and install the openssh code natively from the power PC
    platform. After I completed the installation, I incorporated the shared
    object library files and executables into my initial RAM disk.

    Of course, it would be nice to have the cross compilation working, but
    this dirty trick works should work.

    John Zavgren
    john@zavgren.com

    olivier@singla.us wrote:

    >Hi,
    >
    >Cross-Compiling openssh is failing (target=powerpc).
    >Any ideas why ?
    >
    >Thanks!
    >Olivier
    >
    >~/ice/devel/openssh-3.9p1$ ./configure --prefix=/home/osingla/ice/openssh
    >--build=i686-linux --h ost=powerpc-linux --sysconfdir=/etc/ssh checking
    >for powerpc-linux-gcc... powerpc-linux-gcc
    >checking for C compiler default output file name... a.out
    >checking whether the C compiler works... yes
    >checking whether we are cross compiling... yes
    >checking for suffix of executables...
    >checking for suffix of object files... o
    >checking whether we are using the GNU C compiler... yes
    >checking whether powerpc-linux-gcc accepts -g... yes
    >checking for powerpc-linux-gcc option to accept ANSI C... none needed
    >checking build system type... i686-pc-linux-gnu
    >checking host system type... powerpc-unknown-linux-gnu
    >checking whether byte ordering is bigendian... yes
    >checking for gawk... gawk
    >checking how to run the C preprocessor... powerpc-linux-gcc -E
    >checking for powerpc-linux-ranlib... powerpc-linux-ranlib
    >checking for a BSD-compatible install... /usr/bin/install -c
    >checking for ar... /usr/bin/ar
    >checking for cat... /bin/cat
    >checking for kill... /bin/kill
    >checking for perl5... no
    >checking for perl... /usr/bin/perl
    >checking for sed... /bin/sed
    >checking for ent... no
    >checking for bash... /bin/bash
    >checking for ksh... (cached) /bin/bash
    >checking for sh... (cached) /bin/bash
    >checking for sh... /bin/sh
    >checking for groupadd... /usr/sbin/groupadd
    >checking for useradd... /usr/sbin/useradd
    >checking for pkgmk... no
    >checking for special C compiler options needed for large files... no
    >checking for _FILE_OFFSET_BITS value needed for large files... 64
    >checking for _LARGE_FILES value needed for large files... no
    >checking for login... /bin/login
    >checking for passwd... /usr/bin/passwd
    >checking for inline... inline
    >checking compiler and flags for sanity... no
    >configure: error: *** compiler cannot create working executables, check
    >config.log ***
    >~/ice/devel/openssh-3.9p1$
    >
    >
    >
    >
    >
    >
    >

    
    



  • Next message: C. Linus Hicks: "Re: Password auth turned off in OpenSSH"

    Relevant Pages

    • Re: interesting use of NEXT SENTENCE vs. CONTINUE
      ... These days I don't do compiler maintenance, but I HAVE done in the past, so ... You had a chance to point out how adherence to the standard can improve ... >> compile it WITH MINOR MODIFICATIONS for a specific platform. ... > platform-specific extension to COBOL ...
      (comp.lang.cobol)
    • Re: interesting use of NEXT SENTENCE vs. CONTINUE
      ... I DID think any old compiler would be able to ... > compile it WITH MINOR MODIFICATIONS for a specific platform. ... > not going to go to the Standard to see what SHOULD work. ... If you write your COBOL code avoiding the things that are marked as ...
      (comp.lang.cobol)
    • Re: Standard Ada Preprocessor
      ... because Ada cannot deal with the portability issues. ... > you are interfacing directly to some special-purpose hardware. ... by their nature not compiler ... one platform you get 3 members back, and on another you get 5, ...
      (comp.lang.ada)
    • Re: C portability is a myth
      ... > solicitation for the availability of a compiler for a given platform. ... If the source is pure Standard C ... can be successfully ported to all implementations. ...
      (comp.lang.c)
    • Re: C portability is a myth
      ... > solicitation for the availability of a compiler for a given platform. ... People frequently talk about porting applications where no ... Yet further down you say the Java standard ports. ...
      (comp.lang.c)