NetCube-Systems-Austria/kumquat-buildroot
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
44de1a293e
kumquat-buildroot/package/nfs-utils/Config.in

41 lines
1007 B
Plaintext
Raw Normal View History

Config.in files: use if/endif instead of 'depends on' for main symbol In the Config.in file of package foo, it often happens that there are other symbols besides BR2_PACKAGE_FOO. Typically, these symbols only make sense when foo itself is enabled. There are two ways to express this: with depends on BR2_PACKAGE_FOO in each extra symbol, or with if BR2_PACKAGE_FOO ... endif around the entire set of extra symbols. The if/endif approach avoids the repetition of 'depends on' statements on multiple symbols, so this is clearly preferred. But even when there is only one extra symbol, if/endif is a more logical choice: - it is future-proof for when extra symbols are added - it allows to have just one strategy instead of two (less confusion) This patch modifies the Config.in files accordingly. Signed-off-by: Thomas De Schampheleire <thomas.de.schampheleire@gmail.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2013-12-20 22:31:30 +01:00
comment "nfs-utils needs a toolchain w/ largefile, threads"
depends on BR2_USE_MMU
depends on !BR2_LARGEFILE || \
!(BR2_TOOLCHAIN_HAS_THREADS || BR2_TOOLCHAIN_HAS_NATIVE_RPC)
Add new NFS utilities package with working init script.
2007-01-14 02:46:04 +01:00
config BR2_PACKAGE_NFS_UTILS
bool "nfs-utils"
libtirpc: requires toolchain with threading support Fixes: http://autobuild.buildroot.org/results/8ba720f47f74df94b8c70ac4befd47c47ce65f2f Signed-off-by: Gilles Talis <gilles.talis@gmail.com> Signed-off-by: "Samuel Martin" <s.martin49@gmail.com> Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
2013-09-13 12:41:20 +02:00
depends on BR2_TOOLCHAIN_HAS_NATIVE_RPC || BR2_TOOLCHAIN_HAS_THREADS # libtirpc
nfs-utils: add support to use RPC support from libtirpc Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com> Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
2012-11-04 08:34:13 +01:00
select BR2_PACKAGE_LIBTIRPC if !BR2_TOOLCHAIN_HAS_NATIVE_RPC
nfs-utils: needs largefile support Even though ./configure has a --disable-largefile, functions like statfs64 is used in several places, breaking the build on toolchains without largefile support. Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
2011-02-20 23:31:38 +01:00
depends on BR2_LARGEFILE
nfs-utils: needs mmu Fix below build error: mountd-mountd.o: In function `main': mountd.c:(.text+0x1264): undefined reference to `fork' mountd.c:(.text+0x1320): undefined reference to `fork' mountd-rmtab.o: In function `ha_callout': rmtab.c:(.text+0xa8): undefined reference to `fork' collect2: ld returned 1 exit status make[3]: *** [mountd] Error 1 Signed-off-by: Axel Lin <axel.lin@ingics.com> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2013-10-02 07:49:36 +02:00
depends on BR2_USE_MMU # fork()
Add new NFS utilities package with working init script.
2007-01-14 02:46:04 +01:00
help
The NFS Linux kernel server.
- make it compile if LFS is turned off and add a warning to the help-text. LFS is _not_ turned on by this automagically _on_ _purpose_
2007-01-22 16:56:42 +01:00
Warning: We do not force largefile support on here on purpose.
Enable it yourself if you want to access big exports!
Add new NFS utilities package with working init script.
2007-01-14 02:46:04 +01:00
http://sourceforge.net/projects/nfs
Config.in files: use if/endif instead of 'depends on' for main symbol In the Config.in file of package foo, it often happens that there are other symbols besides BR2_PACKAGE_FOO. Typically, these symbols only make sense when foo itself is enabled. There are two ways to express this: with depends on BR2_PACKAGE_FOO in each extra symbol, or with if BR2_PACKAGE_FOO ... endif around the entire set of extra symbols. The if/endif approach avoids the repetition of 'depends on' statements on multiple symbols, so this is clearly preferred. But even when there is only one extra symbol, if/endif is a more logical choice: - it is future-proof for when extra symbols are added - it allows to have just one strategy instead of two (less confusion) This patch modifies the Config.in files accordingly. Signed-off-by: Thomas De Schampheleire <thomas.de.schampheleire@gmail.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2013-12-20 22:31:30 +01:00
if BR2_PACKAGE_NFS_UTILS
Hint at 'enable RPC' requirement for nfs-utils and portmap
2007-10-30 22:15:46 +01:00
Add new NFS utilities package with working init script.
2007-01-14 02:46:04 +01:00
menu "NFS utilities selection"
config BR2_PACKAGE_NFS_UTILS_RPCDEBUG
bool "rpcdebug"
help
The RPC debugging utility
config BR2_PACKAGE_NFS_UTILS_RPC_LOCKD
bool "rpc.lockd"
help
NFS lock manager for Linux kernels older than 2.4
config BR2_PACKAGE_NFS_UTILS_RPC_RQUOTAD
bool "rpc.rquotad"
help
NFS remote quota server
endmenu
Config.in files: use if/endif instead of 'depends on' for main symbol In the Config.in file of package foo, it often happens that there are other symbols besides BR2_PACKAGE_FOO. Typically, these symbols only make sense when foo itself is enabled. There are two ways to express this: with depends on BR2_PACKAGE_FOO in each extra symbol, or with if BR2_PACKAGE_FOO ... endif around the entire set of extra symbols. The if/endif approach avoids the repetition of 'depends on' statements on multiple symbols, so this is clearly preferred. But even when there is only one extra symbol, if/endif is a more logical choice: - it is future-proof for when extra symbols are added - it allows to have just one strategy instead of two (less confusion) This patch modifies the Config.in files accordingly. Signed-off-by: Thomas De Schampheleire <thomas.de.schampheleire@gmail.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2013-12-20 22:31:30 +01:00
endif
Reference in New Issue Copy Permalink