Valgrind fails to build on Lion (While linking, fails to find __bzero) #13042
Comments
|
You can see the full output here: https://gist.github.com/2997272 |
|
And brew doctor is relatively clean. |
|
Fixed it by extracting valgrind cached zip (got it from /Library/Caches/Homebrew) to my desktop, and just making it like homebrew would: ./configure --prefix=/usr/local/Cellar/valgrind/3.7.0 --mandir=/usr/local/Cellar/valgrind/3.7.0/share/man --enable-only64bit --build=amd64-darwin and then brew link valgrind I don't understand whats wrong. |
|
@samueljohn maybe related to the ENV changes? |
|
Yes may perhaps be related (on Xcode-only building valgrind fails). Then the fix in #13037 should fix this for CLT and Xcode+CLT systems. |
|
Maybe, but i can't guess what is it exactly. On 26.06.2012, at 22:07, Jack Nagelreply@reply.github.com wrote:
|
|
@sharth you doctor shows:
This output is interesting. Let me explain. Some software does use the stuff in The (different) issue @aspcartman has is surly fixed by #13037. |
|
I am still trying to figure out how to persuade valgrind to build with Xcode only :-/ |
|
FWIW - I just got this error on a fresh MBP + Retina on OSX Lion. https://gist.github.com/3001460 I have Xcode + Command Line Tools installed. The output of |
|
If you eager for valgrind - you can do this my way, described above. Homebrew will accept it as it was it's own. Funny it is - noone had this issue before me, i was a first one to get stuck. First one at something, atleast :D Best regards, On Wednesday, June 27, 2012 at 8:28 AM, Jud wrote:
|
|
@samueljohn The Valgrind developers are very active and care about Macs. You should find some good help there. After getting your lastest patches to Homebrew core, I am at ef37ddd80562a48d359ade98f6c5c9c1ed3c38f9 and I can't compile Valgrind. I get the exact same error as the OP here. I also get the same error if I try So I added this to the formula just under By telling the compilers that our minimum version is 10.7 on Lion, we are excluding symbols that come from 10.6 or 10.5. By specifying something like 10.5, any symbols from 10.5 will be there plus symbols from 10.6 and 10.7 will be weak linked and loadable with some runtime searching. I have no idea how many formulas build against earlier API, but we may end up just specifying an earlier version for ML, Lion, and Snow Leopard. Thoughts? |
|
@2bits we currently don't have that |
|
This wasn't done in the formula, and I only modify my PATH and my PYTHONPATH. I'm at ef37ddd80562a48d359ade98f6c5c9c1ed3c38f9 and when I Because the formula hasn't run |
|
So forget what I said. We have these in Do you need to set the |
|
I set |
|
Yep, alright. I thought it was something special for valgrind. |
|
With our latest core fixes from last night, I'm able to build valgrind on Lion with the default Homebrew install folder. |
|
I still can't build valgrind on Lion 10.7.4 with XCode-4.3.3 after I removed 90% of my installed brews. So I don't think it's my system which is raring to brew. I only have these left: |
|
I'm having the same issue with Lion 10.7.4 and Xcode 4.3.3. |
|
You need to edit the valgrind formula in Textedit or using skip_clean 'lib'
def install
# If you force a version, you get missing symbol __bzero. cf #13042
ENV.remove 'CFLAGS', " -mmacosx-version-min=#{MACOS_VERSION}"
ENV.remove 'CXXFLAGS', " -mmacosx-version-min=#{MACOS_VERSION}"
args = ["--prefix=#{prefix}", "--mandir=#{man}"]I just tested that on a clean install of Homebrew on 10.7.4 with XCode-4.3.3 + CLT. |
|
@samueljohn Any progress on XCode only building valgrind? |
|
@2bits thank you |
|
@2bits yes, that did it, thanks! 👍 |
|
@2bits thank you! To all, |
|
@samueljohn does this fix break xcode-only installs of valgrind? |
|
I can check on monday. |
|
@2bits on xcode_only I currently get this The file |
|
I'll continue tomorrow. |
|
There are some good projects like valgrind. You should be able to find a way around this. |
|
Ok, concerning the xcode-only build problems, I just found that I already filed an upstream bug for exactly the hardcoded paths to So for now valgrind needs the CLT and I cannot test the original posters |
|
@2bits I confirmed that unsetting the '-mmacosx-version-min=10.7' solved the |
|
That was funny you made that bug report in February. So can we patch for the hard coded paths until they fix it? |
|
@2bits Yes, that was shoking to find :-) and still no reply yet :-( In my fork I have a patch to compile valgrind on xcode-only. But I am not 100%sure I did everything right because I don't really use and know valgrind. I can open a pull request if you like. |
|
Yes open a pull request for Valgrind, fix it for XCode-only include issue and fix the Searching valgrind bug reports for OSX I found a few things like this thread about -new-linker. I wonder if that would have any affect. I doubt it because it seems to be for 32bit code, but you never know. |
|
You will want to use ENV.remove 'CFLAGS', " -mmacosx-version-min=#{MACOS_VERSION}"
ENV.remove 'CXXFLAGS', " -mmacosx-version-min=#{MACOS_VERSION}" |
|
Okay I'll do that tomorrow. |
|
bump, just hit this as well, the workaround above fixed it. |
|
My pull request #13548 should close this issue, too (and allows successful build of valgrind on Xcode-only systems). |
|
Presuming closed after a |
This is on OS X Lion 10.7.4...
Here's some output. I've reduced it so that the useful parts are more obvious.
As the title states, it's a linking error where it fails to find the symbol
__bzero.The text was updated successfully, but these errors were encountered: