Re: Bug#599093: dh_ocaml: warns on not resolving dependencies on modules contained in the application
On 04-10-2010, Ralf Treinen <Ralf.Treinen@pps.jussieu.fr> wrote:
> On Mon, Oct 04, 2010 at 08:32:21PM +0200, Mehdi Dogguy wrote:
>> severity 599093 wishlist
>> tags 599093 + moreinfo
>> thanks
>>
>> On 10/04/2010 05:41 PM, Ralf Treinen wrote:
>> > Package: dh-ocaml Version: 0.9.6 Severity: normal
>> >
>> > dh_ocaml spits out a list of warnings concerning modules that are in
>> > fact defined in the application program itself, which is annoying.
>> > Example bibtex2html (which is compiled to bytecode, if that
>> > matters):
>> >
>>
>> I don't know what's the purpose of this bug and how you want us to deal
>> with it. So, I'm adding appropriate tags and reducing the severity.
>>
>> Note that those warnings are important to be sure that all external
>> modules are resolved.
>
> They are not external. They are internal to the program.
>
When implementing this warning, we don't know how to be sure that we
don't miss a dependency.
Ralf, do you know how to make the difference between internal/external?
Can we trust that every unresolved symbols are externals?
Regards,
Sylvain Le Gall
Reply to: