On Tue, Feb 14, 2023 at 05:07:49PM +0200, Peter Pentchev wrote:
> Right, when I said "record the compiler flags", I did not mean "and always
> pass them on verbatim". I think you may already know this, since you talk
> about Python, but yeah, in Python's case things are really not that simple.
>
On Tue, Feb 14, 2023 at 09:51:50AM +, Simon McVittie wrote:
> On Tue, 14 Feb 2023 at 10:21:31 +0200, Peter Pentchev wrote:
> > I can't speak of many other systems, but at least with Perl's XS
> > (the standard way to write Perl modules parts of which are compiled C code)
> > and two of the ways
On Tue, 14 Feb 2023 at 10:21:31 +0200, Peter Pentchev wrote:
> I can't speak of many other systems, but at least with Perl's XS
> (the standard way to write Perl modules parts of which are compiled C code)
> and two of the ways this can be done in Python, it is the same:
> the C compiler's name and
On Tue, Feb 14, 2023 at 09:04:47AM +0100, Stéphane Glondu wrote:
> Hi,
>
> Le 08/02/2023 à 10:58, Emilio Pozuelo Monfort a écrit :
> > What is the purpose of having the build flags in a file in the .deb?
>
> ocamlc can act as a driver for the C compiler, to compile C stubs with the
> "right" flag
Hi,
Le 08/02/2023 à 10:58, Emilio Pozuelo Monfort a écrit :
What is the purpose of having the build flags in a file in the .deb?
ocamlc can act as a driver for the C compiler, to compile C stubs with
the "right" flags. These flags are basically the CFLAGS ocaml was
compiled with, plus some a
Hi!
I'm end up with following thing:
https://github.com/rockdrilla/debian-container/blob/808dfa15d130f833602a1486362cc551593a0d8a/image/python/template/rules#L543
Hovewer, "execute_before_dh_builddeb" recipe is for information only
(to be viewed by human) and "execute_before_dh_install" recipe is
On 2023-02-08, Stéphane Glondu wrote:
> Thank you all for your answers!
>
> Using:
>
>DEB_BUILD_MAINT_OPTIONS=reproducible=-fixfilepath,-fixdebugpath
>
> makes the package unreproducible in another way that seems difficult to fix.
Most likely reintroducing the things that the -ffile-prefix-map
On Tue, 2023-02-07 at 20:00:06 +0100, Sven Joachim wrote:
> On 2023-02-07 17:50 +0100, Guillem Jover wrote:
> > On Tue, 2023-02-07 at 16:41:47 +0100, Stéphane Glondu wrote:
> >> I suspect this was added to improve reproducibility. Ironically, it makes
> >> packages that capture this variable non re
Thank you all for your answers!
Using:
DEB_BUILD_MAINT_OPTIONS=reproducible=-fixfilepath,-fixdebugpath
makes the package unreproducible in another way that seems difficult to fix.
Le 07/02/2023 à 19:12, Mattia Rizzolo a écrit :
I actually propose to you to filter out the whole option from b
On 07/02/2023 20:00, Sven Joachim wrote:
On 2023-02-07 17:50 +0100, Guillem Jover wrote:
On Tue, 2023-02-07 at 16:41:47 +0100, Stéphane Glondu wrote:
When building packages, a -ffile-prefix-map option is automatically injected
into CFLAGS. Where does it come from? Since when?
This is coming
On 2023-02-07 17:50 +0100, Guillem Jover wrote:
> On Tue, 2023-02-07 at 16:41:47 +0100, Stéphane Glondu wrote:
>> When building packages, a -ffile-prefix-map option is automatically injected
>> into CFLAGS. Where does it come from? Since when?
>
> This is coming from dpkg-buildflags (in this case
On Tue, Feb 07, 2023 at 04:41:47PM +0100, Stéphane Glondu wrote:
> When building packages, a -ffile-prefix-map option is automatically injected
> into CFLAGS. Where does it come from? Since when?
>
> I suspect this was added to improve reproducibility. Ironically, it makes
> packages that capture
Hi!
On Tue, 2023-02-07 at 16:41:47 +0100, Stéphane Glondu wrote:
> When building packages, a -ffile-prefix-map option is automatically injected
> into CFLAGS. Where does it come from? Since when?
This is coming from dpkg-buildflags (in this case probably indirectly
via debhelper). AFAICS it was a
Hi,
Quoting Stéphane Glondu (2023-02-07 16:41:47)
> When building packages, a -ffile-prefix-map option is automatically injected
> into CFLAGS. Where does it come from? Since when?
probably due to
https://git.hadrons.org/cgit/debian/dpkg/dpkg.git/commit/?id=b60c243ba99b8483202a6f6a814476275204fdf
Hi,
When building packages, a -ffile-prefix-map option is automatically
injected into CFLAGS. Where does it come from? Since when?
I suspect this was added to improve reproducibility. Ironically, it
makes packages that capture this variable non reproducible, since the
build path seems to be
15 matches
Mail list logo
