Skip to content
GitLab
Menu
Why GitLab
Pricing
Contact Sales
Explore
Why GitLab
Pricing
Contact Sales
Explore
Sign in
Get free trial
Primary navigation
Search or go to…
Project
ntpsec
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Iterations
Wiki
Requirements
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Locked files
Build
Pipelines
Jobs
Pipeline schedules
Test cases
Artifacts
Deploy
Releases
Container Registry
Model registry
Operate
Environments
Monitor
Incidents
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Code review analytics
Issue analytics
Insights
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Privacy statement
Keyboard shortcuts
?
What's new
4
Snippets
Groups
Projects
Show more breadcrumbs
NTPsec
ntpsec
Commits
36253592
Commit
36253592
authored
8 years ago
by
Eric S. Raymond
Browse files
Options
Downloads
Patches
Plain Diff
Update on porting requirements.
parent
e6cf5bfd
No related branches found
No related tags found
Loading
Changes
2
Hide whitespace changes
Inline
Side-by-side
Showing
2 changed files
INSTALL
+3
-1
3 additions, 1 deletion
INSTALL
devel/hacking.txt
+14
-3
14 additions, 3 deletions
devel/hacking.txt
with
17 additions
and
4 deletions
INSTALL
+
3
−
1
View file @
36253592
...
...
@@ -6,7 +6,9 @@ This software should build on any operating system conformant to
POSIX.1-2001 and ISO/IEC 9899:1999 (C99). In addition, the
operating system must have either a Linux-like adjtimex(2) call
or a BSD-like pair of ntp_gettime(2)/ntp_adjtime(2) calls. Also,
it must support the IPv6 API defined in RFC2493 and RFC2553.
it must support the IPv6 API defined in RFC2493 and RFC2553. Finally,
it must support iterating over active UDP interfaces via getifaddrs(3)
or some equivalent facility.
There are some prerequisites. Libraries need the library installed
to run and in addition, the development headers installed to build.
...
...
This diff is collapsed.
Click to expand it.
devel/hacking.txt
+
14
−
3
View file @
36253592
...
...
@@ -38,7 +38,8 @@ coexist with distributions that use C89 conventions.
You can download the C99 standard for free from here:
http://atrey.karlin.mff.cuni.cz/projekty/vrr/doc/c99.pdf
Only POSIX-1.2001/SuSv3 library functions should be used. If a library
Only POSIX-1.2001/SuSv3 library functions should be used (a few
specific exceptions are noted below). If a library
function not in POSIX 2001 is required, then a wrapper function for back
compatibility must be provided. One notable case is clock_gettime()
which is used, when available, for increased accuracy, and has a
...
...
@@ -47,8 +48,18 @@ fallback implementation using native time calls.
You can view POSIX-1.2001, with 2004 Corrigendum, online for free here:
http://pubs.opengroup.org/onlinepubs/009695399/toc.htm
You may assume Berkeley sockets and the IPv6 API defined in RFC2493
and RFC2553.
POSIX threads *are* considered part of the standardized API and may be used.
Here are the non-standardized AIs that may be used:
* Linux-style adjtimex() or BSD-style ntp_gettime()/ntp_adjtime().
* Berkeley sockets and the IPv6 API defined in RFC2493 and RFC2553.
* getifaddrs(3) or an equivalent local API for iterating over the
system's active UDP interfaces. However, the local details should be
hidden as an implementation of the interfaceiter.c functions under
libisc - not called directly from the rest of the code.
=== Banned functions ===
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment