I can reproduce the problem on my system with GHC-7.0.3. The flag old-base is meant for base libraries before 3.0.3.1 which didn't export a Control.Category module. It looks like I accidentally inverted the logic of the flag. What is weird is that is still builds okay on my system. I would expect that, given the inverted flag logic, Control.Category.Unicode would be missing from the installed package's exposed module list.
I fixed the logic of the flag and the bug appears to be gone. I uploaded the fixed version 0.2.1.3. Thanks for the bug report! On 31 March 2011 00:05, John Obbele <john.obb...@gmail.com> wrote: > On Wed, Mar 30, 2011 at 10:37:47PM +0200, John Obbele wrote: >> I'm having a problem in GHCi when loading modules relying on the >> base-unicode-symbols package. My prompt gives me the following >> message: >> >> >> ghci $ >> Loading package base-unicode-symbols-0.2.1.2 ... linking ... <interactive>: >> /home/john/.cabal/lib/base-unicode-symbols-0.2.1.2/ghc-7.0.2/HSbase-unicode-symbols-0.2.1.2.o: >> unknown symbol >> `__stginit_basezmunicodezmsymbolszm0zi2zi1zi2_ControlziCategoryziUnicode_' >> ghc: unable to load package `base-unicode-symbols-0.2.1.2' > > > Oki, so I'm answering to myself: the base-unicode-symbols cabal > file introduces a quirk concerning 'base' version which hides the > symbols in Control.Category.Unicode. > >>> base-unicode-symbols.cabal -- line 42-46 > if !flag(old-base) > build-depends: base >= 3.0 && < 4.4 > else > build-depends: base >= 3.0.3.1 && < 4.4 > exposed-modules: Control.Category.Unicode > > I should contact the maintainer about this … _______________________________________________ Haskell-Cafe mailing list Haskell-Cafe@haskell.org http://www.haskell.org/mailman/listinfo/haskell-cafe