Re: update preview: lang/ghc
This looks like you've something left over from a previous build. Please run `make clean' and then rerun the build. (And better wait a little bit, as I'm going to commit some change in a few minutes including a pkgname bump for ghc). ok, my fault I re-ran make to see the error msg again but cleaned before the actual make - I am not that clueless. Anyway the problem was still there with 1.31, I fixed it now by removing the dependency on ghc-paths from haddock.cabal in ghc-6.12.2/utils/haddock (see patch). The compilation succeeds then, ghc seems to work on the programs I tested (very small ones), so maybe ghc-paths is not needed at all for compilation. I made a diff file that does the removal by diff -u file~ file in the pobj/ghc directory. I am sure that is not the way to produce a useable patch. What's the correct command here? Thanks for your efforts and time regards Matthias removeGHC-pathsDeps.diff Description: Binary data
Re: update preview: lang/ghc
On Mon, Apr 26, 2010 at 08:01:39AM +0200, Matthias Guedemann wrote: This looks like you've something left over from a previous build. Please run `make clean' and then rerun the build. (And better wait a little bit, as I'm going to commit some change in a few minutes including a pkgname bump for ghc). ok, my fault I re-ran make to see the error msg again but cleaned before the actual make - I am not that clueless. Anyway the problem was still there with 1.31, I fixed it now by removing the dependency on ghc-paths from haddock.cabal in ghc-6.12.2/utils/haddock (see patch). But this shouldn't be necessary. lang/ghc BUILD_DEPENDS on devel/haddock,no_deps:patch, which means that it gets the haddock sources from devel/haddock including the patch that port has, which in turn disables the dependency on ghc-paths (if built internally within the ghc tree). It may be that I've fucked something in the post-extrac target of lang/ghc. Can you try the following cd /usr/ports/lang/ghc make clean make extract extract.log 21 and then send me the extract.log? I made a diff file that does the removal by diff -u file~ file in the pobj/ghc directory. I am sure that is not the way to produce a useable patch. What's the correct command here? See above; haddock *should* already contain an appropriate patch. Ciao, Kili
Re: update preview: lang/ghc
But this shouldn't be necessary. lang/ghc BUILD_DEPENDS on devel/haddock,no_deps:patch, which means that it gets the haddock sources from devel/haddock including the patch that port has, which in turn disables the dependency on ghc-paths (if built internally within the ghc tree). the ghc-paths dependency for the haddock *executable* is disabled if in ghc-tree, but there is also a dependency for the library. If I am not mistaken this in *not* there after extraction of the ghc tar.gz, only after patching ghc-6.12.2 / moving devel/haddock there. What I did to make it compile was simply to remove the deps after the patches where applied. cd /usr/ports/lang/ghc make clean make extract extract.log 21 and then send me the extract.log? find it attached btw. I also had segfaults, but deleted the core dump before I read your thread. As I'm building on an Atom netbook where the build takes ages, I hope you find enough other people who can send you the backtracks regards Matthias extract.log Description: Binary data
Re: update preview: lang/ghc
On Mon, Apr 26, 2010 at 08:56:36PM +0200, Matthias Guedemann wrote: But this shouldn't be necessary. lang/ghc BUILD_DEPENDS on devel/haddock,no_deps:patch, which means that it gets the haddock sources from devel/haddock including the patch that port has, which in turn disables the dependency on ghc-paths (if built internally within the ghc tree). the ghc-paths dependency for the haddock *executable* is disabled if in ghc-tree, but there is also a dependency for the library. If I am not mistaken this in *not* there after extraction of the ghc tar.gz, only after patching ghc-6.12.2 / moving devel/haddock there. What I did to make it compile was simply to remove the deps after the patches where applied. Well, and this is where something's going wrong (and I really don't understand why). The diff you sent for haddock.cabal (within WRKSRCDIR, i.e. the extracted ghc directory) had two hunks. The first hunk removed ghc-paths from the haddock program: @@ -81,8 +81,6 @@ if flag(in-ghc-tree) cpp-options: -DIN_GHC_TREE extensions: ForeignFunctionInterface - else -build-depends: ghc-paths if flag(test) cpp-options: -DTEST That shouldn't be necessary, as the `in-ghc-tree' flag is set when haddock is configured internally within the ghc build. The second hunk of your diff did address the library part of haddock: @@ -132,8 +130,7 @@ containers, array, Cabal = 1.5, -ghc = 6.12 6.14, -ghc-paths +ghc = 6.12 6.14 That's of course (mostly) correct, but now look at /usr/ports/devel/haddock/patches/patch-haddock_cabal.[1] It already contains a diff similuar to that hunk (with the only difference that it doesn't remove the dependency on ghc-paths unconditionally but only if `in-ghc-tree' isn't set). For reference here's the haddock.cabal hunk that *should* be in your WRKSRC after running `make extract' in /usr/ports/lang/ghc: @@ -132,8 +132,10 @@ library containers, array, Cabal = 1.5, -ghc = 6.12 6.14, -ghc-paths +ghc = 6.12 6.14 + + if !flag(in-ghc-tree) +build-depends: ghc-paths if flag(test) cpp-options: -DTEST But it isn't, and I really don't understand the reason. cd /usr/ports/lang/ghc make clean make extract extract.log 21 and then send me the extract.log? find it attached Perfectly normal beast. Almost identically to what I get here. Now I'm even more confused. After `make extract', /usr/obj/pobj/ghc-6.12.2/ghc-6.12.2/utils/haddock/haddock.cabal should read like this: executable haddock ... if flag(in-ghc-tree) cpp-options: -DIN_GHC_TREE extensions: ForeignFunctionInterface else build-depends: ghc-paths ... library ... if !flag(in-ghc-tree) build-depends: ghc-paths ... btw. I also had segfaults, but deleted the core dump before I read your thread. As I'm building on an Atom netbook where the build takes ages, I hope you find enough other people who can send you the backtracks Yep, I got some reports already (and wait for a report from some kind tester who even got repeated segfaults on amd64). Building this thing on small and slow boxes is no fun at all -- I know, since I built the i386 bootstrapping bindist on a crap box with less than 300 MHz and only 128 MB of RAM ;-) Ciao, Kili [1] You have that patch, don't you? If not, you owe me about 15 bottles of gulden draak.
Re: update preview: lang/ghc
Hi Kili, thanks a lot for your work to port a current GHC. I'm trying to build it on i386 on 4.7-current (lang/ghc cvs rev 1.30), but get the following error: Configuring haddock-2.7.2... ghc-cabal: At least the following dependencies are missing: ghc-paths -any gmake[1]: *** [utils/haddock/dist/package-data.mk] Error 1 gmake: *** [all] Error 2 *** Error code 2 Stop in /usr/ports/lang/ghc (line 2253 of /usr/ports/infrastructure/mk/bsd.port.mk). What am I doing wrong? regards, Matthias
Re: update preview: lang/ghc
On Sun, Apr 25, 2010 at 12:26:18PM +0200, Matthias Guedemann wrote: thanks a lot for your work to port a current GHC. I'm trying to build it on i386 on 4.7-current (lang/ghc cvs rev 1.30), but get the following error: Configuring haddock-2.7.2... ghc-cabal: At least the following dependencies are missing: ghc-paths -any gmake[1]: *** [utils/haddock/dist/package-data.mk] Error 1 gmake: *** [all] Error 2 *** Error code 2 Stop in /usr/ports/lang/ghc (line 2253 of /usr/ports/infrastructure/mk/bsd.port.mk). What am I doing wrong? Are you trying to build it with FLAVOR=native_bootstrap? Please don't use this pseudo flavor for now (unless you really know what you're doing). If you're *not* using FLAVOR=native_bootstrap and it still fails, please send me another mail. Ciao, Kili
Re: update preview: lang/ghc
On Sun, Apr 25, 2010 at 02:52:44PM +0200, Matthias Guedemann wrote: Makefile:62: target `all' given more than once in the same rule. ===--- updating makefiles phase 0 gmake -r --no-print-directory -f ghc.mk phase=0 just-makefiles [...] This looks like you've something left over from a previous build. Please run `make clean' and then rerun the build. (And better wait a little bit, as I'm going to commit some change in a few minutes including a pkgname bump for ghc). Ciao, Kili
Re: update preview: lang/ghc
On Thu Apr 22, 2010 at 11:28:08PM +0200, Matthias Kilian wrote: Hi, On Thu, Apr 22, 2010 at 09:19:26PM +0200, Rafael Sadowski wrote: today I found some time to test and build ghc with your ghc.diff but this diff can't find some distfiles: === Checking files for ghc-6.6.1 This should have been 6.12.1.20100330, not 6.6.1. Something went wrong applying the patch, at least for ghc.port.mk. Anyway, ghc-6.12.2 has been finally released the other day, and I've all required updates in my tree and will them commit very soon (either now or tomorrow, depending on when earth should collapse). Ciao, Kili Hello Kili, I get this error with current ports tree: rm -f compiler/stage2/build/libHSghc-6.12.2_p.a.contents inplace/bin/mkdirhier compiler/stage2/doc/html/ghc/ inplace/bin/ghc-cabal haddock stage2 compiler --with-haddock=/usr/ports/pobj/ghc-6.12.2/ghc-6.12.2/inplace/bin/haddock --with-ghc=/usr/ports/pobj/ghc-6.12.2/ghc-6.12.2/inplace/bin/ghc-stage2 --haddock-option=--optghc=-DSTAGE=2 Running Haddock for ghc-6.12.2... Preprocessing library ghc-6.12.2... Warning: The documentation for the following packages are not installed. No links will be generated to these packages: ffi-1.0, rts-1.0 Warning: CmmExpr: foldRegsDefd is exported separately but will be documented under DefinerOfLocalRegs. Consider exporting it together with its parent(s) for code clarity. Warning: CmmExpr: foldRegsUsed is exported separately but will be documented under UserOfLocalRegs. Consider exporting it together with its parent(s) for code clarity. Warning: CmmExpr: foldSlotsDefd is exported separately but will be documented under DefinerOfSlots. Consider exporting it together with its parent(s) for code clarity. Warning: CmmExpr: foldSlotsUsed is exported separately but will be documented under UserOfSlots. Consider exporting it together with its parent(s) for code clarity. Warning: ZipCfg: succs is exported separately but will be documented under HavingSuccessors. Consider exporting it together with its parent(s) for code clarity. Warning: ZipCfg: fold_succs is exported separately but will be documented under HavingSuccessors. Consider exporting it together with its parent(s) for code clarity. Warning: ZipCfg: mkBranchNode is exported separately but will be documented under LastNode. Consider exporting it together with its parent(s) for code clarity. Warning: ZipCfg: isBranchNode is exported separately but will be documented under LastNode. Consider exporting it together with its parent(s) for code clarity. Warning: ZipCfg: branchNodeTarget is exported separately but will be documented under LastNode. Consider exporting it together with its parent(s) for code clarity. Warning: OptimizationFuel: lastFuelPass is exported separately but will be documented under FuelUsingMonad. Consider exporting it together with its parent(s) for code clarity. Warning: OptimizationFuel: fuelExhausted is exported separately but will be documented under FuelUsingMonad. Consider exporting it together with its parent(s) for code clarity. Warning: OptimizationFuel: fuelRemaining is exported separately but will be documented under FuelUsingMonad. Consider exporting it together with its parent(s) for code clarity. Warning: OptimizationFuel: fuelDecrement is exported separately but will be documented under FuelUsingMonad. Consider exporting it together with its parent(s) for code clarity. Warning: OptimizationFuel: fuelDec1 is exported separately but will be documented under FuelUsingMonad. Consider exporting it together with its parent(s) for code clarity. Warning: DFMonad: markFactsUnchanged is exported separately but will be documented under DataflowAnalysis. Consider exporting it together with its parent(s) for code clarity. Warning: DFMonad: factsStatus is exported separately but will be documented under DataflowAnalysis. Consider exporting it together with its parent(s) for code clarity. Warning: DFMonad: getFact is exported separately but will be documented under DataflowAnalysis. Consider exporting it together with its parent(s) for code clarity. Warning: DFMonad: setFact is exported separately but will be documented under DataflowAnalysis. Consider exporting it together with its parent(s) for code clarity. Warning: DFMonad: getExitFact is exported separately but will be documented under DataflowAnalysis. Consider exporting it together with its parent(s) for code clarity. Warning: DFMonad: setExitFact is exported separately but will be documented under DataflowAnalysis. Consider exporting it together with its parent(s) for code clarity. Warning: DFMonad: forgetFact is exported separately but will be documented under DataflowAnalysis. Consider exporting it together with its parent(s) for code clarity. Warning: DFMonad: botFact is exported separately but will be documented under DataflowAnalysis. Consider exporting it together with its parent(s) for code clarity. Warning: DFMonad:
Re: update preview: lang/ghc
On Fri Apr 09, 2010 at 06:49:55PM +0200, Matthias Kilian wrote: Update to ghc-6.12.1.20100330 (which is ghc-6.12.2-rc1) for testing. For those who already tried the version I mentioned some days ago: there are some additional small changes to ghc.port.mk, so better use the new diff. This is a little bit large, so if you want to give it a test, feel free to fetch it from http://openbsd.dead-parrot.de/ghc.diff Notes: - Bootstrapping is done using precompiled binaries, since .hc bootstrapping still doesn't work. I really hate this. - libgmp is currently disabled, because I didn't yet hack the GHC build system to use the system libgmp instead of the patched one included in GHC. - The testsuite currently doesn't work, because there are some parts calling the test scripts via `/usr/bin/env python' instead of using the PYTHON environment variable. - The ghc package now includes haddock, obsoleting devel/haddock. This may change again in the future. - CLDouble has been removed from GHC some time ago, because it was an alias for double (AFAIK there's now support for long double in GHC). As this isn't a really big problem, it currently breaks c2hs, which I'll mark broken temporarily before committing the ghc update. I'll send around diffs for some additional ports that need to be updated and could need some testing (especially darcs and xmonad). You'll need a very current ports tree (as of: from today) to test those diffs. Ciao, Kili Hello Kili, today I found some time to test and build ghc with your ghc.diff but this diff can't find some distfiles: === Checking files for ghc-6.6.1 Fetch http://openbsd.dead-parrot.de/distfiles/ghc-6.6.20100318-amd64-unknown-openbsd.tar.bz2 ftp: Error retrieving file: 404 Not Found Fetch ftp://ftp.openbsd.org/pub/OpenBSD/distfiles/ghc-6.6.1/ghc-6.6.20100318-amd64-unknown-openbsd.tar.bz2 ghc-6.6.20100318-amd64-unknown-openbsd.tar.bz2: No such file or directory. Fetch ftp://ftp.usa.openbsd.org/pub/OpenBSD/distfiles/ghc-6.6.1/ghc-6.6.20100318-amd64-unknown-openbsd.tar.bz2 ghc-6.6.20100318-amd64-unknown-openbsd.tar.bz2: No such file or directory. `/usr/ports/distfiles/ghc-6.6.1/ghc-6.6.1-src.tar.bz2' is up to date. *** Error code 1 Stop in /usr/ports/mystuff/lang/ghc (line 2433 of /usr/ports/infrastructure/mk/bsd.port.mk). *** Error code 1 Stop in /usr/ports/mystuff/lang/ghc (line 1870 of /usr/ports/infrastructure/mk/bsd.port.mk). *** Error code 1 Stop in /usr/ports/mystuff/lang/ghc (line 2081 of /usr/ports/infrastructure/mk/bsd.port.mk). Is there any new diff with current distfiles? Ciao, Rafael Sadowski -- http://www.sizeofvoid.org - raf...@sizeofvoid.org Jabber: z...@jabber.ccc.de GPG/PGP: 0x8790CC0B
Re: update preview: lang/ghc
Hi, On Thu, Apr 22, 2010 at 09:19:26PM +0200, Rafael Sadowski wrote: today I found some time to test and build ghc with your ghc.diff but this diff can't find some distfiles: === Checking files for ghc-6.6.1 This should have been 6.12.1.20100330, not 6.6.1. Something went wrong applying the patch, at least for ghc.port.mk. Anyway, ghc-6.12.2 has been finally released the other day, and I've all required updates in my tree and will them commit very soon (either now or tomorrow, depending on when earth should collapse). Ciao, Kili
Re: update preview: lang/ghc
Thanks Kili, nice work. I'll test it with xmonad. Now we need a current xmonad port ;) Ciao, Rafael -- http://www.sizeofvoid.org - raf...@sizeofvoid.org Jabber: z...@jabber.ccc.de GPG/PGP: 0x8790CC0B
