From: Dave Love <fx@gnu.org>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 28593@debbugs.gnu.org,
Paul Garlick <pgarlick@tourbillion-technology.com>
Subject: [bug#28593] [PATCH] gnu: openfoam: Clean up to reduce closure.
Date: Wed, 27 Sep 2017 22:30:40 +0100 [thread overview]
Message-ID: <87efqrsubj.fsf@albion.it.manchester.ac.uk> (raw)
In-Reply-To: <873779hdci.fsf@gnu.org> ("Ludovic \=\?iso-8859-1\?Q\?Court\=E8s\?\= \=\?iso-8859-1\?Q\?\=22's\?\= message of "Tue, 26 Sep 2017 14:08:13 +0200")
Ludovic Courtès <ludo@gnu.org> writes:
> That’s because we use ‘--strip-debug’ and not ‘--strip-all’ (in some
> cases, the latter breaks binaries in weird ways, hence the conservative
> choice.)
Is that something Guix-specific? As far as I know, with rpm and dpkg,
the binaries are always stripped, and I'm not aware of any problem with
that.
>> Does adding a debug output achieve the effect of stripping the
>> binaries?
>
> I don’t think it makes any difference.
Right.
Incidentally, you could save about half the size of the boost
contribution to closures like this by separating the headers and the
libraries, but there was some problem I don;t remember when I tried.
next prev parent reply other threads:[~2017-09-27 21:31 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-25 10:44 [bug#28593] [PATCH] gnu: openfoam: Clean up to reduce closure Dave Love
2017-09-25 12:52 ` Ludovic Courtès
2017-09-26 11:40 ` Paul Garlick
2017-09-26 12:08 ` Ludovic Courtès
2017-09-27 21:30 ` Dave Love [this message]
2017-09-28 8:36 ` Ludovic Courtès
2017-10-02 20:41 ` Dave Love
2017-10-03 12:33 ` Ludovic Courtès
2017-10-07 20:45 ` Ludovic Courtès
2017-10-09 11:06 ` Paul Garlick
2017-10-19 11:06 ` Dave Love
2017-10-19 12:15 ` Ludovic Courtès
2017-10-20 10:32 ` Paul Garlick
2017-10-20 11:28 ` Ludovic Courtès
2017-10-20 15:28 ` Dave Love
2017-10-20 15:26 ` Dave Love
2017-10-22 16:15 ` Dave Love
2017-10-23 15:00 ` Paul Garlick
2017-12-01 10:27 ` bug#28593: " Ludovic Courtès
2017-09-27 21:25 ` [bug#28593] " Dave Love
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=87efqrsubj.fsf@albion.it.manchester.ac.uk \
--to=fx@gnu.org \
--cc=28593@debbugs.gnu.org \
--cc=ludo@gnu.org \
--cc=pgarlick@tourbillion-technology.com \
/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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.