I just realised... I will now need an account on the IBM Support Site, a SiteID AND an Entitlement to file bugs on any Redhat packages.
For those who don't know the system - every site (University, company, Laboratory etc) has a SiteID number. You had better know that number - and if someone leaves or retires you had BETTER get than number from them. (I handled a support case once where a customer had someone retire - and not pass on the site ID- we had to get a high up in IBM UK invoplved);. One person on site then has the ability to allow others on the site to open support issues. You just cannot decide to open a support issue -you must have the rights to ask for support for that product. On Mon, 29 Oct 2018 at 16:55, Joe Landman <joe.land...@gmail.com> wrote: > > On 10/29/18 12:44 PM, David Mathog wrote: > > [...] > > > It turns out that getting up to date compilers and libraries has become > >> quite important for those working on large distributed code bases. > > > > Libraries are harder. Try to build a newer one than ships with CentOS > > and it is not uncommon to end up having to build many other libraries > > (recursive dependencies) or to hit a brick wall when a kernel > > dependency surfaces. > > > This was my point about building things in a different tree. I do this > with tools I use in https://github.com/joelandman/nlytiq-base , which > gives me a consistent set of tools regardless of the platform. > > Unfortunately, some of the software integrates Conda, which makes it > actually harder to integrate what you need. Julia, for all its > benefits, is actually hard to build packages for such that they don't > use Conda. > > > > In biology apps of late there is a distressing tendency for software > > to only be supported in a distribution form which is essentially an > > entire OS worth of libraries packaged with the one (often very small) > > program I actually want to run. (See "bioconda".) Most of these > > programs will build just fine from source even on CentOS 6, but often > > the only way to download a binary for them is to accept an additional > > 1Gb (or more) of other stuff. > > > Yeah, this has become common across many fields. Containers become the > new binaries, so you don't have to live with/accept the platform based > restrictions. This was another point of mine. And Greg K @Sylabs is > getting free exposure here :D > > > -- > Joe Landman > e: joe.land...@gmail.com > t: @hpcjoe > w: https://scalability.org > g: https://github.com/joelandman > l: https://www.linkedin.com/in/joelandman > > _______________________________________________ > Beowulf mailing list, Beowulf@beowulf.org sponsored by Penguin Computing > To change your subscription (digest mode or unsubscribe) visit > http://www.beowulf.org/mailman/listinfo/beowulf >
_______________________________________________ Beowulf mailing list, Beowulf@beowulf.org sponsored by Penguin Computing To change your subscription (digest mode or unsubscribe) visit http://www.beowulf.org/mailman/listinfo/beowulf
