aboutsummaryrefslogtreecommitdiff
path: root/Tools/portbuild/errorlogs/index.shtml
blob: 2912bee243c5c221ec5558aa8c843a07e3b79f52 (plain) (blame)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761
762
763
764
765
766
767
768
769
770
771
772
773
774
775
776
777
778
779
780
781
782
783
784
785
786
787
788
789
790
791
792
793
794
795
796
797
798
799
800
801
802
803
804
805
806
807
808
809
810
811
812
813
814
815
816
817
818
819
820
821
822
823
824
825
826
827
828
829
830
831
832
833
834
835
836
837
838
839
840
841
842
843
844
845
846
847
848
849
850
851
852
853
854
855
856
857
858
859
860
861
862
863
864
865
866
867
868
869
870
871
872
873
874
875
876
877
878
879
880
881
882
883
884
885
886
887
888
889
890
891
892
893
894
895
896
897
898
899
900
901
902
903
904
905
906
907
908
909
910
911
912
913
914
915
916
917
918
919
920
921
922
923
924
925
926
927
928
929
930
931
932
933
934
935
936
937
938
939
940
941
942
943
944
945
946
947
948
949
950
951
952
953
954
955
956
957
958
959
960
961
962
963
964
965
966
967
968
969
970
971
972
973
974
975
976
977
978
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 3.2//EN">
<html>
<head>
<meta name="generator" content="HTML Tidy, see www.w3.org">
<title>FreeBSD Package building logs and errors</title>
</head>
<body>
<h1><font color="#990000">FreeBSD Package building logs and errors</font></h1>

<p>FreeBSD maintains a build farm (the "pointyhat cluster") that is used
to build all packages across all supported architectures and major releases.
This page contains the build logs and errors for all the ports built by
the cluster.  See the <a href="#notes">notes</a> for additional information,
or the <a href="#errorlist">types of package errors detected</a>.</p>

<h4><font color="#990000">
Port cross-reference summaries
</font></h4>
<p>These live on
<a href="http://portsmon.FreeBSD.org/index.html">portsmon.FreeBSD.org</a>.</p>
<dl>

<dd><img alt="*" src="/errorlogs/images/blue-ball.gif"> Build errors
<a href="http://portsmon.FreeBSD.org/portserrs.py">by portname</a>;
<a href="http://portsmon.FreeBSD.org/portscrossref.py">by portname vs. build environment</a>;
<a href="http://portsmon.FreeBSD.org/portserrcounts.py">by error type vs. build environment</a></dd>
<dd><img alt="*" src="/errorlogs/images/blue-ball.gif"> Problem Reports
for <a href="http://portsmon.FreeBSD.org/portsprsbyexplanation.py?explanation=existing">existing ports</a>;
for <a href="http://portsmon.FreeBSD.org/portsprsbyexplanation.py?explanation=new">new ports</a>;
for <a href="http://portsmon.FreeBSD.org/portsprsbyexplanation.py?explanation=framework">the ports framework</a>;
for <a href="http://portsmon.FreeBSD.org/portsprsbyexplanation.py?explanation=repocopy">repocopies requested</a>;
for <a href="http://portsmon.FreeBSD.org/portsprsbyexplanation.py?explanation=unknown">unknown</a></dd>
<dd><img alt="*" src="/errorlogs/images/blue-ball.gif"> Build Errors and
Problem Reports
<a href="http://portsmon.FreeBSD.org/portsconcordance.py">by portname</a>;
<a href="http://portsmon.FreeBSD.org/portsconcordanceformaintainer.py">for one maintainer</a>;
<a href="http://portsmon.FreeBSD.org/portsconcordanceforbroken.py">for broken ports</a>;
<a href="http://portsmon.FreeBSD.org/portsconcordancefordeprecated.py">for deprecated ports</a>;
<a href="http://portsmon.FreeBSD.org/portsconcordanceforforbidden.py">for forbidden ports</a></dd>
<dd><img alt="*" src="/errorlogs/images/blue-ball.gif"> Everything about
<a href="http://portsmon.FreeBSD.org/portoverview.py">one port</a></dd>
<dd><img alt="*" src="/errorlogs/images/blue-ball.gif"> The
<a href="http://portsmon.FreeBSD.org/index.html">complete list of all reports</a></dd>
</dl>

<h4><font color="#990000">
New build failures
</font></h4>
<p>Check here to find the most recent error log from your port.</p>

<!--#config timefmt="%F %R" -->

<dl>
<dd>
<img alt="*" src="/errorlogs/images/yellow-ball.gif"> New build
failures on 7.x-stable:
<a href="amd64-7-failure.html">amd64</a>
<a href="i386-7-failure.html">i386</a>
<a href="ia64-7-failure.html">ia64</a>
<a href="sparc64-7-failure.html">sparc64</a>
<br>
<img alt="*" src="/errorlogs/images/yellow-ball.gif"> New build
failures on 8.x-stable:
<a href="amd64-8-failure.html">amd64</a>
<a href="i386-8-failure.html">i386</a>
<a href="ia64-8-failure.html">ia64</a>
<a href="powerpc-8-failure.html">powerpc</a>
<a href="sparc64-8-failure.html">sparc64</a>
<br>
<img alt="*" src="/errorlogs/images/yellow-ball.gif"> New build
failures on 9.x-current:
<a href="amd64-9-failure.html">amd64</a>
<a href="i386-9-failure.html">i386</a>
<a href="ia64-9-failure.html">ia64</a>
<a href="powerpc-9-failure.html">powerpc</a>
<a href="sparc64-9-failure.html">sparc64</a>
<br>
<br>
<img alt="*" src="/errorlogs/images/yellow-ball.gif"> New build failures on 7.x-stable with experimental port patches:
<a href="amd64-7-exp-failure.html">amd64</a>
<a href="i386-7-exp-failure.html">i386</a>
<br>
<img alt="*" src="/errorlogs/images/yellow-ball.gif"> New build failures on 8.x-stable with experimental port patches:
<a href="amd64-8-exp-failure.html">amd64</a>
<a href="i386-8-exp-failure.html">i386</a>
<br>
<img alt="*" src="/errorlogs/images/yellow-ball.gif"> New build failures on 9.x-current with experimental port patches:
<a href="amd64-9-exp-failure.html">amd64</a>
<a href="i386-9-exp-failure.html">i386</a>
<br>
</dd>
</dl>

<h4><font color="#990000">
Error logs
</font></h4>

<dl>
<dd>
<img alt="*" src="/errorlogs/images/yellow-ball.gif"> Previous run
on 7.x-stable:
<a href="amd64-7-full/">amd64</a>
<a href="i386-7-full/">i386</a>
<a href="ia64-7-full/">ia64</a>
<a href="sparc64-7-full/">sparc64</a>
<br>
<img alt="*" src="/errorlogs/images/yellow-ball.gif"> Current run
on 7.x-stable:
<a href="amd64-7-latest/">amd64</a>
<a href="i386-7-latest/">i386</a>
<a href="ia64-7-latest/">ia64</a>
<a href="sparc64-7-latest/">sparc64</a>
<br>
<img alt="*" src="/errorlogs/images/yellow-ball.gif"> Previous run
on 8.x-stable:
<a href="amd64-8-full/">amd64</a>
<a href="i386-8-full/">i386</a>
<a href="ia64-8-full/">ia64</a>
<a href="powerpc-8-full/">powerpc</a>
<a href="sparc64-8-full/">sparc64</a>
<br>
<img alt="*" src="/errorlogs/images/yellow-ball.gif"> Current run
on 8.x-stable:
<a href="amd64-8-latest/">amd64</a>
<a href="i386-8-latest/">i386</a>
<a href="ia64-8-latest/">ia64</a>
<a href="powerpc-8-latest/">powerpc</a>
<a href="sparc64-8-latest/">sparc64</a>
<br>
<img alt="*" src="/errorlogs/images/yellow-ball.gif"> Previous run
on 9.x-current:
<a href="amd64-9-full/">amd64</a>
<a href="i386-9-full/">i386</a>
<a href="ia64-9-full/">ia64</a>
<a href="powerpc-9-full/">powerpc</a>
<a href="sparc64-9-full/">sparc64</a>
<br>
<img alt="*" src="/errorlogs/images/yellow-ball.gif"> Current run
on 9.x-current:
<a href="amd64-9-latest/">amd64</a>
<a href="i386-9-latest/">i386</a>
<a href="ia64-9-latest/">ia64</a>
<a href="powerpc-9-latest/">powerpc</a>
<a href="sparc64-9-latest/">sparc64</a>
<br>
<br>
<img alt="*" src="/errorlogs/images/yellow-ball.gif"> Previous run
on 7.x-stable with experimental port patches:
<a href="amd64-7-exp-full/">amd64</a>
<a href="i386-7-exp-full/">i386</a>
<br>
<img alt="*" src="/errorlogs/images/yellow-ball.gif"> Current run
on 7.x-stable with experimental port patches:
<a href="amd64-7-exp-latest/">amd64</a>
<a href="i386-7-exp-latest/">i386</a>
<br>
<img alt="*" src="/errorlogs/images/yellow-ball.gif"> Previous run
on 8.x-stable with experimental port patches:
<a href="amd64-8-exp-full/">amd64</a>
<a href="i386-8-exp-full/">i386</a>
<br>
<img alt="*" src="/errorlogs/images/yellow-ball.gif"> Current run
on 8.x-stable with experimental port patches:
<a href="amd64-8-exp-latest/">amd64</a>
<a href="i386-8-exp-latest/">i386</a>
<br>
<img alt="*" src="/errorlogs/images/yellow-ball.gif"> Previous run
on 9.x-current with experimental port patches:
<a href="amd64-9-exp-full/">amd64</a>
<a href="i386-9-exp-full/">i386</a>
<br>
<img alt="*" src="/errorlogs/images/yellow-ball.gif"> Current run
on 9.x-current with experimental port patches:
<a href="amd64-9-exp-latest/">amd64</a>
<a href="i386-9-exp-latest/">i386</a>
</dd>
</dl>

<h4><font color="#990000">
Build logs (errors and otherwise)
</font></h4>

<dl>
<dd>
<img alt="*" src="/errorlogs/images/orange-ball.gif">Previous run
on 7.x-stable:
<a href="amd64-7-full-logs">amd64</a>
<a href="i386-7-full-logs">i386</a>
<a href="ia64-7-full-logs">ia64</a>
<a href="sparc64-7-full-logs">sparc64</a>
<br>
<img alt="*" src="/errorlogs/images/orange-ball.gif">Current run on
7.x-stable:
<a href="amd64-7-latest-logs">amd64</a>
<a href="i386-7-latest-logs">i386</a>
<a href="ia64-7-latest-logs">ia64</a>
<a href="sparc64-7-latest-logs">sparc64</a>
<br>
<img alt="*" src="/errorlogs/images/orange-ball.gif">Previous run
on 8.x-stable:
<a href="amd64-8-full-logs">amd64</a>
<a href="i386-8-full-logs">i386</a>
<a href="ia64-8-full-logs">ia64</a>
<a href="powerpc-8-full-logs">powerpc</a>
<a href="sparc64-8-full-logs">sparc64</a>
<br>
<img alt="*" src="/errorlogs/images/orange-ball.gif">Current run on
8.x-stable:
<a href="amd64-8-latest-logs">amd64</a>
<a href="i386-8-latest-logs">i386</a>
<a href="ia64-8-latest-logs">ia64</a>
<a href="powerpc-8-latest-logs">powerpc</a>
<a href="sparc64-8-latest-logs">sparc64</a>
<br>
<img alt="*" src="/errorlogs/images/orange-ball.gif">Previous run
on 9.x-current:
<a href="amd64-9-full-logs">amd64</a>
<a href="i386-9-full-logs">i386</a>
<a href="ia64-9-full-logs">ia64</a>
<a href="powerpc-9-full-logs">powerpc</a>
<a href="sparc64-9-full-logs">sparc64</a>
<br>
<img alt="*" src="/errorlogs/images/orange-ball.gif">Current run on
9.x-current:
<a href="amd64-9-latest-logs">amd64</a>
<a href="i386-9-latest-logs">i386</a>
<a href="ia64-9-latest-logs">ia64</a>
<a href="powerpc-9-latest-logs">powerpc</a>
<a href="sparc64-9-latest-logs">sparc64</a>
<br>
<br>
<img alt="*" src="/errorlogs/images/orange-ball.gif">Previous run
on 7.x-stable with experimental port patches:
<a href="amd64-7-exp-full-logs">amd64</a>
<a href="i386-7-exp-full-logs">i386</a>
<br>
<img alt="*" src="/errorlogs/images/orange-ball.gif">Current run on
7.x-stable with experimental port patches:
<a href="amd64-7-exp-latest-logs">amd64</a>
<a href="i386-7-exp-latest-logs">i386</a>
<br>
<img alt="*" src="/errorlogs/images/orange-ball.gif">Previous run
on 8.x-stable with experimental port patches:
<a href="amd64-8-exp-full-logs">amd64</a>
<a href="i386-8-exp-full-logs">i386</a>
<br>
<img alt="*" src="/errorlogs/images/orange-ball.gif">Current run on
8.x-stable with experimental port patches:
<a href="amd64-8-exp-latest-logs">amd64</a>
<a href="i386-8-exp-latest-logs">i386</a>
<br>
<img alt="*" src="/errorlogs/images/orange-ball.gif">Previous run
on 9.x-current with experimental port patches:
<a href="amd64-9-exp-full-logs">amd64</a>
<a href="i386-9-exp-full-logs">i386</a>
<br>
<img alt="*" src="/errorlogs/images/orange-ball.gif">Current run on
9.x-current with experimental port patches:
<a href="amd64-9-exp-latest-logs">amd64</a>
<a href="i386-9-exp-latest-logs">i386</a>
<br>
</dd>
</dl>

<h4><font color="#990000">
Packages
</font></h4>

<dl>
<dd>
<img alt="*" src="/errorlogs/images/purple-ball.gif"> Packages from
latest run on 6-stable:
<a href="amd64-6-packages-latest/">amd64</a>
<a href="i386-6-packages-latest/">i386</a>
<a href="sparc64-6-packages-latest/">sparc64</a>
<br>
<img alt="*" src="/errorlogs/images/purple-ball.gif"> Packages from
latest run on 7-stable:
<a href="amd64-7-packages-latest/">amd64</a>
<a href="i386-7-packages-latest/">i386</a>
<a href="ia64-7-packages-latest/">ia64</a>
<a href="sparc64-7-packages-latest/">sparc64</a>
<br>
<img alt="*" src="/errorlogs/images/purple-ball.gif"> Packages from
latest run on 8-stable:
<a href="amd64-8-packages-latest/">amd64</a>
<a href="i386-8-packages-latest/">i386</a>
<a href="ia64-8-packages-latest/">ia64</a>
<a href="powerpc-8-packages-latest/">powerpc</a>
<a href="sparc64-8-packages-latest/">sparc64</a>
<br>
<img alt="*" src="/errorlogs/images/purple-ball.gif"> Packages from
latest run on 9-current:
<a href="amd64-9-packages-latest/">amd64</a>
<a href="i386-9-packages-latest/">i386</a>
<a href="ia64-9-packages-latest/">ia64</a>
<a href="powerpc-9-packages-latest/">powerpc</a>
<a href="sparc64-9-packages-latest/">sparc64</a>
<br>
<br>
<img alt="*" src="/errorlogs/images/purple-ball.gif"> Package
<a href="packagestats.html">building statistics</a> (current state of all package builds)
</dd>
</dl>

<h4><font color="#990000">
Archive
</font></h4>

<dl>
<dd><img alt="*" src="/errorlogs/images/red-ball.gif"> All error
logs:
<a href="amd64-errorlogs/">amd64</a>
<a href="i386-errorlogs/">i386</a>
<a href="ia64-errorlogs/">ia64</a>
<a href="powerpc-errorlogs/">powerpc</a>
<a href="sparc64-errorlogs/">sparc64</a>
<br>
<img alt="*" src="/errorlogs/images/red-ball.gif"> All portbuild
logs:
<a href="amd64-buildlogs/">amd64</a>
<a href="i386-buildlogs/">i386</a>
<a href="ia64-buildlogs/">ia64</a>
<a href="powerpc-buildlogs/">powerpc</a>
<a href="sparc64-buildlogs/">sparc64</a>
</dd>
</dl>

<a name="notes">
<h3><font color="#990000">Additional information</font></h3>
</a>

<p>All of the "Current run" links are possibly in progress and may be
partial, so keep that in mind if there appear to be some missing.</p>

<p>None of the ports marked <tt>IS_INTERACTIVE</tt> or
<tt>NO_PACKAGE</tt> are built any more -- if you have ports that
fall into those categories, assume their packages or distfiles will
never show up in ftp sites or CDROMs. <tt>RESTRICTED</tt> packages
are built and deleted (using "<tt>make
clean-restricted-list</tt>"). <tt>NO_CDROM</tt> packages are built
but deleted (using "<tt>make clean-cdrom-list</tt>") before being
put on a CDROM.</p>

<p>See also the <a href="errors.html">types of errors detected</a>.</p>

<p>Notes on the building process:</p>

<ul>
<li><em>Every</em> port is built in its own chroot environment
<!-- MCL 20090823 broken links
(
<a href="i386-7-bindist.tar">tarball for 7.x-stable</a>
|<a href="i386-8-bindist.tar">tarball for 8.x-stable</a>
|<a href="i386-9-bindist.tar">tarball for 9.x-current</a>
)
-->
, starting with an
empty <tt>/usr/local</tt> and <tt>/usr/X11R6</tt>. <a name=
"pkgadd">The dependencies are installed as packages</a> just before
the build. You can see the list of dependencies on the third line
of the log -- the "foo.tgz bar.tgz" stuff are the dependencies. To
make sure that these actually work, <tt>DEPENDS_TARGET</tt> is set
to "/usr/bin/true"; if you see "/usr/bin/true is up to date" or
some such, that means there is something wrong with the dependency
lines or the packages this port is depending on.</li>

<li>The build is done on a shared (read-only) <tt>/usr/ports</tt>
with <a href=
"http://www.freebsd.org/doc/en_US.ISO8859-1/books/porters-handbook/porting-wrkdir.html">
<tt>WRKDIRPREFIX</tt></a> set to <tt>/work</tt>. If your
<tt>WRKSRC</tt> looks funny, that's probably why.</li>

<li><tt>MASTER_SITE_OVERRIDE</tt> is pointing to pointyhat's distfile
dir, and <tt>MASTER_SITE_BACKUP</tt> is pointing to
ftp-master.freebsd.org or a local mirror. <!--Wrong!
The one on pointyhat is empty when the build starts,
and every successful build will copy distfiles to there.  This means
that if there are a few ports that share the same distfile, only
the first one will have to go to the original master site (provided
the second build starts after the first one ends). After the entire
build process, the distfiles are copied over to ftp.freebsd.org.
This means if your port built successfully once, you will never see
a "can't fetch distfile" error again.-->
Please pay attention to
<a href="http://people.freebsd.org/~ehaupt/distilator/">
Emanuel Haupt's distfile checker</a>
for that.</li>

<li>The ports are built on machines that are mostly running
 9-CURRENT, with some 8.x-STABLE machines.  If your port depends on
 the result of uname(3) or sysctl to determine the running version of
 FreeBSD, change it to use uname(1) instead (the builds use a dummy
 uname(1) that reports the target version of FreeBSD), or change it to
 use the value of the OSVERSION variable that can be passed in from
 the port makefile.  </li> </ul>

<a name="errorlist"></a>
<h2><font color="990000">Types of package errors detected</font></h2>

<p>Here is the <b>alphabetical list of current errors</b>
detected by the AI script.  Note that this is all just a rough guess --
it is merely for your aid.</p>

<p>Key:
<dl>
  <dt><img alt="(common)" src="/errorlogs/images/blue-ball.gif">The most common
    errors.</dt> 
  <dt><img alt="(uncommon)" src="/errorlogs/images/purple-ball.gif">Some less common
    errors.</dt> 
  <dt><img alt="(transient)" src="/errorlogs/images/green-ball.gif">Transient
    errors.  These may not be your fault.</dt> 
</dl>
</p>

<p>
<dl>
<dt><img alt="(common)" src="/errorlogs/images/blue-ball.gif"><a name=
"arch">arch</a></dt>

<dd>The port does not build on a particular architecture, due to
assembler or linker errors.  In some easy cases this is due to
not picking up the various <tt>ARCH</tt> configuration variables
in the Makefile; you'll see this via, e.g., a Sparc <tt>make</tt>
failing while looking for an i386 subdirectory.  For the 64-bit
architectures, a common problem is the assumption many programmers
make that pointers may be cast to and from 32-bit  ints.  In other cases
the problems run much deeper, in which case <tt>ONLY_FOR_ARCHS</tt>
may be needed.</dd>

<dt><img alt="(uncommon)" src="/errorlogs/images/purple-ball.gif"><a name=
"autoconf">autoconf</a></dt>

<dd>Your port depends on <tt>autoconf</tt>, but the <tt>Makefile</tt>
either doesn't have <tt>USE_AUTOCONF</tt>, or does not use
<tt>USE_AUTOCONF_VER</tt> correctly.</dd>

<dt><img alt="(uncommon)" src="/errorlogs/images/purple-ball.gif"><a name=
"autoheader">autoheader</a></dt>

<dd>Your port depends on <tt>autoheader</tt>, but the <tt>Makefile</tt>
cannot find it; set <tt>USE_AUTOHEADER</tt>.</dd>

<dt><img alt="(uncommon)" src="/errorlogs/images/purple-ball.gif"><a name=
"automake">automake</a></dt>

<dd>Your port depends on <tt>automake</tt>, but the <tt>Makefile</tt>
either doesn't have <tt>USE_AUTOMAKE</tt>, or does not use
<tt>USE_AUTOMAKE_VER</tt> correctly.</dd>

<dt><img alt="(common)" src="/errorlogs/images/blue-ball.gif"><a name=
"badc++">bad C++ code</a></dt>

<dd>There is a compiler error which is caused by something specific
to C++.</dd>

<dt><img alt="(common)" src="/errorlogs/images/blue-ball.gif"><a name=
"cc">compiler error</a></dt>

<dd>There is a C compiler error which is caused by something other
than e.g. "new compiler error".</dd>

<dt><img alt="(uncommon)" src="/errorlogs/images/purple-ball.gif"><a name=
"categories">CATEGORIES</a></dt>

<dd>The <tt>CATEGORIES</tt> line in <tt>Makefile</tt> includes an
invalid category.</dd>

<dt><img alt="(common)" src="/errorlogs/images/blue-ball.gif"><a name=
"checksum">checksum</a></dt>

<dd>The checksum of one or more of the files is incorrect.</dd>

<dt><img alt="(common)" src="/errorlogs/images/blue-ball.gif"><a name=
"clang">clang</a></dt>

<dd>Your code does not run with the the experimental <tt>clang</tt> compiler.  See
(TBA)
for further information.</dd>

<dt><img alt="(uncommon)" src="/errorlogs/images/purple-ball.gif"><a name=
"clang-bug">clang bug</a></dt>

<dd>You have tickled a bug in <tt>clang</tt> itself.  See
(TBA)
for further information.</dd>

<dt><img alt="(transient)" src="/errorlogs/images/green-ball.gif"><a name=
"cluster">cluster</a></dt>

<dd>There was some kind of transient error on the build cluster. It is not your
fault.</dd>

<dt><img alt="(uncommon)" src="/errorlogs/images/purple-ball.gif"><a name=
"compat6x">compat6x</a></dt>

<dd>This port needs to depend on a port <tt>misc/compat6x</tt>.</dd>

<dt><img alt="(common)" src="/errorlogs/images/blue-ball.gif"><a name=
"configure">configure error</a></dt>

<dd>The port's <tt>configure</tt> script produced some kind of
error.
(Note: using <tt>clang</tt> as the ports compiler can also trigger this message.)</dd>

<dt><img alt="(common)" src="/errorlogs/images/blue-ball.gif"><a name=
"coredump">coredump</a></dt>

<dd>Some process in the build chain dropped core. While your port may indeed 
be faulty, the process that dropped core should also be fixed.</dd>

<dt><img alt="(uncommon)" src="/errorlogs/images/purple-ball.gif"><a name=
"cpusetsize">cpusetsize</a></dt>

<dd>This port needs to catch up with the <tt>cpusetsize</tt> sysctl change in 9-CURRENT.</dd>

<dt><img alt="(common)" src="/errorlogs/images/blue-ball.gif"><a name=
"dependobj">depend object</a></dt>

<dd>The port is trying to reinstall a dependency that already
exists. This is usually caused by the first field of a
<tt>*_DEPENDS</tt> line (the <tt>obj</tt> of
<tt>obj:dir[:target]</tt>) indicating a file that is not installed
by the dependency, causing it to be rebuilt even though it has
already been <a href="#pkgadd">added from a package</a>.</dd>

<dt><img alt="(common)" src="/errorlogs/images/blue-ball.gif"><a name=
"dependpkg">depend package</a></dt>

<dd>There was an error during <a href="#pkgadd">adding dependencies
from packages</a>. It is the fault of the package being added, not
this port.</dd>

<dt><img alt="(uncommon)" src="/errorlogs/images/purple-ball.gif"><a name=
"dirent">dirent</a></dt>

<dd>The port has not caught up with the change to <code>scandir(3)</code>
as committed in FreeBSD version 800501.</dd>

<dt><img alt="(transient)" src="/errorlogs/images/green-ball.gif"><a name=
"df">disk full</a></dt>

<dd>The disk filled up on the build system. It is not your
fault.</dd>

<dt><img alt="(uncommon)" src="/errorlogs/images/purple-ball.gif"><a name=
"display">DISPLAY</a></dt>

<dd>This port requires an X display to build. There is nothing you
can do about it unless you can somehow make it not require an X
connection.</dd>

<dt><img alt="(common)" src="/errorlogs/images/blue-ball.gif"><a name=
"distinfo">distinfo update</a></dt>

<dd>The contents of <tt>distinfo</tt> does not match the list of
distfiles or patchfiles.</dd>

<dt><img alt="(common)" src="/errorlogs/images/blue-ball.gif"><a name=
"fetch">fetch</a></dt>

<dd>One or more of the files could not be fetched.</dd>

<dt><img alt="(uncommon)" src="/errorlogs/images/purple-ball.gif"><a name=
"fetch-timeout">fetch timeout</a></dt>

<dd>Your fetch process was killed because it took too long. (More
accurately, it did not produce any output for a long time.) Please
put sites with better connectivity near the beginning of
<tt>MASTER_SITES</tt>.</dd>

<dt><img alt="(uncommon)" src="/errorlogs/images/purple-ball.gif"><a name=
"forbidden">forbidden</a></dt>

<dd>Someone has marked this port as "forbidden", almost always due
to security concerns.  See the logfile for more information.</dd>

<dt><img alt="(uncommon)" src="/errorlogs/images/purple-ball.gif"><a name=
"gcc-bug">gcc bug</a></dt>

<dd>You have tickled a bug in gcc itself. See the
<a href="http://www.gnu.org/software/gcc/bugs.html">GNU bug report documentation</a>
for further information.</dd>

<dt><img alt="(common)" src="/errorlogs/images/blue-ball.gif"><a name=
"gcc4">gcc4</a></dt>

<dd>Your code does not run with the latest gcc version
See <a href="http://wiki.freebsd.org/gcc4">the wiki page</a>
for further information.</dd>

<dt><img alt="(common)" src="/errorlogs/images/blue-ball.gif"><a name=
"install">install error</a></dt>

<dd>There was an error during installation.</dd>

<dt><img alt="(common)" src="/errorlogs/images/blue-ball.gif"><a name=
"libdepends">LIB_DEPENDS</a></dt>

<dd>The <tt>LIB_DEPENDS</tt> line specifies a library name
incorrectly. This often happens when a port is upgraded and the
shared library version number changes.</dd>

<dt><img alt="(common)" src="/errorlogs/images/blue-ball.gif"><a name=
"ld">linker error</a></dt>

<dd>There is a linker error which is caused by something other than
those flagged elsewhere.
(Note: using <tt>clang</tt> as the ports compiler can also trigger this message.)</dd>

<dt><img alt="(common)" src="/errorlogs/images/blue-ball.gif"><a name=
"makefile">makefile</a></dt>

<dd>There is an error in the <tt>Makefile</tt>, possibly in the default
targets.</dd>

<dt><img alt="(uncommon)" src="/errorlogs/images/purple-ball.gif"><a name=
"manpage">manpage</a></dt>

<dd>There is a manpage listed in a <tt>MAN?</tt> macro that does not
exist or is not installed in the right place.</dd>

<dt><img alt="(common)" src="/errorlogs/images/blue-ball.gif"><a name=
"header">missing header</a></dt>

<dd>There is a missing header file. This is usually caused by
either (1) a missing dependency, or (2) specifying an incorrect
location with <tt>-I</tt> in the compiler command line.</dd>

<dt><img alt="(common)" src="/errorlogs/images/blue-ball.gif"><a name=
"mtree">mtree</a></dt>

<dd>The port leaves <tt>${PREFIX}</tt> in a state that is not
consistent with the mtree definition after <tt>pkg_delete</tt>. This
usually means some files are missing from <tt>PLIST</tt>. It could
also mean that your installation scripts create files or
directories not properly deleted by the deinstallation scripts.
Another possibility is that your port is deleting some directories
it is not supposed to, or incorrectly modifying some directory's
permission.</dd>

<dt><img alt="(uncommon)" src="/errorlogs/images/purple-ball.gif"><a name=
"nested_declaration">nested_declaration</a></dt>

<dd>There is a nested declaration in the source code.</dd>

<dt><img alt="(common)" src="/errorlogs/images/blue-ball.gif"><a name=
"newgcc">new compiler error</a></dt>

<dd>The newest version of gcc in the base does not like the source code. This is
usually due to stricter C++ type checking or changes in register
allocation policy.</dd>

<dt><img alt="(transient)" src="/errorlogs/images/green-ball.gif"><a name=
"nfs">NFS</a></dt>

<dd>There was either a temporary NFS error on the build system
(which is not your fault), or the <tt>WRKSRC</tt> is invalid
(which is your fault).</dd>

<dt><img alt="(common)" src="/errorlogs/images/blue-ball.gif"><a name=
"patch">patch</a></dt>

<dd>One or more of the patches failed.</dd>

<dt><img alt="(uncommon)" src="/errorlogs/images/purple-ball.gif"><a name=
"perl">perl</a></dt>

<dd><tt>perl</tt> is no longer included by default in the base
system, but your port's configuration process depends on it. While
this change helps avoid having a stale version of <tt>perl</tt>
in the base system, it also means that many ports now need to include
<tt>USE_PERL5</tt>.</dd>

<dt><img alt="(common)" src="/errorlogs/images/blue-ball.gif"><a name=
"plist">PLIST</a></dt>

<dd>There is a missing item in the <tt>PLIST</tt>. Note that this is
often caused by an earlier error that went undetected. In this case,
you should fix the error and also the build process so it will fail
upon an error instead of continuing, since that makes debugging
that much harder.</dd>

<dt><img alt="(uncommon)" src="/errorlogs/images/purple-ball.gif"><a name=
"process">process failed</a></dt>

<dd>The <tt>make</tt> process terminated unexpectedly, due to
something like a signal 11 or bus error.</dd>

<dt><img alt="(uncommon)" src="/errorlogs/images/purple-ball.gif"><a name=
"runaway">runaway process</a></dt>

<dd>Your <tt>make package</tt> process was killed because it took
too long. (More accurately, it did not produce any output for a long
time.) It is probably because there is a process spinning in an infinite
loop. Please check the log to determine the exact cause of the
problem.</dd>

<dt><img alt="(uncommon)" src="/errorlogs/images/purple-ball.gif"><a name=
"segfault">segfault</a></dt>

<dd>Some process in the build chain got a segmentation fault.</dd>

<dt><img alt="(uncommon)" src="/errorlogs/images/purple-ball.gif"><a name=
"sem_wait">sem_wait</a></dt>

<dd>This port needs to catch up with semaphore changes in 9-CURRENT.</dd>

<dt><img alt="(uncommon)" src="/errorlogs/images/purple-ball.gif"><a name=
"termios">termios</a></dt>

<dd>This port needs to catch up with the <tt>termios.h</tt> changes in src.</dd>

<dt><img alt="(uncommon)" src="/errorlogs/images/purple-ball.gif"><a name=
"threads">threads</a></dt>

<dd>There is a linker error which is caused by failing to find one of
the thread libraries.</dd>

<dt><img alt="(transient)" src="/errorlogs/images/green-ball.gif"><a name=
"truncated_distfile">truncated_distfile</a></dt>

<dd>A package node encountered an error during pkg_add. It is not your
fault.  Linimon is trying to figure out this problem.</dd>

<dt><img alt="(uncommon)" src="/errorlogs/images/purple-ball.gif"><a name=
"utmp_x">utmp_x</a></dt>

<dd>This port needs to catch up with the <tt>utmp_x.h</tt> changes in src.</dd>

<dt><img alt="(uncommon)" src="/errorlogs/images/purple-ball.gif"><a name=
"wrkdir">WRKDIR</a></dt>

<dd>The port is attempting to change something outside
<tt>${WRKDIR}</tt>. See <a href=
"http://www.freebsd.org/doc/en_US.ISO8859-1/books/porters-handbook/porting-wrkdir.html">handbook</a>
for details.</dd>

<dt><img alt="(common)" src="/errorlogs/images/blue-ball.gif"><a name=
"unknown">??? (unknown)</a></dt>

<dd>The automated script cannot even guess what is wrong with your
port.  <tt>portmgr</tt> tries to keep the <tt>processonelog</tt> script
reasonably efficient while covering as many errors as possible, but many
errors are not common enough to try to catch.</dd>
</dl>

<p>Here is an <b>alphabetical list of obsolete errors</b></a>
that used to be detected by the AI script, but are now uncommon enough to
be skipped:</p>

<dl>
<dt><img alt="(uncommon)" src="/errorlogs/images/purple-ball.gif"><a name=
"alignment">alignment</a></dt>

<dd>You've managed to confuse the assembler with a misaligned
structure.</dd>

<dt><img alt="(uncommon)" src="/errorlogs/images/purple-ball.gif"><a name=
"apxs">apxs</a></dt>

<dd>Your port depends on Apache (in particular, the <tt>apxs</tt>
binary) but the <tt>Makefile</tt> doesn't have Apache in
<tt>BUILD_DEPENDS</tt> and/or <tt>LIB_DEPENDS</tt>.</dd>

<dt><img alt="(uncommon)" src="/errorlogs/images/purple-ball.gif"><a name=
"assert">assert</a></dt>

<dd>Compilation failed due to an assert.  This is often a variation
on <tt>arch</tt> or <tt>missing header</tt>.</dd>

<dt><img alt="(uncommon)" src="/errorlogs/images/purple-ball.gif"><a name=
"awk">awk</a></dt>

<dd><tt>awk</tt> is complaining about some kind of bogus string
expression.</dd>

<dt><img alt="(uncommon)" src="/errorlogs/images/purple-ball.gif"><a name=
"bison">bison</a></dt>

<dd>Your port requires <tt>bison</tt>, which does not exist in
4.x-stable or newer anymore. Either patch it to use <tt>byacc</tt>
instead, or define <tt>USE_BISON</tt>.</dd>

<dt><img alt="(uncommon)" src="/errorlogs/images/purple-ball.gif"><a name=
"cgi-bin">cgi-bin</a></dt>

<dd>Your port assumes that a directory (usually
<tt>/usr/local/www/cgi-bin</tt>) already exists,
but by default it doesn't.</dd>

<dt><img alt="(uncommon)" src="/errorlogs/images/purple-ball.gif"><a name=
"chown">chown</a></dt>

<dd><tt>POSIX</tt> has deprecated the usage
"<tt>chown user.group filename</tt>" in favor of
"<tt>chown user:group filename</tt>". This happened quite some time
ago, actually, but it is only now being enforced. (The change was
made to allow '.' in usernames).</dd>

<dt><img alt="(uncommon)" src="/errorlogs/images/purple-ball.gif"><a name=
"elf">ELF</a></dt>

<dd>The port does not properly work in the new ELF world. It is
probably looking for an <tt>a.out</tt> object (e.g.,
<tt>crt0.o</tt>).</dd>

<dt><img alt="(uncommon)" src="/errorlogs/images/purple-ball.gif"><a name=
"f77">f77</a></dt>

<dd><tt>gcc</tt> in base no longer includes the <tt>Fortran</tt> compiler
by default.</dd>

<dt><img alt="(uncommon)" src="/errorlogs/images/purple-ball.gif"><a name=
"ffs_conflict">ffs conflict</a></dt>

<dd>Both <tt>/usr/include/machine/cpufunc.h</tt> and
<tt>/usr/include/strings.h</tt> are attempting to define <tt>int ffs()</tt>.</dd>

<dt><img alt="(uncommon)" src="/errorlogs/images/purple-ball.gif"><a name=
"getopt.h">getopt.h</a></dt>

<dd><tt>&lt;getopt.h&gt;</tt> is conflicting with <tt>unistd.h</tt>.</dd>

<dt><img alt="(uncommon)" src="/errorlogs/images/purple-ball.gif">
<a name="getopt">getopt</a></dt>

<dd>Your port may need to set the new port variable 
<tt>USE_GETOPT_LONG</tt>.</dd>

<dt><img alt="(uncommon)" src="/errorlogs/images/purple-ball.gif"><a name=
"lc_r">libc_r not found</a></dt>

<dd>This library has not yet been ported to e.g. the Sparc.</dd>

<dt><img alt="(uncommon)" src="/errorlogs/images/purple-ball.gif"><a name=
"malloc.h">malloc.h</a></dt>

<dd>Including <tt>&lt;malloc.h&gt;</tt> is now deprecated in favor of
<tt>&lt;stdlib.h&gt;</tt>.</dd>

<dt><img alt="(uncommon)" src="/errorlogs/images/purple-ball.gif"><a name=
"motif">MOTIF</a></dt>

<dd>This port requires Motif but does not define
<tt>REQUIRES_MOTIF</tt>. See the <a href=
"http://www.freebsd.org/doc/en_US.ISO8859-1/books/porters-handbook/porting-motif.html">handbook</a>
for details.</dd>

<dt><img alt="(uncommon)" src="/errorlogs/images/purple-ball.gif"><a name=
"motiflib">MOTIFLIB</a></dt>

<dd>This port requires Motif but does not refer to the libraries
using <tt>${MOTIFLIB}</tt>. See <a href=
"http://www.freebsd.org/doc/en_US.ISO8859-1/books/porters-handbook/porting-motif.html">handbook</a>
for details.</dd>

<dt><img alt="(uncommon)" src="/errorlogs/images/purple-ball.gif"><a name=
"munmap">munmap</a></dt>

<dd>POSIX specifies that munmap cannot be called on a zero-length file.
Because of this, during 4.X builds, if cp tries to copy a zero-length file, it
may fail saying, "cp: ...: Invalid argument".  This is a problem with the 
bindist image on pointyhat, and not the fault of the porter.</dd>

<dt><img alt="(uncommon)" src="/errorlogs/images/purple-ball.gif"><a name=
"perl5">perl5</a></dt>

<dd>There is a problem in processing a <tt>perl5</tt> module.</dd>

<dt><img alt="(uncommon)" src="/errorlogs/images/purple-ball.gif"><a name=
"pod2man">pod2man</a></dt>

<dd><tt>perl</tt> is no longer included by default in the base
system, but your port's documentation process depends on it. While
this change helps avoid having a stale version of <tt>perl</tt>
in the base system, it also means that many ports now need to include
<tt>USE_PERL5</tt>.</dd>

<dt><img alt="(uncommon)" src="/errorlogs/images/purple-ball.gif"><a name=
"python">python</a></dt>

<dd>The <tt>Makefile</tt> needs to define <tt>USE_PYTHON</tt>.</dd>

<dt><img alt="(uncommon)" src="/errorlogs/images/purple-ball.gif"><a name=
"sed">sed</a></dt>

<dd><tt>sed</tt> is complaining about some kind of bogus regular
expression, probably as a side-effect of its being invoked by
<tt>${REINPLACE_COMMAND}</tt>. This is often a result of having
replaced usages of <tt>perl</tt> in the <tt>Makefile</tt> with usages
of <tt>${REINPLACE_COMMAND}</tt> but having left
<tt>perl</tt>-specific regexps in place.</dd>

<dt><img alt="(uncommon)" src="/errorlogs/images/purple-ball.gif"><a name=
"soundcard.h">soundcard.h</a></dt>

<dd><tt>machine/soundcard.h</tt> has been moved.</dd>

<dt><img alt="(uncommon)" src="/errorlogs/images/purple-ball.gif"><a name=
"stdio">stdio</a></dt>

<dd>You need to bring your port up to date with the current
<tt>&lt;stdio.h&gt;</tt>.</dd>

<dt><img alt="(uncommon)" src="/errorlogs/images/purple-ball.gif"><a name=
"stl">stl</a></dt>

<dd>Your port requires the <tt>STL</tt> library but cannot find it.</dd>

<dt><img alt="(uncommon)" src="/errorlogs/images/purple-ball.gif"><a name=
"struct">struct changes</a></dt>

<dd>Your port is trying to refer to structure elements that are not
really there. This is often due to changes in the underlying
include files.</dd>

<dt><img alt="(uncommon)" src="/errorlogs/images/purple-ball.gif"><a name=
"sysvipc">sysvipc</a></dt>

<dd>Your port is interacting badly with the System V InterProcess
Communication code.</dd>

<dt><img alt="(uncommon)" src="/errorlogs/images/purple-ball.gif"><a name=
"uname">uname</a></dt>

<dd>For a short period of time, gcc was not handling uname properly.</dd>

<dt><img alt="(uncommon)" src="/errorlogs/images/purple-ball.gif"><a name=
"values.h">values.h</a></dt>

<dd><tt>values.h</tt> has been moved.</dd>

<dt><img alt="(uncommon)" src="/errorlogs/images/purple-ball.gif"><a name=
"texinfo">texinfo</a></dt>

<dd>The new <tt>makeinfo</tt> cannot process a texinfo source file.
You can probably add a "--<tt>no-validate</tt>" option to force it
through if you are sure it's correct regardless of what
<tt>makeinfo</tt> says.</dd>

<dt><img alt="(uncommon)" src="/errorlogs/images/purple-ball.gif"><a name=
"wait">union wait</a></dt>

<dd>The compiler could not calculate the storage size of an object,
often due to misuse of a union.</dd>

<dt><img alt="(uncommon)" src="/errorlogs/images/purple-ball.gif"><a name=
"usexlib">USE_XLIB</a></dt>

<dd>You should specify <tt>USE_XLIB</tt> for this port since it
appears to use X.</dd>

<dt><img alt="(uncommon)" src="/errorlogs/images/purple-ball.gif"><a name=
"varargs">varargs</a></dt>

<dd><tt>varargs.h</tt> is obsolete with newer versions of <tt>gcc</tt>.</dd>

<dt><img alt="(uncommon)" src="/errorlogs/images/purple-ball.gif"><a name=
"xfree4man">X manpage</a></dt>

<dd>This port does not install a manpage but <tt>imake</tt> rules are
generating commands to convert manpages to HTML format. This is
most likely fixed by changing <tt>ComplexProgramTarget()</tt> in
<tt>Imakefile</tt> to <tt>ComplexProgramTargetNoMan()</tt>. Note that
defining <tt>NO_INSTALL_MANPAGES</tt> in the <tt>Makefile</tt> is no
longer sufficient in XFree86-4.</dd>
</dl>

<hr>
<center><a href="http://www.freebsd.org/ports/">The ports page</a>
| Maintained by <a href="mailto:portmgr@FreeBSD.org">portmgr@FreeBSD.org</a>
| Last modified 
<br>
$FreeBSD$
</center>
</body></html>
</html>