Bug 57943 - automake has bug WRT lisp makefiles
Summary: automake has bug WRT lisp makefiles
Status: CLOSED RAWHIDE
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: automake   
(Show other bugs)
Version: 7.2
Hardware: noarch Linux
medium
medium
Target Milestone: ---
Assignee: Jens Petersen
QA Contact: Brian Brock
URL:
Whiteboard:
Keywords:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2002-01-02 22:10 UTC by Chris Adams
Modified: 2007-04-18 16:38 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2002-01-07 06:34:24 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)
Patch to fix lisp.am bug (633 bytes, patch)
2002-01-02 22:10 UTC, Chris Adams
no flags Details | Diff

Description Chris Adams 2002-01-02 22:10:19 UTC
automake will generate a bogus Makefile.in when using lisp (the gettext
package is one example).  It puts an @ in the Makefile.in so make won't
quit on an error, but it puts it in the middle of a shell expression (so
the shell barfs on an extraneous @).  It looks like someone created lisp.am
by copying another .am file and didn't take this out.

The patch is easy (and will be attached).

Comment 1 Chris Adams 2002-01-02 22:10:49 UTC
Created attachment 41653 [details]
Patch to fix lisp.am bug

Comment 2 Tom Tromey 2002-01-07 00:20:57 UTC
FYI: this bug is fixed in the CVS automake.
We hope to do a bug-fix release soon.
This release will be in the 1.5 series.
The 1.4 series has ended.
(If Red Hat is sticking with 1.4 for a while, we can
work something out; this bug is also fixed on the 1.4 branch,
but the 1.4 branch can't be released as-is.)



Comment 3 Jens Petersen 2002-01-07 06:56:55 UTC
Thanks.  This already seems fixed in automake-1.5, ie automake-1.5-1.  (It was
also fixed in automake-1.4p5-3.)


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