this patch allow sys-boot/grub-2.02_beta2-r2 to compile and run under gentoo over musl Reproducible: Always
Created attachment 389446 [details, diff] patch
this patch allow dev-libs/pth-2.0.7-r3 to compile and run under gentoo over musl bad copy paste, my bad, trying to keep the format identical
you enable a code that was conditional and probably damage other sequences. please discuss with upstream what should be added, also please notice that pth is no longer used in gnupg-2.1
(In reply to Alon Bar-Lev from comment #3) > you enable a code that was conditional and probably damage other sequences. > musl upstream or pth upstream? > please discuss with upstream what should be added, also please notice that > pth is no longer used in gnupg-2.1 no sure I understand what gnupg has to do with this bug.
(In reply to DaggyStyle from comment #4) > (In reply to Alon Bar-Lev from comment #3) > > you enable a code that was conditional and probably damage other sequences. > > > > musl upstream or pth upstream? > pth upstream... although they will accept no patches. > > please discuss with upstream what should be added, also please notice that > > pth is no longer used in gnupg-2.1 > > no sure I understand what gnupg has to do with this bug. gnupg is the only consumer of this old package as far as I understand. anyway, you should add conditional and not remove conditional when you are porting to another environment.
(In reply to Alon Bar-Lev from comment #5) > (In reply to DaggyStyle from comment #4) > > (In reply to Alon Bar-Lev from comment #3) > > > you enable a code that was conditional and probably damage other sequences. > > > > > > > musl upstream or pth upstream? > > > > pth upstream... although they will accept no patches. > will try. > > > please discuss with upstream what should be added, also please notice that > > > pth is no longer used in gnupg-2.1 > > > > no sure I understand what gnupg has to do with this bug. > > gnupg is the only consumer of this old package as far as I understand. > > anyway, you should add conditional and not remove conditional when you are > porting to another environment. I'm trying to work wit what's stable, that is why gnupg polls it in. technically I didn't removed a condition, the issue is that there is no way codewise to know one is compiling against musl
(In reply to DaggyStyle from comment #6) > > anyway, you should add conditional and not remove conditional when you are > > porting to another environment. > > I'm trying to work wit what's stable, that is why gnupg polls it in. > technically I didn't removed a condition, the issue is that there is no way > codewise to know one is compiling against musl you did remove conditional. if there is no way to detect musl, please contact upstream so they add such to enable use of conditionals.
(In reply to Alon Bar-Lev from comment #7) > (In reply to DaggyStyle from comment #6) > > > anyway, you should add conditional and not remove conditional when you are > > > porting to another environment. > > > > I'm trying to work wit what's stable, that is why gnupg polls it in. > > technically I didn't removed a condition, the issue is that there is no way > > codewise to know one is compiling against musl > > you did remove conditional. > if there is no way to detect musl, please contact upstream so they add such > to enable use of conditionals. it won't be added, see http://openwall.com/lists/musl/2013/03/29/13. I will however try to ask again if there is a way to know that.
(In reply to DaggyStyle from comment #8) > (In reply to Alon Bar-Lev from comment #7) > > (In reply to DaggyStyle from comment #6) > > > > anyway, you should add conditional and not remove conditional when you are > > > > porting to another environment. > > > > > > I'm trying to work wit what's stable, that is why gnupg polls it in. > > > technically I didn't removed a condition, the issue is that there is no way > > > codewise to know one is compiling against musl > > > > you did remove conditional. > > if there is no way to detect musl, please contact upstream so they add such > > to enable use of conditionals. > it won't be added, see http://openwall.com/lists/musl/2013/03/29/13. > > I will however try to ask again if there is a way to know that. so please find a solution to test what you need and define proper conditionals. in any case disabling conditional to damage the environments other than glibc is incorrect. I am closing this, please reopen when you have valid musl specific solution that does not effect any other implementation. Preferably upstream accepts solution.
