search for: lib_dirs

Hi, I am trying to install pdftools package on R 3.3.1 (Ubuntu 16.04), but the following issue occurs: ------------------------- ANTICONF ERROR --------------------------- Configuration failed because poppler-cpp was not found. Try installing: * deb: libpoppler-cpp-dev (Debian, Ubuntu, etc) * rpm: poppler-cpp-devel (Fedora, CentOS, RHEL) * csw: poppler_dev (Solaris) * brew: poppler (Mac OSX)

Hello all, I got this problem while trying to shape traffic with iptables MARK and HTB. MARK: targinfosize 8 != 4 --set-mark gives "invalid argument" error message. Kernel version is 2.4.29 (some patches from patch o matic applied) Iptables version 1.3.4 Intel x86 architecture. I saw this problem discussed in a few places, but the discussions didn''t come to a conclusion

i am trying to install xml2 from CRAN, and it is throwing an error that it cannot find the libxml2 library configuration. The thing is that pkg-config seems to be set up correctly: $ echo $PKG_CONFIG_PATH :/usr/local/opt/libxml2/lib/pkgconfig:/usr/local/opt/libxml2/lib/pkgconfig $ pkg-config --cflags --libs libxml-2.0 -I/usr/local/Cellar/libxml2/2.9.7/include/libxml2

Hi Francois, Thanks for your quick response. Actually, I had already done that... sudo apt-get install libpoppler-cpp-dev Reading package lists... Done Building dependency tree Reading state information... Done libpoppler-cpp-dev is already the newest version (0.41.0-0ubuntu1.1). 0 upgraded, 0 newly installed, 0 to remove and 107 not upgraded. Therefore, I assume I have this installed. Best

Hello, libpoppler-cpp-dev is not an R package but a system library to be installed with (for example) : sudo apt-get install libpoppler-cpp-dev hope this help. Fran?ois Guilhaumon ?? Fran?ois Guilhaumon, research scientist (IRD <http://en.ird.fr>), associate editor (Journal of Biogeography <http://onlinelibrary.wiley.com/journal/10.1111/%28ISSN%291365-2699>). homepage :

...9;, path.join(source_dir, x)]).merge() ++ ['-o', outputs[0]] ++ path.join_all(source_dir, sources)) ] }, # clang, when used as a linker 'linker' = linker { # Inherit from generic linker prototype # Inputs param flags : list[string] param lib_dirs : list[string] param libs : list[string] param sources : list[string] param outputs : list[string] param warnings_as_errors : bool param all_warnings : bool # Outputs build => [ message.status("Linking program ${outputs[0]}\n")...

I'm running Ubuntu 17.04 and R 3.4.1. I installed the latter yesterday, so I presume it's the latest version. I want to install Tidyverse, which I've spent many happy hours with under Windows. But when I do install.packages("tidyverse") , I get errors about unrecognized command line options to gcc. These start when the install hits the colorspace and munsell packages.

Make it behave more or less like a real VDDK. Of course it ignores all parameters passed and emulates a blank disk, but that is sufficient to do some more realistic testing. --- plugins/vddk/vddk-stubs.h | 8 --- tests/dummy-vddk.c | 115 ++++++++++++++++++++++++++++++++++---- 2 files changed, 103 insertions(+), 20 deletions(-) diff --git a/plugins/vddk/vddk-stubs.h

From: "Richard W.M. Jones" <rjones@redhat.com> Do not use LD_LIBRARY_PATH to locate the VDDK library. Setting this always causes problems because VDDK comes bundled with broken replacements for system libraries, such as libcrypto.so and libstdc++.so. Two problems this causes which we have seen in the real world: (1) User does ‘export LD_LIBRARY_PATH=vmware-vix-disklib-distrib’

Probably needs a bit of cleanup, but seems like it is generally the right direction. One thing I've noticed is that the expect test randomly (but rarely) hangs :-( I guess something is racey but I don't know what at the moment. Rich.

# HG changeset patch # User Matt Wilson <msw@amazon.com> # Date 1342481836 0 # Branch efi # Node ID dd1ab0cae2c870942c2e1b6bc3a507b1a40dae16 # Parent 9950f2dc2ee6dfd172258a5a4ee29809b0ff8263 x86/EFI: define and use EFI_DIR make variable, defaulting to /usr/lib64/efi After commit 25594:ad08cd8e7097, EFI Xen binaries were installed to /efi instead of /usr/lib64/efi. This patch restores the