On Thu, Nov 24, 2016 at 04:35:28PM +0100, Guillem Jover wrote:
>...
> On Thu, 2016-11-24 at 14:52:33 +, Thorsten Glaser wrote:
>...
> > Worse, they break *differently* on whether…
> >
> > >Precisely to make the behavior consistent on all architectures, dpkg
> > >enables PIE (conditionally if
Hi Guillem,
2016-11-24 17:00 GMT+01:00 John Paul Adrian Glaubitz
:
> On 11/24/2016 04:35 PM, Guillem Jover wrote:
>> Hi!
>>
>> On Thu, 2016-11-24 at 14:52:33 +, Thorsten Glaser wrote:
>>> clone 845193 -1
>>> reassign -1 dpkg
>>> retitle -1 dpkg: please do not add
On 11/24/2016 04:35 PM, Guillem Jover wrote:
> Hi!
>
> On Thu, 2016-11-24 at 14:52:33 +, Thorsten Glaser wrote:
>> clone 845193 -1
>> reassign -1 dpkg
>> retitle -1 dpkg: please do not add -specs= flags only on some architectures
>> thanks
>
> I'm afraid I'll have to wontfix this because it
Hi!
On Thu, 2016-11-24 at 14:52:33 +, Thorsten Glaser wrote:
> clone 845193 -1
> reassign -1 dpkg
> retitle -1 dpkg: please do not add -specs= flags only on some architectures
> thanks
I'm afraid I'll have to wontfix this because it is not really
implementable. See below… :/
> Guillem Jover
Guillem Jover dixit:
>> Yes, but they *do* break anything that
>> - acts on the CFLAGS (and LDFLAGS) variables
>> - uses klcc or other compiler wrappers that don't understand -specs
>> - uses clang or pcc or whatever other compilers
>
>The default dpkg build flags have always been tied to the
clone 845193 -1
reassign -1 dpkg
retitle -1 dpkg: please do not add -specs= flags only on some architectures
thanks
Guillem Jover dixit:
>> I cannot build openssl1.0 any longer. Downgrading all binary
>> packages from src:dpkg to 1.18.10 makes the build succeed.
Interestingly enough,
6 matches
Mail list logo