| Summary: | dev-lang/mercury-10.04.2 fails to compile | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Sven E. <dark> |
| Component: | [OLD] Development | Assignee: | Keri Harris <keri> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | ||
| Priority: | High | ||
| Version: | unspecified | ||
| Hardware: | AMD64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Attachments: |
Build Log
Requested log file |
||
|
Description
Sven E.
2010-10-19 18:47:51 UTC
Attach the build log, then. The emerge output explicitly asked you to. Created attachment 251343 [details]
Build Log
Well every ebuild does so, no matter if it's sane and worth the effort, doesn't it?
Thanks for taking the time to report this. Alas, I've been unable to reproduce this. :-( It looks like your 'make' thinks it needs to regenerate .c files from .m files (we can't do that since we don't have a Mercury compiler built yet). Can you try emerging mercury again and when it fails, run the following: # cd /var/tmp/portage/dev-lang/mercury-10.04.2-r1/work/mercury-compiler-10.04.2-r1/compiler # MMAKE_DIR=`pwd`/../scripts PATH=`pwd`/../scripts:$PATH ../scripts/mmake -v -d 2>&1 | gzip &> /var/tmp/portage/dev-lang/mercury-10.04.2-r1/temp/log.gz Then please attach the /var/tmp/portage/dev-lang/mercury-10.04.2-r1/temp/log.gz file to this bug. This should give me an idea as to which files it thinks need regenerating and why. Created attachment 253367 [details]
Requested log file
Aside from the log, I just saw that after unpacking the call to autoheader seems to fail - I don't know if that's a problem though.
Thanks very much for the log - it proved a real help! This should now be fixed in CVS. We now use a 2-pass bootstrap that allows us to patch .m files directly. (I've also tidied up the autoheader failure, along with a java/erlang grade failure when using GNU make 3.82). Keri |