-
Notifications
You must be signed in to change notification settings - Fork 114
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
Linker error on -ltbb when building with XCode toolchain (vs. CLT) #4
Comments
Looks like an OpenCV problem. Please post the output of:
On my machine, it's:
If you previously installed opencv, you may need to manually run:
That should fix this for you. I'd suggest deleting the workspace's build and devel folders and re-running the |
Going to close this for now. Please re-open the ticket if the above suggestions do not resolve the issue. |
I tried reinstalling opencv and deleting the workspace and rebuilding, but it still came up with the same error. Here's the output of
|
Hmm, interesting. In that case, I wonder if you have OpenCV installed some other way, for example from MacPorts, or via the OS X Framework scheme? Please post the output of:
|
|
Hmm, well. I'm out of immediate ideas. If you're willing to get more in-depth, a possible next step is, from the indigo_desktop_full_ws folder, to run something like:
Then report the contents of |
I've pasted the log here. And this is the output in the terminal:
Can you spot anything unusual? |
Blah, it didn't do the right thing. Please try:
That should get us verbose make output, which will show that paths that it is trying to link against. Sorry for the runaround. |
All good! Here's the new log And the output in terminal:
|
Bizarre; it's definitely looking for it in the standard location. On my machine this is here:
And this is the version of that homebrew package which is installed:
Perhaps opencv was a red herring. Have you tried:
|
Yep my output for both location & homebrew version are similar to yours. I tried Can you think of anything else that might be causing the problem? |
I'm afraid I'm out of ideas here. If you're really committed to this, you could try the nuclear option of removing your homebrew installation and starting over from scratch. However, I understand that @wjwwood and @j-rivero are in the process of setting up a CI job to check the process for regressions on a daily basis— it may be worth waiting until that is complete so you have the confidence of knowing that at least it's working on a clean-room environment (though I have received feedback from others that this procedure worked for them, and it did also work for me a few weeks ago on a clean Parallels OS X VM). |
I've tried removing homebrew and doing a clean install of ROS by following both your instructions in README.md as well as the ones here, unfortunately neither worked. Are the instructions missing anything that should be removed for a clean install? If not, I will wait for the CI. Where can I check its progress? |
@zoercai Not sure what the timeline is on the CI being set up, but I ran the install again last night on a clean Yosemite VM via Parallels, and got a successful build of desktop_full for indigo. |
Ok I will try a clean install again. |
Sorry, I have the same problem at my MacBookPro OSX 10.10.5. There must be any drawback with already installed homebrew from the past. |
It sounds like @zoercai has tried with a completely clean Homebrew/pip installation, so that suggests that the problem is with something installed outside of Homebrew. The main area where I've found problems there is with Frameworks that overlap Homebrew packages, but at least in Zoe's case, there didn't seem to be any installed. So there's something pre-existing on your machines that's messing up the process at this particular point, but it's not at all clear to me what it is. |
This is a long shot, but one thing I noticed is that @zoercai is using the
Versus:
@mockbot, any chance you're using the Xcode compiler as well? |
I'm getting the same error - I'm also using the XCode C++:
|
I tried using the script on a fresh install of Yosemite with only XCode installed and received the same error described by this issue. After reading this, I then installed CLT and restarted the script. With CLT installed, the error went away and the script finished successfully. |
Interesting, thanks very much for trying this so thoroughly. I have little experience with the full XCode bundle, unfortunately, but is it possible to install the command-line tools at the same time? In any case, the real fix is correcting the FindTBB module. I've raised a ticket to that effect here: |
Sweet, did as @jbartels2006 said. Works as a quick fix for now. For completeness, I had to do a little more after installing CLT with:
Afterwards, when I entered this I got the following (it should be /Library/Developer/CommandLineTools):
I needed to run:
I reran the install script and everything seems dandy. |
For future reference, after switching to the rm -rf /opt/ros/indigo/* # More generally, /opt/ros/${ROS_DISTRO}/*
rm -rf build/ devel/ # Assuming your working dir is the catkin workspace
catkin build \
... # See actual script for the 4-line-long command It just saves a couple of minutes since the PS. Also, you can probably " |
Using this to create a clean install of ROS on OS X Yosemite, however I always come across this error:
How can I resolve this?
The text was updated successfully, but these errors were encountered: