From owner-freebsd-ports Sat Jun 2 6:26:19 2001 Delivered-To: freebsd-ports@freebsd.org Received: from ringworld.nanolink.com (ringworld.nanolink.com [195.24.48.13]) by hub.freebsd.org (Postfix) with SMTP id 52E2037B424 for ; Sat, 2 Jun 2001 06:26:16 -0700 (PDT) (envelope-from roam@orbitel.bg) Received: (qmail 31301 invoked by uid 1000); 2 Jun 2001 13:25:11 -0000 Date: Sat, 2 Jun 2001 16:25:11 +0300 From: Peter Pentchev To: sobomax@FreeBSD.org Cc: durian@man.boogie.com, freebsd-ports@FreeBSD.org Subject: Re: ports/26807: The mozilla 0.8.1 ports build fails under -current Message-ID: <20010602162511.E28335@ringworld.oblivion.bg> Mail-Followup-To: sobomax@FreeBSD.org, durian@man.boogie.com, freebsd-ports@FreeBSD.org References: <200105291416.f4TEGBJ54377@freefall.freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200105291416.f4TEGBJ54377@freefall.freebsd.org>; from sobomax@FreeBSD.org on Tue, May 29, 2001 at 07:16:11AM -0700 Sender: owner-freebsd-ports@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Tue, May 29, 2001 at 07:16:11AM -0700, sobomax@FreeBSD.org wrote: > Synopsis: The mozilla 0.8.1 ports build fails under -current > > State-Changed-From-To: analyzed->closed > State-Changed-By: sobomax > State-Changed-When: Tue May 29 07:12:43 PDT 2001 > State-Changed-Why: > This is known problem with libIDL. When building mozilla please make sure > that you don't have any custom malloc(3) flags set, otherwise you may > have a problems like that. The following should do the trick: > > # rm -f /etc/malloc.conf > # unset MALLOC_OPTIONS > # cd /usr/ports/www/mozilla && make Doesn't the MALLOC_OPTIONS environment variable override /etc/malloc.conf settings? My tests just now indicate that it does. In that case, wouldn't something like: MAKE_ENV+= MALLOC_OPTIONS="abcdefghijklmnopqrstuvwxyz" fix any problems not related to '<' or '>' in /etc/malloc.conf? (and I really doubt that '<' or '>' could make a program fail as opposed to just negatively impact performance..) Yes, I know it's ugly; however, if a port build is really affected by malloc(3) options, IMHO they should be set to a known good value. G'luck, Peter -- No language can express every thought unambiguously, least of all this one. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message