From 4a70bb421e75fddea8e369ce27112e5ae9f07124 Mon Sep 17 00:00:00 2001 From: Lucio Andrés Illanes Albornoz Date: Mar 05 2020 17:26:07 +0000 Subject: etc/README.md: updated. --- diff --git a/etc/README.md b/etc/README.md index 9938ebf..2c34bc7 100644 --- a/etc/README.md +++ b/etc/README.md @@ -3,7 +3,7 @@ the project's IRC channel #midipix on Freenode and ask for the address of the internal repositories required in order to build Midipix. [//]: # "{{{ Table of contents" -# Table of Contents +# Table of Contents 1. [What is midipix, and how is it different?](#1-what-is-midipix-and-how-is-it-different) 2. [Building a midipix distribution](#2-building-a-midipix-distribution) @@ -265,7 +265,24 @@ of package build steps and how they are overriden. [//]: # "{{{ 3.3. Addressing build failure" ## 3.3. Addressing build failure - +During package build, standard error and output are redirected into a log file beneath +``${BUILD_WORKDIR}`` named ``${PKG_NAME}_stderrout.log``, following a package variable +dump. If ``-vv`` was specified, package logs will additionally be printed to standard +output. If ``-vvv`` was specified, ``xtrace`` will be set during package builds for +rudimentary debugging purposes. Additionally, packages using GNU autotools will, if +package configuration failed or appears relevant, log the configuration process in detail +in, most usually, ``${PKG_BUILD_DIR}/config.log``. + +Execute the following command line in order to obtain a package build shell environment: +```shell +export MAKE="make LIBTOOL=slibtool"; # Unless ${PKG_LIBTOOL} is set to any value other than `slibtool' +export PATH="/bin:${PATH:+:${PATH}}"; +cd "/tmp/-*/"; +``` + +Consult sections [3.2](#32-adding-a-package), [3.4](#34-patches-and-vars-files), [4](#4-build-variables), +[4.1](#41-build-steps), and [4.2](#42-package-variables) for further information +concerning the package build process. [Back to top](#table-of-contents)