From: Dan Kegel <dank@kegel.com>
To: "linuxppc-embedded@lists.linuxppc.org"
<linuxppc-embedded@lists.linuxppc.org>
Subject: Re: autoconf and cross-compiling?
Date: Thu, 18 Oct 2001 17:08:42 -0700 [thread overview]
Message-ID: <3BCF6F0A.F83DB82D@kegel.com> (raw)
In-Reply-To: 20011018233528.6F09E10CC5@denx.denx.de
Someone wrote:
> This helps in some situations, but does only part of the job in
> others. In general, autoconf/automake based stuff will fail to build
> more or less completely when it comes to situations where it tries to
> get information of the (supposed target) system by trying to run some
> test programs.
>
> Either it uses the cross compiler to build the test programs - the it
> dies because these programs cannot be run on the host system; or it
> uses the native compiler and it dies later (sometimes REALLY late on
> the target) because it gathers information from the build host which
> does not apply on the target (simple case: getting information about
> endianess when building on a x86 host for a PPC target).
> ...
> There was another posting about this issue by Magnus Damm, see
> http://lists.linuxppc.org/linuxppc-embedded/200109/msg00355.html
Thanks for the link!
I believe there's a fix for the endian problem; see
http://www.gnu.org/software/ac-archive/Cross_Compilation/ac_c_bigendian_cross.html
A similar approch should work for sizeof, shouldn't it?
Don't know about the other ones, like fork etc. :-(
- Dan
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next parent reply other threads:[~2001-10-19 0:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20011018233528.6F09E10CC5@denx.denx.de>
2001-10-19 0:08 ` Dan Kegel [this message]
2001-10-18 22:30 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=3BCF6F0A.F83DB82D@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).