From: Cindy Peters <cinpet@adaptivemicro.com>
To: "'linuxppc-embedded@lists.linuxppc.org'"
<linuxppc-embedded@lists.linuxppc.org>
Subject: Cross-compiling standard utilities for MPC823
Date: Tue, 25 Sep 2001 10:12:33 -0500 [thread overview]
Message-ID: <41EDEC3C1B88D51186EB00A0C9CFADF702FA88@AMWMAIL> (raw)
I am attempting to cross-compile the file utilities that I downloaded from
the linuxppc ftp site for the MPC823 on an x86 PC running Redhat 6.2. I am
getting an error when configure is trying to determine the byte ordering.
Following is a clip from the config.log file.
configure:2220: checking whether byte ordering is bigendian
configure:2242: powerpc-linux-gcc -c -g -O2 conftest.c >&5
configure: In function `main':
configure:2236: `bogus' undeclared (first use in this function)
configure:2236: (Each undeclared identifier is reported only once
configure:2236: for each function it appears in.)
configure:2236: parse error before `endian'
configure: failed program was:
#line 2228 "configure"
#include "confdefs.h"
#include <sys/types.h>
#include <sys/param.h>
int
main ()
{
#if !BYTE_ORDER || !BIG_ENDIAN || !LITTLE_ENDIAN
bogus endian macros
#endif
;
return 0;
}
I have tried defining BIG_ENDIAN and BYTE_ORDERING but that is not helping.
Can someone tell me what I need to do to successfully cross-compile this?
Here is the command line I am using.
AR=powerpc-linux-ar AS=powerpc-linux-as LD=powerpc-linux-ld \
RANLIB=powerpc-linux-ranlib CC=powerpc-linux-gcc NM=powerpc-linux-nm \
./configure --build=i686-pc-linux-gnu --host=powerpc-unknown-linux-gnu \
--target=powerpc-unknown-linux-gnu \
--prefix=/opt/usr/local/powerpc-linux
Thanks,
Cindy Peters
Adaptive Micro-Ware, Inc.
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next reply other threads:[~2001-09-25 15:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-25 15:12 Cindy Peters [this message]
2001-09-25 15:18 ` Cross-compiling standard utilities for MPC823 Mark Hatle
2001-09-26 22:14 ` Magnus Damm
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=41EDEC3C1B88D51186EB00A0C9CFADF702FA88@AMWMAIL \
--to=cinpet@adaptivemicro.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).