[MacPorts] #38214: kerberos5: checking whether compile_et is useful... configure: error: execution failed

[MacPorts]

#38214: kerberos5: checking whether compile_et is useful... configure: error:
execution failed
------------------------+-------------------
  Reporter:  ram@…      |      Owner:  cal@…
      Type:  defect     |     Status:  new
  Priority:  Normal     |  Milestone:
 Component:  ports      |    Version:  2.1.3
Resolution:             |   Keywords:
      Port:  kerberos5  |
------------------------+-------------------

Comment (by cal@…):

 Interesting enough, your compile_et has a different md5 than mine. Can you
 attach it?

 Since the output doesn't seem to help, I took a look at the autoconf macro
 that does the check:

 {{{
 # make sure compile_et provides "et_foo" name
 cat >> conf$$e.et <<EOF
 error_table foo
 error_code ERR_FOO, "foo"
 end
 EOF
 AC_CACHE_CHECK(whether compile_et is useful,krb5_cv_compile_et_useful,[
   if compile_et conf$$e.et >/dev/null 2>&1 ; then true ; else
     AC_MSG_ERROR(execution failed)
   fi
   AC_TRY_COMPILE([#include
 "conf$$e.h"],[&et_foo_error_table;],:,[AC_MSG_ERROR(cannot use
 et_foo_error_table)])
   # Anything else we need to test for?
   rm -f conf$$e.c conf$$e.h
   krb5_cv_compile_et_useful=yes
 ])
 }}}

 So it seems while compiling the file
 {{{
 error_table foo
 error_code ERR_FOO, "foo"
 end
 }}}
 with compile_et as the MacPorts user it returns a non-zero exit code on
 your system. Can you try compiling this file using compile_et? What does
 `which awk` print on your system?

-- 
Ticket URL: <https://trac.macports.org/ticket/38214#comment:5>
MacPorts <http://www.macports.org/>
Ports system for Mac OS