mirror of
https://git.openafs.org/openafs.git
synced 2025-01-19 07:20:11 +00:00
cc7f942a81
The rand-fortuna.c we get from Heimdal's hcrypto currently sometimes causes a warning on LINUX when building in the kernel, because fortuna_reseed() has a (potentially) large stack size: .../src/libafs/MODLOAD-.../rand-fortuna-kernel.c:549:1: error: the frame size of 1032 bytes is larger than 1024 bytes [-Werror=frame-larger-than=] Currently this does not cause the build to fail, even with --enable-checking, since -Werror is not given in the CFLAGS when building our kernel module. But if -Werror is passed in CFLAGS (in a future commit), this would cause the build to fail. Since this is an external source file, we cannot change it directly. At least for now, just prevent this warning from breaking the build by passing -Wno-error=frame-larger-than= into the CFLAGS for that file. Change-Id: Ieefdf2dbc318fdcd559435e5f329eef5cf9bb9ba Reviewed-on: https://gerrit.openafs.org/13684 Tested-by: BuildBot <buildbot@rampaginggeek.com> Reviewed-by: Benjamin Kaduk <kaduk@mit.edu> |
||
---|---|---|
build-tools | ||
doc | ||
src | ||
tests | ||
.gitignore | ||
.gitreview | ||
.mailmap | ||
.splintrc | ||
acinclude.m4 | ||
CODING | ||
configure-libafs.ac | ||
configure.ac | ||
CONTRIBUTING | ||
INSTALL | ||
libafsdep | ||
LICENSE | ||
Makefile-libafs.in | ||
Makefile.in | ||
NEWS | ||
NTMakefile | ||
README | ||
README-WINDOWS | ||
regen.sh |
AFS is a distributed file system that enables users to share and access all of the files stored in a network of computers as easily as they access the files stored on their local machines. The file system is called distributed for this exact reason: files can reside on many different machines, but are available to users on every machine. OpenAFS 1.0 was originally released by IBM under the terms of the IBM Public License 1.0 (IPL10). For details on IPL10 see the LICENSE file in this directory. The current OpenAFS distribution is licensed under a combination of the IPL10 and many other licenses as granted by the relevant copyright holders. The LICENSE file in this directory contains more details, thought it is not a comprehensive statement. See INSTALL for information about building and installing OpenAFS on various platforms. See CODING for developer information and guidelines. See NEWS for recent changes to OpenAFS.