Hi all,
I am preparing a guide for my client.
I have to confess I do not understand the meaning of

| -group=GROUP | Group to be used for software installations (only verified, 
not set)
 |


What is that mean exactly!!! :-|   ?
Please advice

Roberto ScipioniRed Oak Consulting



    Il giovedì 26 settembre 2024 alle ore 23:01:49 GMT+1, Jörg Saßmannshausen 
<[email protected]> ha scritto:  
 
 Hi Loris,

in your first email I spotted two things coming from the OS, apparently:
- git
- cmake

It makes me wonder if we should not add them as build-dependencies, 
unless they are really not being used. Given it tries to use the OS git 
command, I guess they are being used at one point.

Just something I noticed.

All the best from a wet London

Jörg

Am 26.09.24 um 13:33 schrieb Loris Bennett:
> "Loris Bennett" <[email protected]> writes:
> 
>> Hi,
>>
>> With
>>
>>    xtb-6.7.1-gfbf-2023b.eb
>>
>> I'm getting the following error:
>>
>>    Program git found: YES (/usr/bin/git)
>>    WARNING: You should add the boolean check kwarg to the run_command call.
>>            It currently defaults to false,
>>            but it will default to true in future releases of meson.
>>            See also: https://github.com/mesonbuild/meson/issues/9300
>>    Program python3 found: YES 
>>(/trinity/shared/easybuild/software/Python/3.11.5-GCCcore-13.2.0/bin/python3)
>>    Configuring xtb_version.fh using configuration
>>    Library flexiblas found: YES
>>    Run-time dependency OpenMP found: YES 4.5
>>    Run-time dependency threads found: YES
>>    Found pkg-config: 
>>/trinity/shared/easybuild/software/pkgconf/2.0.3-GCCcore-13.2.0/bin/pkg-config
>> (2.0.3)
>>    WARNING: Found CMake '/usr/bin/cmake' but couldn't run it
>>    Found CMake: NO
>>    Run-time dependency mctc-lib found: NO (tried pkgconfig and cmake)
>>    Looking for a fallback subproject for the dependency mctc-lib
>>
>>    ../xtb-6.7.1/meson/meson.build:194:11: ERROR: Git command failed: 
>>['/usr/bin/git', 'clone', 'https://github.com/grimme-lab/mctc-lib', 
>>'mctc-lib']
>>
>> Does anyone know what could be causing this?
>>
>> Running the git command separately works, so the repo seems OK.
> 
> Today the build ran without error, so it seems to have been a temporary
> glitch.
> 
> Cheers,
> 
> Loris
> 
  

Reply via email to