TECLA configure questions

[Ralf Corsepius]

On Thu, 2003-01-23 at 13:16, M.C.Shao wrote:

> Apparently,there are something wrong with the configure files.
Well, you only need to know how to invoke configure scripts for
cross-compilation ;)

Due to many packages not having been prepared for cross-compilation,
finding out the appropriate set of options can be difficult.

So, first question: Where did you get these packages from?

If you've downloaded them from OAR, then there should be some kind of
README or install instruction accompanying them, documenting how to
configure the package. If you can't find a such kind of document, file a
bug report into RTEMS bug tracking system at
http://www.oarcorp.com/cgi-bin/gnatsweb.pl

>  Gcc should be a rtems cross gcc, such as i386-rtems-gcc; and host
> type should be rtems target, such as i386-pc-rtems. And some others.
> I read the configure.ac and Makefile.in, and try to find  the right
> way to build libtecla for my i386-rtems target, but I failed. So I am
> writing to you ask for a help. The following is the process which I
> made:

> --------------
> CC="i386-rtems-gcc " ./configure --host=i386-rtems
> --prefix=/opt/rtems/i386-rtems
> --libdir=/opt/rtems/i386-rtems/pc386/lib \
> --includedir=/opt/rtems/i386-rtems/pc386/lib/include
I don't know libtecla, so I can't comment on it, but basically, there
exist several principles to configure a package for cross compilation,
example

1. Package applies --target 
configure --target=<target>

[Typically only found in complex packages consisting of several
sub-packages; Examples: rtems, gcc, binutils, newlib]

2. Package supports cross compilation (eg. rtems/cpukit/configure)
configure --build=<host> --host=<target>

[This is the working principle all newer autoconf-based packages and
some older autoconf-based packages apply.]

3. Package supports native compilation only:
CC=<target>-gcc ./configure

[This is the working principle, applied by older autoconf-based
configurations]

This already might seem utterly complex (It actually isn't, it's only
confusing when being new to it), there exist several packages with
broken configure scripts, which require a wild mixture of this kind of
option passing and additional tricks. 

IIRC; both readline and ncurses fall into this category, but this should
be documented somewhere inside of the packages at OAR.


> checking for ranlib... ranlib
This should be i386-rtems-ranlib

> checking host system type... i386-pc-rtems
> checking target system type... i386-pc-rtems
> checking build system type... i386-pc-rtems
This definitely is not correct, but helping would require to me to know
the source-code.

Ralf