Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 82186 - GHC Bootstrap with USE="doc" fails
Summary: GHC Bootstrap with USE="doc" fails
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: New packages (show other bugs)
Hardware: All Linux
: High minor (vote)
Assignee: Gentoo's Haskell Language team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-02-15 17:27 UTC by Scott Paeth
Modified: 2005-09-15 03:50 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---


Attachments
Error mesg from when doing emerge -a ghc (ghc-docs-compile-error.txt,71.16 KB, text/plain)
2005-09-15 03:25 UTC, Dario Lopez-Kästen
Details
results of command: emerge --info (emerge-info.txt,1.97 KB, text/plain)
2005-09-15 03:26 UTC, Dario Lopez-Kästen
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Scott Paeth 2005-02-15 17:27:50 UTC
GHC fails its bootstrap using ghc-bin if the doc useflag is set. This is because haddock isn't emerged, presumably; the problem is fixed if this is done, and the error is from the 'haddock' shell script about haddock.bin not being found.

Reproducible: Didn't try
Steps to Reproduce:
1. emerge ghc-bin
2. USE="doc" emerge ghc
Comment 1 Duncan Coutts (RETIRED) gentoo-dev 2005-02-15 19:10:59 UTC
Would you mind posting the full error message?

Also could you check what this says on your system:
USE="doc" emerge -pv ghc

and seperately:
emerge -pv haddock

I would expect that it should try to emerge haddock before ghc since it is a dependency of ghc when USE=doc is set.

My first suspicion is that haddock is actually installed but that it is going wrong for some reason.
Comment 2 Andres Loeh (RETIRED) gentoo-dev 2005-02-16 01:05:50 UTC
Thanks for the report. Yes, a full error message would help.

ks
Comment 3 Gour 2005-03-14 04:11:49 UTC
Hi!

Emerging ghc-6.4 with USE="doc" fails n amd64:

[...]
[ERROR] Unknown enumerated value for property 'relative-align': baseline
[ERROR] Error in relative-align property value 'baseline': org.apache.fop.fo.expr.PropertyException: No conversion defined
[INFO] [129]
Exception in thread "main" java.lang.OutOfMemoryError
make[3]: *** [users_guide.ps] Error 1
make[3]: *** Deleting file `users_guide.ps'
make[2]: *** [all] Error 1
make[1]: *** [all] Error 1
make[1]: Leaving directory `/var/tmp/portage/ghc-6.4/work/ghc-6.4/ghc'
make: *** [build] Error 1

!!! ERROR: dev-lang/ghc-6.4 failed.
!!! Function src_compile, Line 158, Exitcode 2
Comment 4 Andres Loeh (RETIRED) gentoo-dev 2005-03-14 10:41:29 UTC
This is a different problem than originally described in this bug.
Java claiming about an OutOfMemoryError seems like a problem on the fop side.

I would still be interested in getting more information about the original
problem, which I cannot reproduce until now.

ks
Comment 5 Dario Lopez-Kästen 2005-09-15 03:25:18 UTC
Created attachment 68493 [details]
Error mesg from when doing emerge -a ghc

This is the last lines of the output from the command:

emerge -a ghc.

I had no previous install of ghc, and I wanted to have a ghc compiled from
source.
Comment 6 Dario Lopez-Kästen 2005-09-15 03:26:45 UTC
Created attachment 68494 [details]
results of command: emerge --info

additional info for attachment 68493 [details]: Error mesg from when doing emerge -a ghc

Doing a subsequent emerge -a ghc-bin worked allright.
Comment 7 Andres Loeh (RETIRED) gentoo-dev 2005-09-15 03:50:11 UTC
Yes, we have finally identified this problem a while ago, and coincidentally,
I've just committed a "fix" to CVS a moment ago.

There is a problem in portage's dependency resolution. As a result, it sometimes
wants to merge the three packages

haddock
ghc-bin
ghc

in this order. But haddock requires at least ghc-bin! You've done the right
thing, emerging ghc-bin explicitly. You should also re-merge haddock, to get
it installed correctly. Then you can bootstrap ghc if you want.

The "fix" I've committed just explains that you have to do this. Portage
is currently being rewritten in large parts, the next major release (don't
know when) will hopefully handle this correctly.

Thanks for the report.

Cheers,
  ks

PS. I'm marking this as "FIXED" for now, because I've done all that I can
do at the moment.