public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: jeroen.dobbelaere@acunia.com
To: gcc-gnats@gcc.gnu.org
Subject: target/6228: [3.1 regression] _GNU_SOURCE not defined for arm-linux target
Date: Mon, 08 Apr 2002 07:06:00 -0000 [thread overview]
Message-ID: <20020408140557.21079.qmail@sources.redhat.com> (raw)
>Number: 6228
>Category: target
>Synopsis: [3.1 regression] _GNU_SOURCE not defined for arm-linux target
>Confidential: no
>Severity: serious
>Priority: medium
>Responsible: unassigned
>State: open
>Class: ice-on-legal-code
>Submitter-Id: net
>Arrival-Date: Mon Apr 08 07:06:00 PDT 2002
>Closed-Date:
>Last-Modified:
>Originator: jeroen.dobbelaere@acunia.com
>Release: 3.1 20020408 (prerelease)
>Organization:
>Environment:
System: Linux xingu-07 2.4.16-rmk1-xng1 #45 Mon Apr 8 11:19:11 CEST 2002 armv5l unknown
Architecture: armv5l
host: armv5l-unknown-linux-gnu
build: armv5l-unknown-linux-gnu
target: armv5l-unknown-linux-gnu
configured with: ../gcc-3.1.0-pre20020408/configure --prefix=/tmp/gcc310pre --with-cpu=xscale --enable-languages=c,c++
>Description:
C++ tests fail on arm because '_GNU_SOURCE' is not defined.
This is a regression with respect to gcc-3.0.4
build compiler for c,c++; execute the build tests.
libstdc++ tests will look like :
Running /usr/src/build/tmp/gcc-3.1.0-pre20020408/libstdc++-v3/testsuite/libstdc++-v3.dg/dg.exp ...
FAIL: 17_intro/header_cstdio.cc (test for excess errors)
WARNING: 17_intro/header_cstdio.cc compilation failed to produce executable
FAIL: 17_intro/header_cstdlib.cc (test for excess errors)
WARNING: 17_intro/header_cstdlib.cc compilation failed to produce executable
FAIL: 17_intro/header_cwchar.cc (test for excess errors)
WARNING: 17_intro/header_cwchar.cc compilation failed to produce executable
FAIL: 17_intro/header_fstream.cc (test for excess errors)
WARNING: 17_intro/header_fstream.cc compilation failed to produce executable
FAIL: 17_intro/header_iomanip.cc (test for excess errors)
WARNING: 17_intro/header_iomanip.cc compilation failed to produce executable
FAIL: 17_intro/header_ios.cc (test for excess errors)
WARNING: 17_intro/header_ios.cc compilation failed to produce executable
FAIL: 17_intro/header_iosfwd.cc (test for excess errors)
WARNING: 17_intro/header_iosfwd.cc compilation failed to produce executable
FAIL: 17_intro/header_iostream.cc (test for excess errors)
WARNING: 17_intro/header_iostream.cc compilation failed to produce executable
FAIL: 17_intro/header_istream.cc (test for excess errors)
WARNING: 17_intro/header_istream.cc compilation failed to produce executable
>How-To-Repeat:
Get an arm system, build your compiler for c,c++.
make the test suite.
>Fix:
Add
/* The GNU C++ standard library requires that these macros be defined. */
#undef CPLUSPLUS_CPP_SPEC
#define CPLUSPLUS_CPP_SPEC "-D_GNU_SOURCE %(cpp)"
to 'gcc/arm/linux-elf.h'
(see <http://gcc.gnu.org/ml/gcc-patches/2002-03/msg00575.html>)
>Release-Note:
>Audit-Trail:
>Unformatted:
next reply other threads:[~2002-04-08 14:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-08 7:06 jeroen.dobbelaere [this message]
2002-04-18 13:42 rth
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20020408140557.21079.qmail@sources.redhat.com \
--to=jeroen.dobbelaere@acunia.com \
--cc=gcc-gnats@gcc.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).