Hello,
Recently I was trying to profile some code, and GHC complained that it could not find profiling versions of some 3rd party libraries I was using. According to the GHC manual:
5.2. Compiler options for profiling -prof: To make use of the profiling system all modules must be compiled and linked with the -prof option.
Cabal already supports profiling (from the cabal manual section 3.1.3):
--enable-library-profiling or -p
Request that an additional version of the library with profiling features enabled be built and installed (only for implementations that support profiling).
So, perhaps in addition to the libghc6-*-dev packages, we should be providing libghc6-*-prof packages by default? Or is there some trick that will let me profile my application even if I link against some non-profiling-enabled modules?
j.
"Jeremy Shaw" jeremy.shaw@linspireinc.com writes:
Hello,
Recently I was trying to profile some code, and GHC complained that it could not find profiling versions of some 3rd party libraries I was using. According to the GHC manual:
5.2. Compiler options for profiling -prof: To make use of the profiling system all modules must be compiled and linked with the -prof option.
Cabal already supports profiling (from the cabal manual section 3.1.3):
--enable-library-profiling or -p
Request that an additional version of the library with profiling features enabled be built and installed (only for implementations that support profiling).
So, perhaps in addition to the libghc6-*-dev packages, we should be providing libghc6-*-prof packages by default? Or is there some trick that will let me profile my application even if I link against some non-profiling-enabled modules?
I think that providing -prof libraries would be very good. Ian, got an opinion?
peace,
isaac
Op wo, 31-05-2006 te 10:29 -0700, schreef Isaac Jones:
So, perhaps in addition to the libghc6-*-dev packages, we should be providing libghc6-*-prof packages by default? Or is there some trick that will let me profile my application even if I link against some non-profiling-enabled modules?
I think that providing -prof libraries would be very good. Ian, got an opinion?
Yes providing profiled enabled library as well would be quite usefull. In my HaXml package[1] I already build a normal and a profiled version of the HaXml library.
I don't use Cabal though, but most package do and use dh_haskell and as such it would be nice if dh_haskell would support this as well. It should not be to hard to add this to dh_haskell I think.
Greetings Arjan
On Wed, May 31, 2006 at 10:29:10AM -0700, Isaac Jones wrote:
"Jeremy Shaw" jeremy.shaw@linspireinc.com writes:
So, perhaps in addition to the libghc6-*-dev packages, we should be providing libghc6-*-prof packages by default?
I think that providing -prof libraries would be very good. Ian, got an opinion?
Absolutely agreed.
Thanks Ian
debian-haskell@lists.urchin.earth.li