Skip to content
Snippets Groups Projects
Select Git revision
  • dev
  • main default protected
  • base
  • master
4 results
Search by author
  • Any Author
0 authors
  1. Apr 10, 2018
  3. Apr 08, 2018
  5. Apr 07, 2018
  7. Apr 06, 2018
  9. Apr 05, 2018
  11. Apr 03, 2018
  13. Mar 24, 2018
    • bors's avatar
      Auto merge of #955 - afck:master, r=alexcrichton · a7e78a78
      bors authored 
      Add MCL_CURRENT and MCL_FUTURE to s390.
      a7e78a78
    • bors's avatar
      Auto merge of #954 - cphrn:master, r=alexcrichton · 9d6556c9
      bors authored 
      Add strtonum to OpenBSD

OpenBSD provides [strtonum](http://man.openbsd.org/strtonum) but it is not in libc, yet.
      9d6556c9
    • bors's avatar
      Auto merge of #951 - FraGag:rename-dox-cfg, r=alexcrichton · 6fd31ae4
      bors authored 
      Rename the dox configuration option to cross_platform_docs

The libc crate is used as a dependency of the Rust compiler. Its build system passes `--cfg dox` to all crates when generating their documentation. libc's documentation is generated when the build system is asked to generate the compiler documentation because `cargo doc` automatically documents all dependencies.

When the dox configuration option is enabled, libc disables its dependency on the core crate and provides the necessary definitions itself. The dox configuration option is meant for generating documentation for a multitude of targets even if the core crate for that target is not installed. However, when documenting the compiler, it's not necessary to do that; we can just use `core` or `std` as usual.

This change is motivated by the changes made to the compiler in rust-lang/rust#48171. With these changes, it's necessary to provide implementations of the `Clone` and `Copy` traits for some primitive types in the library that defines these traits (previously, these implementations were provided by the compiler). Normally, these traits (and thus the implementations) are provided by core, so any crate that uses `#![no_core]` must now provide its own copy of the implementations.

Because libc doesn't provide its own copy of the implementations yet, and because the compiler's build system passes `--cfg dox` to libc, generating the documentation for the compiler fails when generating documentation for libc. By renaming the configuration option, libc will use `core` or `std` and will thus have the necessary definitions for the documentation to be generated successfully.

**Note:** rust-lang/rust#48171 is blocked on this PR and on a release of libc including this change on crates.io. (Some crates in the compiler use libc as a submodule, while others use a version from crates.io.)
      6fd31ae4
    • Andreas Fackler's avatar
      Add MCL_CURRENT and MCL_FUTURE to s390. · 0bb381c5
      Andreas Fackler authored
      0bb381c5
  15. Mar 22, 2018
  17. Mar 19, 2018
  19. Mar 18, 2018
    • Francis Gagné's avatar
      Rename the dox configuration option to cross_platform_docs · 18341fd2
      Francis Gagné authored 
      The libc crate is used as a dependency of the Rust compiler. Its build
system passes `--cfg dox` to all crates when generating their
documentation. libc's documentation is generated when the build system
is asked to generate the compiler documentation because `cargo doc`
automatically documents all dependencies.

When the dox configuration option is enabled, libc disables its
dependency on the core crate and provides the necessary definitions
itself. The dox configuration option is meant for generating
documentation for a multitude of targets even if the core crate for that
target is not installed. However, when documenting the compiler, it's
not necessary to do that; we can just use core or std as usual.

This change is motivated by the changes made to the compiler in
rust-lang/rust#48171. With these changes, it's necessary to provide
implementations of the Clone and Copy traits for some primitive types in
the library that defines these traits (previously, these implementations
were provided by the compiler). Normally, these traits (and thus the
implementations) are provided by core, so any crate that uses
`#![no_core]` must now provide its own copy of the implementations.

Because libc doesn't provide its own copy of the implementations yet,
and because the compiler's build system passes `--cfg dox` to libc,
generating the documentation for the compiler fails when generating
documentation for libc. By renaming the configuration option, libc will
use core or std and will thus have the necessary definitions for the
documentation to be generated successfully.
      18341fd2
  21. Mar 17, 2018
  23. Mar 16, 2018
  25. Mar 15, 2018
  27. Mar 12, 2018
  29. Mar 10, 2018
  31. Mar 08, 2018
  33. Mar 07, 2018