Summary: | dev-lang/tcl builds from unix directory when building with mingw | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Rob Stoddard <rob> |
Component: | Current packages | Assignee: | TCL/TK Project <tcltk> |
Status: | UNCONFIRMED --- | ||
Severity: | normal | CC: | jstein |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Thank you for the report. Regarding "learning how to sandbox an ebuild" I have had very good experience with the gentoo IRC channels [1] with questions like this. As you know, we can not discuss this in a bugticket. Regarding the digest, you need to update the manifest [2]. [1] https://www.gentoo.org/get-involved/irc-channels/ [2] https://wiki.gentoo.org/wiki/Repoman https://devmanual.gentoo.org/index.html |
The dev-lang/tcl ebuild tries to build TCL in the /unix directory regardless of what system it is building for. In most cases it is safe to assume that you're building for some form of UNIX, but when using mingw to do the building, you're building for Windows, and should be building in the /win directory. Now, I'm not up on my ebuild-fu, but this: SPARENT="${WORKDIR}/${MY_P}" S="${SPARENT}"/unix Needs to change to something a bit more dynamic. I'd have tried my hand at playing with it, but I ran into a "Digest verification failed" issue that prevents me from manipulating this ebuild: Calculating dependencies \ * Digest verification failed: * /usr/portage/dev-lang/tcl/tcl-8.6.6.ebuild * Reason: Filesize does not match recorded size * Got: 4005 * Expected: 3964 ... done! >>> Verifying ebuild manifests !!! Digest verification failed: !!! /usr/portage/dev-lang/tcl/tcl-8.6.6.ebuild !!! Reason: Filesize does not match recorded size !!! Got: 4005 !!! Expected: 3964 I wouldn't mind learning how to sandbox an ebuild like this and tweak it so that it works, since I'll probably be building a lot of stuff for Windows in the near future... but I'm not seeing any information on how to do that yet. I do see how to build your own ebuild, but not how to modify&test one that's already in portage. Thank you for any suggestions, or perhaps... a fix?