Return-Path: Delivered-To: apache-bugdb-archive@hyperreal.org Received: (qmail 24600 invoked by uid 6000); 23 Oct 1997 08:40:05 -0000 Received: (qmail 23859 invoked by uid 2001); 23 Oct 1997 08:40:01 -0000 Received: (qmail 9928 invoked by uid 2012); 23 Oct 1997 08:36:44 -0000 Message-Id: <19971023083644.9927.qmail@hyperreal.org> Date: 23 Oct 1997 08:36:44 -0000 From: Andrey Chernov Reply-To: ache@nagual.pp.ru To: apbugs@hyperreal.org X-Send-Pr-Version: 3.2 Subject: os-freebsd/1311: FreeBSD have better fnmatch.c but Apache still use its own broken version Sender: apache-bugdb-owner@apache.org Precedence: bulk >Number: 1311 >Category: os-freebsd >Synopsis: FreeBSD have better fnmatch.c but Apache still use its own broken version >Confidential: no >Severity: non-critical >Priority: medium >Responsible: apache >State: open >Class: sw-bug >Submitter-Id: apache >Arrival-Date: Thu Oct 23 01:40:01 PDT 1997 >Last-Modified: >Originator: ache@nagual.pp.ru >Organization: apache >Release: 1.3b2 >Environment: FreeBSD >Description: The first disadvantage of Apache's fnmatch.c is that it have several bugs already fixed in FreeBSD fnmatch.c version, just compare latest FreeBSD fnmatch.c code with Apache variant and you'll see. Even if Apache moves to FreeBSD fnmatch.c variant, it will not be nice since internal function occupes code space while standard version taken from shared library once and not occupes memory. >How-To-Repeat: >Fix: Add an option to compile with default system fnmatch.c for people who knows what they do >Audit-Trail: >Unformatted: