| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
TARGET_ARCH and TARGET. This is problematic when one has the =
(unconditional) type of assigment for CPUTYPE in /etc/make.conf.
(This would override what was set on the command line to "make
buildworld".)
Add a (horrible) kludge to Makefile.inc1 to check the type of
assignment for CPUTYPE (only for those who attempts to set it to
a different value). Fix an example make.conf. Fix the kernel's
build-tools target (aicasm only at the moment) to catch up with
bsd.cpu.mk,v 1.15 (BOOTSTRAPPING replaced with NO_CPU_CFLAGS in
Makefile.inc1's BMAKE).
Reviewed by: jhb
|
|
|
|
|
|
| |
Add a DPADD line for ${LIBUGIDFW} for ugidfw.
Submitted by: ru
|
| |
|
|
|
|
| |
prevent its building.
|
| |
|
| |
|
| |
|
|
|
|
| |
MFC after: 3 days
|
|
|
|
|
|
|
|
|
|
|
| |
bsd.cpu.mk doesn't have to worry about compilers other than the current
version.
- Allow TARGET_CPUTYPE to override CPUTYPE in bsd.cpu.mk.
- Treat an empty CPUTYPE the same as an undefined CPUTYPE.
- For buildworld, buildkernel, etc., define TARGET_CPUTYPE to CPUTYPE for
native builds and define it to be empty for cross-builds.
TARGET_CPUTYPE is only defined if it is not already defined via the
commandline or environment.
|
|
|
|
| |
MFC after: 1 week
|
|
|
|
| |
MFC after: 1 week
|
|
|
|
|
|
|
| |
http://www.freebsd.org/handbook/mirrors.html is not working anymore,
http://www.freebsd.org/doc/handbook/mirrors.html is the new link
MFC after: 1 week
|
|
|
|
|
|
| |
Add a warning about the Symbol LA-4100 series of cards. You gotta
load special firmware, and the wi driver in the tree doesn't support
that yet.
|
|
|
|
|
|
| |
for a long time now.
Approved by: bde
|
|
|
|
|
|
|
| |
option. Warn about COPY being phased out. Restore the old method
of always comparing before installing: INSTALL="install -C".
Requested by: bde
|
|
|
|
|
| |
PR: docs/41091
MFC after: 1 day
|
| |
|
|
|
|
|
|
| |
- To minimize whitespace changes, remove a test that didn't define
_CPUCFLAGS if both NO_CPU_CFLAGS and NO_CPU_COPTFLAGS were defined
since it is redundant (we don't use _CPUCFLAGS if those are defined).
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
to tune for more advanced processors while still supporting the minimum
processor in an architecture. We can do this with the '-mtune=' option
to gcc for alpha, sparc64, and powerpc and with the mis-named '-mcpu='
option for i386.
This defaults to tuning i386 builds for i686 machines though not using
any instructions that aren't found on an 80386. For alpha it defaults
to tuning for an EV5.
Approved by: peter
Peril sensitive sunglasses borrowed from: peter
|
| |
|
| |
|
| |
|
|
|
|
| |
- RELEASETAG is an optional variable, not a required one.
|
| |
|
|
|
|
|
| |
Feedback from: ru (Ruslan Ermilov)
MFC after: 3 days
|
|
|
|
|
|
| |
82546 based adapters.
MFC after: 3 days
|
|
|
|
| |
- .Nx -> .Fx
|
| |
|
|
|
|
|
| |
Adviced by: itojun
Obtained from: NetBSD
|
|
|
|
|
|
| |
arch@ between myself, bde and markm. I kept the parts that all of us
agreed to, and omitted some more extensive text that I'd originally
wanted.
|
|
|
|
|
|
|
|
|
| |
http://www.ietf.org/rfc/rfc2401.txt), IPsec is the right word and
already in the dictionary.
PR: in part docs/38668
Reviewed by: murray
MFC after: 10 days
|
| |
|
|
|
|
|
|
|
|
|
| |
since apparently people were missing that you aren't supposed to access
the name buffer following namei() unless you specify one of these flags.
Pointed out by: green
Obtained from: TrustedBSD Project
Sponsored by: DARPA, NAI Labs
|
|
|
|
|
|
|
|
|
| |
including documenting that ucreds must not be pulled out of thin air,
when to use td_cred vs. p_ucred, how to avoid race conditions in
credential updates, and why to use p_ucred when targetting a thread
or process in an access control operation involving two processes.
Reviewed by: julian, jhb (earlier revision)
|
|
|
|
|
|
|
|
|
|
| |
these days, and the average user expects ^A and arrow keys to work, however
if they know nothing of editing modes, they will think sh(1) just sucks. It
is likely that because of defaults on most systems and with most shells that
anyone who actually wants vi(1) editing mode will have 'set -o vi'. This
won't affect existing accounts, this way, of course. Only accounts with
.shrc from new etc/skel will be affected. This is much better than making
the change in sh(1).
|
|
|
|
| |
so that CLEANFILES from bsd.man.mk and bsd.dep.mk are honored.
|
|
|
|
| |
MFC after: 1 week
|
|
|
|
| |
(Useful for RELENG_4's lib/libpam/modules.)
|
|
|
|
|
|
|
| |
editor backups, .orig or .rej files, etc. Make transition
from SHARED=symlinks to SHARED=copies and vice versa work.
Submitted by: des, ru
|
|
|
|
| |
is defined (whether or not LIB is defined).
|
|
|
|
|
|
|
|
| |
now needs to set COPY=-C as -C is no longer compatible with the -d
option. It is also likely to be renamed to INSTALL_COPY soon.
Update documentation to reflect this change.
PR: bin/40724
|
| |
|
| |
|
|
|
|
| |
alias
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
bg
cd
command
fc
fg
getopts
jobs
read
umask
unalias
wait
|
|
|
|
|
| |
PR: 39093
Submitted by: Mike Makonnen <makonnen@packbell.net>
|
|
|
|
|
| |
PR: docs/35967
Submitted by: Gary W. Swearingen <swear@blarg.net>
|
| |
|
|
|
|
|
| |
PR: 39408
Submitted by: Michal Pasternak <doc@pasternak.w.lub.pl>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
to make it call `install' in the bsd.subdir.mk-driven makefiles
too. (share/examples/Makefile,v 1.29 changed the bsd.prog.mk
to bsd.subdir.mk and many stuff was lost during "make release".
I then merged this change in rev. 1.28.2.2 to work around the
namespace pollution (FILES) in this makefile.)
There was an added complexity here. Both the `distribute' and
`install' targets are recursive (they propagate to SUBDIRs).
So `distribute' first calls `install' in the ${.CURDIR}, then
calls `distribute' in each SUBDIR, etc. The problem is that
`install' (being also recursive) causes the stuff from SUBDIR
to be installed twice, first time thru `install' in ${.CURDIR}
triggered by `distribute', second time by `distribute' run in
the SUBDIR. This problem is not new, but it became apparent
only after I moved the `distribute' target from bsd.obj.mk to
bsd.subdir.mk. My first attempt testing the fix failed due to
this, because the whole world was distributed twice, causing
all the imaginable mess (kerberos5 stuff was installed into both
"base" and "krb5" dists, there was /sbin/init.bak, etc.)
I say the problem is not new because bsd.prog.mk and bsd.lib.mk
makefiles with SUBDIR (even without this fix) had this problem
for years. Try e.g. running ``make distribute DISTDIR=/foo''
from usr.bin/bzip2 or from lib/libcom_err (without the fix) and
watch the output.
So the solution was to make `install' behave non-recursive when
executed by `distribute'. My first attempt in passing SUBDIR=
to the `install' in the `distribute' body failed because of the
way how src/Makefile and src/Makefile.inc1 communicate with each
other. SUBDIR='s assignment precedence on the "make install
SUBDIR=" command line is lowered after src/Makefile wrapper calls
"make ... -f ${.CURDIR}/Makefile.inc1 install" because SUBDIR=
is moved into environment, and Makefile.inc1's assignments now
take higher precedence. This may be fixed someday when we merge
Makefile with Makefile.inc1. For now, this is implemented as a
NO_SUBDIR knob.
Spotted by: Dmitry Pryanishnikov <dmitry@atlantis.dp.ua>
Prodded by: des
MFC after: 3 days
|