archive mirror
 help / color / mirror / Atom feed
From: John Paul Adrian Glaubitz <>
To: Debian m68k <>
Cc: Linux/m68k <>
Subject: strip is running out of memory on m68k (Haskell)
Date: Tue, 31 Jul 2018 14:42:23 +0200	[thread overview]
Message-ID: <> (raw)


We have recently made lots of progress fixing bugs on m68k both in various
as well as QEMU. This has lead to the list of successfully built packages
to over 11.500 - Debian/m68k never built so many packages before.

Now, there are a few things that still need to work and one of them is
binutils' strip command which is bailing out for a very low number of
Haskell packages [1]:

debian/hlibrary.setup copy --builddir=dist-ghc --destdir=debian/tmp-inst-ghc
Installing library in debian/tmp-inst-ghc/usr/lib/haskell-packages/ghc/lib/m68k-linux-ghc-8.2.2/criterion-
Installing executable criterion-report in debian/tmp-inst-ghc/usr/bin
Warning: The directory debian/tmp-inst-ghc/usr/bin is not in the system search
/usr/bin/strip:debian/tmp-inst-ghc/usr/bin/criterion-report: memory exhausted
make: *** [/usr/share/cdbs/1/class/ debian/tmp-inst-ghc] Error 1
dpkg-buildpackage: error: fakeroot debian/rules binary-arch subprocess returned exit status 2

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?


> [1]

             reply	other threads:[~2018-07-31 12:42 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-31 12:42 John Paul Adrian Glaubitz [this message]
2018-08-01  8:37 ` strip is running out of memory on m68k (Haskell) John Paul Adrian Glaubitz
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).