From: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>
To: Debian m68k <debian-68k@lists.debian.org>
Cc: Linux/m68k <linux-m68k@vger.kernel.org>
Subject: Re: strip is running out of memory on m68k (Haskell)
Date: Wed, 1 Aug 2018 11:02:50 +0200 [thread overview]
Message-ID: <73bbb43e-731b-5c83-f339-4db276df6901@physik.fu-berlin.de> (raw)
In-Reply-To: <01f02625-3fef-c56f-357a-3e78ba4a4543@physik.fu-berlin.de>
On 08/01/2018 10:37 AM, John Paul Adrian Glaubitz wrote:
> 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.
Ok, downgrading to 2.31.1-1 definitely helps:
(sid-m68k-sbuild)root@epyc:/build/haskell-yaml-bukQp5/haskell-yaml-0.8.31.1/debian# strip tmp-inst-ghc/usr/bin/yaml2json
/usr/bin/strip:tmp-inst-ghc/usr/bin/yaml2json: memory exhausted
(sid-m68k-sbuild)root@epyc:/build/haskell-yaml-bukQp5/haskell-yaml-0.8.31.1/debian# strip tmp-inst-ghc/usr/bin/yaml2json
(sid-m68k-sbuild)root@epyc:/build/haskell-yaml-bukQp5/haskell-yaml-0.8.31.1/debian#
Adrian
next prev parent reply other threads:[~2018-08-01 9:02 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
2018-08-01 9:02 ` John Paul Adrian Glaubitz [this message]
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:
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=73bbb43e-731b-5c83-f339-4db276df6901@physik.fu-berlin.de \
--to=glaubitz@physik.fu-berlin.de \
--cc=debian-68k@lists.debian.org \
--cc=linux-m68k@vger.kernel.org \
/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 NNTP newsgroup(s).