View | Details | Raw Unified | Return to bug 47194
Collapse All | Expand All

(-)index.html (-66 / +279 lines)
Lines 198-204 Link Here
198
198
199
<li>The build is done on a shared (read-only) <tt>/usr/ports</tt>
199
<li>The build is done on a shared (read-only) <tt>/usr/ports</tt>
200
with <a href=
200
with <a href=
201
"http://www.freebsd.org/handbook/porting.html#PORTING-WRKDIRPREFIX">
201
"http://www.freebsd.org/doc/en_US.ISO8859-1/books/porters-handbook/porting-wrkdir.html">
202
<tt>WRKDIRPREFIX</tt></a> set to <tt>/tmp</tt>. If your
202
<tt>WRKDIRPREFIX</tt></a> set to <tt>/tmp</tt>. If your
203
<tt>WRKSRC</tt> looks funny, that's probably why.</li>
203
<tt>WRKSRC</tt> looks funny, that's probably why.</li>
204
204
Lines 211-218 Link Here
211
the second build starts after the first one ends). After the entire
211
the second build starts after the first one ends). After the entire
212
build process, the distfiles are copied over to ftp.freebsd.org.
212
build process, the distfiles are copied over to ftp.freebsd.org.
213
This means if your port built successfully once, you will never see
213
This means if your port built successfully once, you will never see
214
a "can't fetch distfile" error again. Please pay attention to Bill
214
a "can't fetch distfile" error again. Please pay attention to
215
Fenner's distfile checker for that.</li>
215
<a href="http://people.freebsd.org/~fenner/portsurvey/bad.html">
216
Bill Fenner's distfile checker</a>
217
for that.</li>
216
218
217
<li>The ports are built on 4-stable machines. Some of the 5-current
219
<li>The ports are built on 4-stable machines. Some of the 5-current
218
failures may be because of that. 
220
failures may be because of that. 
Lines 224-265 Link Here
224
</ul>
226
</ul>
225
227
226
<hr>
228
<hr>
227
<p>Here is an alphabetical list of errors detected by my AI script.
229
<p><a name="errorlist">Here is an <b>alphabetical list of errors</b></a>
228
Note that this is all just a rough guess -- it is merely for your
230
detected by my AI script.  Note that this is all just a rough guess --
229
aid.</p>
231
it is merely for your aid.</p>
230
232
233
<p>Key (applies only to the items below):
231
<dl>
234
<dl>
232
<dt><img alt="*" src="/errorlogs/images/green-ball.gif"><a tag=
235
  <dt><img alt="(common)" src="/errorlogs/images/blue-ball.gif">The most common
236
    errors.</dt> 
237
  <dt><img alt="(uncommon)" src="/errorlogs/images/purple-ball.gif">Some less common
238
    errors.</dt> 
239
  <dt><img alt="(transient)" src="/errorlogs/images/green-ball.gif">Transient
240
    errors.  These may not be your fault.</dt> 
241
</dl>
242
</p>
243
244
<p>
245
<dl>
246
<dt><img alt="(uncommon)" src="/errorlogs/images/purple-ball.gif"><a tag=
247
"alignment">alignment</a></dt>
248
249
<dd>You've managed to confuse the assembler with a misaligned
250
structure.</dd>
251
252
<dt><img alt="(common)" src="/errorlogs/images/blue-ball.gif"><a tag=
253
"apxs">apxs</a></dt>
254
255
<dd>Your port depends on Apache (in particular, the <tt>apxs</tt>
256
binary) but the <tt>Makefile</tt> doesn't have Apache in
257
<tt>BUILD_DEPENDS</tt> and/or <tt>LIB_DEPENDS</tt>.</dd>
258
259
<dt><img alt="(common)" src="/errorlogs/images/blue-ball.gif"><a tag=
260
"arch">arch</a></dt>
261
262
<dd>The port does not build on a particular architecture, due to
263
assembler or linker errors.  In some easy cases this is due to
264
not picking up the various <tt>ARCH</tt> configuration variables
265
in the Makefile; you'll see this via, e.g., a Sparc <tt>make</tt>
266
failing while looking for an i386 subdirectory.  In other cases
267
the problems run much deeper, in which case <tt>ONLY_FOR_ARCHS</tt>
268
may be needed.</dd>
269
270
<dt><img alt="(uncommon)" src="/errorlogs/images/purple-ball.gif"><a tag=
271
"assert">assert</a></dt>
272
273
<dd>Compilation failed due to an assert.  This is often a variation
274
on <tt>arch</tt> or <tt>missing header</tt>.</dd>
275
276
<dt><img alt="(uncommon)" src="/errorlogs/images/purple-ball.gif"><a tag=
277
"autoconf">autoconf</a></dt>
278
279
<dd>Your port depends on <tt>autoconf</tt>, but the <tt>Makefile</tt>
280
either doesn't have <tt>USE_AUTOCONF</tt>, or does not use
281
<tt>USE_AUTOCONF_VER</tt> correctly.</dd>
282
283
<dt><img alt="(uncommon)" src="/errorlogs/images/purple-ball.gif"><a tag=
284
"autoheader">autoheader</a></dt>
285
286
<dd>Your port depends on <tt>autoheader</tt>, but the <tt>Makefile</tt>
287
cannot find it.</dd>
288
289
<dt><img alt="(uncommon)" src="/errorlogs/images/purple-ball.gif"><a tag=
290
"automake">automake</a></dt>
291
292
<dd>Your port depends on <tt>automake</tt>, but the <tt>Makefile</tt>
293
either doesn't have <tt>USE_AUTOMAKE</tt>, or does not use
294
<tt>USE_AUTOMAKE_VER</tt> correctly.</dd>
295
296
<dt><img alt="(uncommon)" src="/errorlogs/images/purple-ball.gif"><a tag=
297
"awk">awk</a></dt>
298
299
<dd><tt>awk</tt> is complaining about some kind of bogus string
300
expression.</dd>
301
302
<dt><img alt="(common)" src="/errorlogs/images/blue-ball.gif"><a tag=
303
"badc++">bad C++ code</a></dt>
304
305
<dd>There is a compiler error which is caused by something specific
306
to C++.</dd>
307
308
<dt><img alt="(common)" src="/errorlogs/images/blue-ball.gif"><a tag=
233
"bison">bison</a></dt>
309
"bison">bison</a></dt>
234
310
235
<dd>Your port requires <tt>bison</tt>, which doesn't exist in
311
<dd>Your port requires <tt>bison</tt>, which does not exist in
236
4-stable or newer anymore. Either patch it to use <tt>byacc</tt>
312
4-stable or newer anymore. Either patch it to use <tt>byacc</tt>
237
instead, or define <tt>USE_BISON</tt>.</dd>
313
instead, or define <tt>USE_BISON</tt>.</dd>
238
314
239
<dt><img alt="*" src="/errorlogs/images/green-ball.gif"><a tag=
315
<dt><img alt="(common)" src="/errorlogs/images/blue-ball.gif"><a tag=
240
"cc">C compiler error</a></dt>
316
"cc">compiler error</a></dt>
241
317
242
<dd>There is a compiler error which is caused by something other
318
<dd>There is a C compiler error which is caused by something other
243
than e.g. "new compiler error".</dd>
319
than e.g. "new compiler error".</dd>
244
320
245
<dt><img alt="*" src="/errorlogs/images/green-ball.gif"><a tag=
321
<dt><img alt="(uncommon)" src="/errorlogs/images/purple-ball.gif"><a tag=
246
"categories">CATEGORIES</a></dt>
322
"categories">CATEGORIES</a></dt>
247
323
248
<dd>The <tt>CATEGORIES</tt> line in <tt>Makefile</tt> includes an
324
<dd>The <tt>CATEGORIES</tt> line in <tt>Makefile</tt> includes an
249
invalid category.</dd>
325
invalid category.</dd>
250
326
251
<dt><img alt="*" src="/errorlogs/images/green-ball.gif"><a tag=
327
<dt><img alt="(uncommon)" src="/errorlogs/images/purple-ball.gif"><a tag=
328
"cgi-bin">cgi-bin</a></dt>
329
330
<dd>Your port assumes that a directory (usually
331
<tt>/usr/local/www/cgi-bin</tt>) already exists,
332
but by default it doesn't.</dd>
333
334
<dt><img alt="(common)" src="/errorlogs/images/blue-ball.gif"><a tag=
252
"checksum">checksum</a></dt>
335
"checksum">checksum</a></dt>
253
336
254
<dd>The checksum of one or more of the files is incorrect.</dd>
337
<dd>The checksum of one or more of the files is incorrect.</dd>
255
338
256
<dt><img alt="*" src="/errorlogs/images/green-ball.gif"><a tag=
339
<dt><img alt="(uncommon)" src="/errorlogs/images/purple-ball.gif"><a tag=
340
"chown">chown</a></dt>
341
342
<dd><tt>POSIX</tt> has deprecated the usage
343
"<tt>chown user.group filename</tt>" in favor of
344
"<tt>chown user:group filename</tt>". This happened quite some time
345
ago, actually, but it is only now being enforced. (The change was
346
made to allow '.' in usernames).</dd>
347
348
<dt><img alt="(common)" src="/errorlogs/images/blue-ball.gif"><a tag=
257
"configure">configure error</a></dt>
349
"configure">configure error</a></dt>
258
350
259
<dd>The port's <tt>configure</tt> script produced some kind of
351
<dd>The port's <tt>configure</tt> script produced some kind of
260
error.</dd>
352
error.</dd>
261
353
262
<dt><img alt="*" src="/errorlogs/images/green-ball.gif"><a tag=
354
<dt><img alt="(uncommon)" src="/errorlogs/images/purple-ball.gif"><a tag=
355
"coredump">coredump</a></dt>
356
357
<dd>Some process dropped core. While your port may indeed be faulty,
358
the process that dropped core should also be fixed.</dd>
359
360
<dt><img alt="(uncommon)" src="/errorlogs/images/purple-ball.gif"><a tag=
263
"dependobj">depend object</a></dt>
361
"dependobj">depend object</a></dt>
264
362
265
<dd>The port is trying to reinstall a dependency that already
363
<dd>The port is trying to reinstall a dependency that already
Lines 269-313 Link Here
269
by the dependency, causing it to be rebuilt even though it has
367
by the dependency, causing it to be rebuilt even though it has
270
already been <a href="#pkgadd">added from a package</a>.</dd>
368
already been <a href="#pkgadd">added from a package</a>.</dd>
271
369
272
<dt><img alt="*" src="/errorlogs/images/green-ball.gif"><a tag=
370
<dt><img alt="(uncommon)" src="/errorlogs/images/purple-ball.gif"><a tag=
273
"dependpkg">depend package</a></dt>
371
"dependpkg">depend package</a></dt>
274
372
275
<dd>There was an error during <a href="#pkgadd">adding dependencies
373
<dd>There was an error during <a href="#pkgadd">adding dependencies
276
from packages</a>. It is the fault of the package being added, not
374
from packages</a>. It is the fault of the package being added, not
277
this port.</dd>
375
this port.</dd>
278
376
279
<dt><img alt="*" src="/errorlogs/images/green-ball.gif"><a tag=
377
<dt><img alt="(transient)" src="/errorlogs/images/green-ball.gif"><a tag=
280
"df">disk full</a></dt>
378
"df">disk full</a></dt>
281
379
282
<dd>The disk filled up on the build system. It is not your
380
<dd>The disk filled up on the build system. It is not your
283
fault.</dd>
381
fault.</dd>
284
382
285
<dt><img alt="*" src="/errorlogs/images/green-ball.gif"><a tag=
383
<dt><img alt="(uncommon)" src="/errorlogs/images/purple-ball.gif"><a tag=
286
"display">DISPLAY</a></dt>
384
"display">DISPLAY</a></dt>
287
385
288
<dd>This port requires an X display to build. There is nothing you
386
<dd>This port requires an X display to build. There is nothing you
289
can do about it unless you can somehow make it not require an X
387
can do about it unless you can somehow make it not require an X
290
connection.</dd>
388
connection.</dd>
291
389
292
<dt><img alt="*" src="/errorlogs/images/green-ball.gif"><a tag=
390
<dt><img alt="(common)" src="/errorlogs/images/blue-ball.gif"><a tag=
293
"distinfo">distinfo update</a></dt>
391
"distinfo">distinfo update</a></dt>
294
392
295
<dd>The contents of <tt>distinfo</tt> doesn't match the list of
393
<dd>The contents of <tt>distinfo</tt> does not match the list of
296
distfiles or patchfiles.</dd>
394
distfiles or patchfiles.</dd>
297
395
298
<dt><img alt="*" src="/errorlogs/images/green-ball.gif"><a tag=
396
<dt><img alt="(uncommon)" src="/errorlogs/images/purple-ball.gif"><a tag=
299
"elf">ELF</a></dt>
397
"elf">ELF</a></dt>
300
398
301
<dd>The port does not properly work in the new ELF world. It is
399
<dd>The port does not properly work in the new ELF world. It is
302
probably looking for an <tt>a.out</tt> object (e.g.,
400
probably looking for an <tt>a.out</tt> object (e.g.,
303
<tt>crt0.o</tt>).</dd>
401
<tt>crt0.o</tt>).</dd>
304
402
305
<dt><img alt="*" src="/errorlogs/images/green-ball.gif"><a tag=
403
<dt><img alt="(common)" src="/errorlogs/images/blue-ball.gif"><a tag=
306
"fetch">fetch</a></dt>
404
"fetch">fetch</a></dt>
307
405
308
<dd>One or more of the files couldn't be fetched.</dd>
406
<dd>One or more of the files could not be fetched.</dd>
309
407
310
<dt><img alt="*" src="/errorlogs/images/green-ball.gif"><a tag=
408
<dt><img alt="(uncommon)" src="/errorlogs/images/purple-ball.gif"><a tag=
311
"fetch-timeout">fetch timeout</a></dt>
409
"fetch-timeout">fetch timeout</a></dt>
312
410
313
<dd>Your fetch process was killed because it took too long. (More
411
<dd>Your fetch process was killed because it took too long. (More
Lines 315-379 Link Here
315
put sites with better connectivity near the beginning of
413
put sites with better connectivity near the beginning of
316
<tt>MASTER_SITES</tt>.</dd>
414
<tt>MASTER_SITES</tt>.</dd>
317
415
318
<dt><img alt="*" src="/errorlogs/images/green-ball.gif"><a tag=
416
<dt><img alt="(uncommon)" src="/errorlogs/images/purple-ball.gif"><a tag=
319
"instal">install error</a></dt>
417
"ffs_conflict">ffs conflict</a></dt>
418
419
<dd>Both <tt>/usr/include/machine/cpufunc.h</tt> and
420
<tt>/usr/include/strings.h</tt> are attempting to define <tt>int ffs()</tt>.
421
The "correct" fix is not known at this time.</dd>
422
423
<dt><img alt="(uncommon)" src="/errorlogs/images/purple-ball.gif"><a tag=
424
"forbidden">forbidden</a></dt>
425
426
<dd>Someone has marked this port as "forbidden", almost always due
427
to security concerns.  See the logfile for more information.</dd>
428
429
<dt><img alt="(uncommon)" src="/errorlogs/images/purple-ball.gif"><a tag=
430
"gcc-bug">gcc bug</a></dt>
431
432
<dd>You have tickled a bug in gcc itself. See the
433
<a href="http://www.gnu.org/software/gcc/bugs.html">GNU bug report documentation</a>
434
for further information.</dd>
435
436
<dt><img alt="(uncommon)" src="/errorlogs/images/purple-ball.gif"><a tag=
437
"getopt.h">getopt.h</a></dt>
438
439
<dd><tt>&lt;getopt.h&gt;</tt> is conflicting with <tt>unistd.h</tt>.</dd>
440
441
<dt><img alt="(common)" src="/errorlogs/images/blue-ball.gif"><a tag=
442
"install">install error</a></dt>
320
443
321
<dd>There was an error during installation.</dd>
444
<dd>There was an error during installation.</dd>
322
445
323
<dt><img alt="*" src="/errorlogs/images/green-ball.gif"><a tag=
446
<dt><img alt="(common)" src="/errorlogs/images/blue-ball.gif"><a tag=
324
"nfs">NFS</a></dt>
447
"lc_r">lib c_r not found</a></dt>
325
448
326
<dd>There was either a temporary NFS error on the build system
449
<dd>This library has not yet been ported to e.g. the
327
(which is not your fault), or the WRKSRC is invalid (which is your
450
Sparc. (This may have been fixed recently).</dd>
328
fault).</dd>
329
451
330
<dt><img alt="*" src="/errorlogs/images/green-ball.gif"><a tag=
452
<dt><img alt="(common)" src="/errorlogs/images/blue-ball.gif"><a tag=
331
"libdepends">LIB_DEPENDS</a></dt>
453
"libdepends">LIB_DEPENDS</a></dt>
332
454
333
<dd>The <tt>LIB_DEPENDS</tt> line specifies a library name
455
<dd>The <tt>LIB_DEPENDS</tt> line specifies a library name
334
incorrectly. This often happens when a port is upgraded and the
456
incorrectly. This often happens when a port is upgraded and the
335
shared library version number changes.</dd>
457
shared library version number changes.</dd>
336
458
337
<dt><img alt="*" src="/errorlogs/images/green-ball.gif"><a tag=
459
<dt><img alt="(common)" src="/errorlogs/images/blue-ball.gif"><a tag=
338
"ld">linker error</a></dt>
460
"ld">linker error</a></dt>
339
461
340
<dd>There is a linker error which is caused by something other than
462
<dd>There is a linker error which is caused by something other than
341
those flagged by e.g. MOTIF or MOTIFLIB.</dd>
463
those flagged by e.g. MOTIF or MOTIFLIB.</dd>
342
464
343
<dt><img alt="*" src="/errorlogs/images/green-ball.gif"><a tag=
465
<dt><img alt="(common)" src="/errorlogs/images/blue-ball.gif"><a tag=
466
"makefile">makefile</a></dt>
467
468
<dd>There is an error in the <tt>Makefile</tt>, possibly in the default
469
targets.</dd>
470
471
<dt><img alt="(uncommon)" src="/errorlogs/images/purple-ball.gif"><a tag=
472
"malloc.h">malloc.h</a></dt>
473
474
<dd>Including <tt>&lt;malloc.h&gt;</tt> is now deprecated in favor of
475
<tt>&lt;stdlib.h&gt;</tt>.</dd>
476
477
<dt><img alt="(uncommon)" src="/errorlogs/images/purple-ball.gif"><a tag=
344
"manpage">manpage</a></dt>
478
"manpage">manpage</a></dt>
345
479
346
<dd>There is a manpage listed in a <tt>MAN?</tt> macro that doesn't
480
<dd>There is a manpage listed in a <tt>MAN?</tt> macro that does not
347
exist or is not installed in the right place.</dd>
481
exist or is not installed in the right place.</dd>
348
482
349
<dt><img alt="*" src="/errorlogs/images/green-ball.gif"><a tag=
483
<dt><img alt="(common)" src="/errorlogs/images/blue-ball.gif"><a tag=
350
"header">missing header</a></dt>
484
"header">missing header</a></dt>
351
485
352
<dd>There is a missing header file. This is usually caused by
486
<dd>There is a missing header file. This is usually caused by
353
either (1) a missing dependency, or (2) specifying an incorrect
487
either (1) a missing dependency, or (2) specifying an incorrect
354
location with <tt>-I</tt> in the compiler command line.</dd>
488
location with <tt>-I</tt> in the compiler command line.</dd>
355
489
356
<dt><img alt="*" src="/errorlogs/images/green-ball.gif"><a tag=
490
<dt><img alt="(uncommon)" src="/errorlogs/images/purple-ball.gif"><a tag=
357
"motif">MOTIF</a></dt>
491
"motif">MOTIF</a></dt>
358
492
359
<dd>This port requires Motif but does not define
493
<dd>This port requires Motif but does not define
360
<tt>REQUIRES_MOTIF</tt>. See the <a href=
494
<tt>REQUIRES_MOTIF</tt>. See the <a href=
361
"http://www.freebsd.org/handbook/porting.html#PORTING-MOTIF">handbook</a>
495
"http://www.freebsd.org/doc/en_US.ISO8859-1/books/porters-handbook/porting-motif.html">handbook</a>
362
for details.</dd>
496
for details.</dd>
363
497
364
<dt><img alt="*" src="/errorlogs/images/green-ball.gif"><a tag=
498
<dt><img alt="(uncommon)" src="/errorlogs/images/purple-ball.gif"><a tag=
365
"motiflib">MOTIFLIB</a></dt>
499
"motiflib">MOTIFLIB</a></dt>
366
500
367
<dd>This port requires Motif but does not refer to the libraries
501
<dd>This port requires Motif but does not refer to the libraries
368
using <tt>${MOTIFLIB}</tt>. See <a href=
502
using <tt>${MOTIFLIB}</tt>. See <a href=
369
"http://www.freebsd.org/handbook/porting.html#PORTING-MOTIF">handbook</a>
503
"http://www.freebsd.org/doc/en_US.ISO8859-1/books/porters-handbook/porting-motif.html">handbook</a>
370
for details.</dd>
504
for details.</dd>
371
505
372
<dt><img alt="*" src="/errorlogs/images/green-ball.gif"><a tag=
506
<dt><img alt="(uncommon)" src="/errorlogs/images/purple-ball.gif"><a tag=
373
"mtree">mtree</a></dt>
507
"mtree">mtree</a></dt>
374
508
375
<dd>The port leaves <tt>${PREFIX}</tt> in a state that is not
509
<dd>The port leaves <tt>${PREFIX}</tt> in a state that is not
376
consistent with the mtree definiton after <tt>pkg_delete</tt>. This
510
consistent with the mtree definition after <tt>pkg_delete</tt>. This
377
usually means some files are missing from <tt>PLIST</tt>. It could
511
usually means some files are missing from <tt>PLIST</tt>. It could
378
also mean that your installation scripts create files or
512
also mean that your installation scripts create files or
379
directories not properly deleted by the deinstallation scripts.
513
directories not properly deleted by the deinstallation scripts.
Lines 381-422 Link Here
381
it is not supposed to, or incorrectly modifying some directory's
515
it is not supposed to, or incorrectly modifying some directory's
382
permission.</dd>
516
permission.</dd>
383
517
384
<dt><img alt="*" src="/errorlogs/images/green-ball.gif"><a tag=
518
<dt><img alt="(common)" src="/errorlogs/images/blue-ball.gif"><a tag=
385
"newgcc">new compiler error</a></dt>
519
"newgcc">new compiler error</a></dt>
386
520
387
<dd>The new gcc (2.95.x) doesn't like the source code. This is
521
<dd>The new gcc (2.95.x or above) does not like the source code. This is
388
usually due to stricter C++ type checking or changes in register
522
usually due to stricter C++ type checking or changes in register
389
allocation policy.</dd>
523
allocation policy.</dd>
390
524
391
<dt><img alt="*" src="/errorlogs/images/green-ball.gif"><a tag=
525
<dt><img alt="(transient)" src="/errorlogs/images/green-ball.gif"><a tag=
526
"nfs">NFS</a></dt>
527
528
<dd>There was either a temporary NFS error on the build system
529
(which is not your fault), or the <tt>WRKSRC</tt> is invalid
530
(which is your fault).</dd>
531
532
<dt><img alt="(common)" src="/errorlogs/images/blue-ball.gif"><a tag=
392
"patch">patch</a></dt>
533
"patch">patch</a></dt>
393
534
394
<dd>One or more of the patches failed.</dd>
535
<dd>One or more of the patches failed.</dd>
395
536
396
<dt><img alt="*" src="/errorlogs/images/green-ball.gif"><a tag=
537
<dt><img alt="(common)" src="/errorlogs/images/blue-ball.gif"><a tag=
538
"perl">perl</a></dt>
539
540
<dd><tt>perl</tt> is no longer included by default in the base
541
system, but your port's configuration process depends on it. While
542
this change helps avoid having a stale version of <tt>perl</tt>
543
in the base system, it also means that many ports now need to include
544
<tt>USE_PERL5</tt>.</dd>
545
546
<dt><img alt="(uncommon)" src="/errorlogs/images/purple-ball.gif"><a tag=
397
"perl5">perl5</a></dt>
547
"perl5">perl5</a></dt>
398
548
399
<dd>There is a problem in processing a <tt>perl5</tt> module.</dd>
549
<dd>There is a problem in processing a <tt>perl5</tt> module.</dd>
400
550
401
<dt><img alt="*" src="/errorlogs/images/green-ball.gif"><a tag=
551
<dt><img alt="(common)" src="/errorlogs/images/blue-ball.gif"><a tag=
402
"plist">PLIST</a></dt>
552
"plist">PLIST</a></dt>
403
553
404
<dd>There is a missing item in the PLIST. Note that this is often
554
<dd>There is a missing item in the <tt>PLIST</tt>. Note that this is
405
caused by an earlier error that went undetected. In this case, you
555
often caused by an earlier error that went undetected. In this case,
406
should fix the error and also the build process so it will fail
556
you should fix the error and also the build process so it will fail
407
upon an error instead of continuing, since that makes debugging
557
upon an error instead of continuing, since that makes debugging
408
that much harder.</dd>
558
that much harder.</dd>
409
559
410
<dt><img alt="*" src="/errorlogs/images/green-ball.gif"><a tag=
560
<dt><img alt="(common)" src="/errorlogs/images/blue-ball.gif"><a tag=
561
"pod2man">pod2man</a></dt>
562
563
<dd><tt>perl</tt> is no longer included by default in the base
564
system, but your port's documentation process depends on it. While
565
this change helps avoid having a stale version of <tt>perl</tt>
566
in the base system, it also means that many ports now need to include
567
<tt>USE_PERL5</tt>.</dd>
568
569
<dt><img alt="(common)" src="/errorlogs/images/blue-ball.gif"><a tag=
570
"process">process failed</a></dt>
571
572
<dd>The <tt>make</tt> process terminated unexpectedly, due to
573
something like a signal 11 or bus error.</dd>
574
575
<dt><img alt="(uncommon)" src="/errorlogs/images/purple-ball.gif"><a tag=
576
"python">python</a></dt>
577
578
<dd>The <tt>Makefile</tt> needs to define <tt>USE_PYTHON</tt>.</dd>
579
580
<dt><img alt="(uncommon)" src="/errorlogs/images/purple-ball.gif"><a tag=
411
"runaway">runaway process</a></dt>
581
"runaway">runaway process</a></dt>
412
582
413
<dd>Your make package process was killed because it took too long.
583
<dd>Your <tt>make package</tt> process was killed because it took
414
(More accurately, it did not produce any output for a long time.)
584
too long. (More accurately, it did not produce any output for a long
415
It is probably because there is a process spinning in an infinite
585
time.) It is probably because there is a process spinning in an infinite
416
loop. Please check the log to determine the exact cause of the
586
loop. Please check the log to determine the exact cause of the
417
problem.</dd>
587
problem.</dd>
418
588
419
<dt><img alt="*" src="/errorlogs/images/green-ball.gif"><a tag=
589
<dt><img alt="(uncommon)" src="/errorlogs/images/purple-ball.gif"><a tag=
590
"sed">sed</a></dt>
591
592
<dd><tt>sed</tt> is complaining about some kind of bogus regular
593
expression, probably as a side-effect of its being invoked by
594
<tt>${REINPLACE_COMMAND}</tt>. This is often a result of having
595
replaced usages of <tt>perl</tt> in the <tt>Makefile</tt> with usages
596
of <tt>${REINPLACE_COMMAND}</tt> but having left
597
<tt>perl</tt>-specific regexps in place.</dd>
598
599
<dt><img alt="(uncommon)" src="/errorlogs/images/purple-ball.gif"><a tag=
600
"soundcard.h">soundcard.h</a></dt>
601
602
<dd><tt>machine/soundcard.h</tt> has been moved.</dd>
603
604
<dt><img alt="(uncommon)" src="/errorlogs/images/purple-ball.gif"><a tag=
605
"values.h">values.h</a></dt>
606
607
<dd><tt>values.h</tt> has been moved.</dd>
608
609
<dt><img alt="(uncommon)" src="/errorlogs/images/purple-ball.gif"><a tag=
610
"stdio">stdio</a></dt>
611
612
<dd>You need to bring your port up to date with the current
613
<tt>&lt;stdio.h&gt;</tt>.</dd>
614
615
<dt><img alt="(uncommon)" src="/errorlogs/images/purple-ball.gif"><a tag=
616
"stl">stl</a></dt>
617
618
<dd>Your port requires the <tt>STL</tt> library but cannot find it.</dd>
619
620
<dt><img alt="(uncommon)" src="/errorlogs/images/purple-ball.gif"><a tag=
621
"struct">struct changes</a></dt>
622
623
<dd>Your port is trying to refer to structure elements that are not
624
really there. This is often due to changes in the underlying
625
include files.</dd>
626
627
<dt><img alt="(uncommon)" src="/errorlogs/images/purple-ball.gif"><a tag=
420
"texinfo">texinfo</a></dt>
628
"texinfo">texinfo</a></dt>
421
629
422
<dd>The new <tt>makeinfo</tt> cannot process a texinfo source file.
630
<dd>The new <tt>makeinfo</tt> cannot process a texinfo source file.
Lines 424-455 Link Here
424
through if you are sure it's correct regardless of what
632
through if you are sure it's correct regardless of what
425
<tt>makeinfo</tt> says.</dd>
633
<tt>makeinfo</tt> says.</dd>
426
634
427
<dt><img alt="*" src="/errorlogs/images/green-ball.gif"><a tag=
635
<dt><img alt="(uncommon)" src="/errorlogs/images/purple-ball.gif"><a tag=
636
"wait">union wait</a></dt>
637
638
<dd>The compiler could not calculate the storage size of an object,
639
often due to misuse of a union.</dd>
640
641
<dt><img alt="(uncommon)" src="/errorlogs/images/purple-ball.gif"><a tag=
428
"usexlib">USE_XLIB</a></dt>
642
"usexlib">USE_XLIB</a></dt>
429
643
430
<dd>You should specify <tt>USE_XLIB</tt> for this port since it
644
<dd>You should specify <tt>USE_XLIB</tt> for this port since it
431
appears to use X.</dd>
645
appears to use X.</dd>
432
646
433
<dt><img alt="*" src="/errorlogs/images/green-ball.gif"><a tag=
647
<dt><img alt="(uncommon)" src="/errorlogs/images/purple-ball.gif"><a tag=
434
"wrkdir">WRKDIR</a></dt>
648
"wrkdir">WRKDIR</a></dt>
435
649
436
<dd>The port is attempting to change something outside
650
<dd>The port is attempting to change something outside
437
<tt>${WRKDIR}</tt>. See <a href=
651
<tt>${WRKDIR}</tt>. See <a href=
438
"http://www.freebsd.org/handbook/porting.html#PORTING-WRKDIR">handbook</a>
652
"http://www.freebsd.org/doc/en_US.ISO8859-1/books/porters-handbook/porting-wrkdir.html">handbook</a>
439
for details.</dd>
653
for details.</dd>
440
654
441
<dt><img alt="*" src="/errorlogs/images/green-ball.gif"><a tag=
655
<dt><img alt="(uncommon)" src="/errorlogs/images/purple-ball.gif"><a tag=
442
"xfree4man">X manpage</a></dt>
656
"xfree4man">X manpage</a></dt>
443
657
444
<dd>This port doesn't install a manpage but imake rules are
658
<dd>This port does not install a manpage but <tt>imake</tt> rules are
445
generating commands to convert manpages to HTML format. This is
659
generating commands to convert manpages to HTML format. This is
446
most likely fixed by changing <tt>ComplexProgramTarget()</tt> in
660
most likely fixed by changing <tt>ComplexProgramTarget()</tt> in
447
Imakefile to <tt>ComplexProgramTargetNoMan()</tt>. Note that
661
<tt>Imakefile</tt> to <tt>ComplexProgramTargetNoMan()</tt>. Note that
448
defining <tt>NO_INSTALL_MANPAGES</tt> in the Makefile is no longer
662
defining <tt>NO_INSTALL_MANPAGES</tt> in the <tt>Makefile</tt> is no
449
sufficient in XFree86-4.</dd>
663
longer sufficient in XFree86-4.</dd>
450
664
451
<dt><img alt="*" src="/errorlogs/images/green-ball.gif"><a tag=
665
<dt><img alt="(common)" src="/errorlogs/images/blue-ball.gif"><a tag=
452
"unknown">???</a></dt>
666
"unknown">??? (unknown)</a></dt>
453
667
454
<dd>The automated script cannot even guess what is wrong with your
668
<dd>The automated script cannot even guess what is wrong with your
455
port. Either the script is really stupid (more likely), or your
669
port. Either the script is really stupid (more likely), or your
Lines 462-465 Link Here
462
page</a></center>
676
page</a></center>
463
</body>
677
</body>
464
</html>
678
</html>
465

Return to bug 47194