Re: [rb-general] advice on stashing compiler options in a binary

2019-03-20 Thread Eric Myhre
On 3/20/19 12:19 PM, Orians, Jeremiah (DTMB) wrote: In today's world, or you can easily create full containers or at least chroot sandboxes, those are pretty easy to recreate. Or a simpler option, fully static binaries like those M2-Planet creates. https://github.com/oriansj/M2-Planet Where the

Re: [rb-general] advice on stashing compiler options in a binary

2019-03-20 Thread Chris Lamb
Dear Mike, > I recently realized this leads to a paradox with the -fdebug-prefix-map > option, since the original build directory is recorded in the stashed > compiler options. Indeed. I have so far failed to come up with any kind of cleaner solution when fixing packages affected with this "meta"

Re: [rb-general] advice on stashing compiler options in a binary

2019-03-20 Thread Orians, Jeremiah (DTMB)
>> Similarly to other interpreted >>languages, the compiler options used are stashed in the binary for later use. >I don't know what everyone else here believes, but I recommend that those not >be included in the binaries at all, but instead be put elsewhere so they can >be more easily separated.