[ANNOUNCEMENT] Updated: stable compiler package gcc4-4.5.3-2

[ANNOUNCEMENT] Updated: stable compiler package gcc4-4.5.3-2

[Dave Korn]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1


  I have just uploaded an updated GCC-4 package to cygwin.com.  It will be
arriving at your favourite mirror next time it synchronizes itself with the
official Cygwin repository.

  This is a stable release of GCC 4.5.3 which replaces the earlier experimental
release of GCC 4.5.0.


    ------------------------------ooOOOoo------------------------------
    PLEASE SEND BUG REPORTS, PROBLEMS, ETC. TO THE CYGWIN MAILING LIST.
    ------------------------------ooOOOoo------------------------------


OBTAINING THE RELEASE
=====================

To update your installation, click on the "Install Cygwin now" link on the
http://cygwin.com/ web page. This downloads setup.exe to your system. Then,
run setup.exe, fill in all of the options, and make appropriate choices on the
"Select Packages" screen. Because this is a full "current" version release,
any gcc packages you currently have installed will be automatically selected
to update, but you'll need to select the Devel category to see gcc and friends
if you don't have them already installed.

NEWS
====

> > From the README:

gcc4-4.5.3-2
- ------------------------------------------

This is the first full stable production release from the GCC 4.5 compiler
series for Cygwin, which replaces the experimental 4.5.0-1 release.  All
the major runtime libraries are implemented as DLLs as well as static
archives.  It can fully co-exist side-by-side with the older Cygwin gcc-3.4.4
series compiler.  All languages are supported, although Ada and Java remain
works-in-progress.


What happened to gcc4-4.5.3-1?
==============================

This release number was used for the initial cygwinports version of the
gcc4-4.5.3 packages.  Skipping it in the main release series avoids any
problems for cygwinports users.

Known issues in Ada and Java.
=============================

The Ada compiler is currently implemented as a Frankenstein-like hybrid of
Cygwin/POSIX and MinGw/w32api code.  This just barely hangs together, but
does not play nicely with Cygwin's pthread library functions; the outcome
is problems in the tasking implementation, including race conditions that
may lead to failure in early startup or termination.

There are problems with the Java compiler that are less well understood,
but also manifest themselves as testsuite failures in the thread- and
process-related tests.

These issues will be addressed in a future release of the compiler; for
now, Java and Ada cannot be considered first-class languages, but remain
somewhat experimental.  It is likely however that both perform better than
the old 3.4 series compilers.


Cygwin port maintained by: Dave Korn
<dave.korn.cygwin AT mail.com.use.the.list.please>
Please address all questions to the Cygwin mailing list at <cygwin AT cygwin.com>

This is the key used for signing Cygwin GCC releases:

pub   1024D/6A388C3E 2008-05-31
uid                  Dave Korn (release signing key)
                             <dave.korn.cygwin AT gmail.com>
sub   4096g/D4E41590 2008-05-31

Also available at a key-server near you!

- -----BEGIN PGP PUBLIC KEY BLOCK-----
Version: GnuPG v1.4.9 (Cygwin)

mQGiBEhBdVwRBADGS7UWOR8lvHOcOs161cRjTw1Yp3Qj4Xy5JbaSQFZ6m+DTM7GD
y4tPrM1jr6uYGzikdNzYL6tWKUDvVYjs7bwYJXBQ7ryeLJ4LXs+8cmIFIl4uMc8P
BEpT67gs1+MchBemr1B/s4V8s9laX81mMYd73qqefuCnbUU8+iBKBzfDhwCg6xQU
yIORoWJz5qIHwO23N2uuuKUD/0AsLJOMV1Ig/NVK8ZMss4ozIsgOiBBJ7ZQ9bzzR
8D5EhahVTwPJ7dMXGKWfb21gJHtYjOtwDYJyc5HdIHBPWylI0u6vkiIDD4TZjSDA
fIMBgTKp9SjKBtr4ZJzYZUguTFGJFBDLyieyUDWTXBVQSaDASzEjwwdbbKo5/wzY
GzvYA/458txhAz1GoB3hnaEJgIK0HaOVjetvZif9QQ1L0x10EIjdwgxN8pMR3Gv8
d+pALJpivIe5eMrU2QLpSbiK5QRkndJBYdiEobLCY3Ca6elRB8/ioKUyOzngtAe9
ny0dUNEWDxwtk2yJSxMrcfRjSJMs+4efCqXrRIkfXr1ibE1JybQ8RGF2ZSBLb3Ju
IChyZWxlYXNlIHNpZ25pbmcga2V5KSA8ZGF2ZS5rb3JuLmN5Z3dpbkBnbWFpbC5j
b20+iGMEExECACMCGwMGCwkIBwMCBBUCCAMEFgIDAQIeAQIXgAUCSMUtrgIZAQAK
CRBN0oLlajiMPrQTAKCJhzyfI8MKSJjYNTXYCo/GITfvTQCgp2Jw70u5NQojF09f
uPhfnX+xed+IYwQTEQIAIwIbAwYLCQgHAwIEFQIIAwQWAgMBAh4BAheABQJIVRdm
AhkBAAoJEE3SguVqOIw+l4QAoJSM49UfFNHx3jSTV3+o+TQF9Uo/AKDa5iFeDTuO
10t5Rpng0OWJPTR7N7kEDQRIQXVcEBAAnOffXRQSAPcJKW9z8OXwd0UmNFGZbjb5
CW53i2HYmqiYfMLL6XHyyB2o0e0jZuao/+PgxnoVaqpPh7DXYfjup/u5ll2kAK2I
VImGIFYifRLQAWCivQa4LXWR2EvIi1MURrmEjN+JKStBAySiED21QELetUGNzeYT
rsWBpHmAibcBAbwFPw0mhFPqvApcrpMJhALehCqPEu/rfeUnziqo8pdpeKkL0ENl
GsNONGYhDIjzexclRNFFYwzmK2cS5sxwyH94OxBABfgwxsVYB0+zsdjPk3JybK52
+MIcYQU4NBoCYo184pFJ4QhzKmt/8sAicaxLsU4DHqyy9SwFH1cV1Su5RN3DGG2S
0hFImqyTeCiSW2FDSgOtAF0ImEY3HNkfLgych5nFKRj0itPdFG/t6qCJKLf8JsZP
2QDaLQO+42jwn6Y47PaBEMJGttPaY6guATJqVefqayKI4j22w2le4PLxYJ3fIlqi
5rS5m6mJV2ZFRuqSgmGPDgb8+vnvTG/PCTCcK3j4jzUvJ3bX9FtyV9cFnlF+CfQc
ZMdx4qHrhKgoiqJt19Mk8rb19L6KqyLNgJyqvwOcsX8P2yM8t/FAuUeg1EgnYbMz
RywEHEa2+rj2R1FPJGtJdOQLgrPgd4m9t5Eq7zFPuJgKNlWHf1Y0M82A37iYnWna
DyqON5+pPQ8ABAsP/jOOvQjU79Pd8ph7c2LK+UUjGPQVYO5bwUOCDs9ctSIbQgPh
R4l4Ae3Lpgduv7V4ssz15qOGPAe++FmbutyYjF2mxwvwX86coWnkarkhuTrwoB29
Mb9IAqqpWcLqdSzUof5XSm4hesB8PASC5hCJ3D6ztMTX3OOEywSt8LJlOvgaM/YZ
fSit+5xVfGG9AXZya+jKjJnJBCyiqdWZslfRLaSHDF4M4roDk2cl8SxVJTMiBl5g
s84LLnJTIrm8HQ6oeSVrjyt8nGOCoqreOqUH6auWIEzXbjyVmeppwCfdYbG9P+Pn
iwB0GLtofUGrk7WjkThzR1Pi3wIvtYBfIZ2xqFkVM0r3tL3AuzBo6X0N9mcpTom8
PY/i2qxa4SKVrskNWkpEemY0Jt26bRhCA6amfureR9xmpOKTLyvXxiZL73vK0d4r
N1+j4lFgE6nMnAW0Q5DK8Vpa+4cC0pvQI9d0a9dWXA0KkvQCA7wpT8FvQKYYLtyj
K5Gv1wMiG5uuUVMpXk7nl12cYoMVJl2b4yOp1XhoksGArg7OptH3XZj3UahZh302
jalzqijIXaOSf/V9b+LuuhLMTLi4XD7+pmyd5cIf577Kj2UgLYbAnTqx3GNFBYYQ
TtRbSNgS7zSAs+CQGp4Kv2eQRKHTm4oPtKwoKYs1S2o8WZNr3RuNjKYTjRyMiEkE
GBECAAkFAkhBdVwCGwwACgkQTdKC5Wo4jD4O3wCgpS9eVpxbYfMB/xVo1zQDSVQC
mNkAoLd0hCE1VdOP7GK49mYaq8nFRuex
=CI19
- -----END PGP PUBLIC KEY BLOCK-----

 If you have questions or comments, please send them to the cygwin mailing
list at: cygwin AT cygwin.com .

              *** CYGWIN-ANNOUNCE UNSUBSCRIBE INFO ***

If you want to unsubscribe from the cygwin-announce mailing list, look at the
"List-Unsubscribe: " tag in the email header of this message. Send email to
the address specified there. It will be in the format:

cygwin-announce-unsubscribe-you=yourdomain.com AT cygwin.com

If you need more information on unsubscribing, start reading here:

http://sourceware.org/lists.html#unsubscribe-simple

Please read *all* of the information on unsubscribing that is available
starting at this URL.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (Cygwin)

iEYEARECAAYFAk5gUeIACgkQTdKC5Wo4jD4AygCgpTVxv1+Wj9fpGiFiBHVPvCv3
RSUAnA2/YRnjCAB+tzdC7GJuqnvLMd4p
=+msg
-----END PGP SIGNATURE-----

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

Re: [ANNOUNCEMENT] Updated: stable compiler package gcc4-4.5.3-2

[Bernd Prager]

I recompiled the recent boost libraries with the new gcc-4 package.

The thread example fails with:

$ g++ thread.cpp -L /usr/local/lib -lboost_thread
/tmp/cccfCagO.o:thread.cpp:(.text+0xa4): undefined reference to
`__Unwind_Resume'


Cheers,
-- Bernd

On 9/1/2011 11:49 PM, Dave Korn wrote:
>  
>   I have just uploaded an updated GCC-4 package to cygwin.com.  It
> will be
> arriving at your favourite mirror next time it synchronizes itself
> with the
> official Cygwin repository.
>  
>   This is a stable release of GCC 4.5.3 which replaces the earlier
> experimental
> release of GCC 4.5.0.
>  
>  
>     ------------------------------ooOOOoo------------------------------
>     PLEASE SEND BUG REPORTS, PROBLEMS, ETC. TO THE CYGWIN MAILING LIST.
>     ------------------------------ooOOOoo------------------------------
>  
>  ...>



--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

Re: [ANNOUNCEMENT] Updated: stable compiler package gcc4-4.5.3-2

[Yaakov (Cygwin/X)]

On Tue, 2011-09-06 at 15:44 -0400, Bernd Prager wrote:
> I recompiled the recent boost libraries with the new gcc-4 package.
> 
> The thread example fails with:
> 
> $ g++ thread.cpp -L /usr/local/lib -lboost_thread
> /tmp/cccfCagO.o:thread.cpp:(.text+0xa4): undefined reference to
> `__Unwind_Resume'

There will be new boost packages soon built for gcc-4.5.


Yaakov



--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

Re: [ANNOUNCEMENT] Updated: stable compiler package gcc4-4.5.3-2

[Frédéric Bron]

I have recompiled the code I am working on with i686-pc-cygwin-g++ 4.5.3.

I get many of the following messages from the linker:
/usr/lib/gcc/i686-pc-cygwin/4.5.3/../../../../i686-pc-cygwin/bin/ld:
gcc-release/obj/BTest/Test.o: warning: duplicate section
`.rdata$_ZTISs[typeinfo for std::basic_string<char,
std::char_traits<char>, std::allocator<char> >]' has different size

I do not get this error cross-compiling the same code with
i686-pc-mingw32-g++ 4.5.2.

Any chance that this comes from the new version?

Frédéric

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

Re: [ANNOUNCEMENT] Updated: stable compiler package gcc4-4.5.3-2

[Ryan Johnson]

On 08/09/2011 1:32 AM, Frédéric Bron wrote:
> I have recompiled the code I am working on with i686-pc-cygwin-g++ 4.5.3.
>
> I get many of the following messages from the linker:
> /usr/lib/gcc/i686-pc-cygwin/4.5.3/../../../../i686-pc-cygwin/bin/ld:
> gcc-release/obj/BTest/Test.o: warning: duplicate section
> `.rdata$_ZTISs[typeinfo for std::basic_string<char,
> std::char_traits<char>, std::allocator<char>  >]' has different size
>
> I do not get this error cross-compiling the same code with
> i686-pc-mingw32-g++ 4.5.2.
>
> Any chance that this comes from the new version?
In my experience, these sorts of errors arise when there really is 
something wrong with the code, usually involving sizes of integers (e.g. 
'long' in struct's definition and 'int' in another, on a 64-bit 
machine). However, the linker is poorly-equipped to detect such errors 
unless the resulting objects have different sizes.

So, while I wouldn't rule out miscompilation, I would first check for 
silently conflicting definitions in different compilation units.

At least one list discussion for another project reported a similar 
gcc-whines-mingw-silent issue, and the resulting mingw binary didn't run 
properly (which supports the silent conflict hypothesis).

BTW, a STC would have been extremely helpful here -- all we can do is 
speculate without it

Ryan


--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

Re: [ANNOUNCEMENT] Updated: stable compiler package gcc4-4.5.3-2

[Bernd Prager]

On 9/6/2011 5:27 PM, Yaakov (Cygwin/X) wrote:
> On Tue, 2011-09-06 at 15:44 -0400, Bernd Prager wrote:
>> I recompiled the recent boost libraries with the new gcc-4 package.
>>
>> The thread example fails with:
>>
>> $ g++ thread.cpp -L /usr/local/lib -lboost_thread
>> /tmp/cccfCagO.o:thread.cpp:(.text+0xa4): undefined reference to
>> `__Unwind_Resume'
> There will be new boost packages soon built for gcc-4.5.
>
>
> Yaakov
>
>
>
> --
> Problem reports:       http://cygwin.com/problems.html
> FAQ:                   http://cygwin.com/faq/
> Documentation:         http://cygwin.com/docs.html
> Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
>
Yaakov,

Are you certain this is a boost issue?

_Unwind_Resume resumes propagation of an existing exception object and I
think should be a part of the c++ standard library.

-- Bernd

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

Re: [ANNOUNCEMENT] Updated: stable compiler package gcc4-4.5.3-2

[Frédéric Bron]

> In my experience, these sorts of errors arise when there really is something
> wrong with the code, usually involving sizes of integers (e.g. 'long' in
> struct's definition and 'int' in another, on a 64-bit machine). However, the
> linker is poorly-equipped to detect such errors unless the resulting objects
> have different sizes.
>
> So, while I wouldn't rule out miscompilation, I would first check for
> silently conflicting definitions in different compilation units.

Does the linker message gives any hint on where to look?

> BTW, a STC would have been extremely helpful here -- all we can do is
> speculate without it

Could you give more details. I cannot find on the net what you mean by "a STC".

Thanks,

Frédéric

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

Re: [ANNOUNCEMENT] Updated: stable compiler package gcc4-4.5.3-2

[Christopher Faylor]

On Thu, Sep 08, 2011 at 10:17:57PM +0200, Fr?d?ric Bron wrote:
>> In my experience, these sorts of errors arise when there really is something
>> wrong with the code, usually involving sizes of integers (e.g. 'long' in
>> struct's definition and 'int' in another, on a 64-bit machine). However, the
>> linker is poorly-equipped to detect such errors unless the resulting objects
>> have different sizes.
>>
>> So, while I wouldn't rule out miscompilation, I would first check for
>> silently conflicting definitions in different compilation units.
>
>Does the linker message gives any hint on where to look?
>
>> BTW, a STC would have been extremely helpful here -- all we can do is
>> speculate without it
>
>Could you give more details. I cannot find on the net what you mean by "a STC".

http://cygwin.com/acronyms/#STC

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

Re: [ANNOUNCEMENT] Updated: stable compiler package gcc4-4.5.3-2

[Frédéric Bron]

> http://cygwin.com/acronyms/#STC

Thank you. I will try to do that.

Frédéric

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

Re: [ANNOUNCEMENT] Updated: stable compiler package gcc4-4.5.3-2

[Ryan Johnson]

On 08/09/2011 4:17 PM, Frédéric Bron wrote:
>> In my experience, these sorts of errors arise when there really is something
>> wrong with the code, usually involving sizes of integers (e.g. 'long' in
>> struct's definition and 'int' in another, on a 64-bit machine). However, the
>> linker is poorly-equipped to detect such errors unless the resulting objects
>> have different sizes.
>>
>> So, while I wouldn't rule out miscompilation, I would first check for
>> silently conflicting definitions in different compilation units.
> Does the linker message gives any hint on where to look?
Sort of... the error message mentions Test.o and the section 
`.rdata$_ZTISs'

You also presumably have the linker command line, which should tell you 
what other .o and .a are involved. Invoke `objdump -h' and pass as args 
all those .o/.a and examine the output. Most likely you'll see several 
files containing the offending section, and among those there are 
probably two distinct sizes reported. From there you have to work 
backwards to figure out what was different about #defines and #includes 
in the two source files that might have caused the discrepancy.

Top suspects: custom typedefs or #defines which confuse system headers, 
or including Windows headers which make superficially equivalent 
declarations (but which have completely different and incompatible 
implementations). Given that mingw doesn't complain my money's on the 
latter.

Ryan

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

Re: [ANNOUNCEMENT] Updated: stable compiler package gcc4-4.5.3-2

[Dave Korn]

On 08/09/2011 17:33, Bernd Prager wrote:
> On 9/6/2011 5:27 PM, Yaakov (Cygwin/X) wrote:
>> On Tue, 2011-09-06 at 15:44 -0400, Bernd Prager wrote:
>>> I recompiled the recent boost libraries with the new gcc-4 package.
>>>
>>> The thread example fails with:
>>>
>>> $ g++ thread.cpp -L /usr/local/lib -lboost_thread
>>> /tmp/cccfCagO.o:thread.cpp:(.text+0xa4): undefined reference to
>>> `__Unwind_Resume'
>> There will be new boost packages soon built for gcc-4.5.

> Yaakov,
> 
> Are you certain this is a boost issue?
> 
> _Unwind_Resume resumes propagation of an existing exception object and I
> think should be a part of the c++ standard library.

  It is part of libgcc:

> $ nm /usr/lib/gcc/i686-pc-cygwin/4.5.3/libgcc_s.dll.a | grep __Unwind_Resume
> 00000000 T __Unwind_Resume_or_Rethrow
> 00000000 I __imp___Unwind_Resume_or_Rethrow
> 00000000 T __Unwind_Resume
> 00000000 I __imp___Unwind_Resume
> 
> $ nm /usr/lib/gcc/i686-pc-cygwin/4.5.3/libgcc_eh.a | grep __Unwind_Resume
> 00001f10 T __Unwind_Resume
> 00001fd0 T __Unwind_Resume_or_Rethrow
> 
> $

  Adding "-v -Wl,--verbose" to the command line should give us an idea why the
link is failing for you.  I'm also leaving a build of boost running overnight
to see if I can reproduce the problem.

    cheers,
      DaveK


--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

Re: [ANNOUNCEMENT] Updated: stable compiler package gcc4-4.5.3-2

[Dave Korn]

On 09/09/2011 05:23, Dave Korn wrote:
> On 08/09/2011 17:33, Bernd Prager wrote:

>>> On Tue, 2011-09-06 at 15:44 -0400, Bernd Prager wrote:

>>>> $ g++ thread.cpp -L /usr/local/lib -lboost_thread
>>>> /tmp/cccfCagO.o:thread.cpp:(.text+0xa4): undefined reference to
>>>> `__Unwind_Resume'

>> _Unwind_Resume resumes propagation of an existing exception object and I
>> think should be a part of the c++ standard library.
> 
>   It is part of libgcc:

>   Adding "-v -Wl,--verbose" to the command line should give us an idea why the
> link is failing for you.  I'm also leaving a build of boost running overnight
> to see if I can reproduce the problem.

  Couldn't reproduce it, but then I was building the cygwin distro version of
boost rather than the upstream one.  Without further info, I can't offer any
better guess than that maybe something else in your /usr/local prefix is
interfering.

    cheers,
      DaveK


--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

Re: [ANNOUNCEMENT] Updated: stable compiler package gcc4-4.5.3-2

[Bernd Prager]

On 9/9/2011 11:38 AM, Dave Korn wrote:
>>>> $ g++ thread.cpp -L /usr/local/lib -lboost_thread
>>>> /tmp/cccfCagO.o:thread.cpp:(.text+0xa4): undefined reference to
>>>> `__Unwind_Resume'
> Couldn't reproduce it, but then I was building the cygwin distro 
> version of boost rather than the upstream one. Without further info, I 
> can't offer any better guess than that maybe something else in your 
> /usr/local prefix is interfering. cheers, DaveK ...


I tried it on a different computer with a fresh Cygwin install and it 
compiles just fine.
That makes your previous assumption very likely.

Thank you for your effort though.
-- Bernd

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

Re: [ANNOUNCEMENT] Updated: stable compiler package gcc4-4.5.3-2

[Bernd Prager]

On 9/9/2011 11:38 AM, Dave Korn wrote:
>>>> $ g++ thread.cpp -L /usr/local/lib -lboost_thread
>>>> /tmp/cccfCagO.o:thread.cpp:(.text+0xa4): undefined reference to
>>>> `__Unwind_Resume'
> Couldn't reproduce it, but then I was building the cygwin distro 
> version of boost rather than the upstream one. Without further info, I 
> can't offer any better guess than that maybe something else in your 
> /usr/local prefix is interfering. cheers, DaveK ...


I tried it on a different computer with a fresh Cygwin install and it 
compiles just fine.
That makes your previous assumption very likely.

Thank you for your effort though.
-- Bernd

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple