Maybe a further thing to consider is to introduce an environment
variable by which one can avoid `add_build_stamp_to_description_file()`
and any other calls altogether which affect bitwise reproducibility
during the build process. If two users build the same package on exactly
the same hardware
Another thing to consider if one wants to anonymize the build is the
UID/GID of the files in the tarball. So there might be a need for a
R_BUILD_UID and R_BUILD_GID, e.g. by setting those to 32767
("nobody").
/Henrik
On Fri, Jan 25, 2019 at 9:25 AM Will L wrote:
>
> Thanks, Kurt.
>
> I think I
On Fri, Nov 22, 2019 at 2:58 PM Saren Tasciyan wrote:
>
> Hi,
>
> I am trying to build a more recent version (3.6.1 or 3.5.3) of R on
> Ubuntu 18.04 LTS.
Are you aware you can get up-to-date binaries either from PPA or CRAN:
sudo add-apt-repository ppa:marutter/rrutter
sudo apt-get install r
Pure guessing, but a frequent way to get the "have libs, still won't build"
syndrome on Linux variants is not having installed the corresponding -dev or
-devel package.
-pd
> On 21 Nov 2019, at 19:07 , Saren Tasciyan wrote:
>
> Hi,
>
> I am trying to build a more recent version (3.6.1 or 3.5
Hi,
I am trying to build a more recent version (3.6.1 or 3.5.3) of R on
Ubuntu 18.04 LTS. I have installed build-deps with:
sudo apt-get build-dep r-base
and I ran ./configure
During "make", I get the following error:
platform.o: In function `do_eSoftVersion':
/home/user/Desktop/R-3.6.1/src
