From: Mark Pilon <mpilon@midrivers.com>
To: linuxppc-embedded@lists.linuxppc.org
Subject: Re: building gdb ... no input
Date: Wed, 31 Oct 2001 17:16:06 -0700 [thread overview]
Message-ID: <3BE09446.CC614261@midrivers.com> (raw)
In-Reply-To: 3BE08DCE.1B2E78BF@midrivers.com
I've traced the problem as far as configuring w/ --prefix= pointing
to my ppc tools & glibc home, wanting the tools to be installed
w/ gcc et al.
I haven't debugged it all the way, but the build of readline was
complaining of ambiguous endian-ness because it was picking endian.h
from my ppc include dir ...
So. I'll build w/o specifying a --prefix dir, and make install
specifying an install_root ...
Time to watch the Simpsons ... Doh!
Mark
--
Mark Pilon
Minolta-QMS
P.O. Box 37
Fallon, MT. 59326-0037
1-406-853-0433
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
prev parent reply other threads:[~2001-11-01 0:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20011031213937.C0BC611269@denx.denx.de>
2001-10-31 23:19 ` building gdb Mark Pilon
2001-10-31 23:48 ` building gdb ... no input Mark Pilon
2001-11-01 0:16 ` Mark Pilon [this message]
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=3BE09446.CC614261@midrivers.com \
--to=mpilon@midrivers.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).