Errors when running install_packages.sh

[4sfaloth]

Hi,

we are preparing a NIST submission and are facing some issues with the setup of our build & validation environments. In order to make sure we are including all required files in /lib for dynamic linking we

• building our library and exporting the output folders (eg: lib, config and doc) in a development image
• copying these output folders only into a validation image and running the validation scripts there

This validation image is just a raw focal image where we have run

• apt update
• apt -y install sudo lsb-release

And then we run the install_packages.sh script. Problem is the script fails to install many of the packages seemingly due to missing versions on the package repo. For instance libavcodec-dev install fails with
E: Version '7:4.2.4-1ubuntu0.1' for 'libavcodec-dev' was not found

If we edit the install_packages.sh script removing the pinned versions then everything seems to work correctly, though we would no longer be sure to be running in the exact same environment as the NIST benchmark.

Is it possible that the install_packages.sh is pointing to versions no longer available on the public repo and thus needs to be updated, or am I missing something?

Thanks in advance,
Filipe Morais

[mlngan]

Thanks for bringing this to our attention. We will plan to include the actual packages themselves along with an updated install script to address this issue (hopefully in the next week or so).

[Omar-Talabay]

ubuntu iso copy provided at this repo is being used.

I have the same problem specifically the GCC compiler.

The documentation states that GCC version is 9.3.0

while it is 9.4.0 after running install_packages.sh

There are multiple packages that have the same issue.

Should I wait for modification? or package my library and submit with the default installed library?

I appreciate your help @mlngan

[mlngan]

Please go ahead and run/validate with the default installed libraries. The original approach to fixing install_packages.sh is getting a bit more complicated than we originally thought. We will keep this issue open and try to come up with a reasonable solution.