LZ4 is lossless compression algorithm, providing compression speed > 500 MB/s
per core, scalable with multi-cores CPU. It features an extremely fast decoder,
with speed in multiple GB/s per core, typically reaching RAM speed limits on
multi-core systems.
Speed can be tuned dynamically, selecting an "acceleration" factor which trades
compression ratio for faster speed. On the other end, a high compression
derivative, LZ4_HC, is also provided, trading CPU time for improved compression
ratio. All versions feature the same decompression speed.
LZ4 is also compatible with dictionary compression, both at API and CLI levels.
It can ingest any input file as dictionary, though only the final 64KB are used.
This capability can be combined with the Zstandard Dictionary Builder, in order
to drastically improve compression performance on small files.
===> The following configuration options are available for liblz4-1.10.0_2,1:
TEST=off: Run extensive tests
===> Use 'make config' to modify these settings
archivers/liblz4: fix multithreading and tests
- Add -pthread to CFLAGS/LDFLAGS and the needed #define
Reported by: diizzy@
- Fix a bogus shell variable expansion using $$l when it should use $l
- Fix hard-coded "make" with GNU Makefiles BINARY_ALIAS it to ${GMAKE}
- For now, prevent Python 3.14 for tests, until we fully resolve
the circular dependency. Let's investigate if we can unlink lz4
from the zstd build (with its maintainer).
PR: 251183
PR: 290732
Approved by: portmgr@ (just-fix-it blanket)
archivers/liblz4: revert switch to meson
This partially reverts commit 7d6061f15551dcde40cf70fd743d631095360a23
made in the year 2020.
Reason: lang/python314 newly depends on archivers/zstd,
which depends on archivers/liblz4, so neither of the latter two
can use any Python to build lest we create a circular dependency
when Python 3.14 is made the default.
Note: make-based builds remain the documented way
to build/test lz4 1.10.0 in their primary documentation.
Note also that the meson build installed one file less than the
make-based build, which gets re-added, hence bumping PORTREVISION.
PR: 251183
PR: 290732
Approved by: portmgr@ (just-fix-it blanket)
all: remove explicit versions in USES=python for "3.x+"
The logic in USES=python will automatically convert this to 3.8+ by
itself.
Adjust two ports that only had Python 3.7 mentioned but build fine
on Python 3.8 too.
finance/quickfix: mark BROKEN with PYTHON
libtool: compile: c++ -DHAVE_CONFIG_H -I. -I../.. -I -I. -I.. -I../.. -I../C++
-DLIBICONV_PLUG -DPYTHON_MAJOR_VERSION=3 -Wno-unused-variable
-Wno-maybe-uninitialized -O2 -pipe -DLIBICONV_PLUG -fstack-protector-strong
-fno-strict-aliasing -DLIBICONV_PLUG -Wall -ansi
-Wno-unused-command-line-argument -Wpointer-arith -Wwrite-strings
-Wno-overloaded-virtual -Wno-deprecated-declarations -Wno-deprecated -std=c++0x
-MT _quickfix_la-QuickfixPython.lo -MD -MP -MF
.deps/_quickfix_la-QuickfixPython.Tpo -c QuickfixPython.cpp -fPIC -DPIC -o
.libs/_quickfix_la-QuickfixPython.o
warning: unknown warning option '-Wno-maybe-uninitialized'; did you mean
'-Wno-uninitialized'? [-Wunknown-warning-option]
QuickfixPython.cpp:175:11: fatal error: 'Python.h' file not found
^~~~~~~~~~
1 warning and 1 error generated.
Reviewed by: portmgr, vishwin, yuri
Differential Revision: <https://reviews.freebsd.org/D40568>
Remove WWW entries moved into port Makefiles
Commit b7f05445c00f has added WWW entries to port Makefiles based on
WWW: lines in pkg-descr files.
This commit removes the WWW: lines of moved-over URLs from these
pkg-descr files.
Approved by: portmgr (tcberner)
Add WWW entries to port Makefiles
It has been common practice to have one or more URLs at the end of the
ports' pkg-descr files, one per line and prefixed with "WWW:". These
URLs should point at a project website or other relevant resources.
Access to these URLs required processing of the pkg-descr files, and
they have often become stale over time. If more than one such URL was
present in a pkg-descr file, only the first one was tarnsfered into
the port INDEX, but for many ports only the last line did contain the
port specific URL to further information.
There have been several proposals to make a project URL available as
a macro in the ports' Makefiles, over time.
(Only the first 15 lines of the commit message are shown above )
archivers: remove 'Created by' lines
A big Thank You to the original contributors of these ports:
* Aaron Dalton <aaron@FreeBSD.org>
* Akinori MUSHA aka knu <knu@idaemons.org>
* Albert Vernon <f3cun3c02@sneakemail.com>
* Alex Dupre <ale@FreeBSD.org>
* Alex Samorukov <samm@freebsd.org>
* Alexander Kuehn <freebsd@nagilum.org>
* Alexander Logvinov <ports@logvinov.com>
* Alexander Zhuravlev <zaa@zaa.pp.ru>
* Alexey Dokuchaev <danfe@FreeBSD.org>
* Alexey Dokuchaev <danfe@regency.nsu.ru>
* Anders Nordby <anders@FreeBSD.org>
(Only the first 15 lines of the commit message are shown above )
Update to 1.8.2
Remove the now unneeded post-patch section
Enforce usage of our INSTALL_PROGRAM instead of manually strip
Pass variables via MAKE_ARGS to avoid patching
Remove now useless USES=pathfix
PR: 228060
Submitted by: bapt
Reported by: Yann Collet (Upstream)
Reviewed by: Martin Waschbusch (maintainer)
Approved by: Martin Waschbusch (maintainer)
Update to 1.7.5
Notable changes:
- Upstream switched versioning from e.g. r131 to v1.7.5, forcing me to
make use of PORTEPOCH.
- (Submitter) pushed a change upstream to add FreeBSD to the OSs
recognized in Makefile, requiring one less search & replace action
in post-patch section.
PR: 216599
Submitted by: martin@waschbuesch.de (maintainer)
Use USES=pathfix where applicable.
PR: 213195
Submitted by: mat
Exp-run by: antoine
Sponsored by: Absolight
Differential Revision: https://reviews.freebsd.org/D8093
USE_GITHUB: For the new support, fix DISTNAME to be more consistent.
When using GH_TAGNAME the DISTNAME would have GH_PROJECT and GH_ACCOUNT in
it. When not using GH_TAGNAME it would not have this. Now both cases
will add in the GH_PROJECT and GH_ACCOUNT.
Add special care to ensure that the DISTVERSION is not added in twice. If
a port does GH_TAGNAME=v${PORTVERSION} it will be added in twice though. For
that case DISTVERSIONPREFIX=v should be set and no GH_TAGNAME should be used.
empty() is used rather than (!defined || !${}) to support fmake.
The purpose of setting DISTNAME at all in these cases is to make it more clear
that the distfile is from *GITHUB* and to avoid collisions if a project were
to be renamed or moved. Without adding in GH_PROJECT and GH_ACCOUNT then there
are real risks that collisions on filenames would happen on renamed or moved
projects, which is fairly common. A GITHUB-generated file may not match
a custom-rolled or git-archive-rolled distfile.
PR: 199069
With hat: portmgr
Testing done: All USE_GITHUB ports without GH_COMMIT were
checksum/fetch/extract/WRKSRC tested.
Re-add back ALL_TARGET=default. For reasons that I still don't understand,
it breaks the build for some people.
This time, add a comment so I don't try to remove it again in the future.
I was never able to replicate this, but a number of people have reported that
liblz4 fails to build on amd64, and they all agree that this patch fixes it.
PR: 194609
Submitted by: Roland Smith
Add archivers/liblz4. There is already archivers/lz4, which it looks
like might be an old version of this, but it only installs a binary.
This installs binaries and libraries/headers.
LZ4 is a very fast lossless compression algorithm, providing compression speed
at 400 MB/s per core, scalable with multi-cores CPU. It also features an
extremely fast decoder, with speed in multiple GB/s per core, typically
reaching RAM speed limits on multi-core systems.
A high compression derivative, called LZ4_HC, is also provided. It trades CPU
time for compression ratio.
The libraries are BSD licensed, and the binaries are GPLv2.
WWW: https://code.google.com/p/lz4/
