www/ports.html - diff

Return to ports.html CVS log

Up to [local] / www

Diff for /www/Attic/ports.html between version 1.53 and 1.54

version 1.53, 2001/07/27 23:42:52

version 1.54, 2001/08/06 21:57:18

Line 228

<h3><font color="#0000e0">Example Use of the Ports Tree</font></h3>

<p>

First, please read the <pre>/usr/ports/README</pre> file on your system.

</p>

<p>

Let's say you managed to get a ports tree and you want to compile and

install the archiving utility <strong>unzip</strong>. You should be able to

do something like this:

Line 277

Line 281

<h3><font color="#0000e0"><a name="Help">Problems and Contacts</a></font></h3>

<p>

If you have trouble with existing ports, or need information about creating new ports,

If you have trouble with an existing port, please send e-mail to the

please send e-mail to the OpenBSD

port maintainer. To see who is the maintainer of the port, type, for

example:

<pre>

% cd /usr/ports/archivers/unzip

% make show VARNAME=MAINTAINER

</pre>

Alternatively, if there is no maintainer, or you can't reach

him/her, send mail to the OpenBSD

ports mailing list, <a href="mailto:ports@openbsd.org">ports@openbsd.org</a>.

Please don't use the misc@openbsd.org mailing list for questions about ports.

Corrections are always welcome, but in any case do please provide:

<ul>

<li>The output of <code>uname -a</code>,

Line 287

Line 299

<li>A complete description of the problem.

</ul>

For ports that don't build correctly, a complete build transcript is almost

always required. Some ports may have configuration issues linked to what

always required. You can use the portslogger script, found in

is already on your machine.

/usr/ports/infrastructure/build, for this. A sample run of portslogger

might be:

<pre>

% cd /usr/ports/archivers/unzip

% su

# mkdir -p ~/portslogs

# make clean install 2>&1 | /usr/ports/infrastructure/build/portslogger \

~/portslogs

</pre>

After this, you should have a logfile of the build in your ~/portslogs directory

that you can send to the port maintainer. Also, make sure you are not using

any special options in your build, for example in /etc/mk.conf.

<p>

Alternatively, you can

<ul>

<li>Use <a href="http://www.openbsd.org/cgi-bin/man.cgi?query=script&sektion=1&format=html">script(1)</a> to create a complete build transcript. Don't remove the configure information.

<li>Attach the output of <a href="http://www.openbsd.org/cgi-bin/man.cgi?query=pkg_info&sektion=1&format=html">pkg_info(1)</a> if it seems even remotely relevant.