Kenneth Hoste <kenneth.ho...@ugent.be> writes: > On 04/11/2019 09:48, Loris Bennett wrote: >> Loris Bennett <loris.benn...@fu-berlin.de> writes: >> >>> Hi Kenneth, >>> >>> Sorry for the late response - I was on holiday. >>> >>> Kenneth Hoste <kenneth.ho...@ugent.be> writes: >>> >>>> On 02/10/2019 10:31, Loris Bennett wrote: >>>>> Hi, >>>>> >>>>> I'm trying to build an updated version of AIMS. However, there is a >>>>> problem building the dependency >>>>> >>>>> motif-2.3.8-foss-2018b >>>>> >>>>> namely: >>>>> >>>>> I18List.c:38:10: fatal error: X11/bitmaps/gray: No such file or >>>>> directory >>>>> #include <X11/bitmaps/gray> >>>>> ^~~~~~~~~~~~~~~~~~ >>>>> compilation terminated. >>>>> >>>>> The last commit message says >>>>> >>>>> Removed xbitmaps now in X11 bundle >>>>> >>>>> but >>>>> >>>>> X11-20180604-foss-2018b >>>>> >>>>> which is the X11 dependency given in the motif easyconfig doesn't seem >>>>> to create a subdirectory >>>>> >>>>> include/X11/bitmaps >>>>> >>>>> Any thoughts? >>>> >>>> It seems like xbitmaps only was added to X11 easyconfigs using the GCCcore >>>> toolchain, see >>>> https://github.com/easybuilders/easybuild-easyconfigs/pull/7494/files . >>>> >>>> Where did you get X11-20180604-foss-2018b.eb from? >>>> >>>> This is not an easyconfig file in the central repository... >>> >>> My mistake. The easyconfig >>> >>> motif-2.3.8-foss-2018b.eb >>> >>> just contains the dependency >>> >>> ('X11', '20180604') >>> >>>> In any case, the solution is to apply the same changes as shown in the PR >>>> to >>>> X11-20180604-foss-2018b.eb, and reinstalling it. >>> >>> Shouldn't these changes already be included in the easyconfig which is >>> referenced by the motif easybuild? >> >> So I realised that I need to force a reinstall of >> >> X11-20180604-GCCcore-7.3.0.eb >> >> since that now contains the component 'xbitmaps', which my version does >> not. However, the checksum for xbitmaps-1.1.1.tar.gz seems to have >> changed: >> >> ERROR: Build of >> >> /trinity/shared/easybuild/software/EasyBuild/4.0.1/easybuild/easyconfigs/x/X11/X11-20180604-GCCcore-7.3.0.eb >> failed (err: 'build failed (first 300 chars): Checksum verification >> for /trinity/shared/easybuild/sources/x/X11/xbitmaps-1.1.1.tar.gz >> using 3bc89e05be4179ce4d3dbba1ae554da4591d41f7a489d9e2735a18cfd8378188 >> failed.') >> >> I have: >> >> $ sha256sum /trinity/shared/easybuild/sources/x/X11/xbitmaps-1.1.1.tar.gz >> 8dfbf98adfb38f0b612d15b4baccb23de19cf12dee36c9897708d62aaab6d308 >> /trinity/shared/easybuild/sources/x/X11/xbitmaps-1.1.1.tar.gz > > I just did a fresh download of xbitmaps-1.1.1.tar.gz, and I'm still getting > 3bc89e05be4179ce4d3dbba1ae554da4591d41f7a489d9e2735a18cfd8378188 as SHA256 > checksum... > > Are you sure your download didn't get corrupted somehow? > > What does "file xbitmaps-1.1.1.tar.gz" say? How big is the file (in bytes)? > Should be 140011 .
The download was indeed corrupted. Some parts of our network seemed to have experienced difficulty reaching x.org and the other URLs for downloading the packages. Thus the TGZ file I thought I had was actually an HTML error message. At some point the network fixed itself, and I was able to force a reinstall successfully. Now all is good. I assume that such retroactive changes to existing EasyConfigs, such as that to X11-20180604-GCCcore-7.3.0.eb don't happen very often, so it is maybe not such a problem, but is there any way I could have been aware of the issue with xbitmaps before just having the installation of 'motif' fail? Thanks for the help, Loris -- Dr. Loris Bennett (Mr.) ZEDAT, Freie Universität Berlin Email loris.benn...@fu-berlin.de
