From mboxrd@z Thu Jan 1 00:00:00 1970 From: John Paul Adrian Glaubitz Subject: Re: strip is running out of memory on m68k (Haskell) Date: Wed, 1 Aug 2018 10:37:58 +0200 Message-ID: <01f02625-3fef-c56f-357a-3e78ba4a4543@physik.fu-berlin.de> References: <26510258-0207-9e43-0815-f6a56b8f38c3@physik.fu-berlin.de> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <26510258-0207-9e43-0815-f6a56b8f38c3@physik.fu-berlin.de> Content-Language: en-US Resent-Message-ID: List-URL: List-Post: List-Help: List-Subscribe: List-Unsubscribe: List-Archive: https://lists.debian.org/msgid-search/01f02625-3fef-c56f-357a-3e78ba4a4543@physik.fu-berlin.de To: Debian m68k Cc: Linux/m68k List-Id: linux-m68k@vger.kernel.org On 07/31/2018 02:42 PM, John Paul Adrian Glaubitz wrote: > Since I don't think that we have any actual memory limitations on qemu-user (as > compared to qemu-system), this issue might be a result of strip having a hardwired > maximum buffer size for stripping binaries. > > Does anyone know more? If yes, could we patch strip to allow larger binaries? Ok, this seems to be a regression. Packages built with binutils_2.31.1-1 don't show the problem while those built with 2.31.1-2 do: With binutils_2.31.1-1: > https://buildd.debian.org/status/fetch.php?pkg=wireshark&arch=m68k&ver=2.6.2-1&stamp=1532706397&raw=0 With binutils_2.31.1-2: > https://buildd.debian.org/status/fetch.php?pkg=wireshark&arch=m68k&ver=2.6.2-2&stamp=1533058050&raw=0 Will write a bug report upstream once I can confirm this. Adrian