Bug 62526 – Bash doesn't work with make

Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.

Bug 62526 - Bash doesn't work with make

Summary:	Bash doesn't work with make

Status:	CLOSED RAWHIDE

Aliases:	None

Product:	Red Hat Linux
Classification:	Retired
Component:	bash (Show other bugs)
Sub Component:
Version:	7.2
Hardware:	i386 Linux

Priority	medium Severity medium
Target Milestone:	---
Target Release:	---
Assigned To:	wdovlrrw
QA Contact:	Ben Levenson
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2002-04-01 22:47 EST by hjl
Modified:	2007-04-18 12:41 EDT (History)
CC List:	0 users

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2002-04-01 22:48:43 EST
Type:	---
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
A Makefile to show the bash bug (113 bytes, text/plain) 2002-04-01 22:48 EST, hjl	no flags	Details
Add an attachment (proposed patch, testcase, etc.)

Groups: None (edit)

Description hjl 2002-04-01 22:47:57 EST

# make
if [ -n "" ]; then \
  for r in ; do \
    echo $r; \
  done; \
fi
/tmp/bash: -c: line 1: syntax error near unexpected token `;'
/tmp/bash: -c: line 1: `if [ -n "" ]; then  for r in ; do  echo $r;  done;  fi'
make: *** [all] Error 2

Bash in RedHat 7.1 and the current public beta are ok.

Comment 1 hjl 2002-04-01 22:48:38 EST

Created attachment 51744 [details]
A Makefile to show the bash bug

Comment 2 Bernhard Rosenkraenzer 2002-04-02 05:42:05 EST

This is because  
  
for i in ; do something; done  
        ^nothing  
  
isn't part of older standards. 
Support for this construct has been added in 2.05.

Comment 3 hjl 2002-04-02 11:49:00 EST

It is a regression from RedHat 7.1. The build stops working
after upgrading to RedHat 7.2.

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