version 1.57, 2007/06/18 15:27:16 |
version 1.58, 2009/01/27 13:19:14 |
|
|
<meta name="distribution" |
<meta name="distribution" |
content="global"> |
content="global"> |
<meta name="copyright" |
<meta name="copyright" |
content="This document copyright 1997-2006 by OpenBSD."> |
content="This document copyright 1997-2009 by OpenBSD."> |
<title>Building an OpenBSD port</title> |
<title>Building an OpenBSD port</title> |
<link rev="made" HREF="mailto:www@openbsd.org"> |
<link rev="made" HREF="mailto:www@openbsd.org"> |
</head> |
</head> |
|
|
Also, some compilers, such as OpenBSD's own gcc, |
Also, some compilers, such as OpenBSD's own gcc, |
are able to do a better job with some very frequent functions such as |
are able to do a better job with some very frequent functions such as |
<code>strlen</code> if you include the right header file. |
<code>strlen</code> if you include the right header file. |
|
|
|
<li>Carefully check the build log for any compiler warnings. |
|
<ul><li> |
|
<code>implicit declaration of function foo()</code> |
|
indicates that a function prototype is missing. |
|
This means that the compiler will assume the return type |
|
to be an integer. |
|
Where the function actually returns a pointer, on 64-bit |
|
platforms it will be truncated, usually causing a segmentation |
|
fault. |
|
</ul> |
|
|
<li>Don't use the name of a standard system function for anything else. |
<li>Don't use the name of a standard system function for anything else. |
If you want to write your own function, give it its own name, and |
If you want to write your own function, give it its own name, and |