Date: Wed, 15 Mar 2000 21:30:03 -0800 (PST) From: John Polstra <jdp@polstra.com> To: freebsd-ports@FreeBSD.org Subject: Re: ports/17344: devel/boehm-gc fails for www/w3m 3.4 STABLE Message-ID: <200003160530.VAA49098@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
The following reply was made to PR ports/17344; it has been noted by GNATS. From: John Polstra <jdp@polstra.com> To: (Dirk Meyer) <dirk.meyer@dinoex.sub.org> Cc: FreeBSD-gnats-submit@freebsd.org Subject: Re: ports/17344: devel/boehm-gc fails for www/w3m 3.4 STABLE Date: Wed, 15 Mar 2000 21:24:22 -0800 (PST) Dirk Meyer wrote: > >> Could you please test this again with an up-to-date version of the >> boehm-gc port and let me know what happens? I committed a change on >> 11 March 2000 which might possibly fix the problem. > > As far as I can check it, > my test included your latest patch. You are right -- my mistake. I read the date 12.03.2000 in the P/R and my feeble American brain thought it saw December 3. In that case I wonder if my recent update broke the program. Would you mind backing out my change and testing it? To do that, replace "ports/devel/boehm-gc/patches/patch-aa" with revision 1.4 of that file. In case you don't have a CVS repository, you can get revision 1.4 from the web site at: http://www.freebsd.org/cgi/cvsweb.cgi/ports/devel/boehm-gc/patches/patch-aa?rev=1.4 Or, just edit your current patch-aa file and remove the string "-DREDIRECT_MALLOC=GC_malloc" from it. That's the only change I made. To give you a little background: The boehm-gc port originally was configured to replace malloc(), realloc(), calloc(), and free() directly with garbage-collected versions, so that all memory allocation calls would use the GC. When the port was updated for a newer version of boehm-gc last year, the configuration was accidentally changed so that these functions were not overridden directly. My patch a few days ago restored the original behavior. But it is possible that the w3m port relied on the accidental behavior from late last year. If that is the case then my update probably caused the breakage. Regards, John To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200003160530.VAA49098>