[sr #110480] Generated configure script has errors

2021-05-03 Thread anonymous
URL:
  

 Summary: Generated configure script has errors
 Project: Autoconf
Submitted by: None
Submitted on: Mon 03 May 2021 04:00:09 PM UTC
Category: None
Priority: 5 - Normal
Severity: 3 - Normal
  Status: None
 Privacy: Public
 Assigned to: None
Originator Email: skelb...@gmail.com
 Open/Closed: Open
 Discussion Lock: Any
Operating System: Mac OS

___

Details:

A user of the SANE project has an issue with a generated configure script.

A reference to the original conversation is here:

https://gitlab.com/sane-project/backends/-/issues/468

They are running autoconf 2.71. Attached at the above bug report can be found
their generated configure script.

The issue seems to be related to the generation of this segment in a couple of
places which has invalid syntax:


...
for as_dir in $PATH
do
  IFS=$as_save_IFS
  case $as_dir in #(((
''
 as_dir=./ ;;
*/) ;;
*) as_dir=$as_dir/ ;;
  esac
for ac_exec_ext in '' $ac_executable_extensions; do
  if as_fn_executable_p "$as_dir$ac_word$ac_exec_ext"; then
ac_cv_prog_CC="${ac_tool_prefix}gcc"
printf "%s\n" "$as_me:${as_lineno-$LINENO}: found
$as_dir$ac_word$ac_exec_ext" >&5
break 2
  fi
done
...
IFS=$as_save_IFS


In other areas this segment has valid syntax:

...
for as_dir in $PATH
do
  IFS=$as_save_IFS
  case $as_dir in #(((
'') as_dir=./ ;;
*/) ;;
*) as_dir=$as_dir/ ;;
  esac
for ac_exec_ext in '' $ac_executable_extensions; do
  if as_fn_executable_p "$as_dir$ac_word$ac_exec_ext"; then
ac_cv_prog_CC="${ac_tool_prefix}cc"
printf "%s\n" "$as_me:${as_lineno-$LINENO}: found
$as_dir$ac_word$ac_exec_ext" >&5
break 2
  fi
done
...


Any hints as to how we can track this down would be appreciated.




___

Reply to this item at:

  

___
  Message sent via Savannah
  https://savannah.gnu.org/




[sr #110480] Generated configure script has errors

2021-05-03 Thread Paul Eggert
Follow-up Comment #1, sr #110480 (project autoconf):

The bug report doesn't contain enough info to reproduce the problem. That
being said, most likely the problem is that the SANE project's configure.ac
(or some .m4) file is underquoting. If so, it's not an Autoconf bug. See:

https://www.gnu.org/savannah-checkouts/gnu/autoconf/manual/autoconf-2.70/html_node/Balancing-Parentheses.html

___

Reply to this item at:

  

___
  Message sent via Savannah
  https://savannah.gnu.org/




[sr #110480] Generated configure script has errors

2021-05-04 Thread anonymous
Follow-up Comment #2, sr #110480 (project autoconf):

Thanks for your reply!

I did search unsuccessfully through the configure.ac file for references to
the problematic fragment but if you feel that the source is in there
somewhere, I will have a closer look.


___

Reply to this item at:

  

___
  Message sent via Savannah
  https://savannah.gnu.org/




[sr #110480] Generated configure script has errors

2023-12-08 Thread Zack Weinberg
Update of sr#110480 (group autoconf):

Priority:   5 - Unprioritized => 1 - Blocked
  Status:None => Need Info  

___

Follow-up Comment #3:

We can't do anything with this until we know more about the cause of the
problem.

The code fragment you quote comes from the internal macro _AS_PATH_WALK. 
Based on the transcript shown at the beginning of the bug report, I think the
problem is likely to be in the definition of AM_PATH_PYTHON.  A quick skim of
the project's source tree did not show me where that definition is coming
from.  I need you to take it from there.


___

Reply to this item at:

  

___
Message sent via Savannah
https://savannah.gnu.org/