This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug libstdc++/13284] New: 126 g++ failures due to lrand48 not defined
- From: "giovannibajo at libero dot it" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 3 Dec 2003 15:33:54 -0000
- Subject: [Bug libstdc++/13284] New: 126 g++ failures due to lrand48 not defined
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
Hello,
126 out of the 148 failures I see with mainline on cygwin are due to this:
In file included from /home/Administrator/gcc/mainline/out/i686-pc-
cygwin/libstdc++-v3/include/algorithm:69,
from /home/Administrator/gcc/mainline/out/i686-pc-
cygwin/libstdc++-v3/include/string:56,
from /home/Administrator/gcc/mainline/gcc/gcc/testsuite/g++.dg/init/array4.C:8:
/home/Administrator/gcc/mainline/out/i686-pc-cygwin/libstdc++-
v3/include/bits/stl_algo.h: In function `_Distance std::__random_number
(_Distance)':
/home/Administrator/gcc/mainline/out/i686-pc-cygwin/libstdc++-
v3/include/bits/stl_algo.h:1670: error: there are no arguments to `lrand48'
that depend on a templ
ate parameter, so a declaration of `lrand48' must be available
/home/Administrator/gcc/mainline/out/i686-pc-cygwin/libstdc++-
v3/include/bits/stl_algo.h:1670: error: (if you use `-fpermissive', G++ will
accept your code, but allowing the use of an undeclared name is deprecated)
Now, newlib does not define lrand48 if __STRICT_ANSI__, and the testsuite is
run with "-ansi". Danny Smith suggests that cygwin's newlib should always
define those C99 functions in C++ mode.
But I wonder, why _GLIBCXX_HAVE_LRAND48 is defined in the first place?
Shouldn't the configure test for it be run in -ansi mode?
--
Summary: 126 g++ failures due to lrand48 not defined
Product: gcc
Version: 3.4
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: libstdc++
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: giovannibajo at libero dot it
CC: dannysmith at gcc dot gnu dot org,gcc-bugs at gcc dot
gnu dot org
GCC build triplet: i686-pc-cygwin
GCC host triplet: i686-pc-cygwin
GCC target triplet: i686-pc-cygwin
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=13284