public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "anemet at caviumnetworks dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sources.redhat.com
Subject: [Bug libc/6441] New: Value of slibdir changes after reconfigure for 64-bit targets
Date: Tue, 22 Apr 2008 01:55:00 -0000	[thread overview]
Message-ID: <20080422015444.6441.anemet@caviumnetworks.com> (raw)

After reconfiguring, the value of slibdir changes from ${exec_prefix}/lib32 or
${exec_prefix}/lib64 to ${exec_prefix}/lib.

This is because the code that sets libdir is only executed if libc_cv_slibdir
is unset (this is to provide an override mechanism for subtargets).  If the
value of libc_cv_slibdir is read from the config cache the value of libdir is
never adjusted.  Or:

  $ rm config.cache 
  $ ~/src/glibc/configure --host=mips64-unknown-linux-gnu --build=i686-linux
--prefix=/usr --cache-file=config.cache &>/dev/null
  $ grep libdir config.make 
  libdir = ${exec_prefix}/lib32
  slibdir = /lib32
  $ ~/src/glibc/configure --host=mips64-unknown-linux-gnu --build=i686-linux
--prefix=/usr --cache-file=config.cache &>/dev/null
  $ grep libdir config.make 
  libdir = ${exec_prefix}/lib
  slibdir = /lib32

With the current logic, either both libdir and slibdir should be cached or
neither.

-- 
           Summary: Value of slibdir changes after reconfigure for 64-bit
                    targets
           Product: glibc
           Version: unspecified
            Status: NEW
          Severity: normal
          Priority: P2
         Component: libc
        AssignedTo: drepper at redhat dot com
        ReportedBy: anemet at caviumnetworks dot com
                CC: glibc-bugs at sources dot redhat dot com
 GCC build triplet: i686-linux
  GCC host triplet: mips64-unknown-linux-gnu


http://sourceware.org/bugzilla/show_bug.cgi?id=6441

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.


             reply	other threads:[~2008-04-22  1:55 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-22  1:55 anemet at caviumnetworks dot com [this message]
2008-04-22  1:56 ` [Bug libc/6441] " anemet at caviumnetworks dot com
2008-04-22 22:59 ` [Bug ports/6441] " drepper 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=20080422015444.6441.anemet@caviumnetworks.com \
    --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: 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).