kpriv/pkgsrc
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity
pkgsrc/mk/platform/Linux.mk

107 lines
3.5 KiB
Makefile
Raw Normal View History

Begin cleanup of setgid game infrastructure. * Introduce USE_GAMESGROUP, which causes the games user and group to be made available. * Retain SETGIDGAME as an alias for USE_GAMESGROUP. Describe it as deprecated. * Always define GAMES_USER, GAMES_GROUP, GAMEMODE, GAMEDIRMODE, and GAMEDATAMODE, regardless of whether USE_GAMESGROUP is turned on or not. * Define these variables in defaults/mk.conf instead of separately in every platform/*.mk file. The definitions used to be the same for each of these platforms anyway, except for some where they were randomly missing or commented out for no clear reason, leading to broken game packages. * Handle all these variables properly when unprivileged. * Update the comments/documentation for these variables. * Describe GAMEOWN and GAMEGRP as deprecated. These need to be retained as aliases for GAMES_USER and GAMES_GROUP respectively for supporting packages that use bsd.*.mk but should otherwise not be used. * Add GAMEDATA_PERMS and GAMEDIR_PERMS using GAMEDATAMODE and GAMEDIRMODE respectively. * Fix a bug I noticed that was improperly mixing the "games" group and "games" user. Things this does *not* do: - get rid of GAMES_USER, for which there should ultimately be no need. - move the declaration/documentation/default value of USE_GAMESGROUP to a suitable place. (It is currently where SETGIDGAME was, which is suboptimal.) - touch any of the games, all of which need updating with at least s/SETGIDGAME/USE_GAMESGROUP/ and probably more. - update the guide to explain how to handle games properly. Also, it would be nice if using GAMES_GROUP without setting USE_GAMESGROUP=yes caused an error but as far as I know there isn't any particularly good way to arrange this right now. Note that these changes may alter the build/install behavior of broken game packages, e.g. some may silently become setgid when they weren't before or things like that. If you run into any of this file a PR. While one might arguably bump the PKGREVISION of all games or other packages using any of these variables as a precaution, that seems like a bad idea. Instead, I think I will be bumping each game once it itself has been fixed up to do everything the right way.
2010-07-08 06:57:36 +02:00
# $NetBSD: Linux.mk,v 1.40 2010/07/08 04:57:36 dholland Exp $
Migrate some OS-specific variable definitions into OS-specific files. Include it in bsd.prefs.mk to allow their use much earlier in Makefiles, and try to use the variable references instead of directly invoking the programs in bsd.prefs.mk and bsd.pkg.mk where possible.
2001-06-12 14:49:55 +02:00
#
# Variable definitions for the Linux operating system.
First pass at converting pkgsrc to use the new tools framework (still not on by default). Separate out the variable defintions that are now made by the new tools framework. Some of the trickier platforms (AIX, IRIX, Interix, OSF1) still need more work.
2005-05-03 20:30:12 +02:00
ECHO_N?= ${ECHO} -n
Only force gmake for imake on Linux, if using native implementation.
2008-01-12 23:44:10 +01:00
.if !defined(X11_TYPE) || ${X11_TYPE} == "native"
Reverted the last changes, which factored out some definitions that are usually the same on the supported platforms. The reason for having duplicate code in these files is to make it easier to port pkgsrc to a new platform: You just have to copy one of the existing platform files and edit the values in it. With some values factored out, you would have to look at one more file. Pointed out by agc@.
2007-10-19 15:41:34 +02:00
IMAKE_MAKE?= ${GMAKE} # program which gets invoked by imake
imake should only ever use gmake if ${X11_TYPE}==native. Pointed out by joerg@ Fixes PR 42274 OK wiz@
2010-03-18 23:46:01 +01:00
IMAKE_TOOLS= gmake # extra tools required when we use imake
Only force gmake for imake on Linux, if using native implementation.
2008-01-12 23:44:10 +01:00
.endif
First pass at converting pkgsrc to use the new tools framework (still not on by default). Separate out the variable defintions that are now made by the new tools framework. Some of the trickier platforms (AIX, IRIX, Interix, OSF1) still need more work.
2005-05-03 20:30:12 +02:00
IMAKEOPTS+= -DBuildHtmlManPages=NO
Reverted the last changes, which factored out some definitions that are usually the same on the supported platforms. The reason for having duplicate code in these files is to make it easier to port pkgsrc to a new platform: You just have to copy one of the existing platform files and edit the values in it. With some values factored out, you would have to look at one more file. Pointed out by agc@.
2007-10-19 15:41:34 +02:00
PKGLOCALEDIR?= share
First pass at converting pkgsrc to use the new tools framework (still not on by default). Separate out the variable defintions that are now made by the new tools framework. Some of the trickier platforms (AIX, IRIX, Interix, OSF1) still need more work.
2005-05-03 20:30:12 +02:00
PS?= /bin/ps
Fix typo.
2005-08-02 05:38:09 +02:00
# XXX: default from defaults/mk.conf. Verify/correct for this platform
First pass at converting pkgsrc to use the new tools framework (still not on by default). Separate out the variable defintions that are now made by the new tools framework. Some of the trickier platforms (AIX, IRIX, Interix, OSF1) still need more work.
2005-05-03 20:30:12 +02:00
# and remove this comment.
SU?= /bin/su
TYPE?= type # Shell builtin
Reverted the last changes, which factored out some definitions that are usually the same on the supported platforms. The reason for having duplicate code in these files is to make it easier to port pkgsrc to a new platform: You just have to copy one of the existing platform files and edit the values in it. With some values factored out, you would have to look at one more file. Pointed out by agc@.
2007-10-19 15:41:34 +02:00
CPP_PRECOMP_FLAGS?= # unset
DEF_UMASK?= 022
Move some operating-system specific definitions to the individual defs.${OPSYS}.mk files.
2001-11-21 15:10:06 +01:00
DEFAULT_SERIAL_DEVICE?= /dev/null
Apply patches from Lubomir Sedlacik <salo@Xtrmntr.org> in PR 18115 to generalise the linker flags used to export symbols by setting them on a per-OS basis. > many packages force -Wl,-export-dynamic which is not portable outside GNU ld > and cause problems e.g. on Solaris. some of these packages use if > conditionals either only for NetBSD or except SunOS, but the state is not > coherent and it may complicate later when support for new OS is added to > pkgsrc (e.g. ongoing work on HP-UX support). > > jlam proposed the following framework in discussion on tech-pkg: > > http://mail-index.netbsd.org/tech-pkg/2002/06/21/0009.html > > now, ${EXPORT_SYMBOLS_LDFLAGS} is used instead of directly defining > -Wl,-export-dynamic which is set in appropriate defs.*.mk to reasonable > values. packages should be converted to this framework by: > > 1) replacing LDFLAGS+= -Wl,-export-dynamic and LIBS+= -export-dynamic with: > > LDFLAGS+= ${EXPORT_SYMBOLS_LDFLAGS} > > 2) for use in patchfiles, add this variable to MAKE_ENV if needed: > > MAKE_ENV+= EXPORT_SYMBOLS_LDFLAGS=${EXPORT_SYMBOLS_LDFLAGS} > > 3) replace occurances of -Wl,-export-dynamic and -export-dynamic in patch > files with: > > $(EXPORT_SYMBOLS_LDFLAGS)
2002-09-04 16:47:32 +02:00
EXPORT_SYMBOLS_LDFLAGS?= # Don't add symbols to the dynamic symbol table
Move some operating-system specific definitions to the individual defs.${OPSYS}.mk files.
2001-11-21 15:10:06 +01:00
GROUPADD?= /usr/sbin/groupadd
Move MOTIF_TYPE_DEFAULT and MOTIF12_TYPE_DEFAULT definitions into the individual defs.${OPSYS}.mk files. No change in functionality.
2001-11-21 14:54:14 +01:00
MOTIF_TYPE_DEFAULT?= openmotif # default 2.0 compatible libs type
for SSD/Linux, /usr/bin/false, not /bin/false.
2010-02-13 09:29:12 +01:00
.if exists(/usr/bin/false)
NOLOGIN?= /usr/bin/false
.else
Use /bin/false instead of false for NOLOGIN
2004-09-13 14:09:22 +02:00
NOLOGIN?= /bin/false
for SSD/Linux, /usr/bin/false, not /bin/false.
2010-02-13 09:29:12 +01:00
.endif
Reverted the last changes, which factored out some definitions that are usually the same on the supported platforms. The reason for having duplicate code in these files is to make it easier to port pkgsrc to a new platform: You just have to copy one of the existing platform files and edit the values in it. With some values factored out, you would have to look at one more file. Pointed out by agc@.
2007-10-19 15:41:34 +02:00
PKG_TOOLS_BIN?= ${LOCALBASE}/sbin
Provide per-${OPSYS} defaults for how to run a command as root. Darwin ships with a disabled root account and a working "sudo".
2002-07-15 18:24:01 +02:00
ROOT_CMD?= ${SU} - root -c
Add support of SSD/Linux. * ROOT_GROUP=wheel, fixes PR#42073. * LOWER_VENDOR=ssd * adjust paths for some tools
2010-01-16 03:16:35 +01:00
.if exists(/etc/ssdlinux_version)
ROOT_GROUP?= wheel
.else
The standard "root" group under Linux is "root" not "wheel". PR #22566
2003-08-25 17:47:15 +02:00
ROOT_GROUP?= root
Add support of SSD/Linux. * ROOT_GROUP=wheel, fixes PR#42073. * LOWER_VENDOR=ssd * adjust paths for some tools
2010-01-16 03:16:35 +01:00
.endif
Move some operating-system specific definitions to the individual defs.${OPSYS}.mk files.
2001-11-21 15:10:06 +01:00
ROOT_USER?= root
SERIAL_DEVICES?= /dev/null
Reverted the last changes, which factored out some definitions that are usually the same on the supported platforms. The reason for having duplicate code in these files is to make it easier to port pkgsrc to a new platform: You just have to copy one of the existing platform files and edit the values in it. With some values factored out, you would have to look at one more file. Pointed out by agc@.
2007-10-19 15:41:34 +02:00
ULIMIT_CMD_datasize?= ulimit -d `ulimit -H -d`
ULIMIT_CMD_stacksize?= ulimit -s `ulimit -H -s`
ULIMIT_CMD_memorysize?= ulimit -m `ulimit -H -m`
Move some operating-system specific definitions to the individual defs.${OPSYS}.mk files.
2001-11-21 15:10:06 +01:00
USERADD?= /usr/sbin/useradd
Add a definition of _IMAKE_MAKE to the individual defs.${OPSYS}.mk files, defined to be the make program which is invoked by imake, and use it accordingly in bsd.pkg.mk
2001-11-21 13:53:04 +01:00
When using imake, add a bunch of variables to the PLIST_SUBST list, in order to simplify man-page handling across platforms: If your application installs man pages on NetBSD into man/cat1/foo.0 but in man/man1/foo.1x on Linux, simply use ${IMAKE_MAN_DIR}/foo.${IMAKE_MANNEWSUFFIX} Definitions for Darwin provided by grant, others from /usr/X11R6/lib/X11/config/* This allows us to put away with having multiple PLISTs just for the different man page locations. PKGREVISION bumps of `grep -l USE_IMAKE pkgsrc/*/*/Makefile` coming up after revision and adjusting.
2003-02-24 20:49:47 +01:00
# imake installs manpages in weird places
# these values from /usr/X11R6/lib/X11/config/linux.cf
IMAKE_MAN_SOURCE_PATH= man/man
IMAKE_MAN_SUFFIX= 1x
IMAKE_LIBMAN_SUFFIX= 3x
Add some new variables for manual pages when using imake. They are: o IMAKE_KERNMAN_DIR (man4 or cat4) o IMAKE_MISCMAN_DIR (man7 or cat7) o IMAKE_KERNMAN_SUFFIX o IMAKE_MISCMAN_SUFFIX Ok'ed by Hubert Feyrer in private email.
2004-01-31 17:52:16 +01:00
IMAKE_KERNMAN_SUFFIX= 4
When using imake, add a bunch of variables to the PLIST_SUBST list, in order to simplify man-page handling across platforms: If your application installs man pages on NetBSD into man/cat1/foo.0 but in man/man1/foo.1x on Linux, simply use ${IMAKE_MAN_DIR}/foo.${IMAKE_MANNEWSUFFIX} Definitions for Darwin provided by grant, others from /usr/X11R6/lib/X11/config/* This allows us to put away with having multiple PLISTs just for the different man page locations. PKGREVISION bumps of `grep -l USE_IMAKE pkgsrc/*/*/Makefile` coming up after revision and adjusting.
2003-02-24 20:49:47 +01:00
IMAKE_FILEMAN_SUFFIX= 5x
Add IMAKE_GAMEMAN_SUFFIX and IMAKE_GAMEMAN_DIR to allow PLISTs to pick up the correct locations. XXX Default values are guessed, x11/xsnow can be used for testing
2005-12-04 02:44:30 +01:00
IMAKE_GAMEMAN_SUFFIX= 6
Add some new variables for manual pages when using imake. They are: o IMAKE_KERNMAN_DIR (man4 or cat4) o IMAKE_MISCMAN_DIR (man7 or cat7) o IMAKE_KERNMAN_SUFFIX o IMAKE_MISCMAN_SUFFIX Ok'ed by Hubert Feyrer in private email.
2004-01-31 17:52:16 +01:00
IMAKE_MISCMAN_SUFFIX= 7
When using imake, add a bunch of variables to the PLIST_SUBST list, in order to simplify man-page handling across platforms: If your application installs man pages on NetBSD into man/cat1/foo.0 but in man/man1/foo.1x on Linux, simply use ${IMAKE_MAN_DIR}/foo.${IMAKE_MANNEWSUFFIX} Definitions for Darwin provided by grant, others from /usr/X11R6/lib/X11/config/* This allows us to put away with having multiple PLISTs just for the different man page locations. PKGREVISION bumps of `grep -l USE_IMAKE pkgsrc/*/*/Makefile` coming up after revision and adjusting.
2003-02-24 20:49:47 +01:00
IMAKE_MAN_DIR= ${IMAKE_MAN_SOURCE_PATH}1
IMAKE_LIBMAN_DIR= ${IMAKE_MAN_SOURCE_PATH}3
Add some new variables for manual pages when using imake. They are: o IMAKE_KERNMAN_DIR (man4 or cat4) o IMAKE_MISCMAN_DIR (man7 or cat7) o IMAKE_KERNMAN_SUFFIX o IMAKE_MISCMAN_SUFFIX Ok'ed by Hubert Feyrer in private email.
2004-01-31 17:52:16 +01:00
IMAKE_KERNMAN_DIR= ${IMAKE_MAN_SOURCE_PATH}4
When using imake, add a bunch of variables to the PLIST_SUBST list, in order to simplify man-page handling across platforms: If your application installs man pages on NetBSD into man/cat1/foo.0 but in man/man1/foo.1x on Linux, simply use ${IMAKE_MAN_DIR}/foo.${IMAKE_MANNEWSUFFIX} Definitions for Darwin provided by grant, others from /usr/X11R6/lib/X11/config/* This allows us to put away with having multiple PLISTs just for the different man page locations. PKGREVISION bumps of `grep -l USE_IMAKE pkgsrc/*/*/Makefile` coming up after revision and adjusting.
2003-02-24 20:49:47 +01:00
IMAKE_FILEMAN_DIR= ${IMAKE_MAN_SOURCE_PATH}5
Add IMAKE_GAMEMAN_SUFFIX and IMAKE_GAMEMAN_DIR to allow PLISTs to pick up the correct locations. XXX Default values are guessed, x11/xsnow can be used for testing
2005-12-04 02:44:30 +01:00
IMAKE_GAMEMAN_DIR= ${IMAKE_MAN_SOURCE_PATH}6
Add some new variables for manual pages when using imake. They are: o IMAKE_KERNMAN_DIR (man4 or cat4) o IMAKE_MISCMAN_DIR (man7 or cat7) o IMAKE_KERNMAN_SUFFIX o IMAKE_MISCMAN_SUFFIX Ok'ed by Hubert Feyrer in private email.
2004-01-31 17:52:16 +01:00
IMAKE_MISCMAN_DIR= ${IMAKE_MAN_SOURCE_PATH}7
When using imake, add a bunch of variables to the PLIST_SUBST list, in order to simplify man-page handling across platforms: If your application installs man pages on NetBSD into man/cat1/foo.0 but in man/man1/foo.1x on Linux, simply use ${IMAKE_MAN_DIR}/foo.${IMAKE_MANNEWSUFFIX} Definitions for Darwin provided by grant, others from /usr/X11R6/lib/X11/config/* This allows us to put away with having multiple PLISTs just for the different man page locations. PKGREVISION bumps of `grep -l USE_IMAKE pkgsrc/*/*/Makefile` coming up after revision and adjusting.
2003-02-24 20:49:47 +01:00
IMAKE_MANNEWSUFFIX= ${IMAKE_MAN_SUFFIX}
Initial commit of a new module that encapsulates all of the code for manipulating PLISTs. This module is not used by default pending more widespread testing -- currently the variable _USE_PLIST_MODULE must be defined in /etc/mk.conf to enable its use. The main features of the new PLIST module are: (1) Splits out the PLIST-handling code from bsd.pkg.mk into a separate "plist" module. (2) Splits out giant, multi-line awk scripts stored in make variables into separate awk scripts that may be joined together to post-process PLISTs. Each of these awk scripts consolidates the processing for one set of files, e.g., man pages, info pages, etc., and is more easily commented than a make variable. (3) Splits out the print-PLIST code from the regular PLIST code since they have no common pieces (print-plist.mk vs. plist.mk). (4) Completely re-implements the shared-library handling to be more efficient. Along the way, this also fixes a problem for Mac OS X users where the PLISTs incorrectly contained absolute paths. (5) Completely re-implements the info-file handling so that we can migrate from INFO_FILES definitions to just adding info/foo.info entries in the static PLISTs. (6) Adds commented-out support for automatically compressed or decompressed info page entries based on the value of MANZ. These changes will be activated after texinfo.mk has been replaced by something that is built using the more modern primitives now available in pkgsrc. (7) Move the file compression logic into a separate script "doc-compress" that compresses or decompresses files while minding symlinks. This script is now called by bsd.pkg.mk to do the "autmoatic man page handling". In the future, it will also handle the "automatic info page handling" and possible others. In general, the idea is to move stuff out of the Makefiles and into separate files where we don't need to worry about quoting rules and where each file can have a separate history of commits. This simplifies the makefile logic (especially in terms of readability) and also simplifies maintenance of the code.
2006-01-13 00:43:56 +01:00
IMAKE_MANINSTALL?= maninstall catinstall
* Add new emulator framework in pkgsrc/mk/emulator that handles all binary-only packages that require binary "emulation" on the native operating system. Please see pkgsrc/mk/emulator/README for more details. * Teach the plist framework to automatically use any existing PLIST.${EMUL_PLATFORM} as part of the default PLIST_SRC definition. * Convert all of the binary-only packages in pkgsrc to use the emulator framework. Most of them have been tested to install and deinstall correctly. This involves the following cleanup actions: * Remove use of custom PLIST code and use PLIST.${EMUL_PLATFORM} more consistently. * Simplify packages by using default INSTALL and DEINSTALL scripts instead of custom INSTALL/DEINSTALL code. * Remove "SUSE_COMPAT32" and "PKG_OPTIONS.suse" from pkgsrc. Packages only need to state exactly which emulations they support, and the framework handles any i386-on-x86_64 or sparc-on-sparc64 uses. * Remove "USE_NATIVE_LINUX" from pkgsrc. The framework will automatically detect when the package is installing on Linux. Specific changes to packages include: * Bump the PKGREVISIONs for all of the suse100* and suse91* packages due to changes in the +INSTALL/+DEINSTALL scripts used in all of the packages. * Remove pkgsrc/emulators/suse_linux, which is unused by any packages. * cad/lc -- remove custom code to create the distinfo file for all supported platforms; just use "emul-fetch" and "emul-distinfo" instead. * lang/Cg-compiler -- install the shared libraries under ${EMULDIR} instead of ${PREFIX}/lib so that compiled programs will find the shared libraries. * mail/thunderbird-bin-nightly -- update to latest binary distributions for supported platforms. * multimedia/ns-flash -- update Linux version to 9.0.48 as the older version is no longer available for interactive fetch. * security/uvscan -- set LD_LIBRARY_PATH explicitly so that it's not necessary to install library symlinks into ${EMULDIR}/usr/local/lib. * www/firefox-bin-flash -- update Linux version to 9.0.48 as the older version is no longer available for interactive fetch.
2007-07-29 07:18:36 +02:00
_OPSYS_EMULDIR.linux= # empty
_OPSYS_EMULDIR.linux32= # empty
Use mk/check/check-shlibs-elf.awk for the run-time search-path check on linux.
2010-05-16 08:59:26 +02:00
_OPSYS_SYSTEM_RPATH= /lib${LIBABISUFFIX}:/usr/lib${LIBABISUFFIX}
Alternative check if IPv6 is available with the OS. Addresses PR 20019.
2003-03-20 01:34:17 +01:00
.if exists(/usr/include/netinet6) || exists(/usr/include/linux/in6.h)
Introduce _OPSYS_HAS_INET6, and use it to determine the default value of USE_INET6.
2002-12-18 07:18:14 +01:00
_OPSYS_HAS_INET6= yes # IPv6 is standard
.else
_OPSYS_HAS_INET6= no # IPv6 is not standard
.endif
Add a layer of abstraction into bsd.pkg.mk for Java settings - set the path to the java home directory depending upon whether the operating system includes Java by default. Use the operating system-dependent definitions files to set this value.
2002-12-03 21:53:39 +01:00
_OPSYS_HAS_JAVA= no # Java is not standard
Add _OPSYS_HAS_MANZ and _PREFORMATTED_MAN_DIR definitions to the individual defs.${OPSYS}.mk files, and use them in bsd.pkg.mk. + _OPSYS_HAS_MANZ defines whether or not the OS does MANZ handling as standard + _PREFORMATTED_MAN_DIR is the name of directory (cat or man) where preformatted manual pages go. Rename the internal definitions used in the generation of PLIST files to start with '_'. This completes the "generic" changes to bsd.pkg.mk.
2001-11-21 14:44:44 +01:00
_OPSYS_HAS_MANZ= no # no MANZ for gzipping of man pages
Add an _OPSYS_HAS_OSSAUDIO definition to the individual defs.${OPSYS}.mk files, and use it in ossaudio.buildlink.mk. The definition shows whether or not libossaudio is available in the OS.
2001-11-21 14:57:31 +01:00
_OPSYS_HAS_OSSAUDIO= no # libossaudio is available
Eliminate another usage of ${OPSYS} in bsd.pkg.mk - realy on Darwin defining _OPSYS_PERL_REQD to the correct value to make sure there's a valid perl version for that platform.
2002-12-03 22:13:37 +01:00
_OPSYS_PERL_REQD= # no base version of perl required
-lpthread is a no-op on Darwin, but it messes up buildlink. So add a new flag _OPSYS_PTHREAD_AUTO ("yes" for Darwin, "no" for everyone else) and make pthread.buildlink2.mk do basically nothing in that case.
2003-09-14 18:30:34 +02:00
_OPSYS_PTHREAD_AUTO= no # -lpthread needed for pthreads
Set some _OPSYS_SHLIB_TYPE to precisely 'ELF' on platforms where a.out is not being used by pkgsrc at all. This saves some build time in show-shlib-type.
2004-11-15 15:48:18 +01:00
_OPSYS_SHLIB_TYPE= ELF # shared lib type
Use ${_PATCH_CAN_BACKUP} rather than hardcoding an OPSYS value into the logic for doing backups when applying patches, and set the value accordingly in the opsys-dependent defs file.
2002-12-03 20:24:26 +01:00
_PATCH_CAN_BACKUP= yes # native patch(1) can make backups
Allow _PATCH_BACKUP_ARG to be overridden in /etc/mk.conf (in order to use different patch programs). Ok by agc
2003-12-16 23:54:13 +01:00
_PATCH_BACKUP_ARG?= -b -V simple -z # switch to patch(1) for backup suffix
Add _OPSYS_HAS_MANZ and _PREFORMATTED_MAN_DIR definitions to the individual defs.${OPSYS}.mk files, and use them in bsd.pkg.mk. + _OPSYS_HAS_MANZ defines whether or not the OS does MANZ handling as standard + _PREFORMATTED_MAN_DIR is the name of directory (cat or man) where preformatted manual pages go. Rename the internal definitions used in the generation of PLIST files to start with '_'. This completes the "generic" changes to bsd.pkg.mk.
2001-11-21 14:44:44 +01:00
_USE_RPATH= yes # add rpath to LDFLAGS
Add _STRIPFLAG_CC and _STRIPFLAG_INSTALL to fix PR 15467. I'll replace all STRIPFLAG in pkgsrc with STRIPFLAG_CC or STRIPFLAG_INSTALL.
2002-02-27 05:41:22 +01:00
add OPSYS_{,NO_}WHOLE_ARCHIVE_FLAG which defines the argument passed to the linker to (not) extract all symbols from static archives and export these variables to packages as {,NO_}WHOLE_ARCHIVE_FLAG. these are not currently set for IRIX.
2003-04-15 07:29:45 +02:00
# flags passed to the linker to extract all symbols from static archives.
# this is GNU ld.
_OPSYS_WHOLE_ARCHIVE_FLAG= -Wl,--whole-archive
_OPSYS_NO_WHOLE_ARCHIVE_FLAG= -Wl,--no-whole-archive
Fix a gleaming illustration of why using YES/NO variables everywhere possible, just for the sake of doing so, is not a good thing to do: The platform files define _STRIPFLAG_* to determine whether to strip things. But since this is included in bsd.prefs.mk, ".if ..." checks cannot take things set in the Makefile into account. So convert INSTALL_UNSTRIPPED=YES to a defined/undefined variable check in bsd.pkg.mk, and use the :D:U idiom in the _STRIPFLAG_* variables. This should fix PR pkg/28772 and PR pkg/29031.
2005-03-18 19:16:34 +01:00
_STRIPFLAG_CC?= ${_INSTALL_UNSTRIPPED:D:U-s} # cc(1) option to strip
_STRIPFLAG_INSTALL?= ${_INSTALL_UNSTRIPPED:D:U-s} # install(1) option to strip
Use LOCALBASE instead of ZOULARISBASE
2003-09-05 15:54:13 +02:00
Use mk/check/check-shlibs-elf.awk for the run-time search-path check on linux.
2010-05-16 08:59:26 +02:00
_OPSYS_CAN_CHECK_SHLIBS= yes # use readelf in check/bsd.check-vars.mk
Get rid of an abstraction violation which has been in the tree since March 2008. Not vital, but the previous way does not scale well/at all.
2009-07-26 07:32:43 +02:00
Add the 'maximum command line check' to all defs.*.mk files for consistency across all of them, but let it commented out until each responsible person for each system modifies it to work correctly. Requested by agc@.
2004-04-19 22:19:46 +02:00
# check for maximum command line length and set it in configure's environment,
# to avoid a test required by the libtool script that takes forever.
# FIXME: Adjust to work on this system and enable the lines below.
Relax need to put GNU_CONFIGURE before inclusion of bsd.prefs.mk: Convert _OPSYS_MAX_CMDLEN to a plain _OPSYS_MAX_CMDLEN_CMD variable, which is not evaluated by a shell until CONFIGURE_ENV is expanded (and only then if USE_LIBTOOL+GNU_CONFIGURE are both set).
2005-01-25 19:15:58 +01:00
#_OPSYS_MAX_CMDLEN_CMD= /sbin/sysctl -n kern.argmax
Mention how SETGIDGAME and the other GAME vars are set per default. Add commented-out definitions for all OPSYS - please adjust.
2004-05-12 16:10:18 +02:00
set the LIBABISUFFIX to 64 for amd64...
2006-01-06 23:47:24 +01:00
.if (${MACHINE_ARCH} == "x86_64")
Also set ABI like SGI does; from Benjamin Shi.
2006-01-10 17:58:04 +01:00
ABI?= 64
set the LIBABISUFFIX to 64 for amd64...
2006-01-06 23:47:24 +01:00
LIBABISUFFIX?= 64
.endif
On Linux systems record the glibc version in the build information. OKed by wiz@
2010-05-20 09:57:22 +02:00
## Use _CMD so the command only gets run when needed!
.if exists(/lib/libc.so.6)
_GLIBC_VERSION_CMD= /lib/libc.so.6 --version | \
sed -ne's/^GNU C.*version \(.*\),.*$$/\1/p'
GLIBC_VERSION= ${_GLIBC_VERSION_CMD:sh}
.endif
Reference in a new issue Copy permalink