Comment author: zozozo

I forgot to add the 'eval $(opam config env)' to the steps to reproduce.

Comment author: @mshinwell

I will look at this

Comment author: @mshinwell

The problem appears to be that there are references to the same module (e.g. Log) both through the Msat pack (written as "Msat.Log") and not through the pack (written as just "Log").

We are going to clarify what the compiler's behaviour should be in this situation.

In the meantime you should be able to fix your code by either:

• including more modules in the pack that should perhaps be there anyway, for example Expr and Type (you will need to change the references e.g. in Expr to remove any "Msat." prefixes); or

• for the modules outside the pack (e.g. Expr) ensure that all references to modules included in the pack (e.g. Log) are written with the pack-qualified name (e.g. Msat.Log) rather than just (e.g.) "Log".

Comment author: zozozo

Thanks a lot ! I thought something like this might be happening, and had already fixed that in the following commit.

Maybe that situation could deserve a proper compiler error, with the location of the two references that causes the problem ?

Comment author: @mshinwell

This probably does require a proper error.

Comment author: @mshinwell

The error is covered in #7086

Comment author: @mshinwell

As Alain points out, #7086 is actually slightly different.

Comment author: @mshinwell

This is a duplicate of #3922, though.