should only affect current resources, it seems best to wait until all
configuration is done before disabling it. If this fixes any problems, it
is a MT5 candidate.
explanation...
This makefile tries to be smart in determining the minimal list
of ports comprising the docproj meta-port, necessary to build
the FreeBSD documentation and release notes.
To get it absolutely right, it would have to generate the list
at run time, parsing the output of "make all-depends-list" for
ports/textproc/docproj, supplying the same options like in
src/release/Makefile, and trying for different platforms and
FreeBSD versions!
Besides from the complexity involved, this is just not possible
to do from here, because the ports tree may be not up-to-date or
not be available at all -- it's not required to have a checked
out ports tree to start "make release". So makefile copies
some logic from the ports system to try to come up with the
right list...
Unfortunately, it's nearly impossible nor practical to come up
with a proper and complete list from here this way. Such a
list would have to support all possible __FreeBSD_version's,
Perl versions, and so on, and their combinations -- everything
that the ports system would do.
The fix is to stop pretending be smart, and only provide
lists enough to build a docproj port on recent of 4.x, 5.x,
and 6.x systems, where this is practical.
What can break with this change is "make release -DNOPORTS" of
HEAD or RELENG_5, *without* -DNODOC, on older FreeBSD systems
like 5.1-RELEASE. The change in the docproj dependency list
between 5.1 and 5.3 is as follows:
# diff docports.501000 docports.503000
< /usr/ports/devel/p5-File-Temp
< /usr/ports/devel/p5-Test-Harness
< /usr/ports/devel/p5-Test-Simple
< /usr/ports/lang/perl5
> /usr/ports/lang/perl5.8
Since doing "make release" on these old systems is not officially
supported anyway (only one tiny tweak is necessary to make it
work), the practical damage of this change is zero.
Original problem spotted by Scott Long doing "make release
-DNOPORTS RELEASETAG=RELENG_5". That particular problem
was already fixed by the previous change to this file, while
this change is the result of some additional analyzis of the
problem.
Fix was tested by doing a "make release -DNOPORTS" of HEAD on
the 4.10-STABLE machine (with one small tweak I mentioned, to
make it possible).
.h files. This simplifies the Makefile here a bit and makes it behave
better in a couple of situations. While I'm here, clean up some comments
and try to improve the organization a bit.
Thanks to: Ruslan Ermilov (The Marvelous Makefile Guru)
ENOENT when there's no PNP ID for this device node, or ENXIO when there
is one, but it doesn't match.
In the nonPNP case (as most Alpha systems appear to be), we were
treating the error return as an error, when it should be have ignored
it. Version 1.9 properly ignored it, but the attach re-write of 1.10
introduced this logic error.
Pointy Hat to: phk (for breaking it then asking me to fix it :-)
Sponsored by: The Voices in Bill Paul's Head, LLC
pcap_pkthdr. This makes /var/log/pflog standart compliant on 64bit archs.
OpenBSD has fixed this by changing the bpf timeval to 32bit in the kernel,
so no need to report this over (again).
PR: bin/71096 (w/ changes)
Submitted by: Ville-Pertti Keinonen
Tested by: amd64(submitter), sparc64(yongari), i386(myself)
MFC after: 3 days
part of the pf module.
While here fix a comment that was c'n'ped from rc.d/pf
PR: bin/71096 (partly)
Submitted by: Ville-Pertti Keinonen
MFC after: 2 days
update tick count for userland in thread_userret. This change
also removes a "no upcall owned" panic because fuword() schedules
an upcall under heavily loaded, and code assumes there is no upcall
can occur.
Reported and Tested by: Peter Holm <peter@holm.cc>
The removed argument could trivially be derived from the remaining one.
That in turn should be the same as curthread, but it is possible that curthread could be expensive to derive on some syste,s so leave it as an argument.
Having both proc and thread as an argumen tjust gives an opportunity for
them to get out sync.
MFC after: 3 days
in diagnostics. It has outlived its usefulness and has started
causing panics for people who turn on DIAGNOSTIC, in what is otherwise
good code.
MFC after: 2 days
remaining consumers to have the count passed as an option. This is
i4b, pc98/wdc, and coda.
Bump configvers.h from 500013 to 600000.
Remove heuristics that tried to parse "device ed5" as 5 units of the ed
device. This broke things like the snd_emu10k1 device, which required
quotes to make it parse right. The no-longer-needed quotes have been
removed from NOTES, GENERIC etc. eg, I've removed the quotes from:
device snd_maestro
device "snd_maestro3"
device snd_mss
I believe everything will still compile and work after this.
the old one is. Hence we need to evaluate the old one for _FDI since it
has a valid ACPI_HANDLE ivar. This is a minimal fix. Make a note that a
more complete one is to make fdc support the ACPI_HANDLE ivar for its
children.
This and the previous change are MT5 candidates.
concensus seems to be that is best left for doing post-install.
Discussed on: freebsd-current@
Tested with: make release
Approved by: re@
MFC after: 3 days
