-
Notifications
You must be signed in to change notification settings - Fork 196
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update conan packages on our NREL conan Artifactory remote (for MSVC 2022 and mac M1 in particular) #4511
Comments
Same applies to bzip2, for m1 arm64 support. EDIT: bzip2 is fine, it's just that is depends on pcre I think.
|
Similar issue with libffi for M1 macs. |
Packages on our remote are also missing all MSVC 2022 binaries, forcing build on the host machine The b2 package doesn't build (it has to build since we do not have 2022 packages on the remote) correctly with MSVC 2022 either. Apparently that one needs the MSVC 2017 (vc142) to build Workaround for now Basically force download it from conancenter instead of NREL's.
|
boost/1.73.0#4129a76c9b83c300fc103e36d1908792 won't work with MSVC 2022 either. Trying boost/1.73.0#9c4e07063572e776be60507c405b6754 from conancenter.io now... This doesn't have a MSVC 2022 package prebuilt either. I think most (if not all) recipes on conancenter don't have a MSVC 2022 package yet Maybe now would be a good time to bump to boost 1.78? Testing all versions from conancenter until one builds... conan remote add --force --insert 0 conancenter https://center.conan.io
rm ~/.conan/data/boost/
conan install boost/1.74.0@ -b missing # Fails as well
conan install boost/1.77.0@ -b missing # Fails as well
conan install boost/1.78.0@ -b missing # Works Seems like one needs boost 1.78 to have MSVC 2022 support. This confirms what I had found searching online, that's officially the first version of boost that natively supports MSVC 2022 (I have found someone who manually patched 1.77 to make it work, but that's not in conan) |
Ubuntu 20.04, clean cache. Hit the pcre issue with the NREL package. I delete pcre, put the conancenter remote first in line. It tries to build it, then fails with bzip2, so there is a problem with bzip2 indeed
This fixed it: /bin/rm -Rf ~/.conan/data/bzip2/
conan install pcre/8.41@ -b missing bzip2/1.0.8#c33162705fba3ed3998038dd7296d96d is what I got out it. Then I tried to compile conan-openstudio-ruby, hit an issue with gdbm1/18.1 from nrel. |
Thanks for the report @jmarrec If we can summarize any broken dependencies for the currently support platforms, I can upload these to our NREL conan site if you haven't done so already. If these are only for M1 and MSVC 2022, that's fine too but maybe we can change the title to indicate it's only for these two and we will work to update to support them. It'll take a little time to get MSVC 2022 up and running.
|
Issue overview
Updated packages so far:
pcre/8.41@#1afabf78c46a11bdd1755152e44f6e59
bzip2/1.0.8@#9c8b632000a52af5af3f045d3a6db12f
libffi/3.3@#cf635daae2a4fba32eeb982715df9305
gdbm/1.18.1@#ecdb7cd9673803e86868bf3c493c6fa7
b2/4.2.0@#a45bb9ebe2e994daaf83842b5b682eea
bison/3.7.1@#ad29e804e82c8b6d58765096676b5a5e
flex/2.6.4@#e4696e6333f2d486e7073de6a9559712 (due to mistmatch of m4)
gmp/6.2.0@#30cb7f744db8ac600167b05f747178c7 (due to mistmatch of m4)
termcap/1.3.1@#a66ace38d82bcfa0c0b39e9d4d0c71d6 (still chasing the mismatch of m4)
bison/3.5.3@#01aa231aae5441239d4fc697384d1811 : the mistmatch of m4 was coming from there actually...
libyaml/0.2.5@#edaee18262dfefa593ab650babefc80e
readline/8.0@#1d21941e543bef7a06551f5a56c8a87e
autoconf/2.69@# 5f19ba50aed010d74626c5281c65f135 (
'autoconf/2.69' requires 'm4/1.4.18' while 'bison/3.7.1' requires 'm4/1.4.19'
)swig/4.0.2@#187cec21277aafbeae11dcc3b936ce74: since this commit, swig has the correct swiglib so no need to do shenanigans with FindValue and passing SWIG_LIB env variable and co!
Need to replace the pcre recipes we have on our NREL conan Artifactory remote
The old ftp addresses where the pcre tar.gz were hosted are now dead. This is fixed in conan-center, but NREL's artifactory remote uses the old recipes that still point to it.
I got this issue on a clean mac M1 machine (any machine that already have the pcre 8.41 installed from conan will be ok). Edit: I just hit this today on Ubuntu 20.04 with a clean cache
conan-io/conan-center-index#8103
Steps to Reproduce
Remove prce from ~/.conan/data. Try to build openstudio (or conan-openstudio-ruby), which places NREL's remote first in line -> it fails
Possible Solution
Remove pcre package, reupload the current from conan-center-index.
Details
Environment
Some additional details about your environment for this issue (if relevant):
The text was updated successfully, but these errors were encountered: