Bug 221024 - Regression: patsubst causes warnings with empty '?' pattern
Summary: Regression: patsubst causes warnings with empty '?' pattern
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: m4
Version: 6
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Miloslav Trmač
QA Contact: Ben Levenson
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2006-12-30 13:58 UTC by Enrico Scholz
Modified: 2007-11-30 22:11 UTC (History)
0 users

Fixed In Version: 1.4.5-4
Clone Of:
Environment:
Last Closed: 2007-01-12 23:17:27 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Enrico Scholz 2006-12-30 13:58:27 UTC
Description of problem:

Recent 'm4' creates a warning for patsubst expressions with the '?' 
pattern when result is empty

| $ echo 'patsubst(config.h,\([^:]*/\)?.*,\1)' | m4 -E ; echo $?
| stdin:1: m4: Warning: sub-expression 1 not present
| 1
| $

With 'm4-1.4.4' from FC-5, things are fine

| $ echo 'patsubst(config.h,\([^:]*/\)?.*,\1)' | m4 -E ; echo $?
|
| 0
| $


This causes real trouble when building old software which is using
automake-1.4. There, AM_CONFIG_HEADER() contains the pattern

| <<test -z "<<$>>CONFIG_HEADERS" || echo timestamp > patsubst(<<$1>>, <<^\([^:]*/\)?.*>>, <<\1>>)stamp-h<<>>dnl>>,                

and will trigger an error on e.g.

| AM_CONFIG_HEADER(config.h)


Version-Release number of selected component (if applicable):

m4-1.4.5-3

Comment 1 Miloslav Trmač 2007-01-05 04:43:07 UTC
Again, thanks for the report.

Comment 2 Fedora Update System 2007-01-05 17:00:51 UTC
m4-1.4.5-4 has been pushed for fc6, which should resolve this issue.  If these problems are still present in this version, then please make note of it in this bug report.

Comment 3 Fedora Update System 2007-01-12 19:37:17 UTC
m4-1.4.5-4 has been pushed for fc6, which should resolve this issue.  If these problems are still present in this version, then please make note of it in this bug report.


Note You need to log in before you can comment on or make changes to this bug.