James

> log4cxx/1.2.0: WARN: No cppstd compatibility defined for compiler "intel-cc" > settings expected: compiler=intel-cc, compiler.cppstd=gnu14, compiler.mode=dpcpp, compiler.version=2024.0 existing: compiler=gcc, compiler.cppstd=17, compiler.mode=None, compiler.version=11 dependencies expected: apr-util/1.6.Z, apr/1.7.Z, expat/2.6.Z, libiconv/1.17.Z existing: None,...

> existing: None, None, None, None It seems your existing ``log4cxx`` has something broken regarding the dependencies information. Not sure if you created the package with some special ``package_id_mode`` that...

> But why I'm able to download the package if I use my default profile which is compiler=gcc ? I have no problem with conan graph explain with my profile...

I am very confused about one thing: > recipe_hash: d480fe6dc12514162961f183351176394d75a5fb This ``recipe_hash`` is quite a legacy Conan 1.X thing. It shouldn't be there. Also your settings are: ``` settings os:...

> I tried to find it, but there is no conaninfo.txt in my package All package binaries must have a ``conaninfo.txt`` inside them, otherwise they are broken

Some notes: - Dependency graph that have converging requires to the same package both with visible=True and visible=False are ill-formed, and they will be diagnosed as such with a warning...

> I tried your branch and when locking my project, I get hundreds of messages like these: The good news is that apparently it didn't raise a conflict, so it...

> True, but we fixed a lot of such conflicts in the past few months by updating all our packages to the latest versions of all dependencies. It was quite...

I have reduced the warnings strictly to the direct dependencies. Could you please try again @DoDoENT and let us know? Thanks!

> Still hundreds of warnings. Thanks for the feedback. I have further reduced the number of warnings, caching them to avoid duplicates, could you please try again? If you can...