shlib | - Useful Shell routines | Script Programming library

To answer your question: no, it's not possible to change the basic sequence of how packages are build.

The dh-sequencer will run the build-process in stages, such as (very much simplified)

• clean
• build
• package

In your current setup, the "build" stage will run two builds (for your two flavours), and once both builds are completed, it will advance to the next stage where it packages all the artifacts into debs.

Now, unfortunately, your 2nd build will just overwrite your 1st build (alternatively it will detect that it already has the binaries in place (not taking the changed envvars into account) and not re-build at all). this is mainly a problem with the build system of the upstream sources (that is: your build system), rather than with the Debian package toolset.

In order to properly build multiple flavours of your package, your build-system should (really) support out-of-tree builds, where you can build all the binaries for one flavour in subdir1/ and all the binaries for another flavour in subdir2/, so the two builds do not interfere.

Then you need to (manually!) instruct dh to invoke your buildsystem with the proper flags to use those subdirectories (and a different configuration, obviously).

A real-world example of a Debian package (disclaimer: maintained by myself) that builds multiple flavours from the same sources using dh can be found here.

The upstream build system uses autotools (which natively supports out-of-tree builds), and the flavours are distinguished by different configure-flags.

The gist is something like this:

If you use Windows, install the R Tools and set the system path, see

https://cran.r-project.org/bin/windows/Rtools/

but if you use Linux, make also sure to have the compilers installed, see https://cran.r-project.org/bin/linux/ and select the instruction that matches your distribution.

Most Linuxes come with the compilers by default, except Ubuntu.

Installing an archived version from source will work.

You can fix your current build by changing the library type from shared (shlib) to static (stlib), i.e.

In case others also run into this issue in the future, I am posting the solution that was suggested to me by https://answers.launchpad.net/ubuntu. Here is the link to the question I posted: https://answers.launchpad.net/ubuntu/+question/696623.

The issue turned out to be that R was using gcc-9 rather than gcc-10 to compile packages. The older version of gcc was throwing an error. Here are the steps I took to solve the problem:

1. Install gcc-10, which was not available on my system: sudo apt install gcc-10.
2. Edit the CC= pointer in the /usr/lib/R/etc/Makeconf file to gcc-10: open Terminal, type sudo nano /usr/lib/R/etc/Makeconf and replace the current CC= to CC=gcc-10. Save the file.
3. Restart R and run the install.packages() command for those packages that were not compiling correctly.

EDIT: Please see the comments below for a discussion. The above steps resolve the issue, but are not recommended. The issue was related to R not using the system package manager to install packages when the call install.packages() was used in R.

Installing the package bspm solved the issue for me. This package and its utility is discussed here for those who are curious.

To use install.packages() within R, bspm can be used in two ways:

1. bspm::enable() within R and then install.packages()
2. As written in its documentation: To enable bspm system-wide by default, include the following: suppressMessages(bspm::enable()) into the Rprofile.site file.

Thanks very much to Dirk for his guidance.

To make it work on Windows, dll and executable has to be in the same folder. You can either copy them manually or set output directory in your top CMake file like this: set(CMAKE_RUNTIME_OUTPUT_DIRECTORY "yours_output_directory"). This way, both executable and dll will end up in yours_output_directory.

The latest (2.6.2) package of libnlopt-dev is broken in Ubuntu 20, for some reason it is compiled into a static library (.so shared object is missing) I faced the similar problem a couple of days ago. The quick fix is to download NLOPT fron Github and compile it yourself https://nlopt.readthedocs.io/en/latest/NLopt_Installation/ At least, it worked for me.

You are so, so close. You essentially solved this. I just took your file, made a small modification of making the script an argument and (as you didn't post script.scm) commented out the content-specific stuff. We still load it though:

Why would you install lme4 from source?

Debian and Ubuntu came with several hundred packages you can install directly, just do