[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Success cross-compiling ncurses-5.3-20030719 -- but can't install

From: Thomas Dickey
Subject: Re: Success cross-compiling ncurses-5.3-20030719 -- but can't install
Date: Thu, 28 Aug 2003 18:28:16 -0400 (EDT)

On Thu, 28 Aug 2003, Dan Kegel wrote:

> Dan Kegel wrote:
> > ncurses-5.3 seems to be smart about not using strstream,
> > but this fails when you specify a cross-compiler with --build-cc ...

that part I'm curious about - didn't get a chance to follow up on it,
but don't know offhand why build-cc would interfere with the C++ compiler
checks.  build-cc is supposed to be used only for the couple of build-time
executables that generate some source files under the ncurses directory.

> > I gather the "right" way to configure ncurses is to override CC and HOSTCC
> > on the commandline, and ignore the --with-build-cc option.
> The following script seems to successfully configure and cross-compile
> ncurses-5.3 with my local gcc-3.3.1 crosstoolchain.  (It doesn't
> use --with-build-cc, since using that interferes with autoconf
> tests and causes the build to fail.)

> It doesn't install it, though. 'make install' tries to run the
> tic that was compiled for the target, which doesn't work, of course.
> Is the output of 'tic' byte-order independent?  If so, I could
> compile ncurses a second time, for the build system, and use the
> 'tic' it produces to install the terminfo entries.

It is supposed to be byte-order independent, yes.

T.E.Dickey <address@hidden>

reply via email to

[Prev in Thread] Current Thread [Next in Thread]