Error Setting Dyld_library_path Can Break Dynamic Linking
Contents |
Sign in Pricing Blog Support Search GitHub This repository Watch 1,054 Star 29,531 Fork 14,086 Homebrew/legacy-homebrew Code Issues 2 Pull requests 0 Projects 0 Pulse Graphs BREW doctor: setting DYLD_* vars #18990 Closed kuorq opened this dyld: library not loaded: Issue Apr 5, 2013 · 13 comments Projects None yet Labels user configuration
Dylib
Milestone No milestone Assignees No one assigned 8 participants kuorq commented Apr 5, 2013 Hi everyone, sorry I am not homebrew sure if this is the right place to ask the question, anyway: I am trying to have homebrew working. I am still in the phase of solving the warnings produced by doctor and this is the last one: Warning: Setting DYLD_* vars can break dynamic linking. Set variables: DYLD_FALLBACK_LIBRARY_PATH DYLD_FRAMEWORK_PATH Anyone could tell me what am I supposed to do? Thanks in advance. Cheers mistydemeo commented Apr 5, 2013 Those environment variables are probably being set in your ~/.bash_profile (or equivalent). As the warning says, they can break dynamic linking; I recommend removing them from your profile, particularly if you didn't deliberately set them and/or don't know what they're for. kuorq commented Apr 5, 2013 Thanks for your reply. I couldn't figure out which file contains these variables. What if I unset the variables and use homebrew to do whatever I need to do? In that session doctor homebrew doesn't give me any error. I know it is not the best thing in the world, but... mistydemeo commented Apr 5, 2013 Those environment variables can cause issues at runtime, not just compile-time. It's not recommended to use them unless you really have a reason why you know you need them (and are prepared to potentially break other software). If you really need to use them, you should try to have them exported only when you need their effects. samueljohn commented Apr 5, 2013 Note that files starting with a dot are hidden in the finder. You need to use the Terminal to check the .profile or .bash_profile most likely. kuorq commented Apr 6, 2013 :) yes I know that. I have just .tcshrc and no sign of DYLD inside. I tried to unset the variables and install what I needed (python). Though at the beginning doctor wasn't complaining, at the end it couldn't link something, and in addition, it gave me the following: Warning: "config" scripts exist outside your system or Homebrew directories.
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about Stack Overflow the company Business Learn more about hiring developers or posting ads with us Stack Overflow Questions Jobs Documentation Tags Users Badges Ask Question x Dismiss Join the Stack Overflow Community Stack Overflow is a community of 4.7 million programmers, just like you, helping each other. Join them; it only takes a minute: Sign up Ruby Rails Environment Completely Down about Paths, installation and brew up vote 0 down vote favorite and Thank you for Helping https://github.com/Homebrew/legacy-homebrew/issues/18990 me! Long story short, I put this in the terminal curl https://raw.github.com/gist/1688857/rbenv.sh | sh ; rbenv global 1.9.3-p327-perf I ended up downloading/installing ruby over my current ruby/rails. I stopped it in time but it was too late. Both my rails and my ruby commands didn't work ..... Originally I installed railsinstaller to get my rails/ruby up and running. I did rvm implode, removed rvm path in .bash_profile, removed /etc/rvmrc file as well. I figured http://stackoverflow.com/questions/15938487/ruby-rails-environment-completely-down-about-paths-installation-and-brew the rmv clash with the new ruby that I downloaded. Originally I used railsinstaller to get ruby/rails up and running. Then I tried to install railsinstaller but it didn't work! I later uninstalled railsinstaller because I want to try brew. Here is my .bashrc profile export PATH="/usr/bin:$PATH" export PATH="/usr/local:$PATH" export PATH="/usr/local/bin:$PATH" export PATH=/usr/local/mysql/bin:$PATH export PATH="/usr/local/opt/ruby/bin:$PATH" export DYLD_LIBRARY_PATH=/usr/local/mysql/lib:$DYLD_LIBRARY_PATH ### Added by the Heroku Toolbelt export PATH="/usr/local/heroku/bin:$PATH" Here is what I get when I run brew doctor Warning: Setting DYLD_* vars can break dynamic linking. Set variables: DYLD_LIBRARY_PATH Warning: The /usr/local directory is not writable. Even if this directory was writable when you installed Homebrew, other software may change permissions on this directory. Some versions of the "InstantOn" component of Airfoil are known to do this. You should probably change the ownership and permissions of /usr/local back to your user account. Warning: Experimental support for using Xcode without the "Command Line Tools". You have only installed Xcode. If stuff is not building, try installing the "Command Line Tools for Xcode" package provided by Apple. Warning: You have unlinked kegs in your Cellar Leaving kegs unlinked can lead to build-trouble and cause brews that depend on those kegs to fail to run properly once built. Run `brew link` on these: autoconf libtool (I tried brew link above) Error: Could not symlink file
manager for mac is seriously awesome. Setting it up is a bit tricky if you don't know what to do -- and hopefully this post will help. Step 1: The first thing you need to do is https://ricardianambivalence.com/2012/10/02/install-homebrew-on-your-mac-a-tutorial/ to install Xcode. Go to the App store and search for Xcode. Install it. https://forum.kde.org/viewtopic.php?f=203&t=120491 Step 2: wait … It is a BIG file, so it will take some time to download. If you are the impatient type, and want to check on progress, click into the ‘Updates' tab. It should look something like this: … except yours won't be complete! Step 3: Now open Xcode (the easiest way is to command-space error setting and type in ‘Xcode'). You will see the Xcode welcome screen. Step 4: Get an apple developer ID (if you do not have one). You can get it here, if you do not have one. You can sign in with your apple ID you have associated with your app-store and iTunes accounts. Step 5: Go to Xcode preferences. Step 6: Click on the ‘Downloads' tab, and in the ‘Components' section, select install error setting dyld_library_path for the Command Line Tools (wait again). Step 7: open the terminal app (command-space to open spotlight, and type ‘terminal') and check to see if ‘gcc' is installed: $ gcc --version you should see something like this: i686-apple-darwin11-llvm-gcc-4.2 (GCC) 4.2.1 (Based on Apple Inc. build 5658) (LLVM build 2336.11.00) Copyright (C) 2007 Free Software Foundation, Inc. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. If you see that, you're ready for step 8! Step 8: Get the brewer-kit. $ ruby -e "$(curl -fsSL https://raw.github.com/Homebrew/homebrew/go/install)" This will print something like the following to the screen: ==> This script will install: /usr/local/bin/brew /usr/local/Library/… /usr/local/share/man/man1/brew.1 ==> The following directories will be made group writable: /usr/local/. /usr/local/bin /usr/local/etc /usr/local/lib ==> The following directories will have their group set to admin: /usr/local/. /usr/local/bin /usr/local/etc /usr/local/lib Press enter to continue ==> /usr/bin/sudo /bin/chmod g+rwx /usr/local/. /usr/local/bin /usr/local/etc /usr/local/lib Password: You need only enter your ‘sudo' Password and it will complete. Step 9: Required fiddles -- homebrew likes things to be a certain way. It'll tell you what it'd like you to change: $ brew doctor I fixed the following errors on my laptop: E1/ Consider amending your PATH so that /usr/local/bin occurs before /usr/bi
search Information The requested topic does not exist. Board index New Topic Find a Solution KDE Links Top Top The team • Delete all board cookies Powered by phpBB © 2000, 2002, 2005, 2007 phpBB Group © Copyright 2012 KDE Community Forum Team. All rights reserved.KDE Community Forums has no liability for any content or post. All messages belong to and are the opinion of their respective authors.KDE and K Desktop Environment are trademarks of KDE e.V. • For more details, contact the Forum Administrators.