*BSD News Article 94874


Return to BSD News archive

Path: euryale.cc.adfa.oz.au!newshost.carno.net.au!harbinger.cc.monash.edu.au!munnari.OZ.AU!news.ecn.uoknor.edu!feed1.news.erols.com!howland.erols.net!news.sgi.com!csulb.edu!data.ramona.vix.com!nnrp1.crl.com!not-for-mail
From: "Jordan K. Hubbard" <jkh@FreeBSD.org>
Newsgroups: comp.unix.bsd.freebsd.misc
Subject: Re: gnumalloc question (where is it?:)
Date: Thu, 01 May 1997 02:46:18 -0700
Organization: Walnut Creek CDROM
Lines: 21
Message-ID: <3368666A.13728473@FreeBSD.org>
References: <3367893D.41C67EA6@artorius.sunflower.com>
NNTP-Posting-Host: time.cdrom.com
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Mailer: Mozilla 3.01 (X11; I; FreeBSD 2.2-STABLE i386)
Xref: euryale.cc.adfa.oz.au comp.unix.bsd.freebsd.misc:40099


Stephen D. Spencer wrote:
> Note: I am using FreeBSD 2.2.1-R
> 
> I seem to have a problem when trying to compile any source code that is
> prepared to be compiled with gnu development tools.  My current

No, it's actually:

> is the experimentation with X11R6.3; though, this problem has occured
> with other source bundles.

This guy's environment.  Change the FreeBSD.cf file for X11R6.3 so that
it *does not* try to link with -lgnumalloc.

And get rid of -fno-strength-reduce while you're at it.

I think you have a greatly outdated FreeBSD.cf which misidentifies your
release number, actually.  These look like the gcc 2.6.3 options! :)
-- 
- Jordan Hubbard
  FreeBSD core team / Walnut Creek CDROM.