82eec0d023
Waf has a utility function ('lib64' in waflib/Utils.py) which
either returns an empty string or '64' depending on if either of
the paths '/usr/lib64' or '/usr/local/lib64' exist. Then, the
build system itself decides its default LIBDIR to be either
/usr/lib or /usr/lib64 depending on the result of that function,
except when libdir is passed explicitly.
We don't allow lib64 in our packages. We do have the /usr/lib64
path as that is a symlink. Therefore, do not ever allow waf to
configure the path that way.
|
||
|---|---|---|
| .. | ||
| cargo.sh | ||
| cmake.sh | ||
| configure.sh | ||
| fetch.sh | ||
| gem.sh | ||
| gemspec.sh | ||
| gnu-configure.sh | ||
| gnu-makefile.sh | ||
| go.sh | ||
| haskell-stack.sh | ||
| meson.sh | ||
| meta.sh | ||
| perl-module.sh | ||
| perl-ModuleBuild.sh | ||
| perl6-dist.sh | ||
| python-module.sh | ||
| python2-module.sh | ||
| python3-module.sh | ||
| qmake.sh | ||
| R-cran.sh | ||
| README | ||
| ruby-module.sh | ||
| scons.sh | ||
| slashpackage.sh | ||
| waf.sh | ||
| waf3.sh | ||
BUILD STYLES ============ These shell snippets provide support for multiple build systems, i.e GNU configure, CMake, etc. A build style file must provide at least the following functions: - do_configure - do_build - do_install If a source package defines its own do_xxx() function, the function defined in the build style file is simply ignored.