First, the manifest freaks out on the source when you rename the 64bit source tar.gz to the file as requested. (Which can be resolved with updating the SRC_URI to include ${ARCH}) Second when you bump the ebuild and update the SRC_URI to something like the following: SRC_URI="${P}-linux-${ARCH}.tar.gz" to better match the file receieved from the Truecrypt site, the ebuild fails to prepare on: sed: can't read Main/Main.make: No such file or directory. I'll see what I can do tomorrow on this, and maybe get a working ebuild posted. Reproducible: Always Steps to Reproduce: 1. download source 2. rename to requested file name 3. set sail for fail Actual Results: * ERROR: app-crypt/truecrypt-7.0a-r6 failed (prepare phase): * sed Main/Main.make failed * * Call stack: * ebuild.sh, line 56: Called src_prepare * environment, line 3711: Called die * The specific snippet of code: * sed -e "s/WX_CONFIG_LIBS := base/&,core/" -i Main/Main.make || die "sed Main/Main.make failed"; * Expected Results: The package would build
Are you sure you downloaded the *source* tarball and not the precompiled binary one? Given that the Makefile wasn't found, I'm guessing you got the wrong thing. There is no such thing as 64 bit source / 32 bit source from Truecrypt. It's either a) source, b) 32 bit binary, c) 64 bit binary. You want (a).
Note: The correct download page is here - http://www.truecrypt.org/downloads2 and *not* here - http://www.truecrypt.org/download.
@Dane Smith, I think you are correct and this is why package/machine maintenance is a bad idea™ at 3-ish in the morning. I'm cancelling this one cause I'm a moron.
