Continued from closed #25864 ./configure and installing llvm #25885

issue elonlvl openend this issue on August 20, 2022
  1. elonlvl commented at 4:20 am on August 20, 2022: none

    Thanks to everyone and especially fanquake for the help. Here we go… this is a bug continued from ./configure when installing brew install llvm i get a string of this::

     0
     1==> llvm: stable 14.0.6, HEAD [keg-only]
     2Next-gen compiler infrastructure
     3https://llvm.org/
     4Not installed
     5From: https://github.com/Homebrew/homebrew-core/blob/HEAD/Formula/llvm.rb
     6License: Apache-2.0 with LLVM-exception
     7==> Dependencies
     8Build: cmake ✔, swig ✔
     9Required: python@3.10 ✔, libffi ✔
    10==> Options
    11--HEAD
    12	Install HEAD version
    13==> Caveats
    14To use the bundled libc++ please add the following LDFLAGS:
    15  LDFLAGS="-L/usr/local/opt/llvm/lib -Wl,-rpath,/usr/local/opt/llvm/lib"
    

    llvm is keg-only, which means it was not symlinked into /usr/local, because macOS already provides this software and installing another version in parallel can cause all kinds of trouble.

    i feel like i am getting nowhere . still unable to configure the bitcoin/bitcoin git…… its heartwrenching, but I am trying diligently and patiently to fix my issues. is there something wrong with my mac itself. it is very old 2011….. over ten years old!! very outdated. running Mac OS 10.13.6

    do i need to go ahead and usebrew info llvm’s out put of /usr/local/opt/llvm/lib or what sense it is not symlinked… ?? and just use that LDFLAG as the path? it says it can’t symlink? should i use the keg’s path /usr/local/opt/llvm or the other, or will this cause problems. i will get this thing worked out eventually. just need a little nudge in the right direction one more time.

  2. elonlvl added the label Bug on Aug 20, 2022
  3. saranshisatgit commented at 5:51 am on August 20, 2022: none
    Why are you trying to build this using llvm , I don’t see any library recommendations in the doc of -osx.md did you try following up from there? I was able to compile on the latest mac book with M1 chip
  4. saranshisatgit commented at 6:24 am on August 20, 2022: none

    This should work

    ./configure CC=/opt/homebrew/opt/llvm/bin/clang CXX=/opt/homebrew/opt/llvm/bin/clang++

    Based on my assumption you had the files path mapped wrong , they need to be c and c++ compiler CC and CXX..

    Let me know if this work I checked at my end and it worked

  5. MarcoFalke removed the label Bug on Aug 20, 2022
  6. MarcoFalke added the label macOS on Aug 20, 2022
  7. MarcoFalke added the label Questions and Help on Aug 20, 2022
  8. elonlvl commented at 2:11 pm on August 22, 2022: none

    Why are you trying to build this using llvm , I don’t see any library recommendations in the doc of -osx.md did you try following up from there? I was able to compile on the latest mac book with M1 chip

    Llvm happens to be the default for my particular computer* I did follow up -osx.md to no avail. I was not able to compile with my 2008 All-in-one Mac 21.6 with no M1 Chip. It’s quite old and I’m starting to think that’s problem. I am running High Sierra 10.13.6 and it’s the highest upgrade I can do on the particular machine bc of how old it is. Therefore my xcode.app is not fully working and I don’t know much about compiling in the first place. Clang vs. CC vs. C++ vs. gcc@8 . It’s all deconstructed sushi to me… And fish ain’t my strong point. Except Mackerel it’s so damn good. Mackerel box with the thin lemon slice on top. Don’t even take it off for the first bite I love the zest. Anyways sorry. I’m hungry. But why can I not compile with what I got. My config.log gives me a dumb reason for not working….

  9. MarcoFalke commented at 2:18 pm on August 22, 2022: member
    Is this still an issue? Without any info on what you typed and what you got, there is nothing we can do.
  10. saranshisatgit commented at 2:39 pm on August 22, 2022: none

    Why are you trying to build this using llvm , I don’t see any library recommendations in the doc of -osx.md did you try following up from there? I was able to compile on the latest mac book with M1 chip

    Llvm happens to be the default for my particular computer* I did follow up -osx.md to no avail. I was not able to compile with my 2008 All-in-one Mac 21.6 with no M1 Chip. It’s quite old and I’m starting to think that’s problem. I am running High Sierra 10.13.6 and it’s the highest upgrade I can do on the particular machine bc of how old it is. Therefore my xcode.app is not fully working and I don’t know much about compiling in the first place. Clang vs. CC vs. C++ vs. gcc@8 . It’s all deconstructed sushi to me… And fish ain’t my strong point. Except Mackerel it’s so damn good. Mackerel box with the thin lemon slice on top. Don’t even take it off for the first bite I love the zest. Anyways sorry. I’m hungry. But why can I not compile with what I got. My config.log gives me a dumb reason for not working….

    Did you try running the above commands in your terminal ? Let me know if those commands work in your terminal. I ran with llvm using the above file path.

    Your problem stems from the wrong file path mapping, I saw your previous issue #25864, I dont think old PC/MAC has to do with this issue.

    You have to provide the right path for the CC and C++ compilers , that should do the job. Please provide console outputs

  11. fanquake closed this on Aug 22, 2022

  12. bitcoin locked this on Aug 22, 2023

github-metadata-mirror

This is a metadata mirror of the GitHub repository bitcoin/bitcoin. This site is not affiliated with GitHub. Content is generated from a GitHub metadata backup.
generated: 2024-11-21 09:12 UTC

This site is hosted by @0xB10C
More mirrored repositories can be found on mirror.b10c.me