Bug 53526 – aclocal error handling fix

Bug 53526 - aclocal error handling fix

Summary:	aclocal error handling fix

Status:	CLOSED RAWHIDE

Aliases:	None

Product:	Red Hat Public Beta
Classification:	Retired
Component:	automake (Show other bugs)
Sub Component:
Version:	roswell
Hardware:	i386 Linux

Priority	medium Severity medium
Target Milestone:	---
Target Release:	---
Assigned To:	Florian La Roche
QA Contact:	Brian Brock
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2001-09-10 17:56 EDT by Havoc Pennington
Modified:	2007-04-18 12:37 EDT (History)
CC List:	0 users

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2001-11-28 12:53:13 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)
don't consider duplicate macros a fatal error (536 bytes, patch) 2001-09-10 17:58 EDT, Havoc Pennington	no flags	Details \| Diff
Add an attachment (proposed patch, testcase, etc.)

Groups: None (edit)

Description Havoc Pennington 2001-09-10 17:56:57 EDT

aclocal keeps any package that installs .m4 macros from working properly 
if I put build it in two separate prefixes, one of which is the 
standard aclocal build location.

This is because even if I pass "-I /prefix/share/aclocal" when using 
aclocal in "/prefix", aclocal has a fatal error if it finds duplicate
macros. There is no reason this error should be fatal.

Will attach Owen's patch for this.

Comment 1 Havoc Pennington 2001-09-10 17:58:58 EDT

Created attachment 31539 [details]
don't consider duplicate macros a fatal error

Comment 2 Tom Tromey 2001-11-28 12:53:07 EST

FYI: the aclocal that comes with automake 1.5 no longer
generates this error.  There were too many complaints and
problems associated with it, so we took it out.

Comment 3 Havoc Pennington 2001-11-28 13:39:33 EST

Perfect, 1.5 is in rawhide so I guess the bug is closed.

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