Sébastien Villemot:
> My understanding is that .oct files are stripped before creating the
> Debian package (by dh_strip). Hence they no longer contain debugging
> symbol. So removing -g at compilation time should make no difference.
The build id is generated by ld using a checksum of the whole bi
Le mardi 27 octobre 2015 à 13:40 +0100, Rafael Laboissiere a écrit :
> * Reiner Herrmann [2015-10-26 22:06]:
> >
> > [...]
> >
> > Here is a quick proof that the path is responsible for the differences:
> >
> > $ cp test.c tmp-1/ && cd tmp-1 && mkoctfile test.c && md5sum test.o && cd
> > ..
> >
Rafael Laboissiere:
> I think that I found the culprit. The .oct files for octave are built using
> the mkoctfile program, as you pointed out above. This program uses default
> values for the the environment variables containing flags for the to C++
> compilation and binary link. For instance:
>
* Reiner Herrmann [2015-10-26 22:06]:
[...]
Here is a quick proof that the path is responsible for the differences:
$ cp test.c tmp-1/ && cd tmp-1 && mkoctfile test.c && md5sum test.o && cd ..
8cd4b14fc2bab0efad22f17920d02455 test.o
$ cp test.c tmp-1/ && cd tmp-1 && mkoctfile test.c && md
On Mon, Oct 26, 2015 at 08:42:42PM +0100, Rafael Laboissiere wrote:
> Thanks, this is exactly the information that I needed. I think I found a
> fix for this issue by making a change in the octave-pkg-dev package [1].
[...]
> 1.
> http://lists.alioth.debian.org/pipermail/pkg-octave-devel/2015-O
* Reiner Herrmann [2015-10-26 12:05]:
If you look at the page of an affected package [1], you can find a diff
of the logs between both build [2]. There you won't find the build id,
but the cause of the binary variation:
-mkdir (/tmp/oct-RnOahg)
-Copying directory (., /tmp/oct-RnOahg)
-m