OSX curl error with unprivileged user dyld: Library not loaded












3














My MAC OS is Yosemite 10.10, which has an old version of curl. I have installed Xcode and Xcode command line tools.



I run cURL with the "sudo" command as  “sudo curl”:
sudo curl
Password:
curl: try 'curl --help' or 'curl --manual' for more information

However, when I run curl under the common user in the the terminal, it failed as follows:

dyld: Library not loaded: /usr/lib/libcurl.4.dylib
Referenced from: /usr/bin/curl
Reason: Incompatible library version: curl requires version 7.0.0 or later, but libcurl.4.dylib provides version 5.0.0
Trace/BPT trap: 5


I also downloaded the curl version of 7.43, and installed in /usr/local/bin.

— "which curl” shows “/usr/local/bin/curl”
— otool shows:
otool -L /usr/local/bin/curl
/usr/local/bin/curl:
/usr/local/lib/libcurl.4.dylib (compatibility version 8.0.0, current version 8.0.0)
/usr/lib/libssl.0.9.8.dylib (compatibility version 0.9.8, current version 0.9.8)
/usr/lib/libcrypto.0.9.8.dylib (compatibility version 0.9.8, current version 0.9.8)
/System/Library/Frameworks/LDAP.framework/Versions/A/LDAP (compatibility version 1.0.0, current version 2.4.0)
/usr/lib/libz.1.dylib (compatibility version 1.0.0, current version 1.2.5)
/usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 1213.0.0)

otool -L /usr/local/lib/libcurl.4.dylib
/usr/local/lib/libcurl.4.dylib:
/usr/local/lib/libcurl.4.dylib (compatibility version 8.0.0, current version 8.0.0)
/usr/lib/libssl.0.9.8.dylib (compatibility version 0.9.8, current version 0.9.8)
/usr/lib/libcrypto.0.9.8.dylib (compatibility version 0.9.8, current version 0.9.8)
/System/Library/Frameworks/LDAP.framework/Versions/A/LDAP (compatibility version 1.0.0, current version 2.4.0)
/usr/lib/libz.1.dylib (compatibility version 1.0.0, current version 1.2.5)
/usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 1213.0.0)


However, the curl still work with "sudo" but failed for common user, i.e.,



  dyld: Library not loaded: /usr/local/lib/libcurl.4.dylib
Referenced from: /usr/local/bin/curl
Reason: Incompatible library version: curl requires version 8.0.0 or later, but libcurl.4.dylib provides version 5.0.0
Trace/BPT trap: 5


Meanwhile, the previous solution (trying to install curl with homebrew, getting "incompatible library version" for libcurl.4.dylib) did not work for my case.



-- More ----



Actually, the commands which seems to call the libcurl failed to run with the same information, e.g.:



--MacPorts:



  [user @MBK ~]$port

dlopen(/opt/local/libexec/macports/lib/pextlib1.0/Pextlib.dylib, 6): Library not loaded: /usr/lib/libcurl.4.dylib
Referenced from: /opt/local/libexec/macports/lib/pextlib1.0/Pextlib.dylib
Reason: Incompatible library version: Pextlib.dylib requires version 7.0.0 or later, but libcurl.4.dylib provides version 5.0.0
while executing "load /opt/local/libexec/macports/lib/pextlib1.0/Pextlib.dylib"
("package ifneeded Pextlib 1.0" script)
invoked from within "package require Pextlib 1.0"
(file "/opt/local/bin/port" line 47)


-- Netcdf :



 [user@MBK ~]$ncdump 

dyld: Library not loaded: /opt/local/lib/libcurl.4.dylib
Referenced from: /opt/local/bin/ncdump
Reason: Incompatible library version: ncdump requires version 8.0.0 or later, but libcurl.4.dylib provides version 5.0.0
Trace/BPT trap: 5


Again, the commands with "sudo" work.










share|improve this question
























  • The output of type curl while you are using the user would be good to have. Also not sure if OSX includes ldd but give it a try using ldd /path/to/curl where the path is the result of type before.
    – Braiam
    Jul 7 '15 at 0:59










  • Thank you for your comments! type curl shows that "curl is hashed (/usr/local/bin/curl)", however, ldd can not be found in OSX.
    – flyonsnow
    Jul 7 '15 at 1:38












  • What are the permissions of /usr/local/lib/libcurl.4.dylib & /usr/local/lib & /usr/local ?
    – Basile Starynkevitch
    Jun 17 '17 at 8:44
















3














My MAC OS is Yosemite 10.10, which has an old version of curl. I have installed Xcode and Xcode command line tools.



I run cURL with the "sudo" command as  “sudo curl”:
sudo curl
Password:
curl: try 'curl --help' or 'curl --manual' for more information

However, when I run curl under the common user in the the terminal, it failed as follows:

dyld: Library not loaded: /usr/lib/libcurl.4.dylib
Referenced from: /usr/bin/curl
Reason: Incompatible library version: curl requires version 7.0.0 or later, but libcurl.4.dylib provides version 5.0.0
Trace/BPT trap: 5


I also downloaded the curl version of 7.43, and installed in /usr/local/bin.

— "which curl” shows “/usr/local/bin/curl”
— otool shows:
otool -L /usr/local/bin/curl
/usr/local/bin/curl:
/usr/local/lib/libcurl.4.dylib (compatibility version 8.0.0, current version 8.0.0)
/usr/lib/libssl.0.9.8.dylib (compatibility version 0.9.8, current version 0.9.8)
/usr/lib/libcrypto.0.9.8.dylib (compatibility version 0.9.8, current version 0.9.8)
/System/Library/Frameworks/LDAP.framework/Versions/A/LDAP (compatibility version 1.0.0, current version 2.4.0)
/usr/lib/libz.1.dylib (compatibility version 1.0.0, current version 1.2.5)
/usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 1213.0.0)

otool -L /usr/local/lib/libcurl.4.dylib
/usr/local/lib/libcurl.4.dylib:
/usr/local/lib/libcurl.4.dylib (compatibility version 8.0.0, current version 8.0.0)
/usr/lib/libssl.0.9.8.dylib (compatibility version 0.9.8, current version 0.9.8)
/usr/lib/libcrypto.0.9.8.dylib (compatibility version 0.9.8, current version 0.9.8)
/System/Library/Frameworks/LDAP.framework/Versions/A/LDAP (compatibility version 1.0.0, current version 2.4.0)
/usr/lib/libz.1.dylib (compatibility version 1.0.0, current version 1.2.5)
/usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 1213.0.0)


However, the curl still work with "sudo" but failed for common user, i.e.,



  dyld: Library not loaded: /usr/local/lib/libcurl.4.dylib
Referenced from: /usr/local/bin/curl
Reason: Incompatible library version: curl requires version 8.0.0 or later, but libcurl.4.dylib provides version 5.0.0
Trace/BPT trap: 5


Meanwhile, the previous solution (trying to install curl with homebrew, getting "incompatible library version" for libcurl.4.dylib) did not work for my case.



-- More ----



Actually, the commands which seems to call the libcurl failed to run with the same information, e.g.:



--MacPorts:



  [user @MBK ~]$port

dlopen(/opt/local/libexec/macports/lib/pextlib1.0/Pextlib.dylib, 6): Library not loaded: /usr/lib/libcurl.4.dylib
Referenced from: /opt/local/libexec/macports/lib/pextlib1.0/Pextlib.dylib
Reason: Incompatible library version: Pextlib.dylib requires version 7.0.0 or later, but libcurl.4.dylib provides version 5.0.0
while executing "load /opt/local/libexec/macports/lib/pextlib1.0/Pextlib.dylib"
("package ifneeded Pextlib 1.0" script)
invoked from within "package require Pextlib 1.0"
(file "/opt/local/bin/port" line 47)


-- Netcdf :



 [user@MBK ~]$ncdump 

dyld: Library not loaded: /opt/local/lib/libcurl.4.dylib
Referenced from: /opt/local/bin/ncdump
Reason: Incompatible library version: ncdump requires version 8.0.0 or later, but libcurl.4.dylib provides version 5.0.0
Trace/BPT trap: 5


Again, the commands with "sudo" work.










share|improve this question
























  • The output of type curl while you are using the user would be good to have. Also not sure if OSX includes ldd but give it a try using ldd /path/to/curl where the path is the result of type before.
    – Braiam
    Jul 7 '15 at 0:59










  • Thank you for your comments! type curl shows that "curl is hashed (/usr/local/bin/curl)", however, ldd can not be found in OSX.
    – flyonsnow
    Jul 7 '15 at 1:38












  • What are the permissions of /usr/local/lib/libcurl.4.dylib & /usr/local/lib & /usr/local ?
    – Basile Starynkevitch
    Jun 17 '17 at 8:44














3












3








3







My MAC OS is Yosemite 10.10, which has an old version of curl. I have installed Xcode and Xcode command line tools.



I run cURL with the "sudo" command as  “sudo curl”:
sudo curl
Password:
curl: try 'curl --help' or 'curl --manual' for more information

However, when I run curl under the common user in the the terminal, it failed as follows:

dyld: Library not loaded: /usr/lib/libcurl.4.dylib
Referenced from: /usr/bin/curl
Reason: Incompatible library version: curl requires version 7.0.0 or later, but libcurl.4.dylib provides version 5.0.0
Trace/BPT trap: 5


I also downloaded the curl version of 7.43, and installed in /usr/local/bin.

— "which curl” shows “/usr/local/bin/curl”
— otool shows:
otool -L /usr/local/bin/curl
/usr/local/bin/curl:
/usr/local/lib/libcurl.4.dylib (compatibility version 8.0.0, current version 8.0.0)
/usr/lib/libssl.0.9.8.dylib (compatibility version 0.9.8, current version 0.9.8)
/usr/lib/libcrypto.0.9.8.dylib (compatibility version 0.9.8, current version 0.9.8)
/System/Library/Frameworks/LDAP.framework/Versions/A/LDAP (compatibility version 1.0.0, current version 2.4.0)
/usr/lib/libz.1.dylib (compatibility version 1.0.0, current version 1.2.5)
/usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 1213.0.0)

otool -L /usr/local/lib/libcurl.4.dylib
/usr/local/lib/libcurl.4.dylib:
/usr/local/lib/libcurl.4.dylib (compatibility version 8.0.0, current version 8.0.0)
/usr/lib/libssl.0.9.8.dylib (compatibility version 0.9.8, current version 0.9.8)
/usr/lib/libcrypto.0.9.8.dylib (compatibility version 0.9.8, current version 0.9.8)
/System/Library/Frameworks/LDAP.framework/Versions/A/LDAP (compatibility version 1.0.0, current version 2.4.0)
/usr/lib/libz.1.dylib (compatibility version 1.0.0, current version 1.2.5)
/usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 1213.0.0)


However, the curl still work with "sudo" but failed for common user, i.e.,



  dyld: Library not loaded: /usr/local/lib/libcurl.4.dylib
Referenced from: /usr/local/bin/curl
Reason: Incompatible library version: curl requires version 8.0.0 or later, but libcurl.4.dylib provides version 5.0.0
Trace/BPT trap: 5


Meanwhile, the previous solution (trying to install curl with homebrew, getting "incompatible library version" for libcurl.4.dylib) did not work for my case.



-- More ----



Actually, the commands which seems to call the libcurl failed to run with the same information, e.g.:



--MacPorts:



  [user @MBK ~]$port

dlopen(/opt/local/libexec/macports/lib/pextlib1.0/Pextlib.dylib, 6): Library not loaded: /usr/lib/libcurl.4.dylib
Referenced from: /opt/local/libexec/macports/lib/pextlib1.0/Pextlib.dylib
Reason: Incompatible library version: Pextlib.dylib requires version 7.0.0 or later, but libcurl.4.dylib provides version 5.0.0
while executing "load /opt/local/libexec/macports/lib/pextlib1.0/Pextlib.dylib"
("package ifneeded Pextlib 1.0" script)
invoked from within "package require Pextlib 1.0"
(file "/opt/local/bin/port" line 47)


-- Netcdf :



 [user@MBK ~]$ncdump 

dyld: Library not loaded: /opt/local/lib/libcurl.4.dylib
Referenced from: /opt/local/bin/ncdump
Reason: Incompatible library version: ncdump requires version 8.0.0 or later, but libcurl.4.dylib provides version 5.0.0
Trace/BPT trap: 5


Again, the commands with "sudo" work.










share|improve this question















My MAC OS is Yosemite 10.10, which has an old version of curl. I have installed Xcode and Xcode command line tools.



I run cURL with the "sudo" command as  “sudo curl”:
sudo curl
Password:
curl: try 'curl --help' or 'curl --manual' for more information

However, when I run curl under the common user in the the terminal, it failed as follows:

dyld: Library not loaded: /usr/lib/libcurl.4.dylib
Referenced from: /usr/bin/curl
Reason: Incompatible library version: curl requires version 7.0.0 or later, but libcurl.4.dylib provides version 5.0.0
Trace/BPT trap: 5


I also downloaded the curl version of 7.43, and installed in /usr/local/bin.

— "which curl” shows “/usr/local/bin/curl”
— otool shows:
otool -L /usr/local/bin/curl
/usr/local/bin/curl:
/usr/local/lib/libcurl.4.dylib (compatibility version 8.0.0, current version 8.0.0)
/usr/lib/libssl.0.9.8.dylib (compatibility version 0.9.8, current version 0.9.8)
/usr/lib/libcrypto.0.9.8.dylib (compatibility version 0.9.8, current version 0.9.8)
/System/Library/Frameworks/LDAP.framework/Versions/A/LDAP (compatibility version 1.0.0, current version 2.4.0)
/usr/lib/libz.1.dylib (compatibility version 1.0.0, current version 1.2.5)
/usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 1213.0.0)

otool -L /usr/local/lib/libcurl.4.dylib
/usr/local/lib/libcurl.4.dylib:
/usr/local/lib/libcurl.4.dylib (compatibility version 8.0.0, current version 8.0.0)
/usr/lib/libssl.0.9.8.dylib (compatibility version 0.9.8, current version 0.9.8)
/usr/lib/libcrypto.0.9.8.dylib (compatibility version 0.9.8, current version 0.9.8)
/System/Library/Frameworks/LDAP.framework/Versions/A/LDAP (compatibility version 1.0.0, current version 2.4.0)
/usr/lib/libz.1.dylib (compatibility version 1.0.0, current version 1.2.5)
/usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 1213.0.0)


However, the curl still work with "sudo" but failed for common user, i.e.,



  dyld: Library not loaded: /usr/local/lib/libcurl.4.dylib
Referenced from: /usr/local/bin/curl
Reason: Incompatible library version: curl requires version 8.0.0 or later, but libcurl.4.dylib provides version 5.0.0
Trace/BPT trap: 5


Meanwhile, the previous solution (trying to install curl with homebrew, getting "incompatible library version" for libcurl.4.dylib) did not work for my case.



-- More ----



Actually, the commands which seems to call the libcurl failed to run with the same information, e.g.:



--MacPorts:



  [user @MBK ~]$port

dlopen(/opt/local/libexec/macports/lib/pextlib1.0/Pextlib.dylib, 6): Library not loaded: /usr/lib/libcurl.4.dylib
Referenced from: /opt/local/libexec/macports/lib/pextlib1.0/Pextlib.dylib
Reason: Incompatible library version: Pextlib.dylib requires version 7.0.0 or later, but libcurl.4.dylib provides version 5.0.0
while executing "load /opt/local/libexec/macports/lib/pextlib1.0/Pextlib.dylib"
("package ifneeded Pextlib 1.0" script)
invoked from within "package require Pextlib 1.0"
(file "/opt/local/bin/port" line 47)


-- Netcdf :



 [user@MBK ~]$ncdump 

dyld: Library not loaded: /opt/local/lib/libcurl.4.dylib
Referenced from: /opt/local/bin/ncdump
Reason: Incompatible library version: ncdump requires version 8.0.0 or later, but libcurl.4.dylib provides version 5.0.0
Trace/BPT trap: 5


Again, the commands with "sudo" work.







osx curl






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Dec 9 '18 at 21:42









justinnoor.io

355218




355218










asked Jul 7 '15 at 0:27









flyonsnowflyonsnow

1613




1613












  • The output of type curl while you are using the user would be good to have. Also not sure if OSX includes ldd but give it a try using ldd /path/to/curl where the path is the result of type before.
    – Braiam
    Jul 7 '15 at 0:59










  • Thank you for your comments! type curl shows that "curl is hashed (/usr/local/bin/curl)", however, ldd can not be found in OSX.
    – flyonsnow
    Jul 7 '15 at 1:38












  • What are the permissions of /usr/local/lib/libcurl.4.dylib & /usr/local/lib & /usr/local ?
    – Basile Starynkevitch
    Jun 17 '17 at 8:44


















  • The output of type curl while you are using the user would be good to have. Also not sure if OSX includes ldd but give it a try using ldd /path/to/curl where the path is the result of type before.
    – Braiam
    Jul 7 '15 at 0:59










  • Thank you for your comments! type curl shows that "curl is hashed (/usr/local/bin/curl)", however, ldd can not be found in OSX.
    – flyonsnow
    Jul 7 '15 at 1:38












  • What are the permissions of /usr/local/lib/libcurl.4.dylib & /usr/local/lib & /usr/local ?
    – Basile Starynkevitch
    Jun 17 '17 at 8:44
















The output of type curl while you are using the user would be good to have. Also not sure if OSX includes ldd but give it a try using ldd /path/to/curl where the path is the result of type before.
– Braiam
Jul 7 '15 at 0:59




The output of type curl while you are using the user would be good to have. Also not sure if OSX includes ldd but give it a try using ldd /path/to/curl where the path is the result of type before.
– Braiam
Jul 7 '15 at 0:59












Thank you for your comments! type curl shows that "curl is hashed (/usr/local/bin/curl)", however, ldd can not be found in OSX.
– flyonsnow
Jul 7 '15 at 1:38






Thank you for your comments! type curl shows that "curl is hashed (/usr/local/bin/curl)", however, ldd can not be found in OSX.
– flyonsnow
Jul 7 '15 at 1:38














What are the permissions of /usr/local/lib/libcurl.4.dylib & /usr/local/lib & /usr/local ?
– Basile Starynkevitch
Jun 17 '17 at 8:44




What are the permissions of /usr/local/lib/libcurl.4.dylib & /usr/local/lib & /usr/local ?
– Basile Starynkevitch
Jun 17 '17 at 8:44










3 Answers
3






active

oldest

votes


















0














Either you have two problems or one nasty one, to find out which type the command sudo sh -c 'type curl';type curl if both type commands show the same file you have the tough one, but probably you have two simpler ones: curl is installed twice and your dynamic linker is misconfigured.






share|improve this answer

















  • 1




    I'm experiencing the same problem as flyonsnow expressed, and the output of the command you suggested outputs: curl is /usr/local/bin/curl curl is /usr/local/bin/curl, which is the "nasty" problem. Would you have any suggestions on how to solve this one?
    – Jared
    Jul 21 '15 at 23:04












  • @jared I am getting the same result from both commands as well. In my case, curl is /usr/bin/curl for each. Were you able to resolve this? If so, how?
    – Mike Eng
    May 2 '16 at 20:39



















0














Ideally you should re-install curl via: brew reinstall curl so incompatible libraries are re-linked (.dylib files).



If won't help, double check values of DYLD_LIBRARY_PATH and DYLD_FALLBACK_LIBRARY_PATH variables as misconfigured values can cause such problems (e.g. check your ~/.bashrc). Ideally unset them, otherwise if it's not set, try setting it as:



export DYLD_FALLBACK_LIBRARY_PATH="/usr/X11/lib:/usr/lib"


Similar issue: Dylibs and OS X.






share|improve this answer





























    0














    I had a similar issue, running



    curl http://some.site


    gave



    dyld: Library not loaded: @rpath/libssl.1.0.0.dylib
    Referenced from: /Users/samh/anaconda3/lib/libssh2.1.dylib
    Reason: image not found


    however, running conda install libssh2 fixed the problem. This makes no sense to me, since curl has worked on my machine for years... but at least it works now.






    share|improve this answer








    New contributor




    Sam H. is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
    Check out our Code of Conduct.


















      Your Answer








      StackExchange.ready(function() {
      var channelOptions = {
      tags: "".split(" "),
      id: "106"
      };
      initTagRenderer("".split(" "), "".split(" "), channelOptions);

      StackExchange.using("externalEditor", function() {
      // Have to fire editor after snippets, if snippets enabled
      if (StackExchange.settings.snippets.snippetsEnabled) {
      StackExchange.using("snippets", function() {
      createEditor();
      });
      }
      else {
      createEditor();
      }
      });

      function createEditor() {
      StackExchange.prepareEditor({
      heartbeatType: 'answer',
      autoActivateHeartbeat: false,
      convertImagesToLinks: false,
      noModals: true,
      showLowRepImageUploadWarning: true,
      reputationToPostImages: null,
      bindNavPrevention: true,
      postfix: "",
      imageUploader: {
      brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
      contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
      allowUrls: true
      },
      onDemand: true,
      discardSelector: ".discard-answer"
      ,immediatelyShowMarkdownHelp:true
      });


      }
      });














      draft saved

      draft discarded


















      StackExchange.ready(
      function () {
      StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f214295%2fosx-curl-error-with-unprivileged-user-dyld-library-not-loaded%23new-answer', 'question_page');
      }
      );

      Post as a guest















      Required, but never shown

























      3 Answers
      3






      active

      oldest

      votes








      3 Answers
      3






      active

      oldest

      votes









      active

      oldest

      votes






      active

      oldest

      votes









      0














      Either you have two problems or one nasty one, to find out which type the command sudo sh -c 'type curl';type curl if both type commands show the same file you have the tough one, but probably you have two simpler ones: curl is installed twice and your dynamic linker is misconfigured.






      share|improve this answer

















      • 1




        I'm experiencing the same problem as flyonsnow expressed, and the output of the command you suggested outputs: curl is /usr/local/bin/curl curl is /usr/local/bin/curl, which is the "nasty" problem. Would you have any suggestions on how to solve this one?
        – Jared
        Jul 21 '15 at 23:04












      • @jared I am getting the same result from both commands as well. In my case, curl is /usr/bin/curl for each. Were you able to resolve this? If so, how?
        – Mike Eng
        May 2 '16 at 20:39
















      0














      Either you have two problems or one nasty one, to find out which type the command sudo sh -c 'type curl';type curl if both type commands show the same file you have the tough one, but probably you have two simpler ones: curl is installed twice and your dynamic linker is misconfigured.






      share|improve this answer

















      • 1




        I'm experiencing the same problem as flyonsnow expressed, and the output of the command you suggested outputs: curl is /usr/local/bin/curl curl is /usr/local/bin/curl, which is the "nasty" problem. Would you have any suggestions on how to solve this one?
        – Jared
        Jul 21 '15 at 23:04












      • @jared I am getting the same result from both commands as well. In my case, curl is /usr/bin/curl for each. Were you able to resolve this? If so, how?
        – Mike Eng
        May 2 '16 at 20:39














      0












      0








      0






      Either you have two problems or one nasty one, to find out which type the command sudo sh -c 'type curl';type curl if both type commands show the same file you have the tough one, but probably you have two simpler ones: curl is installed twice and your dynamic linker is misconfigured.






      share|improve this answer












      Either you have two problems or one nasty one, to find out which type the command sudo sh -c 'type curl';type curl if both type commands show the same file you have the tough one, but probably you have two simpler ones: curl is installed twice and your dynamic linker is misconfigured.







      share|improve this answer












      share|improve this answer



      share|improve this answer










      answered Jul 14 '15 at 3:12









      hildredhildred

      4,73622137




      4,73622137








      • 1




        I'm experiencing the same problem as flyonsnow expressed, and the output of the command you suggested outputs: curl is /usr/local/bin/curl curl is /usr/local/bin/curl, which is the "nasty" problem. Would you have any suggestions on how to solve this one?
        – Jared
        Jul 21 '15 at 23:04












      • @jared I am getting the same result from both commands as well. In my case, curl is /usr/bin/curl for each. Were you able to resolve this? If so, how?
        – Mike Eng
        May 2 '16 at 20:39














      • 1




        I'm experiencing the same problem as flyonsnow expressed, and the output of the command you suggested outputs: curl is /usr/local/bin/curl curl is /usr/local/bin/curl, which is the "nasty" problem. Would you have any suggestions on how to solve this one?
        – Jared
        Jul 21 '15 at 23:04












      • @jared I am getting the same result from both commands as well. In my case, curl is /usr/bin/curl for each. Were you able to resolve this? If so, how?
        – Mike Eng
        May 2 '16 at 20:39








      1




      1




      I'm experiencing the same problem as flyonsnow expressed, and the output of the command you suggested outputs: curl is /usr/local/bin/curl curl is /usr/local/bin/curl, which is the "nasty" problem. Would you have any suggestions on how to solve this one?
      – Jared
      Jul 21 '15 at 23:04






      I'm experiencing the same problem as flyonsnow expressed, and the output of the command you suggested outputs: curl is /usr/local/bin/curl curl is /usr/local/bin/curl, which is the "nasty" problem. Would you have any suggestions on how to solve this one?
      – Jared
      Jul 21 '15 at 23:04














      @jared I am getting the same result from both commands as well. In my case, curl is /usr/bin/curl for each. Were you able to resolve this? If so, how?
      – Mike Eng
      May 2 '16 at 20:39




      @jared I am getting the same result from both commands as well. In my case, curl is /usr/bin/curl for each. Were you able to resolve this? If so, how?
      – Mike Eng
      May 2 '16 at 20:39













      0














      Ideally you should re-install curl via: brew reinstall curl so incompatible libraries are re-linked (.dylib files).



      If won't help, double check values of DYLD_LIBRARY_PATH and DYLD_FALLBACK_LIBRARY_PATH variables as misconfigured values can cause such problems (e.g. check your ~/.bashrc). Ideally unset them, otherwise if it's not set, try setting it as:



      export DYLD_FALLBACK_LIBRARY_PATH="/usr/X11/lib:/usr/lib"


      Similar issue: Dylibs and OS X.






      share|improve this answer


























        0














        Ideally you should re-install curl via: brew reinstall curl so incompatible libraries are re-linked (.dylib files).



        If won't help, double check values of DYLD_LIBRARY_PATH and DYLD_FALLBACK_LIBRARY_PATH variables as misconfigured values can cause such problems (e.g. check your ~/.bashrc). Ideally unset them, otherwise if it's not set, try setting it as:



        export DYLD_FALLBACK_LIBRARY_PATH="/usr/X11/lib:/usr/lib"


        Similar issue: Dylibs and OS X.






        share|improve this answer
























          0












          0








          0






          Ideally you should re-install curl via: brew reinstall curl so incompatible libraries are re-linked (.dylib files).



          If won't help, double check values of DYLD_LIBRARY_PATH and DYLD_FALLBACK_LIBRARY_PATH variables as misconfigured values can cause such problems (e.g. check your ~/.bashrc). Ideally unset them, otherwise if it's not set, try setting it as:



          export DYLD_FALLBACK_LIBRARY_PATH="/usr/X11/lib:/usr/lib"


          Similar issue: Dylibs and OS X.






          share|improve this answer












          Ideally you should re-install curl via: brew reinstall curl so incompatible libraries are re-linked (.dylib files).



          If won't help, double check values of DYLD_LIBRARY_PATH and DYLD_FALLBACK_LIBRARY_PATH variables as misconfigured values can cause such problems (e.g. check your ~/.bashrc). Ideally unset them, otherwise if it's not set, try setting it as:



          export DYLD_FALLBACK_LIBRARY_PATH="/usr/X11/lib:/usr/lib"


          Similar issue: Dylibs and OS X.







          share|improve this answer












          share|improve this answer



          share|improve this answer










          answered Sep 19 '17 at 15:20









          kenorbkenorb

          8,391370106




          8,391370106























              0














              I had a similar issue, running



              curl http://some.site


              gave



              dyld: Library not loaded: @rpath/libssl.1.0.0.dylib
              Referenced from: /Users/samh/anaconda3/lib/libssh2.1.dylib
              Reason: image not found


              however, running conda install libssh2 fixed the problem. This makes no sense to me, since curl has worked on my machine for years... but at least it works now.






              share|improve this answer








              New contributor




              Sam H. is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
              Check out our Code of Conduct.























                0














                I had a similar issue, running



                curl http://some.site


                gave



                dyld: Library not loaded: @rpath/libssl.1.0.0.dylib
                Referenced from: /Users/samh/anaconda3/lib/libssh2.1.dylib
                Reason: image not found


                however, running conda install libssh2 fixed the problem. This makes no sense to me, since curl has worked on my machine for years... but at least it works now.






                share|improve this answer








                New contributor




                Sam H. is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                Check out our Code of Conduct.





















                  0












                  0








                  0






                  I had a similar issue, running



                  curl http://some.site


                  gave



                  dyld: Library not loaded: @rpath/libssl.1.0.0.dylib
                  Referenced from: /Users/samh/anaconda3/lib/libssh2.1.dylib
                  Reason: image not found


                  however, running conda install libssh2 fixed the problem. This makes no sense to me, since curl has worked on my machine for years... but at least it works now.






                  share|improve this answer








                  New contributor




                  Sam H. is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                  Check out our Code of Conduct.









                  I had a similar issue, running



                  curl http://some.site


                  gave



                  dyld: Library not loaded: @rpath/libssl.1.0.0.dylib
                  Referenced from: /Users/samh/anaconda3/lib/libssh2.1.dylib
                  Reason: image not found


                  however, running conda install libssh2 fixed the problem. This makes no sense to me, since curl has worked on my machine for years... but at least it works now.







                  share|improve this answer








                  New contributor




                  Sam H. is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                  Check out our Code of Conduct.









                  share|improve this answer



                  share|improve this answer






                  New contributor




                  Sam H. is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                  Check out our Code of Conduct.









                  answered 13 mins ago









                  Sam H.Sam H.

                  1012




                  1012




                  New contributor




                  Sam H. is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                  Check out our Code of Conduct.





                  New contributor





                  Sam H. is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                  Check out our Code of Conduct.






                  Sam H. is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                  Check out our Code of Conduct.






























                      draft saved

                      draft discarded




















































                      Thanks for contributing an answer to Unix & Linux Stack Exchange!


                      • Please be sure to answer the question. Provide details and share your research!

                      But avoid



                      • Asking for help, clarification, or responding to other answers.

                      • Making statements based on opinion; back them up with references or personal experience.


                      To learn more, see our tips on writing great answers.





                      Some of your past answers have not been well-received, and you're in danger of being blocked from answering.


                      Please pay close attention to the following guidance:


                      • Please be sure to answer the question. Provide details and share your research!

                      But avoid



                      • Asking for help, clarification, or responding to other answers.

                      • Making statements based on opinion; back them up with references or personal experience.


                      To learn more, see our tips on writing great answers.




                      draft saved


                      draft discarded














                      StackExchange.ready(
                      function () {
                      StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f214295%2fosx-curl-error-with-unprivileged-user-dyld-library-not-loaded%23new-answer', 'question_page');
                      }
                      );

                      Post as a guest















                      Required, but never shown





















































                      Required, but never shown














                      Required, but never shown












                      Required, but never shown







                      Required, but never shown

































                      Required, but never shown














                      Required, but never shown












                      Required, but never shown







                      Required, but never shown







                      Popular posts from this blog

                      CARDNET

                      Boot-repair Failure: Unable to locate package grub-common:i386

                      濃尾地震