similar to: Build On CentOS

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Gus: Is it even worth my time to use any of the 1.1.X versions and only use the 1.0.24 Stable version for a VPN deployment today? Or is the 1.10pre 95% stable and only lacking UDP forwarding? Please do not be optimistic, I My use case is one where I have several servers connected by TCP/UDP and all servers are master, there is no hub and no

On Fri, Dec 05, 2014 at 10:24:27AM -0500, md at rpzdesign.com wrote: > Tried to Build Tinc. Linker was confused, Makefile lacking reference to > -ltinfo I guess. [...] > /usr/bin/../libexec/gcc/x86_64-redhat-linux/4.8.2/ld: top.o: undefined > reference to symbol 'wtimeout' > /usr/bin/../libexec/gcc/x86_64-redhat-linux/4.8.2/ld: note: 'wtimeout' > is defined in

On Sun, Dec 07, 2014 at 04:33:49PM +0100, Guus Sliepen wrote: > Hm, on Debian it works fine, OTOH the command "libncurses5-config > --libs" does tell me to link with -ltinfo. I'll see if I can add that > to the autoconf script. On CentOS 7 tinc 1.1 compiles without problems. Also, both on Debian and CentOS "pkg-config --libs ncurses" only prints

I downloaded the Openssh-2.3.0p1 file and ran configure only to have it fail reporting the lack of libz. I found that configure was failing beacuse the test program did not include the libtinfo and libm which are needed to resolve references in libprot. I made changes to the configure script to add those libraries for SCO Openserver and then tried to compile the programs only to run into another

What is the state of speex support in asterisk? I saw the codec seems to be there. Can speex be used on IAX2 links? Is there much work still to be done? many thanks, --J.

Hardcoding -ltinfo breaks on distros that do not build the sep library (which is the default ncurses behavior). Use pkg-config to look up the right libraries regardless of how the distro built things. --- builder/Makefile.am | 5 +++-- configure.ac | 18 ++++++------------ customize/Makefile.am | 2 +- mllib/Makefile.am | 6 +++--- resize/Makefile.am | 2 +-

Guus: I have been test running the VPN between 2 geographically different clusters on a TINC VPN for a couple of days. How confident are you in the New Protocol in 1.1Pre10? Or should I just play it safe and run the old protocol for production? How long do you think it will take for you to have confidence in the new protocol? When do you think you will gain that confidence? You should be

hi. I suggest you to look at "Automatic Dependencies" in https://www.freedesktop.org/software/systemd/man/systemd.service.html. I think using "After=" and "Recuires=" is more suitable. On Mon, Feb 29, 2016 at 4:48 PM, md at rpzdesign.com <md at rpzdesign.com> wrote: > Hello Tinc'ers: > > I want to use TIncVPN in a systemd Ubuntu environment.

As if our lives were not already complex enough, there is the recent Wall Street Journal article about ipv4 exhaustion: http://www.wsj.com/articles/coming-this-summer-u-s-will-run-out-of-internet-addresses-1431479401 Is the latest version TINC ready for IpV6? Help us Obi-Wan-Sleipen, you are our only hope! md -- No spell checkers were harmed during the creation of this message.

Currently, every single piece of code in amdgpu that loops through connectors does it incorrectly and doesn't use the proper list iteration helpers, drm_connector_list_iter_begin() and drm_connector_list_iter_end(). Yeesh. So, do that. Cc: Juston Li <juston.li at intel.com> Cc: Imre Deak <imre.deak at intel.com> Cc: Ville Syrjälä <ville.syrjala at linux.intel.com> Cc: Harry

[Resending as my previous message was sent to moderation. The list info page doesn't mention this is a subscriber only list] I'm trying to write a .so which will be loaded using dlopen and called using dlopen. The application is written in C and I want to use the LLVM C API jfrom it. Obviously it will end up calling C++ functions internally but as long as I expose a C API to the

On a particular system I am trying to link my application to the LLVM library and it can't find -ltinfo and -lz. The former is part of ncurses (build with term- info). Building ncurses for this system in user space turns out to be not straight-forward (haven't succeeded so far). In LLVM, is there a way to turn the need for -ltinfo and -lz off? Frank

On Tue, Sep 3, 2019 at 4:49 PM Lyude Paul <lyude at redhat.com> wrote: > > Currently, every single piece of code in amdgpu that loops through > connectors does it incorrectly and doesn't use the proper list iteration > helpers, drm_connector_list_iter_begin() and > drm_connector_list_iter_end(). Yeesh. > > So, do that. In fairness, I think the origin of this code

On Fri, Dec 12, 2014 at 02:21:08AM -0500, md at rpzdesign.com wrote: > Oops, I got it to work only after putting the WAN on port 656 so it > did not interfere with port 655 for the LAN. You should not need to have two tinc daemons just because you have a WAN and a LAN interface. By default (ie, if you don't specify BindToAddress and/or BindToInterface), tinc listens on all interfaces,

Hello Tinc users & Guss: I was sleeping last night and I figured out how to accomplish everything I ranted about below with no source code changes to TINC. The first thing to do is create TEMPLATES for tinc.conf, tinc-up, and the NODE files. Then during the startup script, use the linux cp command and sed to copy the template to the correct name and sed to text replace

Am 28.10.19 um 21:10 schrieb Jason Gunthorpe: > From: Jason Gunthorpe <jgg at mellanox.com> > > Remove the interval tree in the driver and rely on the tree maintained by > the mmu_notifier for delivering mmu_notifier invalidation callbacks. > > For some reason amdgpu has a very complicated arrangement where it tries > to prevent duplicate entries in the interval_tree,

From: Jason Gunthorpe <jgg at mellanox.com> Remove the interval tree in the driver and rely on the tree maintained by the mmu_notifier for delivering mmu_notifier invalidation callbacks. For some reason amdgpu has a very complicated arrangement where it tries to prevent duplicate entries in the interval_tree, this is not necessary, each amdgpu_bo can be its own stand alone entry.

From: Mikel Rychliski <mikel at mikelr.com> [ Upstream commit 72e0ef0e5f067fd991f702f0b2635d911d0cf208 ] On some EFI systems, the video BIOS is provided by the EFI firmware. The boot stub code stores the physical address of the ROM image in pdev->rom. Currently we attempt to access this pointer using phys_to_virt(), which doesn't work with CONFIG_HIGHMEM. On these systems,

From: Mikel Rychliski <mikel at mikelr.com> [ Upstream commit 72e0ef0e5f067fd991f702f0b2635d911d0cf208 ] On some EFI systems, the video BIOS is provided by the EFI firmware. The boot stub code stores the physical address of the ROM image in pdev->rom. Currently we attempt to access this pointer using phys_to_virt(), which doesn't work with CONFIG_HIGHMEM. On these systems,

From: Mikel Rychliski <mikel at mikelr.com> [ Upstream commit 72e0ef0e5f067fd991f702f0b2635d911d0cf208 ] On some EFI systems, the video BIOS is provided by the EFI firmware. The boot stub code stores the physical address of the ROM image in pdev->rom. Currently we attempt to access this pointer using phys_to_virt(), which doesn't work with CONFIG_HIGHMEM. On these systems,