This is the mail archive of the
insight@sourceware.org
mailing list for the Insight project.
Re: How do I configure for installation?
- From: Brian Dessent <brian at dessent dot net>
- To: "Petrangelo, Jeanne" <jpetrang at ciena dot com>
- Cc: insight at sourceware dot org
- Date: Mon, 04 Jun 2007 16:00:48 -0700
- Subject: Re: How do I configure for installation?
- References: <5lcvls$7vgjim@ripley.ciena.com> <FFCEBA328C76F3499239CB33F887B754206408@mamxm02.ciena.com>
- Reply-to: insight at sourceware dot org
"Petrangelo, Jeanne" wrote:
> Gleaning advice from other posts, I tried this command:
> jpetrang> <path>/configure --target=powerpc-linux --prefix=~/bin
> --exec-prefix = ~/bin/ppc-insight -v 2>&1 | tee configure.out
Syntax matters. Each configure option needs to be passed to the script
as one word, thus you can't use spaces before or after the equals.
Additionally, the shell does not substitute "~" when it's inside an
argument that doesn't look like a filename, so you should use $HOME.
configure --target=powerpc-linux --prefix=$HOME/bin \
--exec-prefix=$HOME/bin/ppc-insight
The reason this resulted in an unknown machine type error is that
autoconf scripts have a legacy support for an obsolete/antiquated way of
specifying the target as a raw argument without any adornment, e.g.
"configure powerpc-linux". Because of the extra spaces, it saw
"~/bin/ppc-insight" as a bare argument word and tried to interpret it as
a target specification.
Brian