[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: [Uhc-developers] Avoiding uuagc-bootstrap



Hi,

thanks for the instructions, everything back to normal now, it seems.

Greetings,
Joachim

Am Montag, den 08.04.2013, 09:38 +0200 schrieb Jeroen Bransen:
> Your uuagc_0.9.42.2-2 installation is broken, and since you are using
> GHC 7.6.2 I suspect that it is due to a bug in GHC, see [1]. As a
> result of that bug uulib (the parsing library used by GHC) was broken
> when compiled with GHC 7.6.2. I worked around this bug in uulib-0.9.15
> (and the workaround is also backwards compatible btw, I just added a
> type annotation) so updating uulib to that version and then
> recompiling uuagc should solve your problem.
> 
> Regards,
> Jeroen Bransen
> 
> [1] http://hackage.haskell.org/trac/ghc/ticket/7748
> 
> 
> > Hi,
> > 
> > I still get the same error:
> > 
> > if test ! -e Setup.lhs -a ! -e Setup.hs; then echo "No setup script found!"; exit 1; fi
> > for setup in Setup.lhs Setup.hs; do if test -e $setup; then ghc -DEXTERNAL_UUAGC --make $setup -o debian/hlibrary.setup; exit 0; fi; done
> > [1 of 1] Compiling Main             ( Setup.hs, Setup.o )
> > Linking debian/hlibrary.setup ...
> > debian/hlibrary.setup configure --ghc -v2 \
> > 		--prefix=/usr --libdir=/usr/lib/haskell-packages/ghc/lib \
> > 		--builddir=dist-ghc \
> > 		--haddockdir=/usr/lib/ghc-doc/haddock/uuagc-0.9.42.3/ \
> > 		--htmldir=/usr/share/doc/libghc-uuagc-doc/html/   \
> > 		   
> > Configuring uuagc-0.9.42.3...
> > Flags chosen: bootstrap_external=True
> > Dependency array >=0.3.0.1: using array-0.4.0.1
> > Dependency base ==4.*: using base-4.6.0.1
> > Dependency containers >=0.3: using containers-0.5.0.0
> > Dependency directory >=1.0.1.1: using directory-1.2.0.1
> > Dependency filepath >=1.1.0.4: using filepath-1.3.0.1
> > Dependency ghc-prim >=0.2.0.0: using ghc-prim-0.3.0.0
> > Dependency haskell-src-exts >=1.11.1: using haskell-src-exts-1.13.5
> > Dependency mtl >=1.1.1.1: using mtl-2.1.2
> > Dependency uuagc ==0.9.42.3: using uuagc-0.9.42.3
> > Dependency uuagc-cabal >=1.0.2.0: using uuagc-cabal-1.0.4.0
> > Dependency uulib >=0.9.14: using uulib-0.9.14
> > Using Cabal-1.16.0 compiled by ghc-7.6
> > Using compiler: ghc-7.6.2
> > Using install prefix: /usr
> > Binaries installed in: /usr/bin
> > Libraries installed in:
> > /usr/lib/haskell-packages/ghc/lib/uuagc-0.9.42.3/ghc-7.6.2
> > Private binaries installed in: /usr/libexec
> > Data files installed in: /usr/share/uuagc-0.9.42.3
> > Documentation installed in: /usr/share/doc/uuagc-0.9.42.3
> > No alex found
> > Using ar found on system at: /usr/bin/ar
> > No c2hs found
> > No cpphs found
> > No ffihugs found
> > Using gcc version 4.7 found on system at: /usr/bin/gcc
> > Using ghc version 7.6.2 found on system at: /usr/bin/ghc
> > Using ghc-pkg version 7.6.2 found on system at: /usr/bin/ghc-pkg
> > No greencard found
> > Using haddock version 2.13.2 found on system at: /usr/bin/haddock
> > No happy found
> > No hmake found
> > Using hpc version 0.6 found on system at: /usr/bin/hpc
> > Using hsc2hs version 0.67 found on system at: /usr/bin/hsc2hs
> > Using hscolour version 1.19 found on system at: /usr/bin/HsColour
> > No hugs found
> > No jhc found
> > Using ld found on system at: /usr/bin/ld
> > No lhc found
> > No lhc-pkg found
> > No nhc98 found
> > No pkg-config found
> > Using ranlib found on system at: /usr/bin/ranlib
> > Using strip found on system at: /usr/bin/strip
> > Using tar found on system at: /bin/tar
> > No uhc found
> > debian/hlibrary.setup build --builddir=dist-ghc
> > hlibrary.setup: <<loop>>
> > 
> > 
> > The installed version of uuagc is uuagc_0.9.42.2-2, and GHC is 7.6.2.
> > 
> > Any ideas?
> > 
> > Greetings,
> > Joachim
> > 
> > Am Mittwoch, den 03.04.2013, 17:39 +0200 schrieb Jeroen Bransen:
> >> Dear Joachim,
> >> 
> >> The issue below has been solved and I believe that UUAGC 0.9.42.3, which has just been uploaded to Hackage, can be build with "cabal install" from the included generated code, and can be build from AG sources with some older uuagc executable on the system with 'cabal install uuagc --ghc-options="-DEXTERNAL_UUAGC"'.
> >> 
> >> Regards,
> >> Jeroen
> >> 
> >> 
> >>> Hi Joachim,
> >>> 
> >>>>>> In version 0.9.42.1, which is now on Hackage, both the AG sources and
> >>>>>> generated Haskell sources are included. With a standard 'cabal
> >>>>>> install' the generated Haskell sources are used and UUAGC is build as
> >>>>>> any simple Haskell library. However, to build from sources you can now
> >>>>>> do 'cabal install uuagc --ghc-options="-DEXTERNAL_UUAGC"' which of
> >>>>>> course needs a "uuagc" executable to be available. This will ignore
> >>>>>> the generated sources and build everything from AG source.
> >>>>> 
> >>>>> thanks! New Debian package using this infrastructure uploaded. The
> >>>>> setting of configuration variables via CPP flags passed when building
> >>>>> Setup is a bit unusual, but not a problem.
> >>>> 
> >>>> I tried to package 0.9.42.2 using -DEXTERNAL_UUAGC, but failed:
> >>>> debian/hlibrary.setup build --builddir=dist-ghc
> >>>> hlibrary.setup: <<loop>>
> >>>> 
> >>>> [..]
> >>>> 
> >>>> Can you reproduce the problem? Would it be possible to fix it?
> >>> 
> >>> Yes, and unfortunately I realized this only after I uploaded the new
> >>> version to Hackage. Version 0.9.42.2 can only be bootstrapped with itself,
> >>> i.e. to build from source you should first install 0.9.42.2 without the
> >>> -DEXTERNAL_UUAGC flag such that it uses the included generated sources,
> >>> and then another time with that flag. Then it works fine, but if the uuagc
> >>> is preprocessed with any version < 0.9.42.2 it gives a <<loop>>.
> >>> 
> >>> It is still on my todo list to figure out what exactly the problem is. It
> >>> is related to the fact that I added the "kennedywarren" flag in the
> >>> uuagc_options file, for which older versions generate some extra strictness
> >>> annotations which create the loop. I do however think that it should be
> >>> possible to change the code again such that it can be preprocessed with
> >>> older versions too. So, for now the fix would probably just be to skip this
> >>> version and hope that I can figure out the problem soon.
> >>> 
> >>> Otherwise, the "self bootstrap" by building twice can work, but that's of
> >>> course not very nice.
> >>> 
> >>> Regards,
> >>> Jeroen 
> >> 
> >> 
> > 
> > -- 
> > Joachim "nomeata" Breitner
> > Debian Developer
> >  nomeata@debian.org | ICQ# 74513189 | GPG-Keyid: 4743206C
> >  JID: nomeata@joachim-breitner.de | http://people.debian.org/~nomeata
> > 
> 
> 

-- 
Joachim "nomeata" Breitner
Debian Developer
  nomeata@debian.org | ICQ# 74513189 | GPG-Keyid: 4743206C
  JID: nomeata@joachim-breitner.de | http://people.debian.org/~nomeata

Attachment: signature.asc
Description: This is a digitally signed message part


Reply to: