What about boehm-gc under cygwin?

What about boehm-gc under cygwin?

[Christian Jönsson]

I just tried compiling gcc trunk under windows xp/cygwin.

I did the boehm-gc and ran it's test:

make[3]: Entering directory
`/usr/local/src/gcc-dev/objdir/i686-pc-cygwin/boehm-gc'
make "AR_FLAGS=rc"      "CC_FOR_BUILD=gcc"      "CFLAGS=-g -O2"
"CXXFLAGS=-g -O2"       "CFLAGS_FOR_BUILD="     "CFLAGS_FOR_TARGET=-g
-O2"      "INSTALL=/bin/sh /usr/local/src/gcc-dev/gcc/install-sh -c"
"INSTALL_DATA=/bin/sh /usr/local/src/gcc-dev/gcc/install-sh -c -m 644"
"INSTALL_PROGRAM=/bin/sh /usr/local/src/gcc-dev/gcc/install-sh -c "
"INSTALL_SCRIPT=/bin/sh /usr/local/src/gcc-dev/gcc/install-sh -c"
"LDFLAGS="      "LIBCFLAGS=-g -O2"      "LIBCFLAGS_FOR_TARGET=-g -O2"
"MAKE=make"     "MAKEINFO=makeinfo   "  "PICFLAG=" "PICFLAG_FOR_TARGET="
"SHELL=/bin/sh"         "EXPECT=expect"         "RUNTEST=runtest"
"RUNTESTFLAGS="         "exec_prefix=/usr/local"
"infodir=/usr/local/info"       "libdir=/usr/local/lib"
"prefix=/usr/local"
"tooldir=/usr/local/i686-pc-cygwin"     "AR=ar"         "AS=as"
"CC=/usr/local/src/gcc-dev/objdir/gcc/xgcc
-B/usr/local/src/gcc-dev/objdir/gcc/ -B/usr/local/i686-pc-cygwin/bin/
-B/usr/local/i686-pc-cygwin/lib/ -isystem
/usr/local/i686-pc-cygwin/include"
"CXX=/usr/local/src/gcc-dev/objdir/gcc/g++
-B/usr/local/src/gcc-dev/objdir/gcc/ -nostdinc++ -nostdinc++
-I/usr/local/src/gcc-dev/objdir/
i686-pc-cygwin/libstdc++-v3/include/i686-pc-cygwin
-I/usr/local/src/gcc-dev/objdir/i686-pc-cygwin/libstdc++-v3/include
-I/usr/local/src/gcc-dev/gcc/libstdc++-v3/libsupc++
-I/usr/local/src/gcc-dev/gcc/libstdc++-v3/libio
-I/usr/local/src/gcc-dev/gcc/libstdc++-v3/include/backward
-I/usr/local/src/gcc-dev/gcc/libstdc++-v3/testsuite
-L/usr/local/src/gcc-dev/objdir/i686-pc-cygwin/libstdc++-v3/src
-L/usr/local/src/gcc-dev/objdir/i686-pc-cygwin/libstdc++-v3/src/.libs
-B/usr/local/i686-pc-cygwin/bin/ -B/usr/local/i686-pc-cygwin/lib/
-isystem /usr/local/i686-pc-cygwin/include"   "LD=ld"
"LIBCFLAGS=-g -O2"      "NM=nm"         "PICFLAG="      "RANLIB=ranlib"
"DESTDIR=" check-TESTS
make[4]: Entering directory
`/usr/local/src/gcc-dev/objdir/i686-pc-cygwin/boehm-gc'
Completed 1 tests
Allocated 648021 collectable objects
Allocated 101 uncollectable objects
Allocated 1250000 atomic objects
Allocated 10880 stubborn objects
Finalized 2206/2206 objects - finalization is probably ok
Total number of bytes allocated is 60657252
Final heap size is 9428992 bytes
Collector appears to work
PASS: gctest
==================
All 1 tests passed
==================
make[4]: Leaving directory
`/usr/local/src/gcc-dev/objdir/i686-pc-cygwin/boehm-gc'



But if I just run the configure script, I get this:

Configuring for a i686-pc-cygwin host.
*** This configuration is not supported in the following subdirectories:
     target-libffi target-boehm-gc target-zlib target-libjava
    (Any other directories should still work fine.)

So, my questions are these; Is boehm-gc supported under cygwin and if
so, why does the configury report not supported for target-boehm-gc?

Cheers,

/ChJ

RE: What about boehm-gc under cygwin?

[Billinghurst, David (CRTS)]

I got past this bug, and the next one, last night.  I will try and 
post the one line hacks later today.  

Then I will try and work on the bug after that :->.  Actually it doesn't
look too bad.  I suspect we are close to getting something that compiles. 

-----Original Message-----
From: Tom Tromey [mailto:tromey@redhat.com]
Sent: Wednesday, 1 May 2002 7:28 
To: Christian Jönsson
Cc: Billinghurst, David (CRTS); gcc@gcc.gnu.org
Subject: Re: What about boehm-gc under cygwin?


>>>>> "Christian" == Christian Jönsson <christian@j-son.org> writes:

Christian> You're right. It didn't get compiled.
Christian> I just tried the gcc-20020429 snapshot, it came to this:

Thanks.  I guess we still need someone to work on this port.

Tom

Re: What about boehm-gc under cygwin?

[Tom Tromey]

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 255 bytes --]

>>>>> "Christian" == Christian Jönsson <christian@j-son.org> writes:

Christian> You're right. It didn't get compiled.
Christian> I just tried the gcc-20020429 snapshot, it came to this:

Thanks.  I guess we still need someone to work on this port.

Tom

RE: What about boehm-gc under cygwin?

[Christian Jönsson]

You're right. It didn't get compiled.

I just tried the gcc-20020429 snapshot, it came to this:


/usr/local/src/objdir-gcc-20020429/gcc/xgcc -shared-libgcc
-B/usr/local/src/objdir-gcc-20020429/gcc/ -nostdinc++
-L/usr/local/src/objdir-gcc-20020429/i686-pc-cygwin/libstdc++-v3/src
-L/usr/local/src/objdir-gcc-20020429/i686-pc-cygwin/libstdc++-v3/src/.li
bs -B/usr/local/i686-pc-cygwin/bin/ -B/usr/local/i686-pc-cygwin/lib/
-isystem /usr/local/i686-pc-cygwin/include -DHAVE_CONFIG_H -I.
-I../../../gcc-20020429/libjava -I./include -I./gcj
-I../../../gcc-20020429/libjava -Iinclude
-I../../../gcc-20020429/libjava/include
-I../../../gcc-20020429/libjava/../boehm
-gc/include -DSILENT=1 -DNO_SIGNALS=1 -DNO_EXECUTE_PERMISSION=1
-DALL_INTERIOR_POINTERS=1 -DJAVA_FINALIZATION=1 -DGC_GCJ_SUPPORT=1
-DATOMIC_UNCOLLECTABLE=1 -I../../../gcc-20020429/libjava/libltdl
-I../../../gcc-20020429/libjava/libltdl
-I../../../gcc-20020429/libjava/.././libjava/../gcc
-I../../../gcc-20020429/libjava/../libffi/include -I../libffi/include
-fno-rtti -fnon-call-exceptions -fdollars-in-identifiers
-D__NO_MATH_INLINES -ffloat-store -W -Wall -D_GNU_SOURCE
-DPREFIX=\"/usr/local\" -g -O2 -MD -MT java/lang/natSystem.lo -MF
java/lang/natSystem.pp -c
../../../gcc-20020429/libjava/java/lang/natSystem.cc -o
java/lang/natSystem.o
../../../gcc-20020429/libjava/java/lang/natSystem.cc: In static member
function

   `static java::lang::String* java::lang::System::getSystemTimeZone()':
../../../gcc-20020429/libjava/java/lang/natSystem.cc:255: invalid
conversion
   from `char*(*)()' to `long int'
make[3]: *** [java/lang/natSystem.lo] Error 1
make[3]: Leaving directory
`/usr/local/src/objdir-gcc-20020429/i686-pc-cygwin/libjava'
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory
`/usr/local/src/objdir-gcc-20020429/i686-pc-cygwin/libjava'
make[1]: *** [all-target-libjava] Error 2
make[1]: Leaving directory `/usr/local/src/objdir-gcc-20020429'
make: *** [bootstrap-lean] Error 2


Sorry for my mistake previously, I really thought it was built.

Cheers,

/ChJ


-----Original Message-----
From: Tom Tromey [mailto:tromey@redhat.com] 
Sent: Tuesday, April 30, 2002 8:02 PM
To: Christian Jönsson
Cc: 'David Billinghurst'; gcc@gcc.gnu.org
Subject: Re: What about boehm-gc under cygwin?


>>>>> "Christian" == Christian Jönsson <christian@j-son.org> writes:

Christian> I'm on a macine local NTFS (Windows XP). As I mentioned 
Christian> before, the boehm-gc test pass:

Ok.

Christian> When it comes to invetigating... Well, this is a good reason:

Christian> 0: Can't find default package `java.lang'. Check the 
Christian> CLASSPATH environment variable and the access to the archives

Was libgcj actually built?  In particular look for libgcj.jar in the
target build directory (<build>/<target>/libjava/libgcj.jar).
Did you `make install'?  (You shouldn't have to, but maybe there is a
bug.)

Tom

Re: What about boehm-gc under cygwin?

[Tom Tromey]

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 611 bytes --]

>>>>> "Christian" == Christian Jönsson <christian@j-son.org> writes:

Christian> I'm on a macine local NTFS (Windows XP). As I mentioned
Christian> before, the boehm-gc test pass:

Ok.

Christian> When it comes to invetigating... Well, this is a good reason:

Christian> 0: Can't find default package `java.lang'. Check the CLASSPATH
Christian> environment variable and the access to the archives

Was libgcj actually built?  In particular look for libgcj.jar in the
target build directory (<build>/<target>/libjava/libgcj.jar).
Did you `make install'?  (You shouldn't have to, but maybe there is a bug.)

Tom

RE: What about boehm-gc under cygwin?

[Christian Jönsson]

I'm on a macine local NTFS (Windows XP). As I mentioned before, the
boehm-gc test pass:

make[4]: Entering directory
`/usr/local/src/gcc-dev/objdir/i686-pc-cygwin/boehm-gc'
Completed 1 tests
Allocated 648021 collectable objects
Allocated 101 uncollectable objects
Allocated 1250000 atomic objects
Allocated 10880 stubborn objects
Finalized 2206/2206 objects - finalization is probably ok
Total number of bytes allocated is 60657252
Final heap size is 9428992 bytes
Collector appears to work
PASS: gctest
==================
All 1 tests passed
==================
make[4]: Leaving directory
`/usr/local/src/gcc-dev/objdir/i686-pc-cygwin/boehm-gc'

When it comes to invetigating... Well, this is a good reason:

Executing on host:
/usr/local/src/gcc-dev/objdir/i686-pc-cygwin/libjava/testsuite/../libtoo
l --silent --tag=GCJ --mode=compile
/usr/local/src/gcc-dev/objdir/gcc/gcj
-B/usr/local/src/gcc-dev/objdir/gcc/ --encoding=UTF-8
-B/usr/local/src/gcc-dev/objdir/i686-pc-cygwin/libjava/testsuite/../  -c
-o
/usr/local/src/gcc-dev/objdir/i686-pc-cygwin/libjava/testsuite/abstr.o
/usr/local/src/gcc-dev/gcc/libjav
a/testsuite/libjava.compile/abstr.java    (timeout = 300)
spawn
/usr/local/src/gcc-dev/objdir/i686-pc-cygwin/libjava/testsuite/../libtoo
l--silent --tag=GCJ --mode=compile /usr/local/src/gcc-dev/objdir/gcc/gcj
-B/usr/local/src/gcc-dev/objdir/gcc/ --encoding=UTF-8
-B/usr/local/src/gcc-dev/objdir/i686-pc-cygwin/libjava/testsuite/../ -c
-o
/usr/local/src/gcc-dev/objdir/i686-pc-cygwin/libjava/testsuite/abstr.o
/usr/local/src/gcc-dev/gcc/libjava/testsuite/libjava.compile/abstr.java
/usr/local/src/gcc-dev/gcc/libjava/testsuite/libjava.compile/abstr.java:
0: Can't find default package `java.lang'. Check the CLASSPATH
environment variable and the access to the archives
1 error
compiler exited with status 1
output is:
/usr/local/src/gcc-dev/gcc/libjava/testsuite/libjava.compile/abstr.java:
0: Can't find default package `java.lang'. Check the CLASSPATH
environment variable and the access to the archives
1 error

FAIL: abstr compilation from source
FAIL: abstr byte compilation
UNTESTED: abstr compilation from bytecode

Then it goes on...


Anything else I can check?

Cheers,

/ChJ


-----Original Message-----
From: gcc-owner@gcc.gnu.org [mailto:gcc-owner@gcc.gnu.org] On Behalf Of
Tom Tromey
Sent: Monday, April 29, 2002 11:44 PM
To: Christian Jönsson
Cc: 'David Billinghurst'; gcc@gcc.gnu.org
Subject: Re: What about boehm-gc under cygwin?


>>>>> "Christian" == Christian Jönsson <christian@j-son.org> writes:

Christian> Well, it compiles but...

You must be on a case-sensitive file system.  As far as I know we
still can't build libgcj on a case-insensitive file system, due to a
longstanding gcj bug.

Christian> See
Christian> http://gcc.gnu.org/ml/gcc-testresults/2002-04/msg01106.html

When all the exec tests fail like this, it usually means something
fairly fundamental, like a GC or binutils problem.  Can you investigate?

Tom

Re: What about boehm-gc under cygwin?

[Tom Tromey]

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 498 bytes --]

>>>>> "Christian" == Christian Jönsson <christian@j-son.org> writes:

Christian> Well, it compiles but...

You must be on a case-sensitive file system.  As far as I know we
still can't build libgcj on a case-insensitive file system, due to a
longstanding gcj bug.

Christian> See
Christian> http://gcc.gnu.org/ml/gcc-testresults/2002-04/msg01106.html

When all the exec tests fail like this, it usually means something
fairly fundamental, like a GC or binutils problem.  Can you investigate?

Tom

RE: What about boehm-gc under cygwin?

[Christian Jönsson]

Well, it compiles but... See
http://gcc.gnu.org/ml/gcc-testresults/2002-04/msg01106.html

How about using --enable-sjlj-exceptions... Is that really needed
nowadays?

Cheers,

/ChJ

-----Original Message-----
From: kelley.r.cook@gm.com [mailto:kelley.r.cook@gm.com] 
Sent: Monday, April 29, 2002 10:14 PM
To: Christian Jönsson
Cc: David Billinghurst; gcc@gcc.gnu.org
Subject: RE: What about boehm-gc under cygwin?


>I see, thanks for explaining that.
>
>Cheers,
>
>/ChJ
>>It gets built if java is enabled.  Try configuring with:  
>>--enable-languages=c++,g77,java, or
>>  don't specify --enable-languages at all

Not quite,
It will get compiled if "--enable-libgcj" is specified.  Java is enabled
by default under cygwin, but libjava [aka libgcj] is not.

Last time I checked though, libjava wouldn't compile under Cygwin, but
then again, I haven't tried it in a while.

Kelley Cook

RE: What about boehm-gc under cygwin?

[kelley.r.cook]

>I see, thanks for explaining that.
>
>Cheers,
>
>/ChJ
>>It gets built if java is enabled.  Try configuring with:
>> --enable-languages=c++,g77,java, or
>>  don't specify --enable-languages at all

Not quite,
It will get compiled if "--enable-libgcj" is specified.  Java is enabled by default under cygwin, but libjava [aka libgcj] is not.

Last time I checked though, libjava wouldn't compile under Cygwin, but then again, I haven't tried it in a while.

Kelley Cook

RE: What about boehm-gc under cygwin?

[Robert Dewar]

Incidentally, to combine two recent threads, note that the boehm-gc is
incompatible with the use of virtual origins for array addressing. This
is not a bug, it is fundamental, just something you have to keep in mind :-)

RE: What about boehm-gc under cygwin?

[Christian Jönsson]

I see, thanks for explaining that.

Cheers,

/ChJ


-----Original Message-----
From: Billinghurst, David (CRTS)
[mailto:David.Billinghurst@riotinto.com] 
Sent: Monday, April 29, 2002 3:49 PM
To: Christian Jönsson; gcc@gcc.gnu.org
Subject: RE: What about boehm-gc under cygwin?


It gets built if java is enabled.  Try configuring with:
  --enable-languages=c++,g77,java, or
  don't specify --enable-languages at all

-----Original Message-----
From: Christian Jönsson [mailto:christian@j-son.org]
Sent: Monday, 29 April 2002 6:15 
To: gcc@gcc.gnu.org
Subject: What about boehm-gc under cygwin?


I just tried compiling gcc trunk under windows xp/cygwin.

I did the boehm-gc and ran it's test:

make[3]: Entering directory
`/usr/local/src/gcc-dev/objdir/i686-pc-cygwin/boehm-gc'
make "AR_FLAGS=rc"      "CC_FOR_BUILD=gcc"      "CFLAGS=-g -O2"
"CXXFLAGS=-g -O2"       "CFLAGS_FOR_BUILD="     "CFLAGS_FOR_TARGET=-g
-O2"      "INSTALL=/bin/sh /usr/local/src/gcc-dev/gcc/install-sh -c"
"INSTALL_DATA=/bin/sh /usr/local/src/gcc-dev/gcc/install-sh -c -m 644"
"INSTALL_PROGRAM=/bin/sh /usr/local/src/gcc-dev/gcc/install-sh -c "
"INSTALL_SCRIPT=/bin/sh /usr/local/src/gcc-dev/gcc/install-sh -c"
"LDFLAGS="      "LIBCFLAGS=-g -O2"      "LIBCFLAGS_FOR_TARGET=-g -O2"
"MAKE=make"     "MAKEINFO=makeinfo   "  "PICFLAG=" "PICFLAG_FOR_TARGET="
"SHELL=/bin/sh"         "EXPECT=expect"         "RUNTEST=runtest"
"RUNTESTFLAGS="         "exec_prefix=/usr/local"
"infodir=/usr/local/info"       "libdir=/usr/local/lib"
"prefix=/usr/local"
"tooldir=/usr/local/i686-pc-cygwin"     "AR=ar"         "AS=as"
"CC=/usr/local/src/gcc-dev/objdir/gcc/xgcc
-B/usr/local/src/gcc-dev/objdir/gcc/ -B/usr/local/i686-pc-cygwin/bin/
-B/usr/local/i686-pc-cygwin/lib/ -isystem
/usr/local/i686-pc-cygwin/include"
"CXX=/usr/local/src/gcc-dev/objdir/gcc/g++
-B/usr/local/src/gcc-dev/objdir/gcc/ -nostdinc++ -nostdinc++
-I/usr/local/src/gcc-dev/objdir/
i686-pc-cygwin/libstdc++-v3/include/i686-pc-cygwin
-I/usr/local/src/gcc-dev/objdir/i686-pc-cygwin/libstdc++-v3/include
-I/usr/local/src/gcc-dev/gcc/libstdc++-v3/libsupc++
-I/usr/local/src/gcc-dev/gcc/libstdc++-v3/libio
-I/usr/local/src/gcc-dev/gcc/libstdc++-v3/include/backward
-I/usr/local/src/gcc-dev/gcc/libstdc++-v3/testsuite
-L/usr/local/src/gcc-dev/objdir/i686-pc-cygwin/libstdc++-v3/src
-L/usr/local/src/gcc-dev/objdir/i686-pc-cygwin/libstdc++-v3/src/.libs
-B/usr/local/i686-pc-cygwin/bin/ -B/usr/local/i686-pc-cygwin/lib/
-isystem /usr/local/i686-pc-cygwin/include"   "LD=ld"
"LIBCFLAGS=-g -O2"      "NM=nm"         "PICFLAG="      "RANLIB=ranlib"
"DESTDIR=" check-TESTS
make[4]: Entering directory
`/usr/local/src/gcc-dev/objdir/i686-pc-cygwin/boehm-gc'
Completed 1 tests
Allocated 648021 collectable objects
Allocated 101 uncollectable objects
Allocated 1250000 atomic objects
Allocated 10880 stubborn objects
Finalized 2206/2206 objects - finalization is probably ok
Total number of bytes allocated is 60657252
Final heap size is 9428992 bytes
Collector appears to work
PASS: gctest
==================
All 1 tests passed
==================
make[4]: Leaving directory
`/usr/local/src/gcc-dev/objdir/i686-pc-cygwin/boehm-gc'



But if I just run the configure script, I get this:

Configuring for a i686-pc-cygwin host.
*** This configuration is not supported in the following subdirectories:
     target-libffi target-boehm-gc target-zlib target-libjava
    (Any other directories should still work fine.)

So, my questions are these; Is boehm-gc supported under cygwin and if
so, why does the configury report not supported for target-boehm-gc?

Cheers,

/ChJ

RE: What about boehm-gc under cygwin?

[Billinghurst, David (CRTS)]

It gets built if java is enabled.  Try configuring with:
  --enable-languages=c++,g77,java, or
  don't specify --enable-languages at all

-----Original Message-----
From: Christian Jönsson [mailto:christian@j-son.org]
Sent: Monday, 29 April 2002 6:15 
To: gcc@gcc.gnu.org
Subject: What about boehm-gc under cygwin?


I just tried compiling gcc trunk under windows xp/cygwin.

I did the boehm-gc and ran it's test:

make[3]: Entering directory
`/usr/local/src/gcc-dev/objdir/i686-pc-cygwin/boehm-gc'
make "AR_FLAGS=rc"      "CC_FOR_BUILD=gcc"      "CFLAGS=-g -O2"
"CXXFLAGS=-g -O2"       "CFLAGS_FOR_BUILD="     "CFLAGS_FOR_TARGET=-g
-O2"      "INSTALL=/bin/sh /usr/local/src/gcc-dev/gcc/install-sh -c"
"INSTALL_DATA=/bin/sh /usr/local/src/gcc-dev/gcc/install-sh -c -m 644"
"INSTALL_PROGRAM=/bin/sh /usr/local/src/gcc-dev/gcc/install-sh -c "
"INSTALL_SCRIPT=/bin/sh /usr/local/src/gcc-dev/gcc/install-sh -c"
"LDFLAGS="      "LIBCFLAGS=-g -O2"      "LIBCFLAGS_FOR_TARGET=-g -O2"
"MAKE=make"     "MAKEINFO=makeinfo   "  "PICFLAG=" "PICFLAG_FOR_TARGET="
"SHELL=/bin/sh"         "EXPECT=expect"         "RUNTEST=runtest"
"RUNTESTFLAGS="         "exec_prefix=/usr/local"
"infodir=/usr/local/info"       "libdir=/usr/local/lib"
"prefix=/usr/local"
"tooldir=/usr/local/i686-pc-cygwin"     "AR=ar"         "AS=as"
"CC=/usr/local/src/gcc-dev/objdir/gcc/xgcc
-B/usr/local/src/gcc-dev/objdir/gcc/ -B/usr/local/i686-pc-cygwin/bin/
-B/usr/local/i686-pc-cygwin/lib/ -isystem
/usr/local/i686-pc-cygwin/include"
"CXX=/usr/local/src/gcc-dev/objdir/gcc/g++
-B/usr/local/src/gcc-dev/objdir/gcc/ -nostdinc++ -nostdinc++
-I/usr/local/src/gcc-dev/objdir/
i686-pc-cygwin/libstdc++-v3/include/i686-pc-cygwin
-I/usr/local/src/gcc-dev/objdir/i686-pc-cygwin/libstdc++-v3/include
-I/usr/local/src/gcc-dev/gcc/libstdc++-v3/libsupc++
-I/usr/local/src/gcc-dev/gcc/libstdc++-v3/libio
-I/usr/local/src/gcc-dev/gcc/libstdc++-v3/include/backward
-I/usr/local/src/gcc-dev/gcc/libstdc++-v3/testsuite
-L/usr/local/src/gcc-dev/objdir/i686-pc-cygwin/libstdc++-v3/src
-L/usr/local/src/gcc-dev/objdir/i686-pc-cygwin/libstdc++-v3/src/.libs
-B/usr/local/i686-pc-cygwin/bin/ -B/usr/local/i686-pc-cygwin/lib/
-isystem /usr/local/i686-pc-cygwin/include"   "LD=ld"
"LIBCFLAGS=-g -O2"      "NM=nm"         "PICFLAG="      "RANLIB=ranlib"
"DESTDIR=" check-TESTS
make[4]: Entering directory
`/usr/local/src/gcc-dev/objdir/i686-pc-cygwin/boehm-gc'
Completed 1 tests
Allocated 648021 collectable objects
Allocated 101 uncollectable objects
Allocated 1250000 atomic objects
Allocated 10880 stubborn objects
Finalized 2206/2206 objects - finalization is probably ok
Total number of bytes allocated is 60657252
Final heap size is 9428992 bytes
Collector appears to work
PASS: gctest
==================
All 1 tests passed
==================
make[4]: Leaving directory
`/usr/local/src/gcc-dev/objdir/i686-pc-cygwin/boehm-gc'



But if I just run the configure script, I get this:

Configuring for a i686-pc-cygwin host.
*** This configuration is not supported in the following subdirectories:
     target-libffi target-boehm-gc target-zlib target-libjava
    (Any other directories should still work fine.)

So, my questions are these; Is boehm-gc supported under cygwin and if
so, why does the configury report not supported for target-boehm-gc?

Cheers,

/ChJ