From: Mark Hatle <fray@mvista.com>
To: Omanakuttan <omanakuttan@tataelxsi.co.in>
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: installing ncurses for cross compiling
Date: Fri, 07 Mar 2003 14:12:46 -0600 [thread overview]
Message-ID: <3E68FD3E.3070209@mvista.com> (raw)
In-Reply-To: <3E68F912.7000602@tataelxsi.co.in>
Omanakuttan wrote:
>
> Hi,
> I want to write some programs for our serial console using ncurses. I
> have written and tested the apps in i386, now I want to cross compile it.
> When i tried to include the /usr/include/ for ncurses, ppc-gcc issues
> warnings.
Never, NEVER do -I/usr/include. You are attempting to tell the compiler to use
your HOST system's include files when building software for a target. This is
an incorrect development practice. You should be sure to use both headers and
libraries built for the appropriate target architecture.
> I downloaded ncurses-devel-5.2-12.ppc.rpm but rpm refuses to install it
> on i386 because it is not for the architecture. I did not try the
> --force option because of the conflicts.
This will not work. The random RPM you have downloaded is for a host system,
and not a cross development system. You may be able to play some games with it
to get the pieces you want out.. but it's still not the right answer as it was
built with a different compiler and may be linked to other random libraries.
> How shall I get ncurses-devel-5.2-12 for ppc and install it in i386?
You shouldn't. The proper method is to build ncurses in a cross-development
environment and install the components into the appropriate directories. (The
"appropriate directories" varies based on product and what you have built.)
--Mark
> Thanks and regards,
> Om.
>
>
>
>
>
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2003-03-07 20:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-07 19:54 installing ncurses for cross compiling Omanakuttan
2003-03-07 20:12 ` Mark Hatle [this message]
2003-03-07 20:30 ` Wolfgang Denk
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=3E68FD3E.3070209@mvista.com \
--to=fray@mvista.com \
--cc=linuxppc-embedded@lists.linuxppc.org \
--cc=omanakuttan@tataelxsi.co.in \
/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).