Age | Commit message (Collapse) | Author | Files | Lines |
|
|
|
well over a year now. Sorry. :-(
|
|
many packages used to use ${PAX}. Use the common way of directly calling
pax, it is created as tool after all.
|
|
their files via a custom do-install target.
|
|
shortly.
|
|
|
|
|
|
It is more consistent with the tex.buildlink3.mk name. Also, if a package
really needs latex, it just has to set TEX_ACCEPTED to latex distributions
altough today, all TEX_ACCEPTED possibilities are latex distributions
|
|
Accepts teTeX1, teTeX2 and teTeX3
|
|
around at either build-time or at run-time is:
USE_TOOLS+= perl # build-time
USE_TOOLS+= perl:run # run-time
Also remove some places where perl5/buildlink3.mk was being included
by a package Makefile, but all that the package wanted was the Perl
executable.
|
|
|
|
and is recognized by the tools framework automatically.
|
|
|
|
Buildlink files: RECOMMENDED version changed to current version.
|
|
- teTeX 1.0.x packages have been moved to teTeX1* directories.
- teTeX 2.0.x packages have been moved to teTeX* directories and their base
name has been changed to teTeX (instead of teTeX2).
|
|
|
|
2003-04-08, but the maintainers did not version the distfile. So make up
our own versioning, bump this to 4.0.1 and stick the distfile into a
DIST_SUBDIR (as suggested by agc@).
|
|
|
|
|
|
|
|
The SKaMPI-Benchmark is a suite of tests designed to measure the performance
of MPI. MPI (Message Passing Interface) is a machine independent standard to
provide an efficient interface to message passing libraries of different
parallel machines. The goal of SKaMPI is to create a database to illustrate
the performance of these different MPI implementations. This database should
allow to:
1. Decide how to implement portable and efficient MPI programs.
2. Predict the performance of MPI programs.
3. Describe supercomputers in terms of MPI.
|