similar to: tinc under cygwin: lzo-librarys probs

Hello, I downloaded tinc 1.0.9 from the site and tried to build on Fedora 10 on i386 (and also x86_64). I get, during the configure phase: checking for zlib.h... yes checking for compress2 in -lz... yes checking for lzo1x_1_compress in -llzo2... no checking for lzo1x_1_compress in -llzo... no configure: error: "lzo libraries not found." but: # rpm -qi lzo Name : lzo

Hi Can someone please help me with the method of installing the lzo dependancy for tinc to compile. I am getting the following errors when compiling. ./configure .... .... checking for lzo1x_1_compress in -llzo2... no checking for lzo1x_1_compress in -llzo... no configure: error: "lzo libraries not found." Regards Yazeed Fataar <yazeedfataar at hotmail.com> --------------

El 29 de enero de 2016 21:49:04 CET, Yazeed Fataar <yazeedfataar at gmail.com> escribi?: >Hi > >Can someone please help me with the method of installing the lzo >dependancy >for tinc to compile. > >I am getting the following errors when compiling. > >./configure >.... >.... > >checking for lzo1x_1_compress in -llzo2... no > >checking for

Hello, I'm sorry to post this seemingly quite mundane issue, but I just do not find what's wrong with what i did... please help. Basically typing the make command returns a message in french (that one is normal) that says that no goals and no rules were specified. I realize it's a typical make error message but I don't see/am not familiar enough with the output of ./configure to

Hello, I would like to install the latest tinc software on a fedora 8 Linux box. I tried the rpm for FC3 from http://dag.wieers.com/rpm/packages/tinc/, and I got dependency errors complaining that libcrypto.so.4 is needed. I've got openssl rpm package installed which uses a different versino of libcrypto, and creating symbolic links won't solve the issue. Then I found this article

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, I've added lzo compression support for tinc 1.0pre8. Lzo is a very fast compressor (see http://www.oberhumer.com/opensource/lzo/). I've implemented it by using two new compression levels. Compression level 10 is for fast compression using lzo1x-1 algorithm. Compression level 11 is for slow compression using lzo1x-999 algorithm.

Hi, I planned to boost my btrfs performance today. here some errors I met: my ''btrfs filesystem show'' result: ~ # btrfs filesystem show failed to read /dev/sr0 Label: none uuid: 9b9aa9d9-760e-445c-a0ab-68e102d9f02e Total devices 1 FS bytes used 36.59GB devid 1 size 49.52GB used 49.52GB path /dev/sda6 Label: none uuid: 559dec06-4fd0-47c1-97b8-cc4fa6153fa0

Hi all, as suggested on the mailing list I have converted the updated LZO code into git, so please pull my "lzo-update" branch from git://github.com/markus-oberhumer/linux.git lzo-update You can browse the branch at https://github.com/markus-oberhumer/linux/compare/lzo-update I''d ask some official kernel maintainer for review and to push this into linux-next so that it

I just setup a new SSD with my laptop root filesystem, and at the time I though, "eh, I''ll just use zlib compression during the first copy, and then switch to lzo afterwards to maintain write speed when I''m using the laptop after the copy and reboot". Now, I rebooted with the new ssd and zlib compressed rootfs, and it seemed to boot slower than it did before with the

- Add incompat flag, otherwise btrfs-progs will report error when operating on btrfs filesystems mounted with lzo option. - Allow to turn on lzo compression for defrag operation: # btrfs filesystem defragment -c[zlib, lzo] <file> Note: "-c zlib" will fail, because that''s how getopt() works for optional arguments. Signed-off-by: Li Zefan

The prescription for Boot Info Table says that checksumming begins at byte 64 of isolinux.bin. When prepcore writes isolinux.bin it begins copying bytes from the input file at the offset given by variable "start". But it begins checksumming at offset 64 of the input file. The problem exists since introduction of prepcore by release 4.00. ISO 9660 programs usually fix it when they write

The size of de/compress buffer and LZO1X_MEM_COMPRESS is small enough. Allocating it with kmalloc rather than vmalloc is preferred. This patch depends on my previous patch, “btrfs: fix decompress buffer size”. Signed-off-by: Kyungsik Lee <kyungsik.lee@lge.com> Cc: David Sterba <dsterba@suse.cz> --- fs/btrfs/lzo.c | 14 +++++++------- 1 file changed, 7 insertions(+), 7 deletions(-)

Hi Some developers here said a long time ago that someone should show the code for LZO compression support for ZFS before talking about the next step. I made that code with a friend and we also made a little benchmark to give a first impression: http://denisy.dyndns.org/lzo_vs_lzjb/ I hope we made no technical error, but if you find something not accurate, we will correct it. Denis -- This

Hi, I don''t know if this has been discussed before, but have you thought about adding LZO compression to ZFS? One zfs-fuse user has provided a patch which implements LZO compression, and he claims better compression ratios *and* better speed than lzjb. The miniLZO library is licensed under the GPL, but the author specifically says that other licenses are available by request. Has this

CentOS Errata and Security Advisory 2014:0861 Moderate Upstream details at : https://rhn.redhat.com/errata/RHSA-2014-0861.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: 5573a762c075a0d03f070c6bd0b47c41311fff66e21e034863d514ee65d8c081 lzo-2.03-3.1.el6_5.1.i686.rpm

CentOS Errata and Security Advisory 2014:0861 Moderate Upstream details at : https://access.redhat.com/errata/RHSA-2014:0861 The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) x86_64: 898c40521dfa677aa2217a083a9f382618b359d7a1a0361167427123f3397632 lzo-2.06-6.el7_0.2.i686.rpm

[adding libguestfs list, for nbdkit reference below] On 10/4/18 8:39 AM, Stefan Fröberg wrote: > Hello. > Is it possible to improve NBD throughtput with LZO compression ? As in, have a way for the client and server to negotiate that both understand an LZO extension, at which point the client can request a read or write with a flag set to mark that the data is LZO-compressed, for less

I got the file that was sent to me the other day. Unfortunitly it did not solve my problems. After a lot of hacking I have been able to get release 1.0 to almost compile. I have finally gotten all of the dependancies worked out under OpenBSD 3.2. This next error has me stumped. I can tell that it is looking for a file but have no idea how to create the file. This is the output of the the

Originated/took from Steffen Winterfeldt and Michael Matz in opensuse's Syslinux package: https://bugzilla.opensuse.org/show_bug.cgi?id=1125616 "fix lzo memory aliasing issue" --- lzo/Makefile +++ lzo/Makefile @@ -19,6 +19,8 @@ LIB = lzo.a BINS = prepcore +OPTFLAGS += -fno-strict-aliasing + all : makeoutputdirs $(BINS) makeoutputdirs: -- -Ady

I have compiled tinc under windows (MinGW), with the following configuration: ./configure --with-openssl=/opt/openssl-0.9.7b/ --with-zlib=/opt/zlib-1.1.4/ --with-lzo=/opt/lzo-1.08 --prefix=/opt/tinc-1.0.1 It works but configuration files are hardcoded! I've tryed also the --sysconfdir=/aaa parameter. c:\>tincd -n pluto -K Cannot open config file