After trying to install a manual ebuild for BEID runtime (can be found here: http://bugs.gentoo.org/show_bug.cgi?id=187422) I cannot install the libtomcrypt package using emerge, it failes because the patch file doesn't seem to work. I try to install the libtomcrypt package because the beid-runtime-3.5.4 fails with some error referring to the libtomcrypt. Reproducible: Didn't try Steps to Reproduce: 1. I try installing a manual ebuild: beid-runtime-3.5.4 which can be found here: http://bugs.gentoo.org/attachment.cgi?id=235239 after extracting the file, I run: "ebuild app-misc/beid-runtime/beid-runtime-3.5.4.ebuild merge" as root (not sudo) 2. installed the package "pcsc-lite" because it was requested by the ebuild: "sudo emerge -av pcsc-lite" This went ok 3. reran "ebuild app-misc/beid-runtime/beid-runtime-3.5.4.ebuild merge" as root failed with: libtomcrypt/tomcrypt_macros.h:229: warning: asm operand 2 probably doesn't match constraints libtomcrypt/tomcrypt_macros.h:229: error: impossible constraint in 'asm' 4. then I did an ebuild clean and tried to install the libtomcrypt package using emerge: "sudo emerge -av libtomcrypt" which failes with following info: * Failed Patch: libtomcrypt-1.06-makefile.diff ! * ( /usr/portage/dev-libs/libtomcrypt/files/libtomcrypt-1.06-makefile.diff ) retried emerge libtomcrypt but same problem. Actual Results: cannot emerge libtomcrypt cannot install the beid-runtime-3.5.4 manual ebuild Expected Results: I suppose it should have just installed the libtomcrypt package after applying the patch to it without giving me any error. I will add info as attachment as requested by emerge. /var/tmp/portage/dev-libs/libtomcrypt-1.06/temp/libtomcrypt-1.06-makefile.diff.out
Created attachment 241621 [details] makefile.diff.out this file has been requested by emerge to be included in bugreport.
Created attachment 241623 [details] output from the emerge command text output from emerge
Hello, I could reproduce your error. Can you please try to emerge version 1.17-r2 on your system as a work-around? Michael
Hello Thilo, you're mentioned in the ChangeLog as committer of this patch, can you please take a look?! Thanks, Michael
(In reply to comment #3) > Hello, > > I could reproduce your error. > Can you please try to emerge version 1.17-r2 on your system as a work-around? > > Michael > Thanks for the advice Michael, I did the following: $> ACCEPT_KEYWORDS="~amd64" emerge -av libtomcrypt This installed 1.17-r3 on my system, I got no errors here. kind regards, Lieven
this is really really weird, but its fixed now (again). thanks for the report.
