public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "bruce.dubbs at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sources.redhat.com
Subject: [Bug build/14476] New: test-installation.pl fails on x86_64
Date: Thu, 16 Aug 2012 05:03:00 -0000	[thread overview]
Message-ID: <bug-14476-131@http.sourceware.org/bugzilla/> (raw)

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

             Bug #: 14476
           Summary: test-installation.pl fails on x86_64
           Product: glibc
           Version: 2.16
            Status: NEW
          Severity: normal
          Priority: P2
         Component: build
        AssignedTo: unassigned@sourceware.org
        ReportedBy: bruce.dubbs@gmail.com
                CC: carlos@systemhalted.org
    Classification: Unclassified


When building glibc-2.16, 'make install' runs test-installation.pl.  This
fails.

I traced it down to an error in soversions.mk.  A literal extract:

...
ld.so-version=$(if $(abi-64-ld-soname),$(abi-64-ld-soname),ld.so.1)
all-sonames+=ld=$(ld.so-version)
...

The value for ld.so-version crashes test-installation.pl.  It should be
ld-linux-x86-64.so.2.  abi-64-ld-soname is defined correctly in
sysdeps/unix/sysv/linux/x86/Makefile, but it is not getting into soversions.mk.

This problem seems to have been introduced into Makeconfig on 26 May 2012 in
commit 0ab0291b84b45f2389a019af2c88bf5169d14f64

@@ -816,24 +834,17 @@ $(common-objpfx)soversions.i: $(..)scripts/soversions.awk
\
               -f $^ > $@T
        mv -f $@T $@
 $(common-objpfx)soversions.mk: $(common-objpfx)soversions.i $(..)Makeconfig
-       (seen_DEFAULT=0; seen_WORDSIZE32=0; seen_WORDSIZE64=0; \
-        while read which lib number setname; do \
+       (while read which lib number setname; do \
           eval seen_$$which=1; \
           test x"$$which" != xABI || echo abi-name = "$$lib"; \
           test x"$$which" = xDEFAULT || continue; \
           case $$number in \
             [0-9]*) echo "$$lib.so-version=.$$number"; \
                     echo "all-sonames+=$$lib=$$lib.so\$$($$lib.so-version)";;\
-            *)      echo "$$lib.so-version=$$number"; \
+            *)      echo "$$lib.so-version=\$$(if
\$$(abi-$(default-abi)-$$lib-soname),\$$(abi-$(default-abi)-$$lib-soname),$$number)";
\
                     echo "all-sonames+=$$lib=\$$($$lib.so-version)";;\
           esac; \
         done; \

We can work around this by simply deleting the test-installation.pl line from
the Makefile, but that doesn't seem to be a real fix.

  -- Bruce Dubbs
     linuxfromscratch.org

-- 
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.


             reply	other threads:[~2012-08-16  5:03 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-16  5:03 bruce.dubbs at gmail dot com [this message]
2012-08-28 12:53 ` [Bug build/14476] " aj at suse dot de
2012-08-28 16:23 ` hjl.tools at gmail dot com
2012-08-28 17:05 ` bruce.dubbs at gmail dot com
2012-08-28 17:59 ` hjl.tools at gmail dot com
2012-08-28 19:25 ` bruce.dubbs at gmail dot com
2012-08-30 13:48 ` hjl.tools at gmail dot com
2014-06-17 18:37 ` 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-14476-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: 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).