locale set by the user. Add LANG=C and LC_ALL=C at the beginning of
bsd.port.mk and export them so all commands are executed with the C locale.
LC_ALL=C overrides all other LC_* variables. LANG is used by setlocale(3)
as default value for LC_* variables, so normally it isn't used when LC_ALL
is set, but there's code out there that looks at LANG directly so it's safer
to set it as well. The only commands not captured by this are !=
assignments before any inclusion of bsd.port.*mk.
Introduce USE_LOCALE=<locale> that adds LANG=<locale> and LC_ALL=<locale> to
CONFIGURE_ENV and MAKE_ENV so upstream build systems can be executed with a
different locale (e.g. USE_LOCALE=en_US.UTF-8).
PR: 215882
Exp-run by: antoine
Approved by: portmgr (antoine)
- Add PYTHON_PYOEXTENSION and PYTHON_SUFFIX
- Add PYTHON2 and PYTHON3
- Respect PYTHON_VERSION
- Rename PYOEXTENSION to PYTHON_PYOEXTENSION
This change would help:
- Build databases/postgresql*-plpython with Python 3
(It has PLIST issue since bsd.python.mk to Uses/python.mk transition)
- Simplify Makefile
PR: 205807
Differential Revision: https://reviews.FreeBSD.org/D4758
Exp-run by: antoine
up (specifically for math/fftw3-long), although, I can't reproduce them.
Making all in FAQ
restore=: && backupdir=".am$$" && am__cwd=`pwd` && CDPATH="${ZSH_VERSION+.}:"
&& cd . && rm -rf $backupdir && mkdir $backupdir && if (/bin/sh /wrkdirs/usr/
ports/math/fftw3-long/work/fftw-3.3.5/missing makeinfo --version) >/dev/null 2>&1;
then for f in ./fftw3.info ./fftw3.info-[0-9] ./fftw3.info-[0-9][0-9]
./fftw3.i[0-9] ./fftw3.i[0-9][0-9]; do if test -f $f; then mv $f $backupdir;
restore=mv; else :; fi; done; else :; fi && cd "$am__cwd"; if /bin/sh
/wrkdirs/usr/ports/math/fftw3-long/work/fftw-3.3.5/missing makeinfo -I .
-o ./fftw3.info ./fftw3.texi; then rc=0; CDPATH="${ZSH_VERSION+.}:" && cd .;
else rc=$?; CDPATH="${ZSH_VERSION+.}:" && cd . && $restore $backupdir/*
`echo "././fftw3.info" | sed 's|[^/]*$||'`; fi; rm -rf $backupdir; exit $rc
/wrkdirs/usr/ports/math/fftw3-long/work/fftw-3.3.5/missing: makeinfo: not found
WARNING: 'makeinfo' is missing on your system.
You should only need it if you modified a '.texi' file, or
any other file indirectly affecting the aspect of the manual.
You might want to install the Texinfo package:
<http://www.gnu.org/software/texinfo/>
The spurious makeinfo call might also be the consequence of
using a buggy 'make' (AIX, DU, IRIX), in which case you might
want to install GNU make:
<http://www.gnu.org/software/make/>
*** Error code 127
If you want to set WRKSRC, set GH_PROJECT instead.
- The GitHub URLs are case insensitive, but the distribution files you
get out of them are not.
- If the repository was renamed, the old URL will still work, but the
distribution name will be ith the new name.
Sponsored by: Absolight
This is a library for mathematical computations. Our purpose is to express the
mathematical object naturally in Ruby. Though it is not operated fast, we can
see the algorithm of the mathematical processing not in black box but in
scripts. This library is in development stage.
WWW: https://github.com/kunishi/algebra-ruby2
and discrete or sampled data such as particles. Focused on driving
physically-meaningful inquiry, yt has been applied in domains such as
astrophysics, seismology, nuclear engineering, molecular dynamics, and
oceanography.
WWW: http://yt-project.org
PR: 214565
Submitted by: yuri@rawbw.com
Program received signal SIGBUS: Access to an undefined portion of a memory object.
Backtrace for this error:
#0 0x28B2C4D6
#1 0x28B2CB17
#2 0xFFFFE193
gmake[2]: *** [Makefile:10: level1] Bus error (core dumped)
Approved by: portmgr blanket
- updated comment to align with CRAN package
- updated license to align with CRAN package
- add new test dependencies:
- math/R-cran-MatrixModels
- math/R-cran-SparseM
- math/R-cran-lme4
- math/R-cran-nloptr
- math/R-cran-survey
- set NO_ARCH as port does not compile
Generated by: portcran (0.1.3)
Implementations of functions which have been introduced in R since
version 3.0.0. The backports are conditionally exported which results
in R resolving the function names to the version shipped with R (if
available) and uses the implemented backports as fallback. This way
package developers can make use of the new functions without worrying
about the minimum required R version.
WWW: https://cran.r-project.org/web/packages/backports/
Math::BigInt is not very good suited to work with small (read: typical less than
10 digits) numbers, since it has a quite high per-operation overhead and is thus
much slower than normal Perl for operations.
But for some applications, you want fast speed for small numbers without the
risk of overflowing. This is were Math::BigInt::Lite comes into play.
Math::BigInt::Lite objects should behave in every way like Math::BigInt objects,
that is apart from the different label, you should not be able to tell the
difference. Since Math::BigInt::Lite is designed with speed in mind, there are
certain limitations build-in. In praxis, however, you will not feel them,
because everytime something gets to big to pass as Lite (literally), it will
upgrade the objects and operation in question to Math::BigInt.
WWW: http://search.cpan.org/dist/Math-BigInt-Lite/
