From: "Dave Korn" <dave.korn@artimi.com>
To: "'Jim Blandy'" <jimb@red-bean.com>, <jamessteward@optusnet.com.au>
Cc: "'Simon Richter'" <Simon.Richter@picotux.com>, <gdb@sources.redhat.com>
Subject: RE: Re: Really cross compiling gdb.
Date: Thu, 12 Jan 2006 12:41:00 -0000 [thread overview]
Message-ID: <SERRANOUuEhjJ8uT6Ss00000097@SERRANO.CAM.ARTIMI.COM> (raw)
In-Reply-To: <8f2776cb0601111644k15ddf9e7vd021c8a7ce85f2d2@mail.gmail.com>
Jim Blandy wrote:
> On 1/11/06, James Steward <jamessteward@optusnet.com.au> wrote:
>> Thanks for the tip - but it doesn't seem to have worked for me :-(
>
> I'm not too familiar with this sort of cross-building, but I believe
> that ought to work. I think you're going to have to grovel through
> the configure scripts and figure out what's going wrong.
I have an idea!
James Steward wrote:
> My configure command now looks like this.
>
> ../configure
> --prefix=/usr/local/arm-linux/gcc-3.4.4-glibc-2.3.5/arm-xscale-linux-gnu/
> --program-prefix=arm-xscale-linux-gnu- --build=`../config.guess`
> --target=arm-xscale-linux-gnu --host=arm-xscale-linux-gnu
Perhaps this is a manifestation of the
can't-find-cross-tools-when-configuring-with-a-relative-path bug, and perhaps
using an absolute path to the configure script will sort it out?
(Or perhaps not; this is a bit of a WAG :-P)
cheers,
DaveK
--
Can't think of a witty .sigline today....
next prev parent reply other threads:[~2006-01-12 12:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-12 0:12 James Steward
2006-01-12 0:44 ` Jim Blandy
2006-01-12 12:41 ` Dave Korn [this message]
2006-01-12 14:52 ` Daniel Jacobowitz
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=SERRANOUuEhjJ8uT6Ss00000097@SERRANO.CAM.ARTIMI.COM \
--to=dave.korn@artimi.com \
--cc=Simon.Richter@picotux.com \
--cc=gdb@sources.redhat.com \
--cc=jamessteward@optusnet.com.au \
--cc=jimb@red-bean.com \
/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