Bugs item #1083852, was opened at 2004-12-12 13:45 Message generated for change (Comment added) made by as49 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=108032&aid=1083852&group_id=8032
Category: Driver Group: 6.2.2 Status: Open >Resolution: Invalid Priority: 5 Submitted By: Axel Simon (as49) Assigned to: Nobody/Anonymous (nobody) Summary: ghc-pkg ignores library dirs Initial Comment: Hi, I'm installing several packages in sequence. The first package specified /usr/local/lib in the library_dirs field. The .o file is built correctly. The next package depends on the first package. To reduce the size of the command line of any build with the second package, I filter out all flags that are already in the first package. Doing this, the .o file of the second package cannot be built since ghc-pkg does not include the library path of the first package when it searches for the .a file. I think that adding only those flags that are needed in addition to some other dependent package is a reasonable thing to do, so I would like to see ghc-pkg search on the library paths of all dependant packages. Thanks, Axel. ---------------------------------------------------------------------- >Comment By: Axel Simon (as49) Date: 2004-12-13 13:36 Message: Logged In: YES user_id=489164 Yes, that is correct. What is weird is that letting ghc-pkg build an .o file breaks installation. My setup in which the second package uses the include paths of the package it depends upon seems to be sensible and it would work if it weren't for the .o file creation. I guess I just wanted to air that. I would be really good to see the .o file go and ghci use the .a file. It breaks horribly on Solaris when ghc-pkg uses the Solaris linker which doesn't understand --whole-archive . I'll close the bug then. Axel. ---------------------------------------------------------------------- Comment By: Simon Marlow (simonmar) Date: 2004-12-13 12:52 Message: Logged In: YES user_id=48280 Just to check I've understood: you have a package that includes a library foo.a, but the directory containing foo.a does not appear in the library_dirs field of the package? I'd say you really ought to include the directory in library_dirs. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=108032&aid=1083852&group_id=8032 _______________________________________________ Glasgow-haskell-bugs mailing list [EMAIL PROTECTED] http://www.haskell.org/mailman/listinfo/glasgow-haskell-bugs
