Bug#822820: gcl: FTBFS with compilers that default to -fPIE (patch attached)

On Wed, May 04, 2016 at 11:43:13AM -0400, Camm Maguire wrote: > > I intend to sanitize this in the gcl configure script, as is already > done on an ad-hoc basis for osx. The problem is getting the semantics > right for both gcc and clang interfaces to the linker. With gcc, > *appending* -no-pie

Bug#822820: gcl: FTBFS with compilers that default to -fPIE (patch attached)

Greetings, and thanks! I now understand the issue, and it is true that GCL will never work with a position independent executable, as it uses unexec to save memory images to disk for later restart. I intend to sanitize this in the gcl configure script, as is already done on an ad-hoc basis for

Bug#822820: gcl: FTBFS with compilers that default to -fPIE (patch attached)

On Tue, May 03, 2016 at 12:38:26PM -0400, Camm Maguire wrote: > > Greetings! I can add -fPIE without issue to the build flags used for > the failed target you report in an up-to-date Debian unstable chroot > (amd64). Add "-fPIE -pie" (the latter being the linker command, the former should not

Bug#822820: gcl: FTBFS with compilers that default to -fPIE (patch attached)

tags 822820 unreproducible thanks Greetings! I can add -fPIE without issue to the build flags used for the failed target you report in an up-to-date Debian unstable chroot (amd64). Take care, Adam Conrad writes: > Package: gcl > Version: 2.6.12-32 > Severity: normal >

Bug#822820: gcl: FTBFS with compilers that default to -fPIE (patch attached)

Package: gcl Version: 2.6.12-32 Severity: normal Tags: patch User: ubuntu-de...@lists.ubuntu.com Usertags: origin-ubuntu yakkety ubuntu-patch In Ubuntu, the attached patch was applied to achieve the following: * Set CC to 'gcc -fno-pie -no-pie' to prevent FTBFS (LP: #1557236) The patch