reproduce-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[bug #58561] Including GCC tarball, even when it isn't built


From: Mohammad Akhlaghi
Subject: [bug #58561] Including GCC tarball, even when it isn't built
Date: Sat, 13 Jun 2020 22:47:57 -0400 (EDT)
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:77.0) Gecko/20100101 Firefox/77.0

URL:
  <https://savannah.nongnu.org/bugs/?58561>

                 Summary: Including GCC tarball, even when it isn't built
                 Project: Reproducible paper template
            Submitted by: makhlaghi
            Submitted on: Sun 14 Jun 2020 03:47:56 AM BST
                Category: Software
                Severity: 3 - Normal
              Item Group: Output not reasonable
                  Status: Postponed
                 Privacy: Public
             Assigned to: None
             Open/Closed: Open
         Discussion Lock: Any

    _______________________________________________________

Details:

Currently, when GCC isn't built, its tarball is also not downloaded into the
tarball directory. As a result, if a user packages their tarballs for
publication (like in zenodo.3872248 <https://doi.org/10.5281/zenodo.3872248>),
the GCC tarball won't be included.

This can happen when Maneage is run on a macOS, or when the '--host-cc' option
is given on GNU/Linux systems.

In that particular case, it actually happened to me! I had already tested the
build of GCC on my system, but building GCC takes long (~1 hour). So, to have
a fast final build before submission, I configured it with '--host-cc' (being
ignorant of this bug!) and built the project's software tarball
(software-1637cce.tar.gz
<https://zenodo.org/record/3872248/files/software-1637cce.tar.gz>) after the
build finished. As a result, this tarball doesn't include the tarball of the
specific GCC version!

This can also happen for things like 'patchelf' because its only necessary for
GNU/Linux hosts (so if a project is built on a macOS, patchelf's source won't
be in the software tarball directory). 

It generally happens because we completely ignore the build rules of the
software based on the local environment, so its tarball is also ignored! 

To fix it, we should put the check in the build recipe and if the software is
not necessary on the host for some reason, we just don't build it, yet we
download the tarball (it should be an easy fix!).




    _______________________________________________________

Reply to this item at:

  <https://savannah.nongnu.org/bugs/?58561>

_______________________________________________
  Message sent via Savannah
  https://savannah.nongnu.org/




reply via email to

[Prev in Thread] Current Thread [Next in Thread]