ffmpeg-0.9 build fails on 10.5 #9312
Comments
It looks like that workaround was being applied, but only on Snow Leopard for some reason. Leopard was clearly broken too. Fixed in 09d5b0e. Thanks for the report! |
Actually, build fails again with the same error. I'm absolute beginner with programming in Ruby, so can't provide you with more concrete information. However, I noticed this:
Hardware: dual-core 64-bit penryn I'm not sure how "Hardware" (class?) in ffmpeg.rb works, however Homebrew reports hardware as 64-bit and arch as 32-bit. I don't know is there any way to modify FFmpeg formula to test for arch, not hardware. ** Sorry in advance if I'm writing nonsense. **
if MacOS.leopard? and Hardware.is_64_bit? |
Any progress in solving this issue? Problem is still present. Thank you. Alex |
Sorry about that. I don't have a Leopard computer to test with, but it sounds like the problem is that ffmpeg is detecting your processor as 32-bit. On older OS X's, kernel arch and processor arch are separate, and you may have a 32-bit kernel but be able to run 64-bit programs. In this case Homebrew's detecting your processor differently from how ffmpeg does, so Can you tell me what happens if you replace that bit of code with the following? if `uname -m`.chomp == 'i386'
ENV.append_to_cflags "-mdynamic-no-pic"
end |
Also note that Homebrew defaults to building everything 32-bit on Leopard, regardless of hardware. |
Interesting, didn't realize that. In that case, |
Worked like a charm. :) FFmpeg now builds without any problems. Thank you. Alex |
Reopening until the formula is patched. |
Fixed - thanks! |
https://gist.github.com/1528236 "brew install -v ffmpeg" output.
https://gist.github.com/1528246 "brew doctor" output.
Ffmpeg build failed on upgrade to 0.9 and clean install, also.
Found out that this is known problem when using gcc >= 4.2 and PIC on 32-bit x86. Adding "--extra-cflags=-mdynamic-no-pic" to ffmpeg formula finally made build possible.
This is my first bug report, so be gentle. :P
Alex
The text was updated successfully, but these errors were encountered: