Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
S
syscall
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 8
    • Issues 8
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 9
    • Merge Requests 9
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Incidents
    • Environments
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • CI / CD
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
  • redox-os
  • syscall
  • Issues
  • #24

Closed
Open
Opened Jan 25, 2018 by Ian Douglas Scott@ids1024Maintainer

Perhaps building syscall on non-Redox platforms should error

Otherwise it is potentially possible to build a program using the library on other platforms, but it will not work correctly, and potentially cause undefined behaviour. The best way to do this is probably with a build.rs test.

I am somewhat concerned, though, that some software ported to Redox is probably depending unconditionally on the syscall crate, and this change would make it fail to build on other platforms. This is probably the right thing to do though, and those crates can be fixed (I guess we can test every crate on crates.io that depends on redox_syscall?).

Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
Reference: redox-os/syscall#24