[Pkg-octave-devel] Trying to fix random_buildpath_by_octave

[Reiner Herrmann]

On Tue, Oct 27, 2015 at 01:47:20PM +0100, Jérémy Bobbio wrote:
> Rafael Laboissiere:
> > I discovered that the "-g" is responsible for the difffrences in the
> > resulting binaries.  Here is the proof:

@Rafael:
Nice finding that mkoctfile passes -g to the compiler!

> Is `mkoctfile` creating a randomly-named temporary file? g++ will write
> the full path to the source file in the debug symbols. That would
> explain why removing `-g` solve the problem.

No, it is only invoking the compiler (gcc/g++) on the source file that is
already there.
But some helper-script is copying the source to a temporary/random
directory beore calling mkoctfile.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 801 bytes
Desc: Digital signature
URL: <http://lists.alioth.debian.org/pipermail/pkg-octave-devel/attachments/20151027/562269a7/attachment.sig>