helpAutoconf - Support: sr #110480, Generated configure script has...

 
 

sr #110480: Generated configure script has errors

Submitter:  None
Submitted:  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:  -email is unavailable- Open/Closed:  Open
Operating System:  Mac OS
* Mandatory Fields

Add a New Comment (Rich Markup)
   

Comment Type & Canned Response:
       

 

Tue 04 May 2021 03:08:20 PM UTC, comment #2: 

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.

Anonymous
Mon 03 May 2021 05:29:59 PM UTC, comment #1: 

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

Paul Eggert <eggert>
Project Administrator
Mon 03 May 2021 04:00:09 PM UTC, original submission:  

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.

Anonymous

 

(Note: upload size limit is set to 16384 kB, after insertion of the required escape characters.)

Attach Files:
   
   
Comment:
   

No files currently attached

 

Depends on the following items: None found

Items that depend on this one: None found

 

Carbon-Copy List
  • -email is unavailable- added by eggert (Posted a comment)
  • -email is unavailable- added by None (Submitted the item)
  •  

    There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.

    Only logged-in users can vote.

     

     

     

     

    No changes have been made to this item

    Back to the top


    Powered by Savane 3.9