darcs-1.0.5 doesn't compile, stating it cannot find ghc. after installing ghc manually, it works. probably ghc has just to be added as a dependency. Reproducible: Always Steps to Reproduce: root@box / # emerge -pv darcs These are the packages that would be merged, in order: Calculating dependencies... done! [ebuild N ] dev-util/darcs-1.0.5 USE="-doc" 0 kB Total: 1 package (1 new), Size of downloads: 0 kB root@box /h # emerge darcs Calculating dependencies... done! >>> Emerging (1 of 1) dev-util/darcs-1.0.5 to / * darcs-1.0.5.tar.gz MD5 ;-) ... [ ok ] * darcs-1.0.5.tar.gz RMD160 ;-) ... [ ok ] * darcs-1.0.5.tar.gz SHA1 ;-) ... [ ok ] * darcs-1.0.5.tar.gz SHA256 ;-) ... [ ok ] * darcs-1.0.5.tar.gz size ;-) ... [ ok ] * checking ebuild checksums ;-) ... [ ok ] * checking auxfile checksums ;-) ... [ ok ] * checking miscfile checksums ;-) ... [ ok ] * checking darcs-1.0.5.tar.gz ;-) ... [ ok ] >>> Unpacking source... >>> Unpacking darcs-1.0.5.tar.gz to /var/tmp/portage/dev-util/darcs-1.0.5/work * Replacing obsolete head/tail with POSIX compliant ones * - fixed darcs-1.0.5/configure * - fixed darcs-1.0.5/configure.ac >>> Source unpacked. >>> Compiling source in /var/tmp/portage/dev-util/darcs-1.0.5/work/darcs-1.0.5 ... rm -f *.o *.hi unit diff darcs darcs_cgi rm -f Context.hs stringify rm -f darcs.tex darcs.dvi darcs.aux rm -f darcs_print.tex darcs_print.log darcs_print.aux darcs_print.toc rm -f darcs-createrepo preproc darcsman rm -rf tests/temp* darcs.log darcs.toc rm -f conftest* .depend.bak rm -f win32/*.o win32/*.hi rm -f win32/System/*.o win32/System/*.hi rm -f version.nsi rm -f list_authors make_changelog ./configure --prefix=/usr --host=i686-pc-linux-gnu --mandir=/usr/share/man --infodir=/usr/share/info --datadir=/usr/share --sysconfdir=/etc --localstatedir=/var/lib --build=i686-pc-linux-gnu checking for darcs... no checking the release state..... release checking for i686-pc-linux-gnu-gcc... i686-pc-linux-gnu-gcc checking for C compiler default output file name... a.out checking whether the C compiler works... yes checking whether we are cross compiling... no checking for suffix of executables... checking for suffix of object files... o checking whether we are using the GNU C compiler... yes checking whether i686-pc-linux-gnu-gcc accepts -g... yes checking for i686-pc-linux-gnu-gcc option to accept ANSI C... none needed checking how to run the C preprocessor... i686-pc-linux-gnu-gcc -E checking for a BSD-compatible install... /bin/install -c checking for ghc... no configure: error: Cannot find ghc in your path; please set the GHC environment variable!! !!! Please attach the following file when filing a report to bugs.gentoo.org: !!! /var/tmp/portage/dev-util/darcs-1.0.5/work/darcs-1.0.5/config.log !!! ERROR: dev-util/darcs-1.0.5 failed. Call stack: ebuild.sh, line 1614: Called dyn_compile ebuild.sh, line 971: Called qa_call 'src_compile' environment, line 3107: Called src_compile darcs-1.0.5.ebuild, line 57: Called econf ebuild.sh, line 577: Called die !!! econf failed !!! If you need support, post the topmost build error, and the call stack if relevant. !!! A complete build log is located at '/var/tmp/portage/dev-util/darcs-1.0.5/temp/build.log'.
(In reply to comment #0) > !!! Please attach the following file when filing a report to bugs.gentoo.org: > !!! /var/tmp/portage/dev-util/darcs-1.0.5/work/darcs-1.0.5/config.log Please do it.
Created attachment 114034 [details] config.log
config.log attached, as requested.
ghc *is* a dependency of darcs. So it's strange that portage wouldn't want to install it. Neither dev-lang/ghc nor dev-lang/ghc-bin are installed on your machine? Also, what's the portage version you're using? Cheers, ks
sys-apps/portage-2.1.2.2. seems that ghc-bin was indeed installed, jsut my environment didn't conatin it.
But this shouldn't happen. You can reproduce this problem, right? ghc-bin installs into /opt/ghc/bin, but it also adds a file into /etc/env.d that should make sure the ghc-bin is available in the search path. Even more, ghc-package.eclass explicitly adds /opt/ghc/bin to the search path. So there's still a bug to be found ... ks
Timo, can you still reproduce this one? If so, lets investigate further.
If the original reporter or anyone else gets back to us with more info then please reopen.
