DOCSLIB.ORG

R Installation and Administration Version 4.1.1 (2021-08-10)

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
R Installation and Administration Version 4.1.1 (2021-08-10) R Installation and Administration Version 4.1.1 (2021-08-10) R Core Team This manual is for R, version 4.1.1 (2021-08-10). Copyright c 2001{2021 R Core Team Permission is granted to make and distribute verbatim copies of this manual provided the copyright notice and this permission notice are preserved on all copies. Permission is granted to copy and distribute modified versions of this manual under the conditions for verbatim copying, provided that the entire resulting derived work is distributed under the terms of a permission notice identical to this one. Permission is granted to copy and distribute translations of this manual into an- other language, under the above conditions for modified versions, except that this permission notice may be stated in a translation approved by the R Core Team. i Table of Contents 1 Obtaining R :::::::::::::::::::::::::::::::::::::::::::::::::::: 1 1.1 Getting and unpacking the sources ::::::::::::::::::::::::::::::::::::::::::::::::: 1 1.2 Getting patched and development versions ::::::::::::::::::::::::::::::::::::::::: 1 1.2.1 Using Subversion and rsync ::::::::::::::::::::::::::::::::::::::::::::::::::: 1 2 Installing R under Unix-alikes :::::::::::::::::::::::::::::::: 3 2.1 Simple compilation :::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: 3 2.2 Help options ::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: 4 2.3 Making the manuals ::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: 5 2.4 Installation :::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: 6 2.5 Uninstallation ::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: 8 2.6 Sub-architectures :::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: 8 2.6.1 Multilib::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: 9 2.7 Other Options :::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: 10 2.7.1 Debugging Symbols :::::::::::::::::::::::::::::::::::::::::::::::::::::::::: 10 2.7.2 OpenMP Support :::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: 11 2.7.3 C++ Support:::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: 11 2.7.4 Link-Time Optimization ::::::::::::::::::::::::::::::::::::::::::::::::::::: 12 2.7.4.1 LTO with GCC ::::::::::::::::::::::::::::::::::::::::::::::::::::::::: 13 2.7.4.2 LTO with LLVM :::::::::::::::::::::::::::::::::::::::::::::::::::::::: 13 2.7.4.3 LTO for package checking ::::::::::::::::::::::::::::::::::::::::::::::: 14 2.8 Testing an Installation :::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: 14 3 Installing R under Windows ::::::::::::::::::::::::::::::::: 16 3.1 Building from source:::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: 16 3.1.1 The Windows toolset :::::::::::::::::::::::::::::::::::::::::::::::::::::::: 16 3.1.2 LATEX:::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: 16 3.2 Checking the build:::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: 17 3.3 Testing an Installation :::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: 17 4 Installing R under macOS:::::::::::::::::::::::::::::::::::: 18 4.1 Running R under macOS ::::::::::::::::::::::::::::::::::::::::::::::::::::::::: 18 4.2 Uninstalling under macOS :::::::::::::::::::::::::::::::::::::::::::::::::::::::: 19 4.3 Multiple versions ::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: 20 5 Running R::::::::::::::::::::::::::::::::::::::::::::::::::::: 21 6 Add-on packages :::::::::::::::::::::::::::::::::::::::::::::: 22 6.1 Default packages:::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: 22 6.2 Managing libraries :::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: 22 6.3 Installing packages :::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: 22 6.3.1 Windows :::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: 24 6.3.2 macOS :::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: 24 6.3.3 Customizing package compilation::::::::::::::::::::::::::::::::::::::::::::: 26 6.3.4 Multiple sub-architectures:::::::::::::::::::::::::::::::::::::::::::::::::::: 27 6.3.5 Byte-compilation::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: 28 ii 6.3.6 External software :::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: 28 6.4 Updating packages :::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: 28 6.5 Removing packages ::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: 29 6.6 Setting up a package repository ::::::::::::::::::::::::::::::::::::::::::::::::::: 29 6.7 Checking installed source packages :::::::::::::::::::::::::::::::::::::::::::::::: 30 7 Internationalization and Localization:::::::::::::::::::::::: 31 7.1 Locales ::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: 31 7.1.1 Locales under Unix-alikes :::::::::::::::::::::::::::::::::::::::::::::::::::: 31 7.1.2 Locales under Windows :::::::::::::::::::::::::::::::::::::::::::::::::::::: 31 7.1.3 Locales under macOS :::::::::::::::::::::::::::::::::::::::::::::::::::::::: 32 7.2 Localization of messages :::::::::::::::::::::::::::::::::::::::::::::::::::::::::: 32 8 Choosing between 32- and 64-bit builds :::::::::::::::::::: 34 9 The standalone Rmath library ::::::::::::::::::::::::::::::: 35 9.1 Unix-alikes ::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: 35 9.2 Windows ::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: 36 Appendix A Essential and useful other programs under a Unix-alike :::::::::::::::::::::::::::::::::: 38 A.1 Essential programs and libraries :::::::::::::::::::::::::::::::::::::::::::::::::: 38 A.2 Useful libraries and programs::::::::::::::::::::::::::::::::::::::::::::::::::::: 40 A.2.1 Tcl/Tk:::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: 41 A.2.2 Java support :::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: 42 A.2.3 Other compiled languages ::::::::::::::::::::::::::::::::::::::::::::::::::: 43 A.3 Linear algebra:::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: 43 A.3.1 BLAS ::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: 43 A.3.1.1 ATLAS::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: 44 A.3.1.2 OpenBLAS ::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: 45 A.3.1.3 Intel MKL:::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: 46 A.3.1.4 Shared BLAS::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: 47 A.3.2 LAPACK ::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: 47 A.3.3 Caveats ::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: 48 Appendix B Configuration on a Unix-alike ::::::::::::::::::: 50 B.1 Configuration options :::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: 50 B.2 Internationalization support :::::::::::::::::::::::::::::::::::::::::::::::::::::: 51 B.3 Configuration variables ::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: 51 B.3.1 Setting paper size ::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: 51 B.3.2 Setting the browsers ::::::::::::::::::::::::::::::::::::::::::::::::::::::::: 51 B.3.3 Compilation flags:::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: 52 B.3.4 Making manuals ::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: 52 B.4 Setting the shell :::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: 52 B.5 Using make :::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: 52 B.6 Using Fortran :::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: 52 B.7 Compile and load flags ::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: 53 B.8 Maintainer mode ::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: 54 iii Appendix C Platform notes :::::::::::::::::::::::::::::::::::: 55 C.1 X11 issues:::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: 55 C.2 Linux :::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: 56 C.2.1 Clang ::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: 58 C.2.2 Intel compilers :::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: 58 C.3 macOS ::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: 59 C.3.1 Prerequisites :::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: 59 C.3.1.1 Note for Catalina and Big Sur users::::::::::::::::::::::::::::::::::::: 61 C.3.2 Cairo graphics::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: 61 C.3.3 Other C/C++ compilers::::::::::::::::::::::::::::::::::::::::::::::::::::: 62 C.3.4 Other libraries::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: 63 C.3.5 Tcl/Tk headers and libraries::::::::::::::::::::::::::::::::::::::::::::::::: 64 C.3.6 Java::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: 64 C.3.7 Frameworks ::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: 65 C.3.8 Building R.app :::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: 66 C.3.9 Building binary packages :::::::::::::::::::::::::::::::::::::::::::::::::::: 66 C.3.10 `arm64' aka `Apple Silicon':::::::::::::::::::::::::::::::::::::::::::::::::: 67 C.3.10.1 Native builds :::::::::::::::::::::::::::::::::::::::::::::::::::::::::: 67 C.4 Solaris ::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: 68 C.4.1 64-bit
Load more

Recommended publications
  • Source Code Trees in the VALLEY of THE
    PROGRAMMING GNOME Source code trees IN THE VALLEY OF THE CODETHORSTEN FISCHER So you’ve just like the one in Listing 1. Not too complex, eh? written yet another Unfortunately, creating a Makefile isn’t always the terrific GNOME best solution, as assumptions on programs program. Great! But locations, path names and others things may not be does it, like so many true in all cases, forcing the user to edit the file in other great programs, order to get it to work properly. lack something in terms of ease of installation? Even the Listing 1: A simple Makefile for a GNOME 1: CC=/usr/bin/gcc best and easiest to use programs 2: CFLAGS=`gnome-config —cflags gnome gnomeui` will cause headaches if you have to 3: LDFLAGS=`gnome-config —libs gnome gnomeui` type in lines like this, 4: OBJ=example.o one.o two.o 5: BINARIES=example With the help of gcc -c sourcee.c gnome-config —libs —cflags 6: gnome gnomeui gnomecanvaspixbuf -o sourcee.o 7: all: $(BINARIES) Automake and Autoconf, 8: you can create easily perhaps repeated for each of the files, and maybe 9: example: $(OBJ) with additional compiler flags too, only to then 10: $(CC) $(LDFLAGS) -o $@ $(OBJ) installed source code demand that everything is linked. And at the end, 11: do you then also have to copy the finished binary 12: .c.o: text trees. Read on to 13: $(CC) $(CFLAGS) -c $< manually into the destination directory? Instead, 14: find out how. wouldn’t you rather have an easy, portable and 15: clean: quick installation process? Well, you can – if you 16: rm -rf $(OBJ) $(BINARIES) know how.
    [Show full text]
  • Red Hat Enterprise Linux 6 Developer Guide
    Red Hat Enterprise Linux 6 Developer Guide An introduction to application development tools in Red Hat Enterprise Linux 6 Dave Brolley William Cohen Roland Grunberg Aldy Hernandez Karsten Hopp Jakub Jelinek Developer Guide Jeff Johnston Benjamin Kosnik Aleksander Kurtakov Chris Moller Phil Muldoon Andrew Overholt Charley Wang Kent Sebastian Red Hat Enterprise Linux 6 Developer Guide An introduction to application development tools in Red Hat Enterprise Linux 6 Edition 0 Author Dave Brolley [email protected] Author William Cohen [email protected] Author Roland Grunberg [email protected] Author Aldy Hernandez [email protected] Author Karsten Hopp [email protected] Author Jakub Jelinek [email protected] Author Jeff Johnston [email protected] Author Benjamin Kosnik [email protected] Author Aleksander Kurtakov [email protected] Author Chris Moller [email protected] Author Phil Muldoon [email protected] Author Andrew Overholt [email protected] Author Charley Wang [email protected] Author Kent Sebastian [email protected] Editor Don Domingo [email protected] Editor Jacquelynn East [email protected] Copyright © 2010 Red Hat, Inc. and others. The text of and illustrations in this document are licensed by Red Hat under a Creative Commons Attribution–Share Alike 3.0 Unported license ("CC-BY-SA"). An explanation of CC-BY-SA is available at http://creativecommons.org/licenses/by-sa/3.0/. In accordance with CC-BY-SA, if you distribute this document or an adaptation of it, you must provide the URL for the original version. Red Hat, as the licensor of this document, waives the right to enforce, and agrees not to assert, Section 4d of CC-BY-SA to the fullest extent permitted by applicable law.
    [Show full text]
  • The Interplay of Compile-Time and Run-Time Options for Performance Prediction Luc Lesoil, Mathieu Acher, Xhevahire Tërnava, Arnaud Blouin, Jean-Marc Jézéquel
    The Interplay of Compile-time and Run-time Options for Performance Prediction Luc Lesoil, Mathieu Acher, Xhevahire Tërnava, Arnaud Blouin, Jean-Marc Jézéquel To cite this version: Luc Lesoil, Mathieu Acher, Xhevahire Tërnava, Arnaud Blouin, Jean-Marc Jézéquel. The Interplay of Compile-time and Run-time Options for Performance Prediction. SPLC 2021 - 25th ACM Inter- national Systems and Software Product Line Conference - Volume A, Sep 2021, Leicester, United Kingdom. pp.1-12, 10.1145/3461001.3471149. hal-03286127 HAL Id: hal-03286127 https://hal.archives-ouvertes.fr/hal-03286127 Submitted on 15 Jul 2021 HAL is a multi-disciplinary open access L’archive ouverte pluridisciplinaire HAL, est archive for the deposit and dissemination of sci- destinée au dépôt et à la diffusion de documents entific research documents, whether they are pub- scientifiques de niveau recherche, publiés ou non, lished or not. The documents may come from émanant des établissements d’enseignement et de teaching and research institutions in France or recherche français ou étrangers, des laboratoires abroad, or from public or private research centers. publics ou privés. The Interplay of Compile-time and Run-time Options for Performance Prediction Luc Lesoil, Mathieu Acher, Xhevahire Tërnava, Arnaud Blouin, Jean-Marc Jézéquel Univ Rennes, INSA Rennes, CNRS, Inria, IRISA Rennes, France [email protected] ABSTRACT Both compile-time and run-time options can be configured to reach Many software projects are configurable through compile-time op- specific functional and performance goals. tions (e.g., using ./configure) and also through run-time options (e.g., Existing studies consider either compile-time or run-time op- command-line parameters, fed to the software at execution time).
    [Show full text]
  • The GNOME Desktop Environment
    The GNOME desktop environment Miguel de Icaza ([email protected]) Instituto de Ciencias Nucleares, UNAM Elliot Lee ([email protected]) Federico Mena ([email protected]) Instituto de Ciencias Nucleares, UNAM Tom Tromey ([email protected]) April 27, 1998 Abstract We present an overview of the free GNU Network Object Model Environment (GNOME). GNOME is a suite of X11 GUI applications that provides joy to users and hackers alike. It has been designed for extensibility and automation by using CORBA and scripting languages throughout the code. GNOME is licensed under the terms of the GNU GPL and the GNU LGPL and has been developed on the Internet by a loosely-coupled team of programmers. 1 Motivation Free operating systems1 are excellent at providing server-class services, and so are often the ideal choice for a server machine. However, the lack of a consistent user interface and of consumer-targeted applications has prevented free operating systems from reaching the vast majority of users — the desktop users. As such, the benefits of free software have only been enjoyed by the technically savvy computer user community. Most users are still locked into proprietary solutions for their desktop environments. By using GNOME, free operating systems will have a complete, user-friendly desktop which will provide users with powerful and easy-to-use graphical applications. Many people have suggested that the cause for the lack of free user-oriented appli- cations is that these do not provide enough excitement to hackers, as opposed to system- level programming. Since most of the GNOME code had to be written by hackers, we kept them happy: the magic recipe here is to design GNOME around an adrenaline response by trying to use exciting models and ideas in the applications.
    [Show full text]
  • Solaris 10 End of Life
    Solaris 10 end of life Continue Oracle Solaris 10 has had an amazing OS update, including ground features such as zones (Solaris containers), FSS, Services, Dynamic Tracking (against live production operating systems without impact), and logical domains. These features have been imitated in the market (imitation is the best form of flattery!) like all good things, they have to come to an end. Sun Microsystems was acquired by Oracle and eventually, the largest OS known to the industry, needs to be updated. Oracle has set a retirement date of January 2021. Oracle indicated that Solaris 10 systems would need to raise support costs. Oracle has never provided migratory tools to facilitate migration from Solaris 10 to Solaris 11, so migration to Solaris has been slow. In September 2019, Oracle decided that extended support for Solaris 10 without an additional financial penalty would be delayed until 2024! Well its March 1 is just a reminder that Oracle Solaris 10 is getting the end of life regarding support if you accept extended support from Oracle. Combined with the fact gdpR should take effect on May 25, 2018 you want to make sure that you are either upgraded to Solaris 11.3 or have taken extended support to obtain any patches for security issues. For more information on tanningix releases and support dates of old and new follow this link ×Sestive to abort the Unix Error Operating System originally developed by Sun Microsystems SolarisDeveloperSun Microsystems (acquired by Oracle Corporation in 2009)Written inC, C'OSUnixWorking StateCurrentSource ModelMixedInitial release1992; 28 years ago (1992-06)Last release11.4 / August 28, 2018; 2 years ago (2018-08-28)Marketing targetServer, PlatformsCurrent: SPARC, x86-64 Former: IA-32, PowerPCKernel typeMonolithic with dynamically downloadable modulesDefault user interface GNOME-2-LicenseVariousOfficial websitewww.oracle.com/solaris Solaris is the own operating system Of Unix, originally developed by Sunsystems.
    [Show full text]
  • Why and How I Use Lilypond Daniel F
    Why and How I Use LilyPond Daniel F. Savarese Version 1.1 Copyright © 2018 Daniel F. Savarese1 even with an academic discount. I never got my money's Introduction worth out of it. At the time I couldn't explain exactly why, but I was never productive using it. In June of 2017, I received an email from someone using my classical guitar transcriptions inquiring about how I Years later, when I started playing piano, I upgraded to use LilyPond2 to typeset (or engrave) music. He was the latest version of Finale and suddenly found it easier dissatisfied with his existing WYSIWYG3 commercial to produce scores using the software. It had nothing to software and was looking for alternatives. He was im- do with new features in the product. After notating eight pressed with the appearance of my transcription of Lá- original piano compositions, I realized that my previous grima and wondered if I would share the source for it difficulties had to do with the idiosyncratic requirements and my other transcriptions. of guitar music that were not well-supported by the soft- ware. Nevertheless, note entry and the overall user inter- I sent the inquirer a lengthy response explaining that I'd face of Finale were tedious. I appreciated how accurate like to share the source for my transcriptions, but that it the MIDI playback could be with respect to dynamics, wouldn't be readily usable by anyone given the rather tempo changes, articulations, and so on. But I had little involved set of support files and programs I've built to need for MIDI output.
    [Show full text]
  • Salt Documentation Release 2014.7.6
    Salt Documentation Release 2014.7.6 SaltStack, Inc. May 19, 2015 Contents 1 Introduction to Salt 1 1.1 e 30 second summary ........................................... 1 1.2 Simplicity ................................................... 1 1.3 Parallel execution ............................................... 1 1.4 Building on proven technology ....................................... 2 1.5 Python client interface ............................................ 2 1.6 Fast, flexible, scalable ............................................. 2 1.7 Open ...................................................... 2 1.8 Salt Community ................................................ 2 1.9 Mailing List .................................................. 2 1.10 IRC ....................................................... 3 1.11 Follow on Github ............................................... 3 1.12 Blogs ...................................................... 3 1.13 Example Salt States .............................................. 3 1.14 Follow on ohloh ................................................ 3 1.15 Other community links ............................................ 4 1.16 Hack the Source ................................................ 4 2 Installation 5 2.1 ick Install .................................................. 5 2.2 Platform-specific Installation Instructions ................................. 5 2.3 Dependencies ................................................. 26 2.4 Optional Dependencies ............................................ 27 2.5 Upgrading
    [Show full text]
  • Autotools Tutorial
    Autotools Tutorial Mengke HU ECE Department Drexel University ASPITRG Group Meeting Outline 1 Introduction 2 GNU Coding standards 3 Autoconf 4 Automake 5 Libtools 6 Demonstration The Basics of Autotools 1 The purpose of autotools I It serves the needs of your users (checking platform and libraries; compiling and installing ). I It makes your project incredibly portablefor dierent system platforms. 2 Why should we use autotools: I A lot of free softwares target Linux operating system. I Autotools allow your project to build successfully on future versions or distributions with virtually no changes to the build scripts. The Basics of Autotools 1 The purpose of autotools I It serves the needs of your users (checking platform and libraries; compiling and installing ). I It makes your project incredibly portablefor dierent system platforms. 2 Why should we use autotools: I A lot of free softwares target Linux operating system. I Autotools allow your project to build successfully on future versions or distributions with virtually no changes to the build scripts. The Basics of Autotools 1 3 GNU packages for GNU build system I Autoconf Generate a conguration script for a project I Automake Simplify the process of creating consistent and functional makeles I Libtool Provides an abstraction for the portable creation of shared libraries 2 Basic steps (commends) to build and install software I tar -zxvf package_name-version.tar.gz I cd package_name-version I ./congure I make I sudo make install The Basics of Autotools 1 3 GNU packages for GNU build
    [Show full text]
  • 1 What Is Gimp? 3 2 Default Short Cuts and Dynamic Keybinding 9
    GUM The Gimp User Manual version 1.0.0 Karin Kylander & Olof S Kylander legalities Legalities The Gimp user manual may be reproduced and distributed, subject to the fol- lowing conditions: Copyright © 1997 1998 by Karin Kylander Copyright © 1998 by Olof S Kylander E-mail: [email protected] (summer 98 [email protected]) The Gimp User Manual is an open document; you may reproduce it under the terms of the Graphic Documentation Project Copying Licence (aka GDPL) as published by Frozenriver. This document is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANT- ABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the Graphic Documentation Project Copying License for more details. GRAPHIC DOCUMENTATION PROJECT COPYING LICENSE The following copyright license applies to all works by the Graphic Docu- mentation Project. Please read the license carefully---it is similar to the GNU General Public License, but there are several conditions in it that differ from what you may be used to. The Graphic Documentation Project manuals may be reproduced and distrib- uted in whole, subject to the following conditions: The Gimp User Manual Page i Legalities All Graphic Documentation Project manuals are copyrighted by their respective authors. THEY ARE NOT IN THE PUBLIC DOMAIN. • The copyright notice above and this permission notice must be preserved complete. • All work done under the Graphic Documentation Project Copying License must be available in source code for anyone who wants to obtain it. The source code for a work means the preferred form of the work for making modifications to it.
    [Show full text]
  • Download Chapter 3: "Configuring Your Project with Autoconf"
    CONFIGURING YOUR PROJECT WITH AUTOCONF Come my friends, ’Tis not too late to seek a newer world. —Alfred, Lord Tennyson, “Ulysses” Because Automake and Libtool are essen- tially add-on components to the original Autoconf framework, it’s useful to spend some time focusing on using Autoconf without Automake and Libtool. This will provide a fair amount of insight into how Autoconf operates by exposing aspects of the tool that are often hidden by Automake. Before Automake came along, Autoconf was used alone. In fact, many legacy open source projects never made the transition from Autoconf to the full GNU Autotools suite. As a result, it’s not unusual to find a file called configure.in (the original Autoconf naming convention) as well as handwritten Makefile.in templates in older open source projects. In this chapter, I’ll show you how to add an Autoconf build system to an existing project. I’ll spend most of this chapter talking about the fundamental features of Autoconf, and in Chapter 4, I’ll go into much more detail about how some of the more complex Autoconf macros work and how to properly use them. Throughout this process, we’ll continue using the Jupiter project as our example. Autotools © 2010 by John Calcote Autoconf Configuration Scripts The input to the autoconf program is shell script sprinkled with macro calls. The input stream must also include the definitions of all referenced macros—both those that Autoconf provides and those that you write yourself. The macro language used in Autoconf is called M4. (The name means M, plus 4 more letters, or the word Macro.1) The m4 utility is a general-purpose macro language processor originally written by Brian Kernighan and Dennis Ritchie in 1977.
    [Show full text]
  • Nagios Plugins - Installing Nagios Plugins from Source
    Nagios Plugins - Installing Nagios Plugins From Source Article Number: 569 | Rating: 2.4/5 from 7 votes | Last Updated: Mon, Feb 15, 2021 at 1:24 PM O ve r vie w This KB article provides instructions on installing Nagios Plugins from source. You will have observed that most of the existing documentation already includes steps on installing the plugins. However there are some plugins that require other libraries which are not included in those instructions. The goal of this documentation is to provide the instructions to install every possible plugin that exists. Nagios Plugins 2.3.3 is what this guide instructs you to install, however future versions should also work fine with these steps. Some considerations: It is assumed that you are logged onto the machine you are installing Nagios Plugins as the ro o t user, or a user with sufficient privileges. All of the steps below were tested on the operating systems (OS) listed after a clean install of the OS. Some OS's like Ubuntu and SUSE have stricter user permissions, in those cases the listed commands have sudo in front of them to ensure you are able to complete the steps. A best effort has been made to ensure if you follow all the relevant steps you will end up with a working installation of Nagios Plugins. The KB article is broken up into the following steps: Install Prerequisites - Common Install Prerequisites - Package XYZ Some plugins (MySQL for example) require addtional libraries and have their own section. They are also in their own section as not everyone requires to monitor that specific item.
    [Show full text]
  • Microservices
    Implementing DevOps with Ansible 2 Build, develop, test, deploy, and monitor in seconds Jonathan McAllister BIRMINGHAM - MUMBAI Implementing DevOps with Ansible 2 Copyright © 2017 Packt Publishing All rights reserved. No part of this book may be reproduced, stored in a retrieval system, or transmitted in any form or by any means, without the prior written permission of the publisher, except in the case of brief quotations embedded in critical articles or reviews. Every effort has been made in the preparation of this book to ensure the accuracy of the information presented. However, the information contained in this book is sold without warranty, either express or implied. Neither the author, nor Packt Publishing, and its dealers and distributors will be held liable for any damages caused or alleged to be caused directly or indirectly by this book. Packt Publishing has endeavored to provide trademark information about all of the companies and products mentioned in this book by the appropriate use of capitals. However, Packt Publishing cannot guarantee the accuracy of this information. First published: July 2017 Production reference: 1200717 Published by Packt Publishing Ltd. Livery Place 35 Livery Street Birmingham B3 2PB, UK. ISBN 978-1-78712-053-2 www.packtpub.com Credits Author Copy Editors Jonathan McAllister Madhusudan Uchil Stuti Srivastava Reviewer Project Coordinator Matthew Fisher Virginia Dias Acquisition Editor Proofreader Meeta Rajani Safis Editing Content Development Editor Indexer Sharon Raj Aishwarya Gangawane Technical Editor Graphics Vishal Kamal Mewada Kirk D'Penha Production Coordinator Aparna Bhagat About the Author Jonathan McAllister has been creating software and automations since he was a child.
    [Show full text]