TECLA configure questions

[M.C.Shao]

  ----- Original Message ----- 
  From: till 
  To: M.C.Shao 
  Cc: Tech-talk ; rtems-users at oarcorp.com ; Eric Norum 
  Sent: Thursday, January 23, 2003 7:04 AM
  Subject: Re: anyone using EPICS baseR3.14.1 on rtems target?


  It seems to me that these are libtecla build errors rather
  than porting errors. It seems that tecla was not built against
  the proper newlib/rtems headers.


Thanks,till, you're right.I checked the install log when building tecla with that "bit" script under the addon-packages source directory, and I find that it is working improperly.
The following is the configure process when using the "bit" script:
--------------------
...
make: Leaving directory `/usr/local/rtems/rtems-packages/rtems-addon-packages-20030120/readline-4.3'
make: Entering directory `/usr/local/rtems/rtems-packages/rtems-addon-packages-20030120/libtecla-1.4.1'
./configure \
 --prefix=/opt/rtems/i386-rtems \
 --libdir=/opt/rtems/i386-rtems/pc386/lib \
 --includedir=/opt/rtems/i386-rtems/pc386/lib/include
loading cache ./config.cache
checking for gcc... (cached) gcc
checking whether the C compiler (gcc  ) works... yes
checking whether the C compiler (gcc  ) is a cross-compiler... no
checking whether we are using GNU C... (cached) yes
checking whether gcc accepts -g... (cached) yes
checking whether make sets ${MAKE}... (cached) yes
checking whether ln -s works... (cached) yes
checking for gawk... (cached) gawk
checking for ranlib... (cached) ranlib
checking host system type... i686-pc-linux-gnu
checking target system type... i686-pc-linux-gnu
checking build system type... i686-pc-linux-gnu
checking how to run the C preprocessor... (cached) gcc -E
checking for tigetstr in -lcurses... (cached) yes
checking for term.h... (cached) yes
checking for curses.h... (cached) yes
checking for reentrant functions... (cached) yes
checking for select system call... (cached) yes
checking for SysV pseudo-terminals... (cached) yes
checking for --version-script in GNU ld... (cached) yes
creating ./config.status
creating Makefile
...
--------------------
Apparently,there are something wrong with the configure files. 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

creating cache ./config.cache
checking for gcc... i386-rtems-gcc 
checking whether the C compiler (i386-rtems-gcc   ) works... yes
checking whether the C compiler (i386-rtems-gcc   ) is a cross-compiler... yes
checking whether we are using GNU C... yes
checking whether i386-rtems-gcc  accepts -g... yes
checking whether make sets ${MAKE}... yes
checking whether ln -s works... yes
checking for gawk... gawk
checking for ranlib... ranlib
checking host system type... i386-pc-rtems
checking target system type... i386-pc-rtems
checking build system type... i386-pc-rtems
checking how to run the C preprocessor... i386-rtems-gcc  -E
checking for tigetstr in -lcurses... no
checking for tigetstr in -lncurses... no
checking for tgetstr in -lcurses... no
checking for term.h... no
checking for ncurses/term.h... no
checking for curses.h... no
checking for ncurses/curses.h... no
checking for reentrant functions... no
checking for select system call... no
checking for SysV pseudo-terminals... no
updating cache ./config.cache
creating ./config.status
creating Makefile
--------------
Seen from the configuration output, the last few "cheking ..." are set to "no".
So I must have lost some configuration options, please give me some suggestions on this.
Thanks in advance, best regards.
--
Shao Mingchao
Engineering Physics Department
Tsinghua University
Beijing,100084,China
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rtems.org/pipermail/users/attachments/20030123/9c5e9bbe/attachment-0001.html>