public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "hjl.tools at gmail dot com" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sources.redhat.com Subject: [Bug build/14628] New: Inconsistent multi-arch setting Date: Wed, 26 Sep 2012 13:37:00 -0000 [thread overview] Message-ID: <bug-14628-131@http.sourceware.org/bugzilla/> (raw) http://sourceware.org/bugzilla/show_bug.cgi?id=14628 Bug #: 14628 Summary: Inconsistent multi-arch setting Product: glibc Version: unspecified Status: NEW Severity: normal Priority: P2 Component: build AssignedTo: unassigned@sourceware.org ReportedBy: hjl.tools@gmail.com CC: carlos@systemhalted.org Classification: Unclassified When --enable-multi-arch isn't used, we get # grep multi-arch config.make multi-arch = default # grep USE_MULTIARCH config.h #define USE_MULTIARCH 1 due to # If the assembler supports gnu_indirect_function symbol type and the # architecture supports multi-arch, we enable multi-arch by default. case $sysnames_add_ons$sysnames in *"$multi_arch_d"*) ;; *) test x"$multi_arch" = xdefault && multi_arch=no ;; esac if test x"$multi_arch" != xno; then AC_DEFINE(USE_MULTIARCH) fi AC_SUBST(multi_arch) in configure.in. -- 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 reply other threads:[~2012-09-26 13:37 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-09-26 13:37 hjl.tools at gmail dot com [this message] 2012-09-26 14:02 ` [Bug build/14628] " schwab@linux-m68k.org 2012-09-26 14:06 ` hjl.tools at gmail dot com 2012-09-26 14:49 ` schwab@linux-m68k.org 2012-09-26 14:58 ` hjl.tools at gmail dot com 2012-09-26 15:10 ` schwab@linux-m68k.org 2012-09-26 15:29 ` hjl.tools at gmail dot com 2012-09-26 15:42 ` schwab@linux-m68k.org 2012-09-26 17:45 ` hjl.tools at gmail dot com 2014-06-17 4:18 ` 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-14628-131@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).