Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v1 2/2] dhcp: disable isc assertions (reproducible builds)
Date: Sat, 03 Feb 2018 22:54:44 +0100	[thread overview]
Message-ID: <877ert20yj.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20180130175402.GA3468@scaer> (Yann E. MORIN's message of "Tue, 30 Jan 2018 18:54:02 +0100")

>>>>> "Yann" == Yann E MORIN <yann.morin.1998@free.fr> writes:

Hi,

 >> Peter, Arnout, Yann, what do you think, especially about the
 >> assertions ?

 > Assertions are supposed to be usefull during development, not during
 > production use, so I would be fine with disabling them, yes.

 > At least, I would hope that no sane developer uses assertions to check
 > for normal error conditions in normal operation mode... ;-]

Agreed, and the space savings are quite big - So committed, thanks.

 > Now, about reproducibility... We could at least pass -DFILE=\"\" and so
 > on from inside our gcc-wrapper, like we already do for __DATE__ and
 > __TIME__. Yes, that would give an empty filename in assertions and the
 > likes, but do we care in the end?

It would be nicer if we could pass basename($file), but that would break
with compilations with multiple source files passed to gcc or header
files, so yeah, perhaps that is the best way forward.

How does E.G. Debian handle it?

-- 
Bye, Peter Korsgaard

  reply	other threads:[~2018-02-03 21:54 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-27 19:24 [Buildroot] [PATCH v1 1/2] libopenssl: do not leak the compiler path (reproducible builds) Peter Seiderer
2017-10-27 19:24 ` [Buildroot] [PATCH v1 2/2] dhcp: disable isc assertions " Peter Seiderer
2018-01-08 20:18   ` Thomas Petazzoni
2018-01-15 21:46     ` Peter Seiderer
2018-01-30 17:54     ` Yann E. MORIN
2018-02-03 21:54       ` Peter Korsgaard [this message]
2018-02-04  9:54         ` Yann E. MORIN
2018-02-04 21:50           ` Peter Korsgaard
2018-01-08 20:10 ` [Buildroot] [PATCH v1 1/2] libopenssl: do not leak the compiler path " Thomas Petazzoni
2018-01-30 23:15   ` Peter Seiderer

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=877ert20yj.fsf@dell.be.48ers.dk \
    --to=peter@korsgaard.com \
    --cc=buildroot@busybox.net \
    /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