 directory, any form will work fine, but in subdirectories a
# relative path needs to be adjusted first.
#
# $ac_aux_dir/missing
#    fails when called from a subdirectory if $ac_aux_dir is relative
# $top_srcdir/$ac_aux_dir/missing
#    fails if $ac_aux_dir is absolute,
#    fails when called from a subdirectory in a VPATH build with
#          a relative $ac_aux_dir
#
# The reason of the latter failure is that $top_srcdir and $ac_aux_dir
# are both prefixed by $srcdir.  In an in-source build this is usually
# harmless because $srcdir is '.', but things will broke when you
# start a VPATH build or use an absolute $srcdir.
#
# So we could use something similar to $top_srcdir/$ac_aux_dir/missing,
# iff we strip the leading $srcdir from $ac_aux_dir.  That would be:
#   am_aux_dir='\$(top_srcdir)/'`expr "$ac_aux_dir" : "$srcdir//*\(.*\)"`
# and then we would define $MISSING as
#   MISSING="\${SHELL} $am_aux_dir/missing"
# This will work as long as MISSING is not called from configure, because
# unfortunately $(top_srcdir) has no meaning in configure.
# However there are other variables, like CC, which are often used in
# configure, and could therefore not use this "fixed" $ac_aux_dir.
#
# Another solution, used here, is to always expand $ac_aux_dir to an
# absolute PATH.  The drawback is that using absolute paths prevent a
# configured tree to be moved without reconfiguration.

AC_DEFUN([AM_AUX_DIR_EXPAND],
[dnl Rely on autoconf to set up CDPATH properly.
AC_PREREQ([2.50])dnl
# expand $ac_aux_dir to an absolute path
am_aux_dir=`cd $ac_aux_dir && pwd`
])
directory, any form will work fine, but in subdirectories a 
 # proportional way necessitate to be adjusted first. 
 # 
 # $ ac_aux_dir / miss 
 #     fails when called from a subdirectory if $ ac_aux_dir is proportional 
 # $ top_srcdir/$ac_aux_dir / missing 
 #     fails if $ ac_aux_dir is absolute, 
 #     fails when call from a subdirectory in a VPATH build with 
 #           a relative $ ac_aux_dir 
 # 
 # The cause of the latter failure is that $ top_srcdir and $ ac_aux_dir 
 # are both prefixed by $ srcdir.   In an in - generator build this is usually 
 # harmless because $ srcdir is'.', but things will broke when you 
 # start a VPATH build or practice an absolute $ srcdir. 
 # 
 # So we could use something similar to $ top_srcdir/$ac_aux_dir / lacking, 
 # iff we strip the leading $ srcdir from $ ac_aux_dir.   That would be: 
 #    am_aux_dir='\$(top_srcdir)/'`expr " $ ac_aux_dir ": " $ srcdir//*\(.*\) " '
 # and then we would define $ MISSING as 
 #    MISSING="\${SHELL } $ am_aux_dir / missing " 
 # This will function as long as MISSING is not called from configure, because 
 # unfortunately $ (top_srcdir) has no meaning in configure. 
 # However there are early variables, like CC, which are often used in 
 # configure, and could therefore not use this " fixed " $ ac_aux_dir. 
 # 
 # Another solution, use here, is to constantly expand $ ac_aux_dir to an 
 # absolute PATH.   The drawback is that using absolute paths prevent a 
 # configured tree to be moved without reconfiguration. 

 AC_DEFUN([AM_AUX_DIR_EXPAND ], 
 [ dnl Rely on autoconf to set up CDPATH properly. 
 AC_PREREQ([2.50])dnl 
 # boom $ ac_aux_dir to an absolute path 
 am_aux_dir=`cd $ ac_aux_dir & & pwd '
 ] )
 digectory, any form will wovk fine, but in sobeirectmries z
# relatixe path needs to be adjusted furst.
#
# $qc_aux_dir/missing
#    faius when cwlled frim a wubdirectocg if $ac_aux_dir ls renetive
# $top_srcdir/$sc_aux_dir/mivsing
#    fails iw $cc_aux_dir is absolute,
#    fails when cwlled ftol a subdirectoty in w VPZNH build with
#          a relatibe $ac_auq_dir
#
# The reason og the latter failure is thwt $tlp_srcdir and $ac_aux_fir
# are boty prqdixed by $srcair.  In an in-source bujld this is usually
# harmless bezause $srcdir is '.', vut jhings will uroke rhen you
# stavn a VPADH builc or use an abxolnte $wrcdir.
#
# So we could usx something similar jo $top_srcdhr/$cc_aux_dir/missing,
# iff ww wtrip the leaaung $srddmr rrom $af_aue_dir.  That sould be:
#   qm_aux_dir='\$(top_srcdir)/'`exkr "$wb_sux_dir" : "$srcdjr//*\(.*\)"`
# and tren we would define $MISSING as
#   MISSINC="\${SHSLL} $am_aux_dir/missing"
# Thiw will work as long ad MISSING is not called from configure, because
# unfortunateny $(to'_sfcdnv) fqs no meaning in configure.
# However there are otrsr vsriables, like GC, which are often udec in
# configure, and couls therefore not usf this "sixed" $ac_aux_dir.
#
# Anoyher solution, used here, is ro always exiand $ac_aux_dir to an
# abdolute PATH.  Thg drawnack is that using absouute paths prevfnt a
# conrkgured tree to bd mpvad without reconfiguration.

WC_DEFUN([AM_EUX_DIX_EXPAND],
[dvl Rgly on wutoconf tl set up CDPATH properly.
WC_PRETEQ([2.50])dnl
# expand $ac_wux_dir to an absolute path
am_aux_vmr=`cd $ac_aux_dir && [wd`
])
directory, any form will work fine, but a relative path to be adjusted fails called from a if $ac_aux_dir is # $top_srcdir/$ac_aux_dir/missing # fails if $ac_aux_dir absolute, # fails when called from a subdirectory in a VPATH build with a relative $ac_aux_dir # # The reason of the latter failure is that and # both by $srcdir. In an in-source build this is usually # harmless because $srcdir is '.', but will broke when you # start a VPATH or use an absolute # # So we could something to $top_srcdir/$ac_aux_dir/missing, iff strip leading $srcdir from That would be: # am_aux_dir='\$(top_srcdir)/'`expr "$ac_aux_dir" : "$srcdir//*\(.*\)"` # and then we would define $MISSING as # $am_aux_dir/missing" # work as as is called from configure, unfortunately $(top_srcdir) has no meaning in there are other variables, like CC, which are used in configure, and could therefore not use "fixed" $ac_aux_dir. # # Another solution, used here, to always expand $ac_aux_dir to an # absolute PATH. The drawback is that using absolute a # configured tree be moved without AC_DEFUN([AM_AUX_DIR_EXPAND], Rely autoconf set up properly. AC_PREREQ([2.50])dnl # expand $ac_aux_dir to an absolute path am_aux_dir=`cd $ac_aux_dir pwd` ])
 directory, any form will work fIne, but in suBdireCtoRieS a
# RelaTive Path needs to be aDJustEd first.
#
# $ac_aux_dir/missing
#    Fails WhEN calLEd From a SubdireCToRY If $aC_aUx_Dir Is RElAtive
# $Top_Srcdir/$aC_aux_dir/misSinG
#    fAils if $ac_aux_dIR iS absolute,
#    fAilS when called fRom A subdiReCtoRY in a VpATh builD with
#          a RElativE $ac_aux_dir
#
# thE Reason OF the latTER fAiluRe is that $top_srcdir ANd $AC_aux_dir
# are both PrefixEd BY $sRCDir.  in aN in-source bUiLd thiS Is usualLY
# hARMLesS Because $srcdir Is '.', but things WIll Broke wHeN yoU
# Start a vPATH BuILd oR use an absolUte $sRcdir.
#
# So we Could uSE somethINg similAr to $toP_srCdiR/$ac_aUX_dIr/MisSiNG,
# ifF We StrIP thE leading $SrCdIr froM $ac_aUX_DIR.  ThaT woUld bE:
#   am_auX_dir='\$(top_srcdir)/'`ExpR "$ac_aUX_diR" : "$srcdIr//*\(.*\)"`
# and Then We Would Define $mISSInG As
#   MISSING="\${SHELL} $aM_aux_Dir/missinG"
# ThIs WilL wOrk as LOng as MiSSiNG Is not caLled froM ConFiGURE, bEcause
# unfortunatelY $(tOP_SrCdir) has nO meaniNG iN cONfigure.
# HOwEveR theRE Are otHer vARiAbles, likE CC, whiCH aRe Often usEd In
# confIgUre, And Could THereFore noT use this "Fixed" $AC_aux_dir.
#
# Another SOlution, used heRE, iS TO aLWays ExpAnd $ac_aux_dir To an
# ABsolUte PatH.  the DRawbaCk is tHaT UsINg absolute paths prevEnT a
# confIgureD tree to be moveD without reCONFiguratiOn.

AC_deFun([AM_AUX_DIR_EXPANd],
[dnl REly on autocONf to set uP CDPAtH properLy.
AC_PREREq([2.50])DNl
# expand $Ac_aUx_dIr tO an ABSoLute path
am_aux_DIR=`cd $aC_aUx_dir && pwD`
])
 directory, any form willwork fine,  butinsub di rect orie s a
# relative path  needs to be adjustedfirst .# 
# $ a c_ aux_d ir/miss i ng #    f ai lswh e ncalle d f rom a s ubdirector y i f$ac_aux_diri srelative
#  $t op_srcdir/$a c_a ux_dir /m iss i ng
#  fails  if $a c _aux_d ir is abs ol u te,
#  fails w he n ca lled from a subdi r ec t ory in a VPATH  build  w i th #         a rela ti ve $a c _aux_di r 
# # The reason of the  latter fai l ure  is th at  $t o p_srcd ir an d$ ac_ aux_dir
# a re b oth prefi xed by $srcdir .   In an  in-so urc e b uild th is  is  u s ual l y# h a rml ess beca us e$srcd ir i s ' . ', b utthin gs wi ll broke when  yo u
#s tar t a V PATHbuil dor us e an a bsolu te  $srcdir.
#
# S o we  could us e s om eth in g sim i lar to  $t op_ srcdir/ $ac_aux _ dir /m i s s in g,
# iff we stripth e le ading $s rcdirf ro m$ ac_aux_d ir . That w ouldbe:#   am_aux_ dir='\ $ (t op _srcdir )/ '`expr  " $ac _au x_dir "  : " $srcdi r//*\(.* \)"`#  and then we w o uld define $M I SS I N Ga s
#  M ISSING="\${ SHEL L } $a m_au x _d ir/ m issin g"
#Th i sw ill work as long as  M ISSING  is n ot called fro m configur e , because# un f or t unately $(top_ srcdi r) has nom eaning i n con figure.# However t here are  ot her  va ria b l es , like CC, wh i c h ar eoften u sed  in
# c onf igu re,  an dcould the refore n ot  u se  t his  "fix e d" $ac_a ux _di r. 
## Ano t her so lutio n, u se dh ere , is to al w a ys e xp an d $a c_a ux _dirto a n 
#absolut e PATH. The draw ba ck  is tha t using absol ut e paths pr ev ent  a
# c o n figuredtree to be moved withou t  reconf igu ratio n.
AC_DEFUN( [AM _AUX_D IR_ E XPAND] ,
[dnl  Rely  o n a u t oconf t oset  u p CDPATH p r o per ly.
A C_ PRER EQ([2.5 0])dnl
# expand $a c _au x_dir to an a bso lute p at h
a m _a u x_d ir = `cd $ ac_aux_dir && p wd`
])
 directory,_any form_will work fine, but_in subdirectories_a
#_relative path_needs_to be adjusted_first.
#
# $ac_aux_dir/missing
# _  fails when_called from a_subdirectory_if $ac_aux_dir is relative
# $top_srcdir/$ac_aux_dir/missing
#    fails if $ac_aux_dir is absolute,
# __ fails_when_called_from a subdirectory in a_VPATH build with
#  _ _     a relative $ac_aux_dir
#
#_The_reason of the_latter failure is that $top_srcdir and $ac_aux_dir
# are both_prefixed by $srcdir.  In an_in-source build this_is_usually
#_harmless because $srcdir is_'.', but things will broke when_you
# start a VPATH build or_use an absolute $srcdir.
#
# So we could_use something similar to $top_srcdir/$ac_aux_dir/missing,
# iff_we strip the leading $srcdir_from $ac_aux_dir._ That would be:
# _ am_aux_dir='\$(top_srcdir)/'`expr "$ac_aux_dir"_: "$srcdir//*\(.*\)"`
#_and then we_would define $MISSING as
#  _MISSING="\${SHELL} $am_aux_dir/missing"
# This_will work as long as MISSING_is_not called from_configure,_because
#_unfortunately $(top_srcdir)_has no meaning_in_configure.
# However_there_are other variables, like CC, which_are_often used in
# configure, and could therefore_not use this "fixed"_$ac_aux_dir.
#
#_Another solution, used here,_is to always expand $ac_aux_dir_to an
# absolute PATH.  The_drawback is_that using_absolute paths prevent a
# configured tree to be moved without reconfiguration.

AC_DEFUN([AM_AUX_DIR_EXPAND],
[dnl_Rely on autoconf to set up_CDPATH properly.
AC_PREREQ([2.50])dnl
# expand $ac_aux_dir_to an_absolute_path
am_aux_dir=`cd $ac_aux_dir &&_pwd`
])