>Number: 5767 >Category: config >Synopsis: configure fails because of peculiarity in sed >Confidential: no >Severity: non-critical >Priority: medium >Responsible: apache >State: open >Class: sw-bug >Submitter-Id: apache >Arrival-Date: Wed Feb 16 08:10:01 PST 2000 >Closed-Date: >Last-Modified: >Originator: [EMAIL PROTECTED] >Release: 1.3.11 >Organization: apache >Environment: Not relevant >Description: When using a custom layout file (--with-layout=customfile:Custom) that starts immediately with <Layout Custom> in line 1, the sed construction used in configure fails to extract the proper parameters. This is documented as a feature in the sed man page: In the construction "sed -e 1,/.../d" sed starts looking for ... from line 2 onwards. Ofcourse the same holds if you edit the standerd config.layout file. >How-To-Repeat:
>Fix: Any way you like... the problem is rather small. >Release-Note: >Audit-Trail: >Unformatted: [In order for any reply to be added to the PR database, you need] [to include <[EMAIL PROTECTED]> in the Cc line and make sure the] [subject line starts with the report component and number, with ] [or without any 'Re:' prefixes (such as "general/1098:" or ] ["Re: general/1098:"). If the subject doesn't match this ] [pattern, your message will be misfiled and ignored. The ] ["apbugs" address is not added to the Cc line of messages from ] [the database automatically because of the potential for mail ] [loops. If you do not include this Cc, your reply may be ig- ] [nored unless you are responding to an explicit request from a ] [developer. Reply only with text; DO NOT SEND ATTACHMENTS! ]
