[bug] Package not found when using Compiler Any

Hi,

I’ve recently been setting up Conan with our Azure DevOps based build system. Everything has gone through (relatively) smoothly on Windows, but I’ve hit a road block on our Linux builds.

On Linux we don’t generally care whether a library has been built with GCC or Clang, as long as they’re using the same runtime library (libc++ Vs libstdc++). I couldn’t figure out how to set this up in the settings for the consumer, so I decided to work from the other end and remove [compiler] from the conanfile settings when building the package (we have full control over all build processes so at this stage it seemed like the easiest option):

settings = "os", "build_type", "arch"

So now on our JFrog server I have a package uploaded with the following properties:

However, Conan is unable to resolve this when attempting to fetch the package:

Configuration:
[settings]
arch=x86_64
arch_build=x86_64
build_type=Release
compiler=clang
compiler.libcxx=libstdc++11
compiler.version=9
os=Linux
os_build=Linux
[options]
[build_requires]
[env]

libjpeg/9.3@3dv/stable: Not found in local cache, looking in remotes...
libjpeg/9.3@3dv/stable: Trying with 'CogsDev'...
Downloading conanmanifest.txt
Downloading conanfile.py
libjpeg/9.3@3dv/stable: Downloaded recipe revision d6eb47ebfa8b1fc8fd5aa96ec4744893
Installing package: libjpeg/9.3@3dv/stable
Requirements
    libjpeg/9.3@3dv/stable from 'CogsDev' - Downloaded
Packages
    libjpeg/9.3@3dv/stable:24647d9fe8ec489125dfbae4b3ebefaf7581674c - Missing

Installing (downloading, building) binaries...

ERROR: Missing binary: libjpeg/9.3@3dv/stable:24647d9fe8ec489125dfbae4b3ebefaf7581674c
libjpeg/9.3@3dv/stable: WARN: Can't find a 'libjpeg/9.3@3dv/stable' package for the specified settings, options and dependencies:
- Settings: arch=x86_64, build_type=Release, os=Linux
- Options: 
- Dependencies: 
- Requirements: 
- Package ID: 24647d9fe8ec489125dfbae4b3ebefaf7581674c

ERROR: Missing prebuilt package for 'libjpeg/9.3@3dv/stable'

Am I missing something blindingly obvious here?

[memsharded]

Yeah, I realise I’m not going to change anybody’s mind here. But that never stopped me from having a good old grumble in the past. 😃

We change our minds often, but in many cases too, we also have a lot of scars of having been there many times in the past, tried different things, struggled, going back and forth… But even in the case we would not change our mind, the feedback is very welcomed, we really need to hear that too, so please keep coming those good old grumbles! 😃 😃 😃

Anyway, back to the problem at hand… I finally had time to revisit this, and can confirm setting up .gitattributes to force conanfile.py to always use LF does indeed fix the issue.

Great to know, happy that it is solved.

At least, it’s fixed one of the issues. I suspect the remaining problems, though, are all my own doing. 😃

Ok, then I think we can close this issue at this moment, but please let us know if you have any further questions or issues. Thanks!

[crazydef]

Yeah, I realise I’m not going to change anybody’s mind here. But that never stopped me from having a good old grumble in the past. 😃

Anyway, back to the problem at hand… I finally had time to revisit this, and can confirm setting up .gitattributes to force conanfile.py to always use LF does indeed fix the issue.

At least, it’s fixed one of the issues. I suspect the remaining problems, though, are all my own doing. 😃