OpenVSP 3.25.0 Ubuntu 18.04 error and fix

[michael...@gmail.com]

Hi all,

I tried to install 3.25.0 with the Ubuntu 18.04 .deb package, but installation fails with:

This package is uninstallable

Dependency is not satisfiable: libgcc-s1 (>= 4.0)

The fix:

wget http://mirrors.edge.kernel.org/ubuntu/pool/main/g/gcc-10/gcc-10-base_10-20200411-0ubuntu1_amd64.deb

wget http://mirrors.xmission.com/ubuntu/pool/main/g/gcc-10/libgcc-s1_10-20200411-0ubuntu1_amd64.deb

sudo gdebi gcc-10-base_10-20200411-0ubuntu1_amd64.deb

sudo gdebi libgcc-s1_10-20200411-0ubuntu1_amd64.deb

Then installing VSP should work.

Cheers

Michael

[Rob McDonald]

When you diagnosed this, did you come to understand the root issue?  What is really wrong -- is there something we can do differently to fix this?

I recently installed a clean Ubuntu and then installed the OpenVSP package from the website -- it worked great for me.  But, this was for 20.04...

Rob

--
You received this message because you are subscribed to the Google Groups "OpenVSP" group.
To unsubscribe from this group and stop receiving emails from it, send an email to openvsp+u...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/openvsp/74346d97-a4d3-436a-881b-369c9f691b36n%40googlegroups.com.

[michael...@gmail.com]

Hi Rob,

I've been running the same 18.04 install since its LTS release in 2018 and even though I do regular updates, it's possible there were updates to gcc that were not part of any official Ubuntu updates.

If someone else can chime in who received the same error it could mean this is a more general problem and adding those two lines to the build sequence should be sufficient?

Otherwise it might just have been a fluke issue for me since my base install is quite old.

Michael

[Rob McDonald]

We've somewhat recently changed our automated builds from Travis to GitHub -- it is likely something to do with how the GitHub machine is configured.

If we can figure that out, we can add an additional dependency and I suspect it could take care of things -- I'm just not sure what is going wrong right now...

Rob

To view this discussion on the web visit https://groups.google.com/d/msgid/openvsp/2cdf9432-a69f-41dd-9506-154b81c318e1n%40googlegroups.com.

[michael...@gmail.com]

That makes sense.

So maybe adding libgcc dependancies here or manually pulling and installing .deb's somewhere here?

Although I would think most people are using 20.04 by now, so maybe just wait to see if this is an issue for others.

[cibinj...@gmail.com]

@Rob

I've been using Ubuntu 18.04 since release and never had this problem. However, I've installed gcc-10 previously for my own work, which might be why I never had this issue.

I think I might have an idea of what this is. Sometimes when packages are built for Ubuntu 18.04 in frameworks like Appveyor, the libgcc-s1 library is added as a dependency. Ubuntu 18.04 by default does not have any repository that contains this library as it seems to be part of the newer gcc-10 compiler package. 

Appveryor probably adds the dependency because admins of those systems add the repository http://ppa.launchpad.net/ubuntu-toolchain-r/test/ubuntu to their Ubuntu 18.04 nodes so that users have access to the latest gcc-10.

I'm not sure if GitHub Actions has this same issue. If this is indeed the cause, simply adding libgcc-s1 as a dependency will not work. It is already present in the dependency list which is also why the build fails. Instead, the above repository would have to be added earlier on like in a pre-install script.

I am leaning towards Michael's suggestion of waiting to see if any others come up with the same issue.

@Micheal, you might be better off adding the above repository and installing gcc-10 from it, since you'll be able to get updates. If you do plan to remove your installed gcc-10 package and re-install it from that ubuntu-toolchain-r repository, I would love to know if OpenVSP installs without issues after adding the repository before re-installing gcc-10. APT should pick up that libgcc-s1 as a dependency and install it by itself once the repository is available.

- Cibin

[Rob McDonald]

Those are the places where we set up the build virtual machine -- and then go through the build process.  Fixing the problem might happen there.

However, the package is built here.  With some magic CMake commands to detect what packages are required to make something work.  I.e. our *.deb dependency list is built implicitly using this magic.  It may be that it is getting something wrong or is missing something.

Rob

To view this discussion on the web visit https://groups.google.com/d/msgid/openvsp/de30dfbb-fa63-4116-ad9a-dfdd3b8865e2n%40googlegroups.com.

[michael...@gmail.com]

Cibin, I tried doing what you say, but after running `sudo apt-get remove libgcc-10' I get the error `apt-get: error while loading shared libraries: libgcc_s.so.1: cannot open shared object file: No such file or directory'.

So basically removing libgcc-s1 breaks apt. Trying to do anything with apt then results in the same error mentioned above.

I could fix apt by manually reinstalling it using the two files I linked in my original post, and I have to do that using dpkg since apt is broken.

So not sure how I would install libgcc-10 from your linked repository if I cannot use apt. Open to suggestions.

[cibinj...@gmail.com]

Oh that sounds like it would turn into a mess pretty fast. I think the package to be removed is gcc-10 and not libgcc-10. However, ensure the default compilers like gcc-7 are not removed when playing around with other new versions. C libraries/compilers are pretty important to get new packages installed, and removing them might nuke your OS altogether.

I'll try to set up a virtual machine over the weekend and confirm this issue.

[michael...@gmail.com]

Sounds good, let me know if you want me to test something on my side.