Home/ Questions/Q 6557253
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-25T13:03:01+00:00

The error I get is like this: [DCC Fatal Error] myunit3.pas(244): E2411 Unit XBAT

  • 0

The error I get is like this:

[DCC Fatal Error] myunit3.pas(244): E2411 Unit XBAT in package B_Dsgn refers to unit QBEE which is not found in any package. Packaged units must refer only to packaged units

I need to know what this error I am encountering really means, and if possible how to troubleshoot and solve such problems, especially when the facts stated in the error message are not correct (the units are in fact referring to other units in other valid packages).

Such problems involve package dependencies. I am having an interesting problem with a series of three designtime and three runtime packages related like this:

enter image description here

What is most odd about it is that each time I clean and rebuild, I get a different unit name in the error. (Shown above as Unit XBAT refers to unit QBEE).

The other odd thing is that it’s referring to units that are in a top level dependency, and are part of a package that was already built.

Steps;

  1. Compile A, it works.
  2. Compile A_Dsgn, it works.
  3. Compile B, it Works.
  4. Compile B_Dsgn, it works.
  5. Compile C, and it fails with this E2411 error.

Since I doubt anybody can tell me how to fix this exactly, I am looking for the steps to troubleshoot a complex dependency problem in a package. The literal meaning of the above error suggests for example, that I should have a corresponding message about an implicit linked unit, which I do not have. I have added all implicitly used units to the base packages A, and B, so that no implicit unit warnings are made.

My next idea was to separate the DCU output folders for each package, to prevent the DCU outputs from one from confusing the compiler. Now I can not even build the packages.

Update I tried playing with the Explicit Rebuild and Rebuild as Needed options. I have found that this error is related to having ‘Rebuild as Needed’ turned on. When it is turned off, the packages fail with other errors which are more to the point. I find it odd that the compiler emits weird errors that can be disabled by turning off Rebuild as needed. Any ideas what is going on?

Update 2 The basic underlying problem is not solved by turning on or off explicit rebuild. Instead of getting this error, I get annoying runtime/designtime package problems, which result in a set of packages, that can not be loaded at the same time. (Can not load package foo because it contains unit bar which is also in package bat. Do you want to attempt to load this package the next time a project is loaded?).

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    I suspect it is an obscure compiler bug.

    The project I experienced it in had at least 4 levels of dependent runtime packages:

    PackageA <- PackageB <- PackageC <- PackageD

    E2411 Unit ‘%s’ in package PackageD refers to unit ‘%s’ which is not
    found in any package. Packaged units must refer only to packaged units.

    The only solution I found that worked was to make packages A, B and C never-build (i.e. Explicit Build) packages and use Project Dependencies to enforce build order instead. I had to make all three never-build or I would get

    E2220 Never-build package ‘%s’ requires always-build package ‘%s’

    I know its probably not the answer you were looking for but there it is.

    Btw, this happened to me in Delphi 2009.

    • 0