archive mirror
 help / color / mirror / Atom feed
From: John Paul Adrian Glaubitz <>
To: Debian m68k <>
Cc: Linux/m68k <>
Subject: Re: strip is running out of memory on m68k (Haskell)
Date: Wed, 1 Aug 2018 10:37:58 +0200	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

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:


With binutils_2.31.1-2:


Will write a bug report upstream once I can confirm this.


  reply	other threads:[~2018-08-01  8:37 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-31 12:42 strip is running out of memory on m68k (Haskell) John Paul Adrian Glaubitz
2018-08-01  8:37 ` John Paul Adrian Glaubitz [this message]
2018-08-01  9:02   ` John Paul Adrian Glaubitz
2018-08-01  9:58     ` John Paul Adrian Glaubitz
2018-08-01 14:40       ` John Paul Adrian Glaubitz
2018-08-02 14:04         ` Wouter Verhelst

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \

* 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 NNTP newsgroup(s).