public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "2947868523 at qq dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug build/16989] New: check_fds.c:85:1: internal compiler error: Segmentation fault
Date: Tue, 27 May 2014 03:02:00 -0000	[thread overview]
Message-ID: <bug-16989-131@http.sourceware.org/bugzilla/> (raw)

https://sourceware.org/bugzilla/show_bug.cgi?id=16989

            Bug ID: 16989
           Summary: check_fds.c:85:1: internal compiler error:
                    Segmentation fault
           Product: glibc
           Version: 2.13
            Status: NEW
          Severity: critical
          Priority: P2
         Component: build
          Assignee: unassigned at sourceware dot org
          Reporter: 2947868523 at qq dot com
                CC: carlos at redhat dot com
              Host: i686-pc-linux
            Target: arm-linux

centos 6.0
glibc-2.13 + glibc-ports-2.13

//make error
check_fds.c: In function ‘check_one_fd’:
check_fds.c:85:1: internal compiler error: Segmentation fault
Please submit a full bug report,
with preprocessed source if appropriate.
See <http://gcc.gnu.org/bugs.html> for instructions.
make[2]: *** [/home/lianhua/arm-linux/4.6.0/build/glibc2/csu/check_fds.o] Error
1

//host gcc version
gcc -v
Using built-in specs.
Target: i686-redhat-linux
Configured with: ../configure --prefix=/usr --mandir=/usr/share/man
--infodir=/usr/share/info --with-bugurl=http://bugzilla.redhat.com/bugzilla
--enable-bootstrap --enable-shared --enable-threads=posix
--enable-checking=release --with-system-zlib --enable-__cxa_atexit
--disable-libunwind-exceptions --enable-gnu-unique-object
--enable-languages=c,c++,objc,obj-c++,java,fortran,ada --enable-java-awt=gtk
--disable-dssi --with-java-home=/usr/lib/jvm/java-1.5.0-gcj-1.5.0.0/jre
--enable-libgcj-multifile --enable-java-maintainer-mode
--with-ecj-jar=/usr/share/java/eclipse-ecj.jar --disable-libjava-multilib
--with-ppl --with-cloog --with-tune=generic --with-arch=i686
--build=i686-redhat-linux
Thread model: posix
gcc version 4.4.7 20120313 (Red Hat 4.4.7-4) (GCC) 

//configure command
CC=${TARGET}-gcc LD=${TARGET}-ld AR=${TARGET}-ar RANLIB=${TARGET}-ranlib
CFLAGS="-g -O2 -march=armv4t" ../../src/glibc-2.13/configure
--build=$(../glibc-2.13/scripts/config.guess) --host=arm-linux --target=$TARGET
--prefix=$TARGET_PREFIX  --disable-profile --enable-add-ons
--with-headers=$TARGET_PREFIX/include libc_cv_forced_unwind=yes 
libc_cv_c_cleanup=yes --enable-kernel=2.6.38 --with-binutils=$PREFIX/bin
--enable-languages=c

-- 
You are receiving this mail because:
You are on the CC list for the bug.
>From glibc-bugs-return-22418-listarch-glibc-bugs=sources.redhat.com@sourceware.org Tue May 27 03:21:15 2014
Return-Path: <glibc-bugs-return-22418-listarch-glibc-bugs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-glibc-bugs@sources.redhat.com
Received: (qmail 1029 invoked by alias); 27 May 2014 03:21:14 -0000
Mailing-List: contact glibc-bugs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <glibc-bugs.sourceware.org>
List-Subscribe: <mailto:glibc-bugs-subscribe@sourceware.org>
List-Post: <mailto:glibc-bugs@sourceware.org>
List-Help: <mailto:glibc-bugs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: glibc-bugs-owner@sourceware.org
Delivered-To: mailing list glibc-bugs@sourceware.org
Received: (qmail 958 invoked by uid 48); 27 May 2014 03:21:08 -0000
From: "2947868523 at qq dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug build/16982] configure: error: linker with -z relro support required
Date: Tue, 27 May 2014 03:21:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: glibc
X-Bugzilla-Component: build
X-Bugzilla-Version: 2.19
X-Bugzilla-Keywords: glibc_2.19
X-Bugzilla-Severity: critical
X-Bugzilla-Who: 2947868523 at qq dot com
X-Bugzilla-Status: NEW
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: unassigned at sourceware dot org
X-Bugzilla-Target-Milestone: 2.19
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: assigned_to
Message-ID: <bug-16982-131-wsQ4QTL3VW@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-16982-131@http.sourceware.org/bugzilla/>
References: <bug-16982-131@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2014-05/txt/msg00201.txt.bz2
Content-length: 405

https://sourceware.org/bugzilla/show_bug.cgi?id\x16982

Chenyuan.Liu <2947868523 at qq dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Assignee|2947868523 at qq dot com           |unassigned at sourceware dot org

--
You are receiving this mail because:
You are on the CC list for the bug.


             reply	other threads:[~2014-05-27  3:02 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-27  3:02 2947868523 at qq dot com [this message]
2014-05-27  4:32 ` [Bug build/16989] " 2947868523 at qq dot com
2014-05-27  4:36 ` 2947868523 at qq dot com
2014-05-27  7:42 ` schwab@linux-m68k.org
2014-06-12 19:10 ` fweimer at redhat dot com

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=bug-16989-131@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=glibc-bugs@sourceware.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).