configuration

[Joel Sherrill]

"D.G.Somerton" wrote:
> 
> Hello,
> 
>   I am 'trying' to configure the RTEMS on cygwin. This is failing. see
> previous posts.
> 
>   Someone suggested that VC environment variables may clashing.
>   This cannot be, as VC uses LIB, INCLUDE, MSVCDIR, MSDEVDIR
>   info gcc: Invoking: Environment Variables:
>     LIBRARY_PATH
>     C_INCLUDE_PATH
> 
>   Someone suggested linking cc to gcc.
>   This is no good, as gcc is /bin/../lib/gcc-lib/i686-pc-cygwin/2.95.2
>   The cross compiler is /tool/bin/m68k-rtems-gcc.exe
>   I have linked cc to the cross compiler.

cc.exe should be the native compiler.  Whereever gcc.exe is.. make a
link
to cc.exe there.

Make sure you have untar'ed the source and are building in a directory
that is mounted with -b.

>   Compiling a test program works. i.e. cc -v -S f.c produces f.s.
> 
> file f.c
> int f(int x)
> {
>   return x + 1;
> }
> 
> Reading specs from /opt/rtems/lib/gcc-lib/m68k-rtems/2.95.2/specs
> gcc version 2.95.2 19991024 (release)
> /opt/rtems/lib/gcc-lib/m68k-rtems/2.95.2/cpp.exe -lang-c -v -D__GNUC__=2 -D_
> _GNUC_MINOR__=95 -Dmc68000 -Drtems -D__rtems__ -D__ELF__ -D__mc68000__ -D__r
> tems__ -D__rtems__ -D__ELF__ -D__mc68000 -D__rtems -Asystem(rtems) -Acpu(mc6
> 8000) -Acpu(m68k) -Amachine(m68k) f.c H:\TEMP/ccLDGzBk.i
> GNU CPP version 2.95.2 19991024 (release) (68k, Motorola syntax)
> #include "..." search starts here:
> #include <...> search starts here:
> /opt/rtems/lib/gcc-lib/m68k-rtems/2.95.2/include
> /opt/rtems/lib/gcc-lib/m68k-rtems/2.95.2/../../../../m68k-rtems/include
> End of search list.
> The following default directories have been omitted from the search path:
> /opt/rtems/lib/gcc-lib/m68k-rtems/2.95.2/../../../../include/g++-3
> /opt/rtems/lib/gcc-lib/m68k-rtems/2.95.2/../../../../m68k-rtems/sys-include
> End of omitted list.
> /opt/rtems/lib/gcc-lib/m68k-rtems/2.95.2/cc1.exe
> H:\TEMP/ccLDGzBk.i -quiet -dumpbase f.c -version -o f.s
> GNU C version 2.95.2 19991024 (release) (m68k-rtems) compiled by GNU C
> version 2.95.2 19991024 (release).
> 
> file f.s
>  .file "f.c"
> gcc2_compiled.:
> .text
> .globl f
>  .type  f, at function
> f:
>  link.w %a6,#0
>  move.l 8(%a6),%d1
>  addq.l #1,%d1
>  move.l %d1,%d0
>  jbra .L2
> .L2:
>  unlk %a6
>  rts
> .Lfe1:
>  .size  f,.Lfe1-f
>  .ident "GCC: (GNU) 2.95.2 19991024 (release)"
> 
> --------------------------------------------
> 
> After the failed configure, here are the logs.
> /tools/../build/config.log and /tools/../build/tools/build/config.log
> 
> It seems that the configuration cannot determine that this is cygwin.
> 
> This file contains any messages produced by compilers while
> running configure, to aid debugging if configure makes a mistake.
> 
> Firstly: /tools/../build/config.log
> configure:566: checking for RTEMS Version
> configure:635: checking host system type
> configure:656: checking target system type
> configure:674: checking build system type
> configure:697: checking rtems target cpu
> configure:734: checking for a BSD compatible install
> configure:787: checking whether build environment is sane
> configure:844: checking whether make sets ${MAKE}
> configure:883: checking for working aclocal
> configure:896: checking for working autoconf
> configure:909: checking for working automake
> configure:922: checking for working autoheader
> configure:935: checking for working makeinfo
> configure:949: checking whether to enable maintainer-specific portions of
> Makefiles
> configure:1138: checking if the test suites are enabled?
> configure:1159: checking if cpu m68k is supported
> 
> Secondly: /tools/../build/tools/build/config.log
> This file contains any messages produced by compilers while
> running configure, to aid debugging if configure makes a mistake.
> 
> configure:544: checking for RTEMS Version
> configure:583: checking host system type
> configure:616: checking for a BSD compatible install
> configure:669: checking whether build environment is sane
> configure:726: checking whether make sets ${MAKE}
> configure:765: checking for working aclocal
> configure:778: checking for working autoconf
> configure:791: checking for working automake
> configure:804: checking for working autoheader
> configure:817: checking for working makeinfo
> configure:831: checking whether to enable maintainer-specific portions of
> Makefiles
> configure:854: checking for Cygwin environment
> configure:870: cc -c   conftest.c 1>&5
> configure: In function `main':
> configure:866: `__CYGWIN32__' undeclared (first use in this function)
> configure:866: (Each undeclared identifier is reported only once
> configure:866: for each function it appears in.)
> configure: failed program was:
> #line 859 "configure"
> #include "confdefs.h"
> 
> int main() {
> 
> #ifndef __CYGWIN__
> #define __CYGWIN__ __CYGWIN32__
> #endif
> return __CYGWIN__;
> ; return 0; }
> configure:887: checking for mingw32 environment
> configure:899: cc -c   conftest.c 1>&5
> configure: In function `main':
> configure:895: `__MINGW32__' undeclared (first use in this function)
> configure:895: (Each undeclared identifier is reported only once
> configure:895: for each function it appears in.)
> configure: failed program was:
> #line 892 "configure"
> #include "confdefs.h"
> 
> int main() {
> return __MINGW32__;
> ; return 0; }
> configure:918: checking for executable suffix
> configure:928: cc -o conftest    conftest.c  1>&5
> Assembler messages:
> Error: Can't open
>  for reading.
> : No such file or directory
> 
> ---------------------------------
> 
> So as you can see,  it is looking for __CYGWIN32__
> What is this?
> Where does it come from?
> How do I set it so the configuration works?
> 
> D.G.Somerton
> Very frustrated, a supposedly simple procedure is in fact extremely
> complicated. Why?

-- 
Joel Sherrill, Ph.D.             Director of Research & Development
joel at OARcorp.com                 On-Line Applications Research
Ask me about RTEMS: a free RTOS  Huntsville AL 35805
   Support Available             (256) 722-9985