Reports: i686-pc-linux-gnu-gcc: -pie and -pg|p|profile are incompatible when linking Failed to link atheme-services! Reproducible: Always Steps to Reproduce: 1. ACCEPT_KEYWORDS="~86" emerge atheme-services Actual Results: i686-pc-linux-gnu-gcc: -pie and -pg|p|profile are incompatible when linking Failed to link atheme-services! Expected Results: Compiles
Created attachment 276613 [details] emerge info
Comment on attachment 276613 [details] emerge info May you test if the attachment you made was uploaded properly? ohnobinki@mommylappy /tmp $ tar -xvzf logs.tar.gz tar: This does not look like a tar archive tar: Skipping to next header tar: Exiting with failure status due to previous errors
Created attachment 276701 [details] emerge info Previous was corrupt.
Created attachment 276703 [details] emerge info Maybe file auto-detect was corrupting?
attachment 276703 [details] works. Had to manually select binary. Sorry about that.
(In reply to comment #5) > attachment 276703 [details] works. Had to manually select binary. Sorry about that. No, you had accidentally run tar -cvzf logs.tar <filenames> and then subsequently run gzip logs.tar, resulting in me being able to retrieve the original files with `zcat logs.tar.gz | tar -xvz'. One note: are you sure you're interested in having USE=profile on (do you know what this flag actually does)? If you want a more secure installation of atheme-services, you should disable this useflag. I have just added some code to the ebuild in CVS which automatically disables PIE when USE=profile (following what was done for wireshark in bug 292991). May you test that USE=profile ACCEPT_KEYWORDS=~x86 emerge atheme-services works now and then comment on this bug?
(In reply to comment #6) > One note: are you sure you're interested in having USE=profile on (do you know > what this flag actually does)? If you want a more secure installation of > atheme-services, you should disable this useflag. No, I am not sure I want to use that flag or I am using that flag: ACCEPT_KEYWORDS="~x86" emerge -vp atheme-services reports: [ebuild N ] net-irc/atheme-services-6.0.8 USE="nls pcre perl ssl -largenet -ldap -profile" Or am I misunderstanding you? > I have just added some code to the ebuild in CVS which automatically disables > PIE when USE=profile (following what was done for wireshark in bug 292991). May > you test that > USE=profile ACCEPT_KEYWORDS=~x86 emerge atheme-services > works now and then comment on this bug? I think I am misunderstanding you. USE=profile ACCEPT_KEYWORDS=~x86 emerge atheme-services Fails with the same error.
(In reply to comment #7) > (In reply to comment #6) > > One note: are you sure you're interested in having USE=profile on (do you know > > what this flag actually does)? If you want a more secure installation of > > atheme-services, you should disable this useflag. > > No, I am not sure I want to use that flag or I am using that flag: > ACCEPT_KEYWORDS="~x86" emerge -vp atheme-services > reports: > [ebuild N ] net-irc/atheme-services-6.0.8 USE="nls pcre perl ssl > -largenet -ldap -profile" > > Or am I misunderstanding you? Sorry, I'm completely wrong about this. I should have read your emerge --info and seen that you don't have `profile' in USE. The problem is that atheme's ./configure script was interpreting --disable-profile as if I meant --enable-profile. Which means that the profile stuff was enabled unconditionally. I've added a patch which fixes that into CVS; hopefully that'll work. I've confirmed that it removed "-pg" from the compilation arguments. > I think I am misunderstanding you. > > USE=profile ACCEPT_KEYWORDS=~x86 emerge atheme-services > > Fails with the same error. Sorry again for the trouble, but thanks for testing this for me. If you are willing to test this again for me with the updated version, I'd be grateful.
