Bug#845193: dpkg: recent -specs PIE changes break openssl

On Sat, 19 Aug 2017, Sebastian Andrzej Siewior wrote: > This is currently still open against openssl1.0, the package is built > without a log so I assume that it has been built manually. > Is there anything we can/should do here? Hm, it currently builds as-is (log attached), so I think that all

Bug#845193: dpkg: recent -specs PIE changes break openssl

On 2016-11-21 12:01:21 [+0100], Thorsten Glaser wrote: > I’m suspecting it tries to compile library code (which must > be PIC) as PIE, or something. I got this advice from the > openssl maintainer: This is currently still open against openssl1.0, the package is built without a log so I assume

Bug#845193: [Pkg-openssl-devel] Bug#845193: Bug#845193: dpkg: recent -specs PIE changes break openssl

On 2016-12-29 00:25:05 [+0100], To Kurt Roeckx wrote: > > Figure out why it uses link_a instead of link_o, and maybe fix it? so that link_a instead of link_o is always used - not just on x32. Replacing _a with _o here gets the build to continue but fails later in a (normal) link_o rule:

Bug#845193: [Pkg-openssl-devel] Bug#845193: dpkg: recent -specs PIE changes break openssl

On 2016-12-28 17:01:10 [+0100], Kurt Roeckx wrote: > On Wed, Dec 28, 2016 at 02:59:18PM +0100, Sebastian Andrzej Siewior wrote: > > On 2016-12-08 01:20:06 [+0100], Guillem Jover wrote: > > > Hi! > > Hi, > > > > > The actual problem here, is that for whatever reason on x32 and only > > > x32, the

Bug#845193: [Pkg-openssl-devel] Bug#845193: dpkg: recent -specs PIE changes break openssl

On Wed, Dec 28, 2016 at 02:59:18PM +0100, Sebastian Andrzej Siewior wrote: > On 2016-12-08 01:20:06 [+0100], Guillem Jover wrote: > > Hi! > Hi, > > > The actual problem here, is that for whatever reason on x32 and only > > x32, the build system is (as I noted in #845193#10) calling link_a.gnu > >

Bug#845193: [Pkg-openssl-devel] Bug#845193: dpkg: recent -specs PIE changes break openssl

On 2016-12-08 01:20:06 [+0100], Guillem Jover wrote: > Hi! Hi, > The actual problem here, is that for whatever reason on x32 and only > x32, the build system is (as I noted in #845193#10) calling link_a.gnu > instead of the link_o.gnu target, which tries to link a static library > composed of PIE

Bug#845193: [Pkg-openssl-devel] Bug#845193: dpkg: recent -specs PIE changes break openssl

Hi! On Wed, 2016-11-30 at 22:00:12 +0100, Kurt Roeckx wrote: > On Wed, Nov 30, 2016 at 07:55:55PM +, Thorsten Glaser wrote: > > Kurt Roeckx dixit: > > >> Unfortunately, I have no idea; 1.1 builds, 1.0 doesn’t. > > > > > >But both are actually in installed state now? > > Yes because I built

Bug#845193: [Pkg-openssl-devel] Bug#845193: dpkg: recent -specs PIE changes break openssl

On Wed, 2016-11-30 at 19:55:55 +, Thorsten Glaser wrote: > Kurt Roeckx dixit: > >And if only 1.0 is affected, I'm not sure why it's assigned to the > >openssl source package. It's not. > I’m not sure why Guillem reassigned the bug either, considering > I cloned it in the first place to have

Bug#845193: [Pkg-openssl-devel] Bug#845193: Bug#845193: dpkg: recent -specs PIE changes break openssl

On Wed, Nov 30, 2016 at 11:43:13PM +0100, Sebastian Andrzej Siewior wrote: > On 2016-11-30 21:22:38 [+], Thorsten Glaser wrote: > > Kurt Roeckx dixit: > > > > >But the errors I've always been seeing is a segfault during the > > >tests, and I have no idea what that is about. > > > > That

Bug#845193: [Pkg-openssl-devel] Bug#845193: Bug#845193: dpkg: recent -specs PIE changes break openssl

On 2016-11-30 21:22:38 [+], Thorsten Glaser wrote: > Kurt Roeckx dixit: > > >But the errors I've always been seeing is a segfault during the > >tests, and I have no idea what that is about. > > That didn't happen for me, but I found a wrong codegen bug in a > testsuite recently (probably not

Bug#845193: [Pkg-openssl-devel] Bug#845193: dpkg: recent -specs PIE changes break openssl

Kurt Roeckx dixit: >But the errors I've always been seeing is a segfault during the >tests, and I have no idea what that is about. That didn't happen for me, but I found a wrong codegen bug in a testsuite recently (probably not the cause here), we had kernel issues (4.7 is broken, 4.8 is mostly

Bug#845193: [Pkg-openssl-devel] Bug#845193: dpkg: recent -specs PIE changes break openssl

On Wed, Nov 30, 2016 at 07:55:55PM +, Thorsten Glaser wrote: > Kurt Roeckx dixit: > > >> Unfortunately, I have no idea; 1.1 builds, 1.0 doesn’t. > > > >But both are actually in installed state now? > > Yes because I built it in a chroot in which I downgraded dpkg > to .10, which led to a

Bug#845193: [Pkg-openssl-devel] Bug#845193: dpkg: recent -specs PIE changes break openssl

Kurt Roeckx dixit: >> Unfortunately, I have no idea; 1.1 builds, 1.0 doesn’t. > >But both are actually in installed state now? Yes because I built it in a chroot in which I downgraded dpkg to .10, which led to a completely fine build of openssl1.0 with testsuite enabled even. >And if only 1.0

Bug#845193: [Pkg-openssl-devel] Bug#845193: dpkg: recent -specs PIE changes break openssl

On Wed, Nov 30, 2016 at 12:07:44PM +, Thorsten Glaser wrote: > Kurt Roeckx dixit: > > >So can someone explain what needs to be fixed in openssl? The > >order of the CFLAGS needs to be changed? > > Unfortunately, I have no idea; 1.1 builds, 1.0 doesn’t. But both are actually in installed

Bug#845193: [Pkg-openssl-devel] Bug#845193: dpkg: recent -specs PIE changes break openssl

Kurt Roeckx dixit: >So can someone explain what needs to be fixed in openssl? The >order of the CFLAGS needs to be changed? Unfortunately, I have no idea; 1.1 builds, 1.0 doesn’t. If you have an amd64 host (recent enough but not kernel 4.7) you can add syscall.x32=y to GRUB_CMDLINE_LINUX and

Bug#845193: [Pkg-openssl-devel] Bug#845193: dpkg: recent -specs PIE changes break openssl

On Wed, Nov 30, 2016 at 05:38:45AM +0100, Guillem Jover wrote: > Control: reassign -1 openssl1.0 > > 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 > >

Bug#845193: dpkg: recent -specs PIE changes break openssl

Control: reassign -1 openssl1.0 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 > > Guillem Jover dixit: > >> I cannot build openssl1.0 any longer. Downgrading

Bug#845193: dpkg: recent -specs PIE changes break openssl

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

Bug#845193: dpkg: recent -specs PIE changes break openssl

John Paul Adrian Glaubitz dixit: >Fixing the issue in a similar way as it was fixed on sparc64 [1] is >not possible? Which of the issues? #845193 is likely a genuine issue in openssl1.0, as 1.1 works fine, although triggered by the dpkg flags. #845550 (the clone) is about dpkg adding some

Bug#845193: dpkg: recent -specs PIE changes break openssl

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

Bug#845193: dpkg: recent -specs PIE changes break openssl

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

Bug#845550: Bug#845193: dpkg: recent -specs PIE changes break openssl

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

Bug#845193: dpkg: recent -specs PIE changes break openssl

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

Bug#845193: dpkg: recent -specs PIE changes break openssl

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,

Bug#845193: dpkg: recent -specs PIE changes break openssl

Control: retitle -1 dpkg: openssl1.0 broken on x32 due to PIE -specs Hi! On Mon, 2016-11-21 at 12:01:21 +0100, Thorsten Glaser wrote: > Source: dpkg > Version: 1.18.15 > Severity: important > I cannot build openssl1.0 any longer. Downgrading all binary > packages from src:dpkg to 1.18.10 makes