| Age | Commit message (Collapse) | Author |
|
|
|
It seems like latest build of Xcode 4.2 doesn't create "-4.2" links in /usr/bin. Because of this recipes fail with "configure: error: C compiler cannot create executables" error.
Closes Homebrew/homebrew#7254.
Closes Homebrew/homebrew#7276.
Signed-off-by: Max Howell <max@methylblue.com>
Amended to work as intended, since /usr/bin/cc is actually since Xcode 4.
Amended commit message. First line must be less than 72 characters! :P
|
|
Signed-off-by: Mike McQuaid <mike@mikemcquaid.com>
|
|
Deprecated use_clang? etc. since the logic was such that multiple states could be set, when in reality only one compiler can be set.
Changed fails_with_llvm handling so if HOMEBREW_USE_LLVM is set then it tries to build even if the formula has fails_with_llvm set. Rationale: mostly they will no longer fail and we need to catch these cases.
|
|
Also tidied it up a little, reducing duplication as per original patch.
|
|
Fixes Homebrew/homebrew#7185.
|
|
|
|
Let an environment variable, HOMEBREW_MAKE_JOBS, override the default
'-j<cores>' make flag.
Now we can more easily debug formula that normally build in parallel, or
(potentially) speed up lengthy builds.
|
|
I believe this works nowadays. When I created Homebrew originally, it did nothing. Hence all the other logic.
|
|
|
|
Signed-off-by: Adam Vandenberg <flangy@gmail.com>
|
|
|
|
Longer-term we'll try and use install_name_tool to fix Lion
bottles so they run fine on 10.5 and/or 10.6.
Closes Homebrew/homebrew#6699.
|
|
This is needed for Ruby 1.9.x compatibility, but we still don't support
running Homebrew with anything other than a system provided 1.8.[67].
Fixes Homebrew/homebrew#6546
Signed-off-by: Adam Vandenberg <flangy@gmail.com>
|
|
|
|
|
|
|
|
|
|
|
|
This allows its use in Leopard, which has Ruby 1.8.6.
|
|
|
|
Before we would always make the symlink itself have a basename the same as what it pointed to.
I donât think this breaks any of the other usages as they were working by coincidence.
|
|
|
|
|
|
Signed-off-by: Adam Vandenberg <flangy@gmail.com>
|
|
|
|
|
|
|
|
|
|
`ENV.Og` clears all optimization flags and adds `-g -O0`.
Signed-off-by: Adam Vandenberg <flangy@gmail.com>
|
|
Signed-off-by: Adam Vandenberg <flangy@gmail.com>
|
|
|
|
|
|
|
|
SourceForge links can end with /download which appears to be part of
what is used to drive mirror selection. Modifying the version detection
extension of pathname.rb to detect this case for both sourceforge.net
and sf.net download selections.
This is sufficient for version detection but may not be sufficient for
other uses of /download links. I have not found any problems with links
that use /download, though.
Signed-off-by: Adam Vandenberg <flangy@gmail.com>
|
|
|
|
|
|
Be more useful by being more concise. I referenced dozens of other mature commandsâ usage to figure out what to do here.
Also separated out the help into its own command for consistency.
|
|
This provides a uniform way for formulae to indicate a Fortran compiler
is required.
Signed-off-by: Adam Vandenberg <flangy@gmail.com>
|
|
|
|
This allows you to use llvm as your default compiler and keep the cc symlink
pointed at llvm, while allowing you to build forumla that requires the gcc.
Signed-off-by: Adam Vandenberg <flangy@gmail.com>
|
|
More robust code than before, and replaces all usage of `xcode-select -print-path`.
|
|
Rationale: this is more useful than the union, and you can still easily get the union by running the command twice and concatenating the result.
|
|
Yields after chmoding (if necessary), once block is complete restores permissions.
|
|
|
|
|
|
|
|
|
|
The code was sucking. To the extent that maintenance was hard. It's a lot
easier to work with code that is sensibly split at sensible boundaries. So
now it is more like that.
But the refactor is minimal. Because we don't want you to have more merge
hell than absolutely necessary.
If you merge you will need to pay attention to brew.h.rb (as it is deleted)
and bin/brew (as command logic is gone). It will be painful, but you will just
have to help git out by moving any changes around manually.
Note compatibility.rb. It ensures that any function renames or removals don't
break anything. We're pretty serious about backwards compatibility. And that's
because we encourage you to hack around with the innards. And we couldn't do
that if we would then just make stuff disappear behind your back.
|
|
|