All of lore.kernel.org
 help / color / mirror / Atom feed
From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v1 2/2] dhcp: disable isc assertions (reproducible builds)
Date: Sun, 4 Feb 2018 10:54:13 +0100	[thread overview]
Message-ID: <20180204095413.GA2411@scaer> (raw)
In-Reply-To: <877ert20yj.fsf@dell.be.48ers.dk>

Peter, All,

On 2018-02-03 22:54 +0100, Peter Korsgaard spake thusly:
> >>>>> "Yann" == Yann E MORIN <yann.morin.1998@free.fr> writes:
[--SNIP--]
>  > 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?

I could not find an authoritative source for this, but from what I could
hint from [0] (see the part about "Qt tests and __FILE__"), they do have
a patched gcc and a special dpkg which use the BUILD_PATH_PREFIX_MAP
environment variable as specified iby reproducible-builds.org [1].

Also, upstream gcc has an "in-progress" upstream solution being worked
on, based on BUILD_PATH_PREFIX_MAP, but they did not like it [2]...

[0] https://reproducible.alioth.debian.org/blog/posts/134/
[1] https://reproducible-builds.org/specs/build-path-prefix-map/
[2] https://gcc.gnu.org/ml/gcc-patches/2017-08/msg00232.html

Regards,
Yann E. MORIN.

-- 
.-----------------.--------------------.------------------.--------------------.
|  Yann E. MORIN  | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software  Designer | \ / CAMPAIGN     |  ___               |
| +33 223 225 172 `------------.-------:  X  AGAINST      |  \e/  There is no  |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL    |   v   conspiracy.  |
'------------------------------^-------^------------------^--------------------'

  reply	other threads:[~2018-02-04  9: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
2018-02-04  9:54         ` Yann E. MORIN [this message]
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=20180204095413.GA2411@scaer \
    --to=yann.morin.1998@free.fr \
    --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 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.