bug-binutils
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Bug ld/20531] New: [Regression/2.27]: Not enough room for program heade


From: glaubitz at physik dot fu-berlin.de
Subject: [Bug ld/20531] New: [Regression/2.27]: Not enough room for program headers, try linking with -N
Date: Mon, 29 Aug 2016 06:06:51 +0000

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

            Bug ID: 20531
           Summary: [Regression/2.27]: Not enough room for program
                    headers, try linking with -N
           Product: binutils
           Version: 2.27
               URL: https://buildd.debian.org/status/fetch.php?pkg=tcpdump
                    &arch=powerpcspe&ver=4.7.4-2&stamp=1472415288
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: ld
          Assignee: unassigned at sourceware dot org
          Reporter: glaubitz at physik dot fu-berlin.de
                CC: jrtc27 at jrtc27 dot com
  Target Milestone: ---
            Target: powerpc-linux-gnuspe

After upgrading binutils to 2.27 on the powerpcspe buildds in Debian, running
the strip command fails with:

(sid2-powerpcspe-sbuild)address@hidden:/build/tcpdump-t4oxHH/tcpdump-4.7.4#
strip --remove-section=.comment --remove-section=.note
debian/tcpdump/usr/sbin/tcpdump
strip: debian/tcpdump/usr/sbin/stMmiNLY: Not enough room for program headers,
try linking with -N
strip:debian/tcpdump/usr/sbin/stMmiNLY[.interp]: Bad value
(sid2-powerpcspe-sbuild)address@hidden:/build/tcpdump-t4oxHH/tcpdump-4.7.4

This problem is immediately resolved by downgrading binutils to 2.26.1 and
rebuilding the package.

The full build root for the test package tcpdump can be found in [1]. The full
build log in [2].

Adrian

> [1] https://people.debian.org/~glaubitz/tcpdump_ppcspe_debug.tgz
> [2] 
> https://buildd.debian.org/status/fetch.php?pkg=tcpdump&arch=powerpcspe&ver=4.7.4-2&stamp=1472415288

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


reply via email to

[Prev in Thread] Current Thread [Next in Thread]