Description of problem: This package contains a configuration file (spec) that changes the compilers default setting to build all ELF binaries in the Position Independend Executable (PIE) variant. This enables better address space randomization (ASLR). Version-Release number of selected component (if applicable): 13
Created attachment 14145 [details] Proposal spec file
CC: (none) => lovaren
Can you explain where this would apply. An optional component for users? For all Mageia compiled packages? Which compilers?
Severity: normal => enhancementCC: (none) => lewyssmith
Unfortunately Kristoffer posted the original openSUSE/SUSE spec which can not even be used by Mageia. A quick glance over the spec file shows clearly that it can not be used easily for Mageia. - It references openSUSE/SUSE packages - it does not follow Mageias naming convention for packages - it uses openSUSE/SUSE package naming conventions and structures - … That means using this spec would produce a complette set of gcc packages which can not be used on Mageia but would definitely break the complete development tools… Additionally, a new package request should contain a description, what it is used for and why it would be good to have it (advantages). So again this is only a dumped spec file without explanation for the usecase, which would need a heavy rework by a maintainer to be able to use it for Mageia…
Yes Kristoffer, you need to give a better defined case for adding this thing.
*** Bug 33215 has been marked as a duplicate of this bug. ***
No answer from TO. But the duplicate bug 33215 shows that this package is only needed for ghc-bootstrap. So technically it is a package dependency for another package which won't get build for Mageia. See bug 31446 Closing then...
Status: NEW => RESOLVEDResolution: (none) => WONTFIX
(In reply to sturmvogel from comment #6) > No answer from TO. > > But the duplicate bug 33215 shows that this package is only needed for > ghc-bootstrap. > So technically it is a package dependency for another package which won't > get build for Mageia. See bug 31446 > > Closing then... I am trying to get it built for Mageia since we already have dependencies for it in the official repos (ghc-rpm-macros, llvm, libnuma plus many more). To have gcc-PIE would make it a lot easier.
(In reply to sturmvogel from comment #3) > Unfortunately Kristoffer posted the original openSUSE/SUSE spec which can > not even be used by Mageia. A quick glance over the spec file shows clearly > that it can not be used easily for Mageia. > > - It references openSUSE/SUSE packages > - it does not follow Mageias naming convention for packages > - it uses openSUSE/SUSE package naming conventions and structures > - … > > That means using this spec would produce a complette set of gcc packages > which can not be used on Mageia but would definitely break the complete > development tools… > > Additionally, a new package request should contain a description, what it is > used for and why it would be good to have it (advantages). > > So again this is only a dumped spec file without explanation for the > usecase, which would need a heavy rework by a maintainer to be able to use > it for Mageia… Is there a workaround to get ghc-bootstrap built even though it needs gcc-PIE?
Could we perhaps create a standalone package for gcc then to meet halfway? That way we have it if one needs it and it won't install together with gcc if one doesn't specifically tell urpmi, dnf or yum to install it as well. You know there's a good saying that I like: "It's better to have and not need it than to need it and not have it." I'm working on making a spec file that anyone is free to continue on if they wish to help.
Created attachment 14572 [details] A spec to develop I took the liberty of starting the rewrite of the gcc spec file to only build gcc-PIE if that's even possible as so many are against including PIE for the ordinary gcc package. Feel free to adapt it and think of this as a standalone package for gcc.
Attachment 14145 is obsolete: 0 => 1