summaryrefslogtreecommitdiffstats
path: root/Tools
diff options
context:
space:
mode:
authorkris <kris@FreeBSD.org>2002-02-24 00:44:15 +0000
committerkris <kris@FreeBSD.org>2002-02-24 00:44:15 +0000
commitf2880940e3ea87d1e94591fa8568838c132510c6 (patch)
treea9c4281e6f9fefcbf82b9adb4bff2100bc04fd16 /Tools
parentb8a25d72c9d3305e02f4e0fce4dd35b9e87a2902 (diff)
downloadFreeBSD-ports-f2880940e3ea87d1e94591fa8568838c132510c6.zip
FreeBSD-ports-f2880940e3ea87d1e94591fa8568838c132510c6.tar.gz
When the 'makeduds' script fails, show the contents of the duds file instead
of just proclaiming "error(s) occurred". This should immediately identify which port is causing the build to break (although it's a bit of a verbose solution).
Diffstat (limited to 'Tools')
-rwxr-xr-xTools/portbuild/scripts/dopackages3
1 files changed, 2 insertions, 1 deletions
diff --git a/Tools/portbuild/scripts/dopackages b/Tools/portbuild/scripts/dopackages
index 06ef148..677eab4 100755
--- a/Tools/portbuild/scripts/dopackages
+++ b/Tools/portbuild/scripts/dopackages
@@ -74,7 +74,8 @@ makeduds () {
echo "================================================"
echo "duds generation started at $(date)"
if ! ${scripts}/makeduds ${branch}; then
- echo "error(s) detected, exiting script at $(date)"
+ echo "error(s) detected, exiting script at $(date). Failed duds list was:"
+ cat ${pb}/${branch}/duds
errorexit 1
fi
echo "duds generation ended at $(date)"
OpenPOWER on IntegriCloud