Guten Tag Jack, Thanks, grepping for 'build_step' did the trick. I'd accumulated a few too many /tmp/eb* directories and lost my bearings somewhat.
Thanks too for the pointer to (and the warning about) '--dump-env-script'. I hadn't been aware of that option. Cheers, Loris Jack Perdue <j-per...@tamu.edu> writes: > Howdy Loris, > > In easybuild*.log file that EB leaves in > the easybuild directory of a successful > build, you can find that information. > Just search for 'configure_step' and then > 'build_step'. Its a few lines after that. > > As for someone who wants to replicate > a build, I'd suggest you also give them the > output of 'eb --dump-env-script my.eb'... > be aware though that will wipe out the previous > install so you have to install again. But, the .env > script is very helpful for setting up to replicate > a build. > > Jack Perdue > Lead Systems Administrator > High Performance Research Computing > TAMU Division of Research > j-per...@tamu.edu http://hprc.tamu.edu > HPRC Helpdesk: h...@hprc.tamu.edu > > On 5/22/20 7:17 AM, Loris Bennett wrote: >> Hi, >> >> To help a developer, I need the log file with the actual 'configure' and >> 'make' commands used for a successful build. I've tried >> >> --disable-cleanup-tmpdir --disable-cleanup-builddir >> >> but I the only log file that seems to be left over is one which contains >> just EasyBuild information. >> >> What am I missing here? >> >> Cheers, >> >> Loris >> > -- Dr. Loris Bennett (Mr.) ZEDAT, Freie Universität Berlin Email loris.benn...@fu-berlin.de
