text:
|Return to bsd.README CVS log
|Up to [cvs.NetBSD.org] / src / share / mk
|File: [cvs.NetBSD.org] / src / share / mk / bsd.README (download)
Revision 18.104.22.168, Sat Jun 6 22:10:12 2009 UTC (11 years, 4 months ago) by bouyer
Pull up following revision(s) (requested by snj in ticket #790): share/mk/bsd.lib.mk: revision 1.298 share/mk/bsd.man.mk: revision 1.100 share/mk/bsd.hostprog.mk: revision 1.55 distrib/sets/maketars: revision 1.66 share/zoneinfo/Makefile: revision 1.43 share/mk/bsd.kmodule.mk: revision 1.19 usr.bin/xinstall/xinstall.c: revisions 1.106 - 1.108 via patch share/mk/bsd.prog.mk: revision 1.241 share/dict/Makefile: revision 1.17 share/mk/bsd.README: revision 1.249 distrib/common/parselist.awk: revision 1.16 share/mk/bsd.links.mk: revision 1.34 Explicitly sort entries on preparing set files from METALOG. METALOG could have different order due to install(1) race on parallel builds, and mtree(8) doesn't sort files. Should fix inconsistent shared sets among builds as seen in /pub/NetBSD-daily/netbsd-5/200904010000Z/shared/ and /pub/NetBSD-daily/netbsd-5/200904010002Z/shared/ dirs. Okay'ed by snj@. Changes for installing with a metalog: * When installing hard links and using a metalog, if -o, -g, -m, or -f args were explicitly specified on the command line, then believe them, but do not implicitly believe uname/gname/mode/flags from the file system. * Output fields in the same order used by mtree. Fix -Wshadow -Wcast-qual issues Re-calculate size and digestresult after stripping, to ensure that correct values appear in the metalog. Add LINKSOWN, LINKSGRP, and LINKSMODE variables for use by bsd.links.mk when installing hard links. They have no effect except when using a metalog, in which case the information is added to the metalog. In the future, these variables may be replaced by a method for explicitly recording hard links in a metadata log. Also change a few things that called ${INSTALL_LINK} without going through bsd.links.mk. Reviewed by perry and joerg. This should fix PR 24457 and PR 41155.
# $NetBSD: bsd.README,v 18.104.22.168 2009/06/06 22:10:12 bouyer Exp $ # @(#)bsd.README 8.2 (Berkeley) 4/2/94 This is the README file for the make "include" files for the NetBSD source tree. The files are installed in /usr/share/mk, and are, by convention, named with the suffix ".mk". Note, this file is not intended to replace reading through the .mk files for anything tricky. =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= RANDOM THINGS WORTH KNOWING: The files are simply C-style #include files, and pretty much behave like you'd expect. The syntax is slightly different in that a single '.' is used instead of the hash mark, i.e. ".include <bsd.prog.mk>". One difference that will save you lots of debugging time is that inclusion of the file is normally done at the *end* of the Makefile. The reason for this is because .mk files often modify variables and behavior based on the values of variables set in the Makefile. To make this work, remember that the FIRST target found is the target that is used, i.e. if the Makefile has: a: echo a a: echo a number two the command "make a" will echo "a". To make things confusing, the SECOND variable assignment is the overriding one, i.e. if the Makefile has: a= foo a= bar b: echo ${a} the command "make b" will echo "bar". This is for compatibility with the way the V7 make behaved. It's fairly difficult to make the BSD .mk files work when you're building multiple programs in a single directory. It's a lot easier to split up the programs than to deal with the problem. Most of the agony comes from making the "obj" directory stuff work right, not because we switched to a new version of make. So, don't get mad at us, figure out a better way to handle multiple architectures so we can quit using the symbolic link stuff. (Imake doesn't count.) The file .depend in the source directory is expected to contain dependencies for the source files. This file is read automatically by make after reading the Makefile. The variable DESTDIR works as before. It's not set anywhere but will change the tree where the file gets installed. The profiled libraries are no longer built in a different directory than the regular libraries. A new suffix, ".po", is used to denote a profiled object, and ".so" denotes a shared (position-independent) object. There are various make variables used during the build. Many variables support a (case sensitive) value of "no" or "yes", and are tested with ${VAR} == "no" and ${VAR} != "no" . The basic rule for the variable naming scheme is as follows: HOST_xxx A command that runs on the host machine regardless of whether or not the system is being cross compiled, or flags for such a command. MKxxx Can be set to "no" to disable functionality, or "yes" to enable it. Usually defaults to "yes", although some variables default to "no". Due to make(1) implementation issues, if a temporary command-line override of a mk.conf(5) or <bsd.own.mk> setting is required whilst still honoring a particular Makefile's setting of MKxxx, use env MKxxx=value make instead of make MKxxx=value NOxxx If defined, disables a feature. Not intended for users. This is to allow Makefiles to disable functionality that they don't support (such as missing man pages). NOxxx variables must be defined before <bsd.own.mk> is included. TOOL_xxx A tool that is provided as part of the USETOOLS framework. When not using the USETOOLS framework, TOOL_xxx variables should refer to tools that are already installed on the host system. The following variables that control how things are made/installed that are not set by default. These should not be set by Makefiles; they're for the user to define in MAKECONF (see <bsd.own.mk>, below, or mk.conf(5)) or on the make(1) command line: BUILD If defined, 'make install' checks that the targets in the source directories are up-to-date and remakes them if they are out of date, instead of blindly trying to install out of date or non-existent targets. MAKEVERBOSE Control how "verbose" the standard make(1) rules are. Default: 2 Supported values: 0 Minimal output ("quiet") 1 Describe what is occurring 2 Describe what is occurring and echo the actual command MKATF If "no", don't build libatf-c, libatf-c++ libraries associated with the Automated Testing Framework (ATF). Default: yes MKBFD If "no", don't build libbfd, libiberty, or any of the things that depend on them (binutils/gas/ld, gdb, dbsym, mdsetimage). Default: yes MKCATPAGES If "no", don't build or install the catman pages. Default: yes MKCOMPAT If "no", don't build or install the src/compat. Default: yes on amd64/sparc64, no elsewhere. MKCOMPLEX If "no", don't build libm support for <complex.h> Default: yes MKCRYPTO If "no", no cryptography support will be built into the system, and also acts as "MKKERBEROS=no". Default: yes MKCRYPTO_IDEA If not "no", IDEA support will be built into libcrypto_idea.a. Default: no MKCRYPTO_MDC2 If not "no", MDC2 support will be built into libcrypto_mdc2.a Default: no MKCRYPTO_RC5 If not "no", RC5 support will be built into libcrypto_rc5.a. Default: no MKCVS If "no", don't build or install cvs(1). Default: yes MKDEBUG If "no", don't build and install separate debugging symbols into /usr/libdata/debug. Default: no MKDEBUGLIB Build *_g.a debugging libraries, which are compiled with -DDEBUG. Default: no MKDOC If "no", don't build or install the documentation. Default: yes MKDYNAMICROOT If "no", build programs in /bin and /sbin statically, don't install certain libraries in /lib, and don't install the shared linker into /libexec. Default: yes MKGCC If "no", don't build gcc(1) or any of the GCC-related libraries (libgcc, libobjc, libstdc++). Default: yes MKGCCCMDS If "no", don't build gcc(1), but do build the GCC-related libraries (libgcc, libobjc, libstdc++). Default: yes MKGDB If "no", don't build gdb(1). Default: yes MKHESIOD If "no", disables building of Hesiod infrastructure (libraries and support programs). Default: yes MKHOSTOBJ If not "no", for programs intended to be run on the compile host, the name, release, and architecture of the host operating system will be suffixed to the name of the object directory created by "make obj". Default: no MKHTML If "no", don't build or install the HTML man pages. Default: yes MKIEEEFP If "no", don't add code for IEEE754/IEC60559 conformance. Has no effect on most platforms. Default: yes MKSTRIPIDENT Strip the RCS IDs from program binaries and shared libraries. Default: no MKINET6 If "no", disables building of INET6 (IPv6) infrastructure (libraries and support programs). Default: yes MKINFO If "no", don't build or install Info documentation from Texinfo source files. Default: yes MKIPFILTER If "no", don't build or install the IP Filter programs and LKM. Default: yes MKISCSI If "no", don't build or install iSCSI library or applications (depends on libpthread.) Default: yes MKKERBEROS If "no", disables building of Kerberos v5 infrastructure (libraries and support programs). Default: yes MKLDAP If "no", disables building of LDAP infrastructure (libraries and support programs). Default: yes MKLINKLIB If "no", act as "MKLINT=no MKPICINSTALL=no MKPROFILE=no". Also: - don't install the .a libraries - don't install _pic.a libraries on PIC systems - don't build .a libraries on PIC systems - don't install the .so symlink on ELF systems I.e, only install the shared library (and the .so.major symlink on ELF). Default: yes MKLINT If "no", don't build or install the lint libraries. Default: yes MKMAN If "no", don't build or install the man or catman pages, and also acts as "MKCATPAGES=no MKHTML=no". Default: yes MKMANZ If not "no", compress manual pages at installation time. Default: no MKMODULAR If "no", don't build the versions of modload(8), modstat(8) and modunload(8) that use the new modules framework present in the kernel (enabled separately using 'options MODULAR' int the configuration file). Also don't build any other stuff that may rely on this support, such as tests or kernel modules. Note: This flag will disappear when the new modules framework is complete enough to replace the old LKM, effectively switching it to "yes" by default. Default: no MKNLS If "no", don't build or install the NLS files and locale definition files. Default: yes MKOBJ If "no", don't enable the rule which creates objdirs, and also acts as "MKOBJDIRS=no". Default: yes MKOBJDIRS If "no", don't create objdirs during a "make build". Default: no MKPAM If "no", disables building of PAM authentication infrastructure (libraries and support programs). Default: yes MKPCC If "no", don't build pcc(1) or any of the PCC-related libraries (libpcc, libpccsoftfloat). Default: no MKPCCCMDS If "no", don't build pcc(1), but do build the PCC-related libraries (libpcc, libpccsoftfloat). Default: no MKPF If "no", don't build or install the pf programs and LKM. Default: yes MKPIC If "no", don't build or install shared libraries, and also acts as "MKPICLIB=no" Default: yes (for MACHINE_ARCHs that support it) MKPICINSTALL If "no", don't install the *_pic.a libraries. Default: yes MKPICLIB If "no", don't build *_pic.a libraries, and build the shared object libraries from the .a libraries. A symlink is installed in ${DESTDIR}/usr/lib for the _pic.a library pointing to the .a library. Default: yes MKPIE If "no", create regular executables. Otherwise create PIE (Position Independent Executables). Default: no MKPOSTFIX If "no", don't build or install postfix(1). Default: yes MKPROFILE If "no", don't build or install the profiling (*_p.a) libraries. Default: yes MKSHARE If "no", act as "MKCATPAGES=no MKDOC=no MKHTML=no MKINFO=no MKMAN=no MKNLS=no". I.e, don't build catman pages, documentation, Info documentation, man pages, NLS files, ... Default: yes MKSKEY If "no", disables building of S/key authentication infrastructure (libraries and support programs). Default: yes MKSOFTFLOAT If not "no", build with options to enable the compiler to generate output containing library calls for floating point and possibly soft-float library support. Default: no MKSTATICLIB If "no", don't build or install the normal static (*.a) libraries. Default: yes MKUNPRIVED If not "no", don't set the owner/group/mode when installing files or directories, and keep a metadata log of what the owner/group/mode should be. This allows a non-root "make install". Default: no MKUPDATE If not "no", 'make install' only installs targets that are more recently modified in the source directories that their installed counterparts. Default: no MKX11 If not "no", depending on the value of ${X11FLAVOUR}, 'make build' also descends into either src/x11 (XFree86) or src/external/mit/xorg (modular Xorg) to cross-build X11 and automatically enables creation of X sets. Default: no MKYP If "no", disables building of YP (NIS) infrastructure (libraries and support programs). Default: yes USE_HESIOD If "no", disables building Hesiod support into various system utilities/libraries that support it. If ${MKHESIOD} is "no", USE_HESIOD will also be forced to "no". USE_INET6 If "no", disables building INET6 (IPv6) support into various system utilities/libraries that support it. If ${MKINET6} is "no", USE_INET6 will also be forced to "no". USE_JEMALLOC If "no", disables building the "jemalloc" allocator designed for improved performance with threaded applications. The "phkmalloc" allocator as used up before NetBSD-5.0 will be substituted. USE_KERBEROS If "no", disables building Kerberos v5 support into various system utilities/libraries that support it. If ${MKKERBEROS} is "no", USE_KERBEROS will also be forced to "no". USE_LDAP If "no", disables building LDAP support into various system utilities/libraries that support it. If ${MKLDAP} is "no", USE_LDAP will also be forced to "no". USE_PAM If "no", disables building PAM authentication support into various system utilities/libraries that support it. If ${MKPAM} is "no", USE_PAM will also be forced to "no". USE_SKEY If "no", disables building S/key authentication support into various system utilities/libraries that support it. If ${MKSKEY} is "no", USE_SKEY will also be forced to "no". Default: no USE_SSP If "no", disables GCC stack protection code, which detects stack overflows and aborts the program. This imposes some performance penalty. Default: no USE_FORT If "yes" turns on substitute wrappers for commonly used functions that do not do bounds checking regularly, but they could in some cases by using the gcc __builtin_object_size() function to determine the buffer size where it is known and detect buffer overflows. These substitute functions are in /usr/include/ssp. Default: no USE_YP If "no", disables building YP (NIS) support into various system utilities/libraries that support it. If ${MKYP} is "no", USE_YP will also be forced to "no". X11FLAVOUR Set to "Xorg" or "XFree86", depending on whether to build XFree86 or modular Xorg. Only matters if MKX11!=no. Default: "Xorg" on amd64, i386, macppc, shark and sparc64, "XFree86" on everything else. COPTS.lib<lib> OBJCOPTS.lib<lib> LDADD.lib<lib> CPPFLAGS.lib<lib> CXXFLAGS.lib<lib> COPTS.<prog> OBJCCOPTS.<prog> LDADD.<prog> CPPFLAGS.<prog> CXXFLAGS.<prog> These provide a way to specify additions to the associated variables in a way that applies only to a particular library or program. <lib> corresponds to the LIB variable set in the library's makefile. <prog> corresponds to either PROG or PROG_CXX (if set). For example, if COPTS.libcrypto is set to "-g", "-g" will be added to COPTS only when compiling the crypto library. =-=-=-=-= sys.mk =-=-=-=-= The include file <sys.mk> has the default rules for all makes, in the BSD environment or otherwise. You probably don't want to touch this file. =-=-=-=-= bsd.own.mk =-=-=-=-= The include file <bsd.own.mk> contains source tree configuration parameters, such as the owners, groups, etc. for both manual pages and binaries, and a few global "feature configuration" parameters. It has no targets. To get system-specific configuration parameters, <bsd.own.mk> will try to include the file specified by the "MAKECONF" variable. If MAKECONF is not set, or no such file exists, the system make configuration file, /etc/mk.conf is included. These files may define any of the variables described below. <bsd.own.mk> sets the following variables, if they are not already defined (defaults are in brackets): NETBSDSRCDIR Top of the NetBSD source tree. If _SRC_TOP_ != "", that will be used as the default, otherwise BSDSRCDIR will be used as the default. Various makefiles within the NetBSD source tree will use this to reference the top level of the source tree. _SRC_TOP_ Top of the system source tree, as determined by <bsd.own.mk> based on the presence of tools/ and build.sh. This variable is "internal" to <bsd.own.mk>, although its value is only determined once and then propagated to all sub-makes. BSDSRCDIR The real path to the system sources, so that 'make obj' will work correctly. [/usr/src] BSDOBJDIR The real path to the system 'obj' tree, so that 'make obj' will work correctly. [/usr/obj] BINGRP Binary group. [wheel] BINOWN Binary owner. [root] BINMODE Binary mode. [555] NONBINMODE Mode for non-executable files. [444] MANDIR Base path for manual installation. [/usr/share/man/cat] MANGRP Manual group. [wheel] MANOWN Manual owner. [root] MANMODE Manual mode. [${NONBINMODE}] MANINSTALL Manual installation type. Space separated list: catinstall, htmlinstall, maninstall [catinstall maninstall htmlinstall] LDSTATIC Control program linking; if set blank, link everything dynamically. If set to "-static", link everything statically. If not set, programs link according to their makefile. LIBDIR Base path for library installation. [/usr/lib] LINTLIBDIR Base path for lint(1) library installation. [/usr/libdata/lint] LIBGRP Library group. [${BINGRP}] LIBOWN Library owner. [${BINOWN}] LIBMODE Library mode. [${NONBINMODE}] DOCDIR Base path for system documentation (e.g. PSD, USD, etc.) installation. [/usr/share/doc] HTMLDOCDIR Base path for html system documentation installation. [/usr/share/doc/html] DOCGRP Documentation group. [wheel] DOCOWN Documentation owner. [root] DOCMODE Documentation mode. [${NONBINMODE}] NLSDIR Base path for Native Language Support files installation. [/usr/share/nls] NLSGRP Native Language Support files group. [wheel] NLSOWN Native Language Support files owner. [root] NLSMODE Native Language Support files mode. [${NONBINMODE}] X11SRCDIR The path to the xsrc tree. [/usr/xsrc] X11SRCDIR.xc The path to the (old) X11 xc src tree. [${X11SRCDIR}/xfree/xc] X11SRCDIR.local The path to the local X11 src tree. [${X11SRCDIR}/local] X11SRCDIR.lib<package> X11SRCDIR.<package> The path to the xorg src tree for the specificed package>. [${X11SRCDIR}/external/mit/xorg/<package>/dist] X11ROOTDIR Root directory of the X11 installation. [/usr/X11R6 or [/usr/X11R7] X11BINDIR X11 bin directory. [${X11ROOTDIR}/bin] X11FONTDIR X11 font directory. [${X11ROOTDIR}/lib/X11/fonts] X11INCDIR X11 include directory. [${X11ROOTDIR}/include] X11LIBDIR X11 lib/x11 (config) directory. [${X11ROOTDIR}/lib/X11] X11MANDIR X11 manual directory. [${X11ROOTDIR}/man] X11USRLIBDIR X11 library directory. [${X11ROOTDIR}/lib] STRIPFLAG The flag passed to the install program to cause the binary to be stripped. This is to be used when building your own install script so that the entire system can be made stripped/not-stripped using a single knob. [] COPY The flag passed to the install program to cause the binary to be copied rather than moved. This is to be used when building our own install script so that the entire system can either be installed with copies, or with moves using a single knob. [-c] MAKEDIRTARGET dir target [params] Runs "cd $${dir} && ${MAKE} [params] $${target}", displaying a "pretty" message whilst doing so. RELEASEMACHINEDIR Subdirectory used below RELEASEDIR when building a release. [${MACHINE}] RELEASEMACHINE Subdirectory or path component used for the following paths: distrib/${RELEASEMACHINE} distrib/notes/${RELEASEMACHINE} etc/etc.${RELEASEMACHINE} Used when building a release. [${MACHINE}] Additionally, the following variables may be set by <bsd.own.mk> or in a make configuration file to modify the behavior of the system build process (default values are in brackets along with comments, if set by <bsd.own.mk>): USETOOLS Indicates whether the tools specified by ${TOOLDIR} should be used as part of a build in progress. Supported values: yes Use the tools from TOOLDIR. Must be set to this if cross-compiling. no Do not use the tools from TOOLDIR, but refuse to build native compilation tool components that are version-specific for that tool. never Do not use the tools from TOOLDIR, even when building native tool components. This is similar to the traditional NetBSD build method, but does not verify that the compilation tools in use are up-to-date enough in order to build the tree successfully. This may cause build or runtime problems when building the whole NetBSD source tree. Default: "yes" if building all or part of a whole NetBSD source tree (detected automatically); "no" otherwise (to preserve traditional semantics of the <bsd.*.mk> make(1) include files). OBJECT_FMT Object file format. [set to "ELF" on architectures that use ELF -- currently all architectures]. TOOLCHAIN_MISSING If not "no", this indicates that the platform being built does not have a working in-tree toolchain. If the ${MACHINE_ARCH} in question falls into this category, TOOLCHAIN_MISSING is conditionally assigned the value "yes". Otherwise, the variable is unconditionally assigned the value "no". If not "no", ${MKBFD}, ${MKGCC}, and ${MKGDB} are unconditionally assigned the value "no". EXTERNAL_TOOLCHAIN This variable is not directly set by <bsd.own.mk>, but including <bsd.own.mk> is the canonical way to gain access to this variable. The variable should be defined either in the user's environment or in the user's mk.conf file. If defined, this variable indicates the root of an external toolchain which will be used to build the tree. For example, if a platform is a ${TOOLCHAIN_MISSING} platform, EXTERNAL_TOOLCHAIN can be used to re-enable the cross-compile framework. If EXTERNAL_TOOLCHAIN is defined, ${MKGCC} is unconditionally assigned the value "no", since the external version of the compiler may not be able to build the library components of the in-tree compiler. NOTE: This variable is not yet used in as many places as it should be. Expect the exact semantics of this variable to change in the short term as parts of the cross-compile framework continue to be cleaned up. The following variables are defined to commands to perform the appropriate operation, with the default in [brackets]. Note that the defaults change if USETOOLS == "yes": TOOL_AMIGAAOUT2BB aout to Amiga bootblock converter. [amiga-aout2bb] TOOL_AMIGAELF2BB ELF to Amiga bootblock converter. [amiga-elf2bb] TOOL_AMIGATXLT Amige assembly language format translator. [amiga-txlt] TOOL_ASN1_COMPILE ASN1 compiler. [asn1_compile] TOOL_ATF_COMPILE Generate POSIX shell test programs. [atf-compile] TOOL_AWK Pattern-directed scanning/processing language. [awk] TOOL_CAP_MKDB Create capability database. [cap_mkdb] TOOL_CAT Concatenate and print files. [cat] TOOL_CKSUM Display file checksums. [cksum] TOOL_COMPILE_ET Error table compiler. [compile_et] TOOL_CONFIG Build kernel compilation directories. [config] TOOL_CRUNCHGEN Generate crunched binary build environment. [crunchgen] TOOL_CTAGS Create a tags file. [ctags] TOOL_DB Manipulate db(3) databases. [db] TOOL_DISKLABEL Read and write disk pack label. [disklabel] TOOL_EQN Format equations for groff. [eqn] TOOL_FDISK MS-DOS partition maintenance program. [fdisk] TOOL_FGEN IEEE 1275 Open Firmware FCode Tokenizer. [fgen] TOOL_GENASSYM Generate constants for assembly files. [genassym] TOOL_GENCAT Generate NLS message catalogs. [gencat] TOOL_GMAKE GNU make utility. [gmake] TOOL_GROFF Front end for groff document formatting system. [groff] TOOL_HEXDUMP Ascii, decimal, hexadecimal, octal dump. [hexdump] TOOL_HP300MKBOOT Make bootable image for hp300. [hp300-mkboot] TOOL_HP700MKBOOT Make bootable image for hp700. [hp700-mkboot] TOOL_INDXBIB Make bibliographic database's inverted index. [indxbib] TOOL_INSTALLBOOT Install disk bootstrap software. [installboot] TOOL_INSTALL_INFO Update info/dir entries. [install-info] TOOL_JOIN Relational database operator. [join] TOOL_M4 M4 macro language processor. [m4] TOOL_MACPPCFIXCOFF Fix up xcoff headers for macppc. [macppc-fixcoff] TOOL_MAKEFS Create file system image from directory tree. [makefs] TOOL_MAKEINFO Translate Texinfo documents. [makeinfo] TOOL_MAKEWHATIS Create a whatis.db database. [makewhatis] TOOL_MDSETIMAGE Set kernel RAM disk image. [mdsetimage] TOOL_MENUC Menu compiler. [menuc] TOOL_MIPSELF2ECOFF Convert ELF-format executable to ECOFF for mips. [mips-elf2ecoff] TOOL_MKCSMAPPER Make charset mapping table. [mkcsmapper] TOOL_MKESDB Make encoding scheme database. [mkesdb] TOOL_MKLOCALE Make LC_CTYPE locale files. [mklocale] TOOL_MKMAGIC Create database for file(1). [file] TOOL_MKTEMP Make (unique) temporary file name. [mktemp] TOOL_MSGC Simple message list compiler. [msgc] TOOL_MTREE Map a directory hierarchy. [mtree] TOOL_PAX Manipulate file archives and copy directories. [pax] TOOL_PIC Compile pictures for groff. [pic] TOOL_POWERPCMKBOOTIMAGE Make bootable image for powerpc. [powerpc-mkbootimage] TOOL_PWD_MKDB Generate the password databases. [pwd_mkdb] TOOL_REFER Preprocess bibliographic references for groff. [refer] TOOL_ROFF_ASCII Generate ASCII groff output. [nroff] TOOL_ROFF_DVI Generate DVI groff output. [${TOOL_GROFF} -Tdvi] TOOL_ROFF_HTML Generate HTML groff output. [${TOOL_GROFF} -Tlatin1 -mdoc2html] TOOL_ROFF_PS Generate PS groff output. [${TOOL_GROFF} -Tps] TOOL_ROFF_RAW Generate "raw" groff output. [${TOOL_GROFF} -Z] TOOL_RPCGEN Remote Procedure Call (RPC) protocol compiler. [rpcgen] TOOL_SED Stream editor. [sed] TOOL_SOELIM Eliminate .so's from groff input. [soelim] TOOL_SPARKCRC Generate a crc suitable for use in a sparkive file. [sparkcrc] TOOL_STAT Display file status. [stat] TOOL_STRFILE Create a random access file for storing strings. [strfile] TOOL_SUNLABEL Read or modify a SunOS disk label. [sunlabel] TOOL_TBL Format tables for groff. [tbl] TOOL_UUDECODE Uudecode a binary file. [uudecode] TOOL_VGRIND Grind nice listings of programs. [vgrind -f] TOOL_ZIC Time zone compiler. [zic] <bsd.own.mk> is generally useful when building your own Makefiles so that they use the same default owners etc. as the rest of the tree. =-=-=-=-= bsd.dep.mk =-=-=-=-= The include file <bsd.dep.mk> contains the default targets for building .depend files. It creates .d files from entries in SRCS and DPSRCS that are C, C++, or Objective C source files, and builds .depend from the .d files. All other files in SRCS and all of DPSRCS will be used as dependencies for the .d files. In order for this to function correctly, it should be .included after all other .mk files and directives that may modify SRCS or DPSRCS. It uses the following variables: SRCS List of source files to build the program. DPSRCS List of source files which are needed for generating dependencies, but are not needed in ${SRCS}. =-=-=-=-= bsd.files.mk =-=-=-=-= The include file <bsd.files.mk> handles the FILES variables and is included from <bsd.lib.mk> and <bsd.prog.mk>, and uses the following variables: FILES The list of files to install. CONFIGFILES Similar semantics to FILES, except that the files are installed by the `configinstall' target, not the `install' target. The FILES* variables documented below also apply. FILESOWN File owner. [${BINOWN}] FILESGRP File group. [${BINGRP}] FILESMODE File mode. [${NONBINMODE}] FILESDIR The location to install the files. FILESNAME Optional name to install each file as. FILESOWN_<fn> File owner of the specific file <fn>. FILESGRP_<fn> File group of the specific file <fn>. FILESMODE_<fn> File mode of the specific file <fn>. FILESDIR_<fn> The location to install the specific file <fn>. FILESNAME_<fn> Optional name to install <fn> as. FILESBUILD_<fn> A value different from "no" will add the file to the list of targets to be built by `realall'. Users of that variable should provide a target to build the file. BUILDSYMLINKS List of two word items: lnsrc lntgt For each lnsrc item, create a symlink named lntgt. The lntgt symlinks are removed by the cleandir target. UUDECODE_FILES List of files which are stored as <file>.uue in the source tree. Each one will be decoded with ${TOOL_UUDECODE}. The source files have a `.uue' suffix, the generated files do not. UUDECODE_FILES_RENAME_<fn> Rename the output from the decode to the provided name. *NOTE: These files are simply decoded, with no install or other rule applying implicitly except being added to the clean target. =-=-=-=-= bsd.gcc.mk =-=-=-=-= The include file <bsd.gcc.mk> computes various parameters related to GCC support libraries. It defines no targets. <bsd.own.mk> MUST be included before <bsd.gcc.mk>. The primary users of <bsd.gcc.mk> are <bsd.prog.mk> and <bsd.lib.mk>, each of which need to know where to find certain GCC support libraries. The behavior of <bsd.gcc.mk> is influenced by the EXTERNAL_TOOLCHAIN variable, which is generally set by the user. If EXTERNAL_TOOLCHAIN it set, then the compiler is asked where to find the support libraries, otherwise the support libraries are found in ${DESTDIR}/usr/lib. <bsd.gcc.mk> sets the following variables: _GCC_CRTBEGIN The full path name to crtbegin.o. _GCC_CRTBEGINS The full path name to crtbeginS.o. _GCC_CRTEND The full path name to crtend.o. _GCC_CRTENDS The full path name to crtendS.o. _GCC_LIBGCCDIR The directory where libgcc.a is located. =-=-=-=-= bsd.inc.mk =-=-=-=-= The include file <bsd.inc.mk> defines the includes target and uses the variables: INCS The list of include files. INCSDIR The location to install the include files. INCSNAME Target name of the include file, if only one; same as FILESNAME, but for include files. INCSYMLINKS Similar to SYMLINKS in <bsd.links.mk>, except that these are installed in the 'includes' target and not the (much later) 'install' target. INCSNAME_<file> The name file <file> should be installed as, if not <file>, same as FILESNAME_<file>, but for include files. =-=-=-=-= bsd.info.mk =-=-=-=-= The include file <bsd.info.mk> is used to generate and install GNU Info documentation from respective Texinfo source files. It defines three implicit targets (.txi.info, .texi.info, and .texinfo.info), and uses the following variables: TEXINFO List of Texinfo source files. Info documentation will consist of single files with the extension replaced by .info. INFOFLAGS Flags to pass to makeinfo. [] =-=-=-=-= bsd.kernobj.mk =-=-=-=-= The include file <bsd.kernobj.mk> defines variables related to the location of kernel sources and object directories. KERNSRCDIR Is the location of the top of the kernel src. [${_SRC_TOP_}/sys] KERNARCHDIR Is the location of the machine dependent kernel sources. [arch/${MACHINE}] KERNCONFDIR Is where the configuration files for kernels are found. [${KERNSRCDIR}/${KERNARCHDIR}/conf] KERNOBJDIR Is the kernel build directory. The kernel GENERIC for instance will be compiled in ${KERNOBJDIR}/GENERIC. The default value is ${MAKEOBJDIRPREFIX}${KERNSRCDIR}/${KERNARCHDIR}/compile if it exists or the target 'obj' is being made. Otherwise the default is ${KERNSRCDIR}/${KERNARCHDIR}/compile. It is important that Makefiles (such as those under src/distrib) that wish to find compiled kernels use <bsd.kernobj.mk> and ${KERNOBJDIR} rather than make assumptions about the location of the compiled kernel. =-=-=-=-= bsd.kinc.mk =-=-=-=-= The include file <bsd.kinc.mk> defines the many targets (includes, subdirectories, etc.), and is used by kernel makefiles to handle include file installation. It is intended to be included alone, by kernel Makefiles. It uses similar variables to <bsd.inc.mk>. Please see <bsd.kinc.mk> for more details, and keep the documentation in that file up to date. =-=-=-=-= bsd.lib.mk =-=-=-=-= The include file <bsd.lib.mk> has support for building libraries. It has the same eight targets as <bsd.prog.mk>: all, clean, cleandir, depend, includes, install, lint, and tags. Additionally, it has a checkver target which checks for installed shared object libraries whose version is greater that the version of the source. It has a limited number of suffixes, consistent with the current needs of the BSD tree. <bsd.lib.mk> includes <bsd.shlib.mk> to get shared library parameters. It sets/uses the following variables: LIB The name of the library to build. LIBDIR Target directory for libraries. SHLIBINSTALLDIR Target directory for shared libraries if ${USE_SHLIBDIR} is not "no". USE_SHLIBDIR If not "no", use ${SHLIBINSTALLDIR} instead of ${LIBDIR} as the path to install shared libraries to. USE_SHLIBDIR must be defined before <bsd.own.mk> is included. Default: no LIBISMODULE If not "no", install as ${LIB}.so (without the "lib" prefix), and act as "MKDEBUGLIB=no MKLINT=no MKPICINSTALL=no MKPROFILE=no MKSTATICLIB=no". Default: no LIBISPRIVATE If not "no", act as "MKDEBUGLIB=no MKLINT=no MKPIC=no MKPROFILE=no", and don't install the (.a) library. This is useful for "build only" helper libraries. Default: no LIBISCXX If not "no", Use ${CXX} instead of ${CC} to link shared libraries. This is useful for C++ libraries. Default: no LINTLIBDIR Target directory for lint libraries. LIBGRP Library group. LIBOWN Library owner. LIBMODE Library mode. LDADD Additional loader objects. MAN The manual pages to be installed (use a .1 - .9 suffix). NOCHECKVER_<library> NOCHECKVER If set, disables checking for installed shared object libraries with versions greater than the source. A particular library name, without the "lib" prefix, may be appended to the variable name to disable the check for only that library. SRCS List of source files to build the library. Suffix types .s, .c, and .f are supported. Note, .s files are preferred to .c files of the same name. (This is not the default for versions of make.) LIBDPLIBS A list of the tuples: libname path-to-srcdir-of-libname For each tuple; * LIBDO.libname contains the .OBJDIR of the library `libname', and if it is not set it is determined from the srcdir and added to MAKEOVERRIDES (the latter is to allow for build time optimization). * LDADD gets -L${LIBDO.libname} -llibname added. * DPADD gets ${LIBDO.libname}/liblibname.so or ${LIBDO.libname}/liblibname.a added. This variable may be used for individual libraries, as well as in parent directories to cache common libraries as a build-time optimization. The include file <bsd.lib.mk> includes the file named "../Makefile.inc" if it exists, as well as the include file <bsd.man.mk>. It has rules for building profiled objects; profiled libraries are built by default. Libraries are ranlib'd when made. =-=-=-=-= bsd.links.mk =-=-=-=-= The include file <bsd.links.mk> handles the LINKS and SYMLINKS variables and is included from from <bsd.lib.mk> and <bsd.prog.mk>. LINKSOWN, LINKSGRP, and LINKSMODE, are relevant only if a metadata log is used. The defaults may be modified by other bsd.*.mk files which include bsd.links.mk. In the future, these variables may be replaced by a method for explicitly recording hard links in a metadata log. LINKS The list of hard links, consisting of pairs of paths: source-file target-file ${DESTDIR} is prepended to both paths before linking. For example, to link /bin/test and /bin/[, use: LINKS=/bin/test /bin/[ CONFIGLINKS Similar semantics to LINKS, except that the links are installed by the `configinstall' target, not the `install' target. SYMLINKS The list of symbolic links, consisting of pairs of paths: source-file target-file ${DESTDIR} is only prepended to target-file before linking. For example, to symlink /usr/bin/tar to /bin/tar resulting in ${DESTDIR}/usr/bin/tar -> /bin/tar: SYMLINKS=/bin/tar /usr/bin/tar CONFIGSYMLINKS Similar semantics to SYMLINKS, except that the symbolic links are installed by the `configinstall' target, not the `install' target. LINKSOWN Link owner. [${BINOWN}] LINKSGRP Link group. [${BINGRP}] LINKSMODE Link mode. [${NONBINMODE}] LINKSOWN_<fn> Link owner of the specific file <fn>. LINKSGRP_<fn> Link group of the specific file <fn>. LINKSMODE_<fn> Link mode of the specific file <fn>. =-=-=-=-= bsd.man.mk =-=-=-=-= The include file <bsd.man.mk> handles installing manual pages and their links. It has a three targets: catinstall: Install the preformatted manual pages and their links. htmlinstall: Install the HTML manual pages and their links. maninstall: Install the manual page sources and their links. It sets/uses the following variables: MANDIR Base path for manual installation. MANGRP Manual group. MANOWN Manual owner. MANMODE Manual mode. MANSUBDIR Subdirectory under the manual page section, i.e. "/vax" or "/tahoe" for machine specific manual pages. MAN The manual pages to be installed (use a .1 - .9 suffix). MLINKS List of manual page links (using a .1 - .9 suffix). The linked-to file must come first, the linked file second, and there may be multiple pairs. The files are soft-linked. The include file <bsd.man.mk> includes a file named "../Makefile.inc" if it exists. =-=-=-=-= bsd.obj.mk =-=-=-=-= The include file <bsd.obj.mk> defines targets related to the creation and use of separated object and source directories. If an environment variable named MAKEOBJDIRPREFIX is set, make(1) uses ${MAKEOBJDIRPREFIX}${.CURDIR} as the name of the object directory if it exists. Otherwise make(1) looks for the existence of a subdirectory (or a symlink to a directory) of the source directory into which built targets should be placed. If an environment variable named MAKEOBJDIR is set, make(1) uses its value as the name of the object directory; failing that, make first looks for a subdirectory named "obj.${MACHINE}", and if that doesn't exist, it looks for "obj". Object directories are not created automatically by make(1) if they don't exist; you need to run a separate "make obj". (This will happen during a top-level build if "MKOBJDIRS" is set to a value other than "no"). When the source directory is a subdirectory of ${BSDSRCDIR} -- and this is determined by a simple string prefix comparison -- object directories are created in a separate object directory tree, and a symlink to the object directory in that tree is created in the source directory; otherwise, "make obj" assumes that you're not in the main source tree and that it's not safe to use a separate object tree. Several variables used by <bsd.obj.mk> control exactly what directories and links get created during a "make obj": MAKEOBJDIR If set, this is the component name of the object directory. OBJMACHINE If this is set but MAKEOBJDIR is not set, creates object directories or links named "obj.${MACHINE}"; otherwise, just creates ones named "obj". USR_OBJMACHINE If set, and the current directory is a subdirectory of ${BSDSRCDIR}, create object directory in the corresponding subdirectory of ${BSDOBJDIR}.${MACHINE}; otherwise, create it in the corresponding subdirectory of ${BSDOBJDIR} BUILDID If set, the contents of this variable are appended to the object directory name. If OBJMACHINE is also set, ".${BUILDID}" is added after ".${MACHINE}". =-=-=-=-= bsd.prog.mk =-=-=-=-= The include file <bsd.prog.mk> handles building programs from one or more source files, along with their manual pages. It has a limited number of suffixes, consistent with the current needs of the BSD tree. <bsd.prog.mk> includes <bsd.shlib.mk> to get shared library parameters. It has eight targets: all: build the program and its manual page. This also creates a GDB initialization file (.gdbinit) in the objdir. The .gdbinit file sets the shared library prefix to ${DESTDIR} to facilitate cross-debugging. clean: remove the program, any object files and the files a.out, Errs, errs, mklog, and ${PROG}.core. cleandir: remove all of the files removed by the target clean, as well as .depend, tags, and any manual pages. `distclean' is a synonym for `cleandir'. depend: make the dependencies for the source files, and store them in the file .depend. includes: install any header files. install: install the program and its manual pages; if the Makefile does not itself define the target install, the targets beforeinstall and afterinstall may also be used to cause actions immediately before and after the install target is executed. lint: run lint on the source files tags: create a tags file for the source files. It sets/uses the following variables: BINGRP Binary group. BINOWN Binary owner. BINMODE Binary mode. CLEANFILES Additional files to remove for the clean and cleandir targets. COPTS Additional flags to the compiler when creating C objects. COPTS.<fn> Additional flags to the compiler when creating the C objects for <fn>. For <fn>.[ly], "<fn>.c" must be used. CPUFLAGS Additional flags to the compiler/assembler to select CPU instruction set options, CPU tuning options, etc. CPUFLAGS.<fn> Additional flags to the compiler/assembler for <fn>. For <fn>.[ly], "<fn>.c" must be used. CPPFLAGS Additional flags to the C pre-processor. CPPFLAGS.<fn> Additional flags to the C pre-processor for <fn>. For <fn>.[ly], "<fn>.c" must be used. GDBINIT List of GDB initialization files to add to "source" directives in the .gdbinit file that is created in the objdir. LDADD Additional loader objects. Usually used for libraries. For example, to load with the compatibility and utility libraries, use: LDADD+=-lutil -lcompat LDFLAGS Additional linker flags (passed to ${CC} during link). LINKS See <bsd.links.mk> OBJCOPTS Additional flags to the compiler when creating ObjC objects. OBJCOPTS.<fn> Additional flags to the compiler when creating the ObjC objects for <fn>. For <fn>.[ly], "<fn>.c" must be used. SYMLINKS See <bsd.links.mk> MAN Manual pages (should end in .1 - .9). If no MAN variable is defined, "MAN=${PROG}.1" is assumed. PAXCTL_FLAGS If defined, run paxctl(1) on the program binary after link time, with the value of this variable as args to paxctl(1). PAXCTL_FLAGS.${PROG} Custom override for PAXCTL_FLAGS. PROG The name of the program to build. If not supplied, nothing is built. PROG_CXX If defined, the name of the program to build. Also causes <bsd.prog.mk> to link the program with the C++ compiler rather than the C compiler. PROG_CXX overrides the value of PROG if PROG is also set. PROGNAME The name that the above program will be installed as, if different from ${PROG}. SRCS List of source files to build the program. If SRCS is not defined, it's assumed to be ${PROG}.c. DPSRCS List of source files which are needed for generating dependencies, but are not needed in ${SRCS}. DPADD Additional dependencies for the program. Usually used for libraries. For example, to depend on the compatibility and utility libraries use: DPADD+=${LIBCOMPAT} ${LIBUTIL} The following libraries are predefined for DPADD: LIBCRT0?= ${DESTDIR}/usr/lib/crt0.o LIBARCHIVE?= ${DESTDIR}/usr/lib/libarchive.a LIBASN1?= ${DESTDIR}/usr/lib/libasn1.a LIBBLUETOOTH?= ${DESTDIR}/usr/lib/libbluetooth.a LIBBSDMALLOC?= ${DESTDIR}/usr/lib/libbsdmalloc.a LIBBZ2?= ${DESTDIR}/usr/lib/libbz2.a LIBC?= ${DESTDIR}/usr/lib/libc.a LIBC_PIC?= ${DESTDIR}/usr/lib/libc_pic.a LIBCOM_ERR?= ${DESTDIR}/usr/lib/libcom_err.a LIBCOMPAT?= ${DESTDIR}/usr/lib/libcompat.a LIBCRYPT?= ${DESTDIR}/usr/lib/libcrypt.a LIBCRYPTO?= ${DESTDIR}/usr/lib/libcrypto.a LIBCRYPTO_IDEA?=${DESTDIR}/usr/lib/libcrypto_idea.a LIBCRYPTO_MDC2?=${DESTDIR}/usr/lib/libcrypto_mdc2.a LIBCRYPTO_RC5?= ${DESTDIR}/usr/lib/libcrypto_rc5.a LIBCURSES?= ${DESTDIR}/usr/lib/libcurses.a LIBDBM?= ${DESTDIR}/usr/lib/libdbm.a LIBDES?= ${DESTDIR}/usr/lib/libdes.a LIBEDIT?= ${DESTDIR}/usr/lib/libedit.a LIBEVENT?= ${DESTDIR}/usr/lib/libevent.a LIBFETCH?= ${DESTDIR}/usr/lib/libfetch.a LIBFORM?= ${DESTDIR}/usr/lib/libform.a LIBGCC?= ${DESTDIR}/usr/lib/libgcc.a LIBGNUMALLOC?= ${DESTDIR}/usr/lib/libgnumalloc.a LIBGSSAPI?= ${DESTDIR}/usr/lib/libgssapi.a LIBHDB?= ${DESTDIR}/usr/lib/libhdb.a LIBINTL?= ${DESTDIR}/usr/lib/libintl.a LIBIPSEC?= ${DESTDIR}/usr/lib/libipsec.a LIBKADM5CLNT?= ${DESTDIR}/usr/lib/libkadm5clnt.a LIBKADM5SRV?= ${DESTDIR}/usr/lib/libkadm5srv.a LIBKAFS?= ${DESTDIR}/usr/lib/libkafs.a LIBKRB5?= ${DESTDIR}/usr/lib/libkrb5.a LIBKVM?= ${DESTDIR}/usr/lib/libkvm.a LIBL?= ${DESTDIR}/usr/lib/libl.a LIBLBER?= ${DESTDIR}/usr/lib/liblber.a LIBLDAP?= ${DESTDIR}/usr/lib/libldap.a LIBLDAP_R?= ${DESTDIR}/usr/lib/libldap_r.a LIBM?= ${DESTDIR}/usr/lib/libm.a LIBMENU?= ${DESTDIR}/usr/lib/libmenu.a LIBOBJC?= ${DESTDIR}/usr/lib/libobjc.a LIBOSSAUDIO?= ${DESTDIR}/usr/lib/libossaudio.a LIBPAM?= ${DESTDIR}/usr/lib/libpam.a LIBPCAP?= ${DESTDIR}/usr/lib/libpcap.a LIBPCI?= ${DESTDIR}/usr/lib/libpci.a LIBPMC?= ${DESTDIR}/usr/lib/libpmc.a LIBPOSIX?= ${DESTDIR}/usr/lib/libposix.a LIBPTHREAD?= ${DESTDIR}/usr/lib/libpthread.a LIBPTHREAD_DBG?=${DESTDIR}/usr/lib/libpthread_dbg.a LIBRADIUS?= ${DESTDIR}/usr/lib/libradius.a LIBRESOLV?= ${DESTDIR}/usr/lib/libresolv.a LIBRMT?= ${DESTDIR}/usr/lib/librmt.a LIBROKEN?= ${DESTDIR}/usr/lib/libroken.a LIBRPCSVC?= ${DESTDIR}/usr/lib/librpcsvc.a LIBRT?= ${DESTDIR}/usr/lib/librt.a LIBSDP?= ${DESTDIR}/usr/lib/libsdp.a LIBSKEY?= ${DESTDIR}/usr/lib/libskey.a LIBSL?= ${DESTDIR}/usr/lib/libsl.a LIBSS?= ${DESTDIR}/usr/lib/libss.a LIBSSH?= ${DESTDIR}/usr/lib/libssh.a LIBSSL?= ${DESTDIR}/usr/lib/libssl.a LIBSSP?= ${DESTDIR}/usr/lib/libssp.a LIBSTDCXX?= ${DESTDIR}/usr/lib/libstdc++.a LIBSUPCXX?= ${DESTDIR}/usr/lib/libsupc++.a LIBTERMCAP?= ${DESTDIR}/usr/lib/libtermcap.a LIBUSBHID?= ${DESTDIR}/usr/lib/libusbhid.a LIBUTIL?= ${DESTDIR}/usr/lib/libutil.a LIBWRAP?= ${DESTDIR}/usr/lib/libwrap.a LIBY?= ${DESTDIR}/usr/lib/liby.a LIBZ?= ${DESTDIR}/usr/lib/libz.a SHAREDSTRINGS If defined, a new .c.o rule is used that results in shared strings, using xstr(1). Note that this will not work with parallel makes. STRIPFLAG The flag passed to the install program to cause the binary to be stripped. SUBDIR A list of subdirectories that should be built as well. Each of the targets will execute the same target in the subdirectories. SCRIPTS A list of interpreter scripts [file.{sh,csh,pl,awk,...}]. These are installed exactly like programs. SCRIPTSDIR The location to install the scripts. Each script can be installed to a separate path by setting SCRIPTSDIR_<script>. SCRIPTSNAME The name that the above program will be installed as, if different from ${SCRIPTS}. These can be further specialized by setting SCRIPTSNAME_<script>. FILES See description of <bsd.files.mk>. SHLINKDIR Target directory for shared linker. See description of <bsd.own.mk> for additional information about this variable. The include file <bsd.prog.mk> includes the file named "../Makefile.inc" if it exists, as well as the include file <bsd.man.mk>. Some simple examples: To build foo from foo.c with a manual page foo.1, use: PROG= foo .include <bsd.prog.mk> To build foo from foo.c with a manual page foo.2, add the line: MAN= foo.2 If foo does not have a manual page at all, add the line: MKMAN= no If foo has multiple source files, add the line: SRCS= a.c b.c c.c d.c =-=-=-=-= bsd.rpc.mk =-=-=-=-= The include file <bsd.rpc.mk> contains a makefile fragment used to construct source files built by rpcgen. The following macros may be defined in makefiles which include <bsd.rpc.mk> in order to control which files get built and how they are to be built: RPC_INCS: construct .h file from .x file RPC_XDRFILES: construct _xdr.c from .x file (for marshalling/unmarshalling data types) RPC_SVCFILES: construct _svc.c from .x file (server-side stubs) RPC_SVCFLAGS: Additional flags passed to builds of RPC_SVCFILES. RPC_XDIR: Directory containing .x/.h files =-=-=-=-= bsd.shlib.mk =-=-=-=-= The include file <bsd.shlib.mk> computes parameters for shared library installation and use. It defines no targets. <bsd.own.mk> MUST be included before <bsd.shlib.mk>. <bsd.own.mk> sets the following variables, if they are not already defined (defaults are in brackets): SHLIBINSTALLDIR If ${USE_SHLIBDIR} is not "no", use ${SHLIBINSTALLDIR} instead of ${LIBDIR} as the base path for shared library installation. [/lib] SHLIBDIR The path to USE_SHLIBDIR shared libraries to use when building a program. [/lib for programs in /bin and /sbin, /usr/lib for all others.] _LIBSODIR Set to ${SHLIBINSTALLDIR} if ${USE_SHLIBDIR} is not "no", otherwise set to ${LIBDIR} SHLINKINSTALLDIR Base path for shared linker. [/libexec] SHLINKDIR Path to use for shared linker when building a program. [/libexec for programs in /bin and /sbin, /usr/libexec for all others.] =-=-=-=-= bsd.subdir.mk =-=-=-=-= The include file <bsd.subdir.mk> contains the default targets for building subdirectories. It has the same eight targets as <bsd.prog.mk>: all, clean, cleandir, depend, includes, install, lint, and tags. It uses the following variables: NOSUBDIR If this variable is defined, then the SUBDIR variable will be ignored and subdirectories will not be processed. SUBDIR For all of the directories listed in ${SUBDIR}, the specified directory will be visited and the target made. There is also a default target which allows the command "make subdir" where subdir is any directory listed in ${SUBDIR}. As a special case, the use of a token .WAIT as an entry in SUBDIR acts as a synchronization barrier when multiple make jobs are run; subdirs before the .WAIT must complete before any subdirs after .WAIT are started. See make(1) for some caveats on use of .WAIT and other special sources. =-=-=-=-= bsd.sys.mk =-=-=-=-= The include file <bsd.sys.mk> is used by <bsd.prog.mk> and <bsd.lib.mk>. It contains overrides that are used when building the NetBSD source tree. The following variables control how various files are compiled/built. (Note that these may be overridden in <bsd.own.mk> if USETOOLS == "yes"): AR Create, modify, and extract from archives. [ar] ARFLAGS Options to ${AR}. [rl] AS Assembler. [as] AFLAGS Options to ${CC} when compiling or linking .s or .S assembly source files. [] BUILDSEED GCC uses random numbers when compiling C++ code. If this option is present, seed the random number generator based on the value, source file names and the output file name to make builds more deterministic. Additional information is available in the GCC documentation of -frandom-seed. CC C compiler. [cc] CFLAGS Options to ${CC}. [Usually -O or -O2] CPP C Pre-Processor. [cpp] CPPFLAGS Options to ${CPP}. [] CPUFLAGS Optimization flags for ${CC}. [] CXX C++ compiler. [c++] CXXFLAGS Options to ${CXX}. [${CFLAGS}] ELF2ECOFF Convert ELF-format executable to ECOFF. [elf2ecoff] FC Fortran compiler. [f77] FFLAGS Options to {$FC}. [-O] HOST_SH Shell. This must be an absolute path, because it may be substituted into "#!" lines in scripts. [/bin/sh] INSTALL install(1) command. [install] LEX Lexical analyzer. [lex] LFLAGS Options to ${LEX}. [] LPREFIX Symbol prefix for ${LEX} (see -P option in lex(1)) [yy] LD Linker. [ld] LDFLAGS Options to ${CC} during the link process. [] LINT C program verifier. [lint] LINTFLAGS Options to ${LINT}. [-chapbxzFS] LORDER List dependencies for object files. [lorder] MAKE make(1). [make] MKDEP Construct Makefile dependency list. [mkdep] NM List symbols from object files. [nm] PC Pascal compiler. [pc] (Not present) PFLAGS Options to ${PC}. [] OBJC Objective C compiler. [${CC}] OBJCFLAGS Options to ${OBJC}. [${CFLAGS}] OBJCOPY Copy and translate object files. [objcopy] OBJDUMP Display information from object files. [objdump] RANLIB Generate index to archive. [ranlib] SIZE List section sizes and total size. [size] STRIP Discard symbols from object files. [strip] TSORT Topological sort of a directed graph. [tsort -q] YACC LALR(1) parser generator. [yacc] YFLAGS Options to ${YACC}. [] YHEADER If defined, add "-d" to YFLAGS, and add dependencies from <file>.y to <file>.h and <file>.c, and add <foo>.h to CLEANFILES. YPREFIX If defined, add "-p ${YPREFIX}" to YFLAGS. Other variables of note (incomplete list): NOGCCERROR If defined, prevents passing certain ${CFLAGS} to GCC that cause warnings to be fatal, such as: -Werror -Wa,--fatal-warnings (The latter being for as(1).) WARNS Crank up GCC warning options; the distinct levels are: WARNS=1 WARNS=2 WARNS=3 WARNS=4 =-=-=-=-= bsd.x11.mk =-=-=-=-= The include file <bsd.x11.mk> contains parameters and targets for cross-building X11 from ${X11SRCDIR.xc} / ${X11MITSRCDIR.*}. It should be included after the general Makefile contents but before the include files such as <bsd.prog.mk> and <bsd.lib.mk>. It provides the following targets: .man.1 .man.3 .man.4 .man.5 .man.7: If ${MAN} or ${PROG} is set and ${MKMAN} != "no", these rules convert from X11's manual page source into an mdoc.old source file. cleanx11man: Clean up the mdoc.old files generated by the above. It sets the following variables: BINDIR Set to ${X11BINDIR}. To override, define after including <bsd.x11.mk> LIBDIR Set to ${X11USRLIBDIR}. To override, define after including <bsd.x11.mk> MANDIR Set to ${X11MANDIR}. To override, define after including <bsd.x11.mk> CPPFLAGS Appended with definitions to include from ${DESTDIR}${X11INCDIR} LDFLAGS Appended with definitions to link from ${DESTDIR}${X11USRLIBDIR} X11FLAGS.CONNECTION Equivalent to X11's CONNECTION_FLAGS. X11FLAGS.EXTENSION Equivalent to X11's EXT_DEFINES. X11FLAGS.LOADABLE Equivalent to X11's LOADABLE. X11FLAGS.OS_DEFINES Equivalent to X11's OS_DEFINES. X11FLAGS.SERVER Equivalent to X11's ServerDefines. X11FLAGS.THREADLIB Equivalent to X11's THREADS_DEFINES for libraries. X11FLAGS.THREADS Equivalent to X11's THREADS_DEFINES. X11FLAGS.VERSION cpp(1) definitions of OSMAJORVERSION and OSMINORVERSION. X11FLAGS.DIX Equivalent to X11's DIX_DEFINES. X11TOOL_UNXCOMM Commandline to convert `XCOMM' comments to `#' It uses the following variables: APPDEFS List of app-default files to install. CPPSCRIPTS List of files/scripts to run through cpp(1) and then ${X11TOOL_UNXCOMM}. The source files have a `.cpp' suffix, the generated files do not. CPPSCRIPTFLAGS Additional flags to cpp(1) when building CPPSCRIPTS. CPPSCRIPTFLAGS_<fn> Additional flags to cpp(1) when building CPPSCRIPT <fn>. =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=


text:
Let me offer you a real estate advantage!
My goal is to provide you with the perfect buying and selling experience by making the process more manageable. By leveraging the power of the CENTURY 21 brand with market knowledge and dedicated service I am confident that I can provide an integrated real estate solution for real people.
There are a total of 50 properties matching your search.
To gain unrestricted access to the full details of available listings please login or click here to create a free account.
Sign In or Create Free Account
Register Login

subset: commoncrawl


text:
Senator Rand Paul (R-KY) is supporting a bill to ban the use of domestic drones to monitor citizens in the U.S. He spoke with CNN's Carol Costello a day after a U.S. Navy drone crashed in Salisbury, Maryland.
Here is the transcript:
Costello: The smoldering wreckage is still there lying in a marsh in Salisbury, Maryland. It's what's left of a military drone. No injuries. No property damage, but $176 million loss for the air force. The air force is still investigating why this thing crashed. The drone is used for military purposes, but smaller drones are being used by law enforcement agencies across the country. Police say these small drones can fly low and undetected and help them fight crime. The American Civil Liberties Union says it's a violation of personal rights. Republican Senator Rand Paul does too. He's here now. Welcome, Senator.
Paul: Good to be with you.
Costello: Tell us about your anti-drone bill. I actually have it right here, and I'm amazed it's three pages long.
Paul: Well, you know, I got the idea from Representative Austin Scott. So I have to give him some credit from Georgia. He told me about the bill recently. We picked it up and are introducing it as the senate version. Yeah, I'm a big fan of the fourth amendment. Not only do I like the second amendment, I like the fourth amendment. I think you should have to have a warrant to invade people's privacy and to spy on them. And so I think it's very important. And this just basically restates the Constitution. But sometimes you have to restate the Constitution because many up here seem so ignore it. And Representative Scott when he told me about the bill he said, look, when I'm out hunting on my property, I don't want them spying on me. And I'm not a hunter. But when I'm separating out my recyclables, I don't want them having a drone to make sure I'm putting my newspaper in the proper bin.
Costello: Well, we've already got drone launch sites in more than 20 states. Police are pretty excited about this new crime fighting tool. So would your bill make these launch sites go away?
Paul: What it would do is there's a balancing act. I mean police do have power and I want police to catch rapists and murderers. But they ask a judge and we separate the police from the people who finally make the decision on someone coming in your house. So even if a rapist is loose in D.C. tonight, the police will call a judge in the middle of the night, wake him or her up and say, we think there's a rapist in the neighborhood. Can we go in x address? And so those are things that are very, very important to protecting innocent individuals. And a drone is a very, very powerful way of snooping on behavior. And I don't want them monitoring every bit of my behavior. And I'm not joking about the recyclables. I mean, we've had different states and cities trying to punish people criminally for not separating out the recyclables. We don't want a nanny state that watches every minute of our day. It's not that there will be no drones it's just that drones will only be used when a judge says that it's proper.
Costello: What about in this instance? One Texas sheriff told reporters his agency is considering arming his drones with rubber bullets and tear gas. Let's say there's a large crowd gathering and you need some crowd control. This type of drone might be able to diminish any problems on the ground. Would that be allowed under your bill?
Paul: Anything that would require a warrant. It would have to have a warrant. And I'm concerned about obviously arming drones. But I don't want to say that I'm arguing against technology. For example, there's a bomb in a car, I'm very happy that we have automated robots that can go up to the car and investigate the bomb and we don't have to risk a human. Same with drones. If they can save lives, that'd be one thing. Arming drones obviously sends up pictures of the military and I don't think domestically armed drones are a good idea. What I would say is that drones could be used if you have a proper warrant. But that means you go through a judge. A judge has to say there is probable cause of a crime. But I don't want drones roaming across, crisscrossing our cities and our country snooping on Americans. And that's the surveillance state that I'm very concerned about. And that's what our bill would stop.
Costello: This military drone that crashed in Salisbury, Maryland, the ACLU is also concerned that these domestic drones may crash randomly in some neighborhood and hurt people. Is that a concern you have too?
Paul: I think that could be a danger. I don't know the safety profile of you know how good they are. But they do crash occasionally. So this one crashed and we also lost the one in Iran. So I think there is some danger. But I'm not against technology per se. What I am for are the constitutional processes that protect our civil liberties. So, you know, it's not like I'm against the police using cars or against them using airplanes or helicopters or robots. But I am for personal privacy for saying that no policeman will ever do this without asking a judge for permission. That was the recent case where the police were tagging GPS tags on your car without a warrant. The Supreme Court was very clear on this. Struck it down 9-0. So I feel comfortable that conservatives and liberals on the Supreme Court are concerned about privacy and technology's ability to invade our privacy. So I am very, very concerned about this, and I think this is a very serious bill. And we'll push forward and I'm going to talk to Senator Reid and Senator McCconnell about allowing a vote on it.
Costello: Do you have the same types of concerns about military drones being used in other countries or does your bill just specifically deal with drones flying over the United States?
Paul: This would only be domestic.
Costello: Do you have concerns about the use of military drones in other countries?
Paul: I am concerned about one person deciding the life or death of not only foreigners but U.S. citizens around the world. And the chance that one person could make a mistake, you know, is a possibility. So having the president decide who he's going to kill concerns me. I would rather it go through a court, and there are actually secret courts, the FISA court investigates intelligence information. And most of these decisions aren't made like this. They make the decision over weeks and months. They target people and go after them. I see no reason why there couldn't be some sort of court preceding, even a secret court preceding, to allow some protection. I mean even in the United States where we have the best due process probably in the world, we have probably executed people wrongfully for the death penalty. They have found out through DNA testing, many people on death row are there inaccurately. And even Republicans have pulled back their beliefs some on death penalty. So I think when we decide to kill someone, that's obviously the ultimate punishment. We need to be very, very certain that what we're doing is not in error.
Costello: Senator Paul, thank you so much for being with us this morning. We appreciate it.
The bodily and economic consequences of an automobile accident can injure for years. Visit here to discover how our auto crash lawyers can protect your civil liberties.
auto accident lawyer http://cars-accident-lawyer.blogspot.com/
Hello! dddkfkg interesting dddkfkg site! I'm really like it! Very, very dddkfkg good!
This is another one of Rand Paul's lies..Ron Paul has never lied to anyone..he has always spoken the truth and he didn't come to Rands aid after he endorsed Romney and we all rejected his son.I think Ron Paul figures my Son is a man and makes his own decisions and also will have to pay the price of those decisions,Now Rand just came out with Legislation he is trying to sell to us..Giving Cops around our Nation Drones but only with a Judges signature, now doesn;t that make u feel cozy..Cops with drones flying over us Rand's Legislation!!!..No Rand and no to your right to work Law..We have enough Federal laws stamped on our backs..this guy is scary don't give a dime to his so called Liberty movement ..It's the slavery movement!!!
you need to relisten to what he is saying. He is triing to stop them from having free range.
Man now they are taking away our freedom of speech o this site!!!..It won't let me post what i really want to say..Don't even vote for Rand Paul not even for Dog catcher...He's advocating a Tyrrntical police state a Dictatorship!!! We aren't giving up our freedom for any amount of Security when u do u loose both!!!
I hope the cameras on the domestically employed drones have sufficient resolution to detect my upraised middle finger.
Let's see you liberals were screaming at the top of your lungs about how the "Patriot Act" was an invasion of privacy when Bush introduced it.
Yet now that your man is in office and kept the PA in place, instead of repealing it like he promised during his campain. He even wants to take it a step further and start using "Domestic Drones".
So tell me liberals where is the invasion of privacy outrage? Me I'm against the PA and these so called domestic drones.
Oh but haven't you heard, Rand Paul just introduced legislation for all cops across our Nation to have and use drones ..as long as they have a Judges Signature..oh well that makes it all better now doesn't it?..Rand Paul is more than a sell out..He is a devil in diguise ..don't give a dime to his Liberty movement, Its the slavery movement and he is not a Patriot he is N.W.O.
Honesty you're name is wrong it should be full of crap.
It's only a matter of time. We're headed toward that sci-fi world where the government controls everyone and everything from the sky. Spy cameras that can see through the roof of your home, drones that can strike at a moment's notice. All to keep the populace in check. THAT is the ultimate democracy.
Bob - Seek professional help ! ! !
Hate to tell you this but he is not far off. The police already are using an exray robot that they control by remote that looks through walls and can tell where the people are at in the house.
If this is the case, then it's time for a Revolution!!!
Obama might use domestic drones to get rid of his opposition. He might designate his opposition as enemy of the US and enter them on his hit list.
Also there is not compeling reason to have drones fight crime in the US. Helicopters with personnel provide better acountability for actions.
In addition to giving big brother more power, the drones mean another use of our budget and more income for the drones' manufactuerers. Since their lobby is just unbeatable, expect to have them drones flying all over us.
Unless we get united and vote out any politician supporting the use of those machines. I am sure they will continue to crash down putting in danger of death citizens wherever the drone fly.
This "government" is not concerned with saving lives, they are only concerned with controlling people, and the best way to do that is to keep them in a constant state of fear. Who have them the right to even consider using drones on us? We should kick them ALL out, and don't replace them! Elections are so stupid, anyway, and we don't need rulers, and laws. They have no right taking our money for taxes, either.
So this loser is against the drones but voted for the patriot act. I find it very difficult to care about anything in this country anymore. This nation of idiots gets exactly what it deserves. Personally, I just don't give a damn.
Hey The King, isn't Senator Paul the guy who actually defied Harry Reid and held up the vote for the Patriot Act until the gun records search provision was removed? At least he's trying...
so he ehld up the patriot act so that the government couldn't ensure that guns are registered. so any nut can get a gun, but the rest of the patriot act was just fine with him. give me a break!
Can you show me where Rand voted for the PATRIOT Act? Because I have yet to find anything verifying that...only the fact that he fought against it, tried to amend it, and stalled it as long as he could.
This is just another corporate take over. The manufacturers of these drones stand to lose billions. I heard they are manufactured in Israel. So what about American jobs? Naturally we get screwed both ways!
lol they are NOT made in israel.
The important point is that the Jews want the drones. Jews are turning America into a giant gulag. Exactly what they did to Russia.
Most of the jews in Israel came from Russia. Stalin was hunting them down and killing them as bad as Hitler...maybe worst.
I just farted.
The very people complaining so hard about it will be the 1st ones wondering where was our technology when something catastropic happens. if your doing nothing wrong why worry ?
Then why not set up cameras in every single household in America, starting with yours.? If you're not doing anything wrong...
Well Adam, I'm going to need you to submit to random searches of your house at any time, for any reason, as the police see fit.
Of course if you're not doing anything wrong, you should have nothing to hide, so you shouldn't mind the intrusion, right?
There's a big difference between cameras in my home and cameras outside. You go into my home, that's an invasion of privacy. My girlfriend and I don't want the government watching us in bed, etc. Once you're outside you can't expect any privacy. Duh. You might expect cops to be driving around looking for crime, though. So you have to explain why it's ok for cops to drive cars or fly helicopters to look for crime, but not ok to fly drones. Why draw the line at drones? And what about self-driving cars? Those will be common in the future, do you not want them either?
It makes me angry that so many people are against this, especially because it's coming from Rand. I love the Pauls, but this doesn't make sense. I had a friend, he was a music producer. One night he and his co-worker were leaving their studio, two thugs approached them right there on the sidewalk, shot 'em both dead and took their money. If they knew they were being filmed by drones that would not have happened. My friend would still be alive. There would be way fewer victims of murder/rape/theft. But you guys don't want drones all because of your precious "privacy" ...which does not even exist outside.
"But what about drones crashing? They could cause damage!"
So can cops, google "Cop Crashes Into Car Killing 2 Teens"
I bet the likelihood of a drone crashing is smaller than a cop crashing.
"But what if they catch me not recycling?"
This is a ridiculous argument. I really, really doubt they would be looking for relatively tiny things like that. And how would they catch that anyway? Don't you use trash bags? And even if they did catch you and punish you for this, so what? As Mr. Cheese explained above, recycling is important and it's law for good reason. Follow the law and there's no problem. But really, this is not the issue.
I haven't seen a single one of you give a valid reason for why there shouldn't be drones.
Contrary to Jeremy, being outside gives no one a right to invade my privacy. If Im walking or standing on a public street and having a private conversation with someone, it's still private. And if Im sitting on a river bank fishing, I still have a right to my privacy...NOT to be spied on. It wasnt that long ago when the camera was invented and less time since everyone had one. In some countries it was against the law to take someones picture without permission. Where is the moral character in culture any more? It's all been reduced down to copper and silver.
that's what they where saying in 1939 germany too, but yeah nothing bad happened from that right ? -_-
Personally I don't want the government using drones to determine that I am taking care of my personal business in a manner that some bureaucrat somewhere finds unacceptable. It's none of their beeswax what I do for fun with myself. Their drones need to stay away from my missile.
I think we need the most powerful drones one watching congress and the other watching wall street. We have the biggest thieves and thugs there, that are looting middle class Americans dry.
What is truely funny about the hand wringing about domestic drones is that far more powerful sensors have been flying over the US mounted to some very large manned aircraft for many decades. If people understood the power and discrimination of the sensors on aircraft like the U-2, EC-135 Rivet Joint, E-3 AWACS and E-8 JSTARS aircraft, they wouldn't be so excited about a comparatively simple think like a Global Hawk. Read up on the combat histories of these aircraft, what little is declassified, and you will be amazed what they can do. The Global Hawk is far less able to spy on you than some of these aircraft.
Two dang wrongs don't make a right..Rand Paul is a Red..He is a turncoat and his father is pleased with this legislation?..There is no one to vote for none..They all belong to the same club!!!..You don't give cops anymore power over Americans ..this is George Orwell stuff..The best thing we can do is Leave amarika..It has been demoralized which takes the communsist about 15 to 20 years..Thats done!..Then they Create Order out of Chaos..so they will create Chaos and then will come Normalcy...Which simply means We will be under total Communist Rule..This is how Hitler did it ,stalin and Mao se tung..Say goodbye to America with Rand's Legislation ..We don't give up 1/8th of one ounce of Freedom for any amount of security..When we do we loose both!!!..Who can trust a cop with a drone??.Innocent Americans are killed everyday by cops.We had one shoot a man from our church 7 times in the head for speeding..Now what do u think they are going to do with drones?..These guys are so pumped up with Testosterone they can't wait to try any new toy!!!..Ron Paul thinks this is good Legislation?..It looks like there is no one to vote for...When there looking for some rapist they will be looking in everyone's home that he was seen near..Nope ..This will cause a cival war in our own back yards and that is what they want Order out of chaos!!!
@ Cheese Wanton, a slight correction to an earlier statement you made; the Army does in fact have armed drones. Please see Sky Warrior or Grey Eagle, which are very similar to predators however have a diesel engine. These routinely are armed with hellfires and due to the diesel engine can carry 4 vs the standard 2 a regular pred-A can. Other than that though you seem pretty spot on.
I stand corrected, and learned something today. I have spoken to Army UAV crews in the past but my information in this case was stale. Thanks.
Cheeze you were right on the ones that were pre 2001. Before 2001 their main use was servailance and they could be aquiped with laser guided ability. In 2001 they started arming them with hell fire.
So Ron thinks that local police will use a UAV to "spy" on him and his recycle bins. I'm pretty sure the dude rapping a 13 year old in an ally will have priority over the recyclables. UAV's can be used for much more than just "spying" on citizens. Natural disasters, for one, a UAV could conduct search and rescue operations, and cover far more ground that a foot patrol could. Imagine, you are hiking with your family, and your child wonders off, you lose track of them...you contact the park ranger...they contact the local authorities that have access to a UAV, within a few hours that UAV could search for you missing child. Search parties on foot have to stop at some point, but the UAV and its crew could continue to search for hours after the foot patrol could.
There are far more advantages of having a UAV patrolling our cities than not. Most of you are saying that you have to have a warrant for a UAV to monitor you...in most cases that is true, but what about the police officer in his patrol car, does he need a warrant to look at drives and his surroundings? Same printable for the UAV crew.
Finally as far as the recent Global Hawk that went down this week, it is unfortunate that it went down...but don't all aircraft have the possibility of going down. I know in the past month, I have read many articles of manned aircraft crashing. So don't say UAV's are dangerous...manned aircraft are just as dangerous as unmanned.
Flying at night over large wildland fires in mountainous terrain is butt-puckering work. It is the natural environment for UAV's, to be used as sensor platforms that can stay aloft for very long times and serve as the eyes of the fire fighters on the ground.
Look, yes there is a huge difference between the military drones used for the "war on terror" vs the police drones they desire to use for domestic purposes. She states this plainly in the beginning. However, his example is just that, an example, from fighting "domestic terror" to citing you for your recyclables and -everything- in between. I agree yes in some cases, catching house robbery or domestic violence, it'd be awesome to have an immediate response but for every thing safety feature you are granted 10 freedoms are taken away.
Like cell phones text messages and phone conversations, a drone video feed will be a recording of everyone's actions during their day, a change in routine will most likely make you suspect just like saying any keyword over a phone or the internet can. I'm not saying factually this is true but who knows it could.
I know it seems ludicrous now and some joke about it, look back on other well-intended ideas that now are ridiculous and further obsessively used feature for law enforcement, red light cameras? It still costs more for them to keep them then be rid of them and the citation rate is still fairly low but it's just more then cops on the streets can produce so it's 'justified spending.' Realistic cost? Who knows what it will cost. Drone, maintenance, controller for drone, launch site costs etc. Just another tool to keep the nation bankrupt.
Armed domestic drones? I'm sorry US soil is not a massive prison yard (even if it feels like it sometimes.) Arming them in any fashion is not safe even if only for crowd control, police abusing power is bad enough, giving them a bigger fish to slap you isn't a good idea.
At very least, it should take a warrant and probable cause for a drone of any kind to be used for any purpose of security and defense.
You are exatley right and Rand Paul with this Legislation has sold america down the drain!!!
Domestic drones are already in use, at least he's trying to slow the madness that there is surrounding these machines. They already patrol some city streets. Again, at very least probable clause, not just whimsical privacy invasion.
You all need to not talk about something you know ABSOLUTELY nothing about. I work on these aircraft. They have a flight crew to prep them and redundant controls in place. A licensed military pilot flies these drones, all have prior experience flying "real" aircraft. The smaller drones are trouble because they are not regulated yet. Any technology can be exploited. Just because a jet goes down people jump on the "evil drone" evil big brother bandwagon. These MILITARY drones are a tool, just like any other the military uses. Civilian drones are a different story and up for debate as far as I'm concerned. You simply can't group the two together.
I like how you can just make a blanket statement like that. Should we just assume that you are privileged to all classified military information because of your post on a CNN board? You simply work on the equipment (probably has an enlisted person, no college degree) Our perpetual war on terrorism will slowly erode what is left of the republic, we will continue to slowly bankrupt ourselves to maintain this unrealistic military empire. Yes men like you will go along thinking that they are making the country safer, thinking that because you are "in" the military that you are privileged to all the information that is held for military purposes.
I also was in the military as an officer in the intel community. All tools of war have, historically, be abused by our government. It is the duty of the people and congress to maintain CHECKS on these tools. I can't even go into how stupid you sound right now.......
So all enlisted guys are dummies? I was enlisted, I have a college degree in Electrical Engineering and my position on the program is not something to divulge here. I'm sure there is information at a higher classification and everything I mentioned here is not classified. The particular aircraft that crashed takes pictures. What those pictures are used for I do know, most of the time. And you, Lieutenant Colonel sir, don't really know what is going on with the program. Most UAV's are used for reconnaissance, few as weapons. I agree with this Paul when it comes to domestic use. This technology would probably be abused. As for the war on terror, I can't argue it is bankrupting us. It's an issue there is no easy answer for. How many thousands of people and their families (military, contractor, corporate) depend on the defense industry to pay their bills? You, LTC, have a retirement check. How would you go about solving this issue? Will your degree and experience give you better insight? If so, please try to make a difference. I posted here because of the constant villainizing of a UAV that costs less to run than its manned counterpart and that is used MAINLY for lifesaving purposes. Read the other comments before blasting another.
You can't go into how stupid he sounds ... because you just realized you're operating on exactly the same wavelength? Or is it because you realized that you're actually operating below his because you're making wild assumptions about someone you don't even know on the intarwebs just because you don't agree (politically or philosophically) with his statement(s)? I'm former military intel myself, and guess what, it has absolutely no bearing on this conversation or anything I say. It doesn't necessarily make me more or less knowledgeable on the subject than anyone else, and to assume that it (or my former rank, or my former branch, or my former MOS, or the type and focus of my degree(s), or my work experience) gives me carte blanche to stomp on the opinions of others would just make me a sniveling worthless trollbag who bellows impotently across the webs at strangers - but I haven't done that, you have - so congrats on that.
It's a Military weapon used on combatants, American citizens are NOT Combatants. This is not a military nor a police state and marshal law is NOT authorized. NO Drones in the United States EVER for any reason!
Except on muslims right? They dont have any rights cuz all of them just want to kill americans
I believe you would prefer Christians die
Neither group looks to be worth saving, IMHO.
Civilian drones and Military drones are very different. Military ones are expensive, have vastly larger ranges, are significantly "hardened" against attack, etc. Civilian ones are essentially R/C aircraft with small video cameras. The results of a crash of Military drones are totally different from the results of a crash of civilian ones. (R/C vs very small plane.)
Those who worry excessively about them should also be worrying about street-view cameras etc. Those who don't think they should be restricted are far too trusting of government (and corporations.) So, yes, some restrictions should be applied. But let's not get carried away, either. Anyone taken a look at their house on Google Maps lately?
Have you looked at the crash site in Maryland? That was not a "RC Plane". If that crashed in a residential area it WOULD have killed people.
Refresh me...
Is America the calculating, devisive, duplicitous, omnipotent Big Brother who is hell bent on stealing away your privacy and rights for no lucrative reason...
or is America the sort who crashes RC planes on accident in densely populated areas.
You do realize this UAV was a test article for the Navy and crashed just outside the naval air station where the test program is conducted? And I assume you aware the UAV is being tested as a replacement for manned long range maritime patrol aircraft used to track ships and submarines? Just asking ................
Thermal you are wrong. The police departments are buying up the army drones as they are coming back from the middle east.
These are the same as the ones that are armed with hell fire missles. This is fact. I have read up on this and at any time they can rearm these drones.
Bzzzt. Wrong. None of the UAV's the Army operates are armed. Only the USAF and CIA operate armed drones, and these are quite large and expensive. What the US Army operates have some cameras and laser designators that allow them to lase targets for laser guided bombs and missiles fired by other aircraft, but they are too small to cary any sort of armament.
BZZZT Cheeze head I have seen the specks on the drones the police are buying up and they have tha capabilty of being armed with hell fire missiles. So before you try and sound like you know what you are talking about you need to read up on it. The government stated that they wouldn't use the satilite photo's against thepeople and what happens the people get a sapeena in the mail because they seen from 40 miles up that you built a deck that they can't tell from the air was legal. All you people on hear that think it won't happen that way you need to wake up.
Great job on this one, Rand Paul! You are a fool if you don't think domestic government agencies will start to abuse drones – finding ways to fine you for violations of an infinite code of laws and regulations. Red light cameras are really just a way for starved city governments to raise money...not for safety. Always follow the money. Contracts to make the drones and means of revenue raising through fines.
The UAV that crashed is being tested by the Navy as a means to find enemy ships and submarines in the open ocean. It is different from what the Air Force operates. It crashed outside the well known naval air station where the test program is conducted. It really is that simple.
You told everybody that this is a test aircraft operating in a test range. They should be able to grasp that. The crash plane is an Air Force Global Hawk transferred to the Navy to help develop their own variant for ocean surveillance. The Global hawk Block 30 is not wanted by the Air Force but congress tries to force it on them. Global Hawk has been unreliable and the NAvy is also trying to fix that.
Every time I try to post an explanation of what the UAV that crashed is and why it was flying where it was, my post is deleted. This is frustrating, because the UAV in question is not a dark conspiracy but is being tested by the Navy to replace a huge fleet of manned maritime patrol aircraft. What is with the censors at CNN?
I'm not trying to conspire, but seems to me like CNN sort of exalt the fanatics and fringe to sort of justify their own existence. I've had several very plain spoken, based on reason comments simply not show up. Most recently in telling a man who promoted "shoot the drones out of your neighborhood its time!" that he was dangerously misinformed...
Ditto, and it is tiring. I have tried to put some simple explanations of what the UAV is, what it does for the Navy and where it was flying from, none of which are even remotely secret, and the comments simply never appear.
Mr. Paul's worry about people being cited for not putting recyclable material in the proper bin is a vivid demonstration of how out of touch the man is. The reason for curbside recycling isn't some feel good greeny thing. No, it is done for the very practical reason that landfill space is limited, new landfills are extremely difficult to site and costly to develop, so municipalities and states try very hard to find ways to extend the life of existing landfills. That means the amount of trash going into land fills each year has to be reduced, and to do that you have to maximize recycling.
Recycling laws are written to require citizens to put recyclables into certain containers so they are segregated from the trash going into the landfill. Sorting wet trash for recyclables is difficult and costly. Having residents and businesses sort them and put them in dedicated containers is cheap and effective, which is why cities all over the world have curbside recycliing programs. Where has Mr. Paul been the last three decades?
LOL So your reply is that recycling laws are a good thing, and we should be punishing people for not doing it? Well played.
So you just respond with sarcasm without offering a counter-argument. Why shouldn't they be punished? Follow the law and there's no problem. If you don't agree with the law then say why.
Cities do not usually cite families for getting the wrong items in the trash bin. LA has had such a system for decades and it works well. They spot check bins and will issue a written warning and give the family some informaiton on what goes in what bin if it's discovered the family is not using the recycling bins correctly.
LA County is closing their largest landfill next year. It is beyond full and it's height was extended another 50 feet upwards to save the county money. Now, the trash that used to go into the Puente Hills landfill has to go by train to the Imperial Valley. This is hideously expensive. Another LA County landfill in Lancaster also closes next year. The Lopez Canyon Landfill closed last year as did the Bradly Dump. All of these are full. San Diego City has only one landfill adjacent MCAS Miramar, and the County down there already rail ships trash to Arizona. San Francisco's only landfill will have to close in 2014 and they haven't identified a new landfill, but that city already recycles over 75% of all solid waste (LA recycles around 60% and is striving for 75%). By 2020 all California cities and counties are required by law to divert a minimum of 75% of their solid waste into recycling programs to conserve landfill space. This is a big deal.
Believe it or not, there is also a little bit of a revenue stream in those recyclables that cities try to guard. It helps defray the costs of running recycling programs.
This is grandstanding pure and simple. From a practical perspective this is not an issue. Every drone costs a lot of money and needs several people to operate it. If the government is that interested in what I am doing then let them have at it. The accountants will stop them soon enough. They don't have the money to monitor known pedophiles so why the hell would I think they would watch me. It is not an issue unless you are growing marijuana on the back forty or buggering the neighbors kids. Find something important to care about.
The government doesn't care what you are doing. They are interested in finding and, if necessary, sinking the ships and submarines of nations we come into conflict with. That is why the Navy was flying this UAV. It crash right next to the naval air station where the test program is being conducted. The test ranges are all off the coast.
you have know idea what you are talking about. Drones take one person to operate and they are far cheaper to perchace and operate than a hellicopter. They are now triing to build and are in testing a drone that will not require a human at all but a computer will operate the drone. I think there might be something to what Rand is saying
There is a pilot and weapons/sensor operator in direct control of the UAV, but if there is an engagement authority to use deadly force requires decisions from higher in the chain of command, including attorneys and intel specialists. It is not a one person job.
Cheeze it takes only one man to operate a drone and one person to do the maintnance on it. I don't care what the protocall is that is all that is required to operate this equipment.
I don't think Ron Paul is really foolish enough to believe that the US military would use drones to spy on its own citizens, so this leads me to believe that he's against the existence of drones because it conveniently serves his narrative. Not a single one of you reading this article are interesting enough, dastardly enough, sneaky enough, or remote enough to justify the use of a $176 million dollar piece of equipment. I spent years basking in the anti-establishment train of thought and Ron Paul was someone I admired above all others (I still hold a great deal of admiration for him, for the record) But as I grow older and open more history books, his interpretation of history and his perception of what America is and intends to do is driven by paranoia and delusions of grandeur.
How do I know the military isn't using drones to spy on citizens? Because you and I aren't worth that much and aren't capable of anything that couldn't be stopped by local law enforcement. Oh, you are? State law enforcement then. Oh you are? Federal investigators then. Oh you are?
no you aren't. get over yourselves people.
The military isn't using drones domestically to monitor civilians.
But DHS is.
Do the research .
Cite your sources. My point is this:
We are all already uncontested, under their thumb so to speak. The establishment doesn't need to use drones on you because you live in their back yard. It would be similar to you grabbing your head with both hands, and snapping your neck backwards just to see what was causing the itch on your back. It sounds so juicy, drones on American soil, but when you strip away the conspiratorial frill, it is surprisingly underwhelming. If I could beg anyone to just temporarily see America for a global force for stability and good, just a split second:
If we cant build and test these units here in America, where would we test these things? On foreign soil? Oh, I don't think so, Ron Paul is avidly against virtually any sort of American military presence overseas. If we can't build them and test them to make sure they perform we'll, we automatically resort to wasting the lives of American soldiers to do surveillance on the ground which could be done ELEVEN miles high, with no possibility of casualty.
This was a Navy UAV that is being tested for patrolling the oceans looking for enemy ships and subs. Nothing more. It crashed near a well known naval air station. It is not a dark conspiracy.
Really Parker? You haven't heard of domestic UAV use? It's been in the news quite a bit for the last couple of years... DHS has a bunch (of Predator B drones, a variant of the Predator you hear about in Afghanistan) and is buying more and giving money to other law enforcement agencies to do the same.
No disrespect, but it might be worth doing more research before chiming in.
Don't you mean RAND Paul?
The U.S. military can't be trusted. They are being trained to kill American civilians without question. I was asked during training if I would fire on unarmed American civilians if ordered by my superiors. Do not be foolish enough to believe that they are there to help us.
Can't wait until I can fly my drones over the White House – they have nothing to hide, right?
If you do not like what your government is doing, vote it out. Shoot down drones in your neighborhoods. Write to your newspapers and congressmen. Make yourself heard. It is only going to get worse if we tolerate it.
You are telling me that you can shoot a bullet 11 miles into the air to hit a drone with 100% accuracy. Keep in mind if you miss that bullet does come back down.
And if that bullet doesn't get it then his laser pointer will blind the UAV's sensors, lol. People have funny ideas, don't they?
Remember that old adage "It is better to keep your mouth shut and be thought a fool, than to open your mouth and remove all doubt." Well Mr. Paul has removed all doubt as far as I'm concerned. Also, no the police will not stop you unless they have resonable doubt. And they don't put up cameras in your neighborhood to spy on you. That's paranoid, unless of course you have something to hide, or maybe you are doing something illegal, Mr. Terrorist? "So stay right where you are we will be right there."
The police have been using drones to map (quoting the news and other sources) large citys in the US for tactical responces. Realy. Do you realy think that is the only reason they are using the drones for. The satilites (hope I spelled that right) have been mapping out our citys for years so what are the drones doing fliing over the citys.
I never thought I would say this but I actually agree with Paul. I mean what's next? Are they going to lock cameras and microphones around everyones neck? Enough already with the big brother stuff and the morality taxes.
The government just needs to look up your Facebook if they want any info on you
Lil Paul is a pretty good speaker. He makes an easy point, I don't see what's so hard for our government to grasp about this. People are willing to let surveillance happen, they just want some accountability via a court issued warrant with it. Drones will be used in America one time or or another. It is much different to use them with purpose and oversight via a warrant to using them indiscriminately and flying them all the time. The same applies to the Patriot Act, I don't see why it is so hard to get a warrant to investigate terrorism. For that matter you can put NDAA up there too. Is it really so hard to just get a warrant or to take someone you detain to trial instead of just locking them away indefinately?
I'm not sure I see any difference between a drone, police helicopter or a million security cameras mounted on every street corner. I'm a law abiding citizen, but the police don't need to know that at 10:32pm Sunday night I took my trash out, looked up the street and down the street, spent 3 minutes talking to my neighbor while he was taking his trash out. Just because we can observe anything and everything, doesn't mean we should.
OK, I'm putting up cameras to monitor my neighbors back yards.
What an idiot. He does not understand even the basics of what it takes to control a drone or that the expectation of privacy is really pretty limited to the inside of your home.
The expecation of privacy means the police or any government agency doesn't have the right to stop, question, or search me, my car or residence without probable cause. The police stops you for running a red light and asks if he can search your car? You're Joe Public and have never broken a law until now. You know your car is clean, do you let him or do you tell him, "Sorry officer, there is no reason for you to search." I'll tell him no. If he wants to get a warrant I'll wait.
He is briefed at a far higher security level, than your punk ass...
And no, the gov DOES need a warrant to spy on somebody, regardless of their location.
Look it up.
Can you point us to where that can be looked up?