linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Dan Kegel <dank@kegel.com>
To: "linuxppc-embedded@lists.linuxppc.org"
	<linuxppc-embedded@lists.linuxppc.org>
Subject: autoconf and cross-compiling?
Date: Thu, 18 Oct 2001 15:30:37 -0700	[thread overview]
Message-ID: <3BCF580D.47B44367@kegel.com> (raw)


I'm trying to document the right way to cross-compile
applications which use autoconf/automake.  configure
has a --target flag, but I can't see how to get it to do anything
useful.

The goat book has what looks like a helpful section
  http://sources.redhat.com/autobook/autobook/autobook_261.html#SEC261
which talks about the macros AC_CANONICAL_SYSTEM and AC_ARG_PROGRAM,
but it turns out this only affects tool names *when installing*.
It's useful when *building* cross compilers, not when using them.

My best guess at the moment is:
  Before running 'configure', set the environment variables
  CC, CXX, RANLIB, and AR to point to the cross-development
  tools you want to use, *and* tell configure the target name,
  e.g.
    CC=powerpc-linux-gcc CXX=powerpc-linux-g++ RANLIB=powerpc-linux-ranlib AR=powerpc-linux-ar ./configure --target=powerpc-linux

Is this right?

If so, this is suprisingly clumsy.  I would expect configure to let you set
both the target name and the tool names in one fell swoop, e.g.
    ./configure --with-target=powerpc-linux
but since few people do cross-development, maybe this hasn't been made easy.

- Dan

(originally posted to gnu.gcc.help, but no response there)

** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

             reply	other threads:[~2001-10-18 22:30 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-10-18 22:30 Dan Kegel [this message]
     [not found] <20011018233528.6F09E10CC5@denx.denx.de>
2001-10-19  0:08 ` autoconf and cross-compiling? Dan Kegel

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3BCF580D.47B44367@kegel.com \
    --to=dank@kegel.com \
    --cc=linuxppc-embedded@lists.linuxppc.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).