<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto"><div>On Sep 18, 2014, at 10:45, David Strubbe wrote:</div><div><br></div><blockquote type="cite"><div dir="ltr"><div>Is there a way to access a file such as a config.log from a failed port build on a buildslave?</div><div><br></div><div>After my recent changes r125398 and r125404 to the abinit port, the build failed on Mountain Lion, in the configure stage, as follows:</div><div><br></div><div><div>checking for mpicc-mpich-mp... /opt/local/bin/mpicc-mpich-mp</div><div>checking for gcc... mpicc-mpich-mp</div><div>checking whether the C compiler works... no</div><div>configure: error: in `/opt/local/var/macports/build/_opt_mports_dports_science_abinit/abinit/work/abinit-7.8.2':</div><div>configure: error: C compiler cannot create executables</div><div>See `config.log' for more details</div></div><div><br></div><div>(<a href="http://build.macports.org/builders/buildports-mtln-x86_64/builds/17388">http://build.macports.org/builders/buildports-mtln-x86_64/builds/17388</a>)</div><div><br></div><div>I checked that the same happened the last time a revision touched the port. I am not sure how to tackle the problem other than to see what config.log has to say. I am running Mountain Lion on my laptop and I built the same version and everything worked fine, so I am not sure what is different on the buildslave from my machine.</div><div></div></div></blockquote><blockquote type="cite"><div><br></div></blockquote><br><div>We don't have a way to access files on the build servers. The Mac OS Forge admins can, but we shouldn't bother them for this unless absolutely necessary. </div><div><br></div><div>I can try building this port on my system later. </div></body></html>