public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "joseph at codesourcery dot com" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sources.redhat.com Subject: [Bug build/14724] glibc build error getconf Date: Mon, 15 Oct 2012 14:34:00 -0000 [thread overview] Message-ID: <bug-14724-131-IjbiqcIXdg@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-14724-131@http.sourceware.org/bugzilla/> http://sourceware.org/bugzilla/show_bug.cgi?id=14724 --- Comment #1 from joseph at codesourcery dot com <joseph at codesourcery dot com> 2012-10-15 14:34:17 UTC --- On Mon, 15 Oct 2012, xsmyqf at qq dot com wrote: > This occured when I was doing someting in the LFS 7.2,chapter 5,Glibc-2.16.0. > when I was doing "make",all is ok.but when I doing "make install",this > occured: Try "make check" before installing; testsuite failures may be easier to debug than getconf crashing on installation. (But in any case you'll need to debug the failures since you have access to the system on which they occur.) > # ../glibc-2.16.0/configure --prefix=/root/lfs/gcc --disable-profile > --enable-add-ons=nptl,../glibc-libidn-2.10.1 --enable-kernel=2.6.25 Do not mix pieces of different glibc versions (the ../glibc-libidn-2.10.1 here); that's never going to do anything sensible. Just --enable-add-ons with no argument; libidn is part of the main release tarball and has been for years. > --with-headers=/root/lfs/gcc/include libc_cv_forced_unwind=yes > libc_cv_ctors_header=yes libc_cv_c_cleanup=yes Do not include any libc_cv_* settings. They should not be needed for 2.16 even for bootstrap builds. -- Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
next prev parent reply other threads:[~2012-10-15 14:34 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-10-15 5:52 [Bug build/14724] New: " xsmyqf at qq dot com 2012-10-15 5:53 ` [Bug build/14724] " xsmyqf at qq dot com 2012-10-15 14:34 ` joseph at codesourcery dot com [this message] 2012-11-21 20:13 ` jsm28 at gcc dot gnu.org 2014-06-13 19:51 ` 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-14724-131-IjbiqcIXdg@http.sourceware.org/bugzilla/ \ --to=sourceware-bugzilla@sourceware.org \ --cc=glibc-bugs@sources.redhat.com \ /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: linkBe 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).