bug-autoconf
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

openmpi: FTBFS: Compilation errors


From: Ralf Wildenhues
Subject: openmpi: FTBFS: Compilation errors
Date: Wed, 18 Aug 2010 19:31:42 +0200
User-agent: Mutt/1.5.20 (2010-04-22)

clone 592892 -1
reassign -1 autoconf
retitle -1 AS_VAR_GET regression
tags -1 + upstream
thanks

[ http://bugs.debian.org/592892 ]

If I got above right, then I'm cloning this bug for Autoconf and
marking it as upstream bug; adding bug-autoconf in Cc:.

* Sebastian Andrzej Siewior wrote on Wed, Aug 18, 2010 at 04:53:44PM CEST:
> config/f77_get_alignment.m4.
> The value should be set in third last line
> 
> | $2=AS_VAR_GET([type_var])
> 
> It was transformed earlier into
> | ofc_type_alignment=$ompi_cv_f77_alignment_LOGICALp1
> but become something totally differnt,
> 
> |ofc_type_alignment=`eval 'as_val=${'type_var'};$as_echo "$as_val"'`

> After carefully replacing it with AS_VAR_COPY we get
> | eval ofc_type_alignment=\$$as_type_var
> 
> which does the job for now. Puh. Now out quick!

Well, AS_VAR_GET is (intentionally) undocumented, so your use of
AS_VAR_COPY is the right thing to do (which is why I'll leave the
original bug for openmpi).  Still, this is a regression in upstream
Autoconf that I think should be fixed.  The issue is that '*' needs to
be translated to 'p' here and the string treated as literal here:

cat >configure.ac <<\EOF
AC_DEFUN([OMPI_F77_GET_ALIGNMENT],[
    AS_VAR_PUSHDEF([type_var], [ompi_cv_f77_alignment_$1])
    $2=AS_VAR_GET([type_var])
    AS_VAR_POPDEF([type_var])dnl
])

AC_INIT
OMPI_F77_GET_ALIGNMENT([LOGICAL*1], [result])
EOF

autoconf
tail configure

should contain a line like:
  result=$ompi_cv_f77_alignment_LOGICALp1

but instead has something like:
    as_type_var=`$as_echo "ompi_cv_f77_alignment_LOGICAL*1" | $as_tr_sh`
    result=`eval 'as_val=${'type_var'};$as_echo "$as_val"'`

Thanks,
Ralf



reply via email to

[Prev in Thread] Current Thread [Next in Thread]