summary refs log tree commit diff
path: root/pkgs/os-specific/darwin/binutils
Commit message (Collapse)AuthorAge
* darwin binutils: Better handling of man pages and infoJohn Ericson2017-12-13
|
* bintools-wrapper: Import separately from cc-wrapperJohn Ericson2017-12-13
|
* treewide: Use `targetPrefix` instead of `prefix` for platform name prefixesJohn Ericson2017-11-27
| | | | | | | | | Certain tools, e.g. compilers, are customarily prefixed with the name of their target platform so that multiple builds can be used at once without clobbering each other on the PATH. I was using identifiers named `prefix` for this purpose, but that conflicts with the standard use of `prefix` to mean the directory where something is installed. To avoid conflict and confusion, I renamed those to `targetPrefix`.
* cctools: Don't always bring in headersJohn Ericson2017-11-16
| | | | | | | | | - Give cctools a dev output for the headers - Update Libsystem to grab the headers from that dev output - Don't include the headers in Darwin binutils, just as GNU Binutils no longer does.
* darwin-bintuils: Don't try to bring in missing bits of GNU BinutilsJohn Ericson2017-11-16
| | | | | libbfd and libopcdes are separate derivations which now provide all headers and libraries. Binutils should just provide executables.
* treewide: Fix some references to binutilsJohn Ericson2017-09-14
| | | | | | | - Compiler's shouldn't use `binutils.dev` as that doesn't yet exist with a cross binutils. - Last two `binutils.binutils` which weren't reverted
* misc pkgs: Remove unneeded *Platform == *Platform comparisonsJohn Ericson2017-06-30
| | | | | PR #26007 used these to avoid causing a mass rebuild. Now that we know things work, we do that to clean up.
* binutils and cctools: Prefix derivation names with target for crossJohn Ericson2017-05-17
| | | | | | | | | | | | We want platform triple prefixes and suffixes on derivation names to be used consistently. The ideom this commit strives for is - suffix means build != host, i.e. cross *built* packages. This is already done. - prefix means build != target, i.e. cross tools. This matches the tradition of such binaries themselves being prefixed to disambiguate.] Binutils and cctools, as build tools, now use the latter
* binutils on darwin: Clean up the rats nestJohn Ericson2017-05-17
| | | | | | | | | | | | - No more *Cross duplication for binutils on darwin either. `cctools_cross` is merged into plain `cctools`, so `buildPackages` chains alone are used to disambiguate. - Always use a mashup of cctools and actual GNU Binutils as `binutils`. Previously, this was only done in the native case as nobody had bothered to implement the masher in the cross case. Implemented it basically consisted of extending the wrapper to deal with prefixed binaries.
* darwin binutils: Fix binutils-raw output referencesTuomas Tynkkynen2016-08-30
|
* treewide: Make explicit that 'dev' output of binutils-raw is usedTuomas Tynkkynen2016-05-19
|
* treewide: Mass replace 'binutils-raw}/lib' to refer the 'out' outputTuomas Tynkkynen2016-01-24
|
* pure darwin stdenvJude Taylor2015-06-18