stdcxx-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Martin Sebor (JIRA)" <j...@apache.org>
Subject [jira] Closed: (STDCXX-123) EDG eccp 3.7] misconfiguration due to ill-formed C++ code in libc_decl.sh
Date Thu, 19 Jan 2006 19:40:43 GMT
     [ http://issues.apache.org/jira/browse/STDCXX-123?page=all ]
     
Martin Sebor closed STDCXX-123:
-------------------------------

    Resolution: Fixed

Fixed by the referenced change.

> EDG eccp 3.7] misconfiguration due to ill-formed C++ code in libc_decl.sh
> -------------------------------------------------------------------------
>
>          Key: STDCXX-123
>          URL: http://issues.apache.org/jira/browse/STDCXX-123
>      Project: STDCXX
>         Type: Bug
>   Components: Configuration
>     Versions: 4.1.3
>  Environment: EDG eccp 3.7
>     Reporter: Martin Sebor
>     Assignee: Martin Sebor
>     Priority: Critical
>      Fix For: 4.1.4

>
> EDG eccp 3.7 (released in January '06) started to issue a new error (see below). The
error is causing all config tests for the presence of libc function declarations in libc headers
to fail.
> eccp -c -DCHECK_DECL -A -x --template_directory=/build/sebor/eccp-3.7-15s/lib -g  --display_error_number
--remarks --diag_suppress 193,236,340,401,261,479,487,678,679,815                  -DHDRNAME=<math.h>
-DFUNNAME=acos                  -DFUN=acos(0.0) -DTAKE_ADDR=0 /tmp/libc_decl_tmpsrc-27371.cpp
-o /tmp/acos-27371.o  && eccp /tmp/libc_decl_tmpsrc-27371.cpp --template_directory=/build/sebor/eccp-3.7-15s/lib
 /usr/lib/libpthread.so  -lm
> "/tmp/libc_decl_tmpsrc-27371.cpp", line 13: error #961-D: use of a type with
>           no linkage to declare a variable with linkage
>   } funptri;
>     ^
> 1 error detected in the compilation of "/tmp/libc_decl_tmpsrc-27371.cpp".
> Note that gcc detects the same violation but only issues a warning:
> non-local variable '<anonymous union> u' uses anonymous type

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


Mime
View raw message