Hi, Yes, my point was indeed about the second compilation stage : once you have build the libs (comlib, the ihc tool and hdirect), you have to install them (com and hdirect) as packages in order to rebuild the ihc tool with the support for type libraries. At this point, the makefile-based build process fails, and I did not succeed in building the ihc tool with the support for typelibs without the packages because of my lack of knowledge with Cabal. Note that Sigbjorn Finne also kindly answered my post, so I will have look at the cvs version of hdirect. Sincerely yours, Samuel ----- Message d'origine ---- De : Marc Weber <marco-oweber@gmx.de> À : glasgow-haskell-users@haskell.org Envoyé le : Jeudi, 11 Janvier 2007, 13h44mn 35s Objet : Re: HDirect and GHC-6.6 Hi Samuel. I know. If you want to use hdirect with com support you need some kind of 2 stage build. I've tried to compile it some time ago and I failed (lack of knowledge and understanding haskell at that time).. So you did succeed? similar to ghc its using a 2 stage build. I will post a link to this message on cabal-devel@haskell.org avoiding cross-posting, too So we have by now 4 packagers having problems with the current cabal system? wxwidgets, gtk2hs, hdirect and ghc itself? Greetings Marc _______________________________________________ Glasgow-haskell-users mailing list Glasgow-haskell-users@haskell.org http://www.haskell.org/mailman/listinfo/glasgow-haskell-users ___________________________________________________________________________ Nouveau : téléphonez moins cher avec Yahoo! Messenger ! Découvez les tarifs exceptionnels pour appeler la France et l'international. Téléchargez sur http://fr.messenger.yahoo.com