Ethereal-dev: Re: [Ethereal-dev] problems building on mac os x

Note: This archive is from the project's previous web site, ethereal.com. This list is no longer active.

Date Index Thread Index Other Months All Mailing Lists
Date Prev Date Next Thread Prev Thread Next
From: Guy Harris <guy@xxxxxxxxxx>
Date: Fri, 7 Dec 2001 15:08:52 -0800 (PST)
> The "Apple's GCC is buggy" hypothesis appears correct:
> 
> http://www.stacken.kth.se/lists/arla-drinkers/2001-04/msg00001.html

Well, *maybe* there are multiple programs that are committing some sin
against the C standard that causes them not to work with Apple's
precompiled headers.  Anybody know why those precompiled headers cause
so much trouble?

> This site recommends -no-cpp-precomp, and goes into more
> detail about apple's gcc:
> 
> http://fink.sourceforge.net/doc/porting/basics.php

I've checked in changes to use "-no-cpp-precomp" rather than
"-traditional-cpp", and to do so on Darwin regardless of whether the
compiler is called "gcc" or not, as per that page.

Currently, "config.guess" is in CVS, but "config.sub" isn't; is there
any reason why?  We should perhaps either

	1) remove "config.guess" from CVS, and have the source tarballs
	   built on a machine with a shiny new autoconf installed (new
	   enough to know about Darwin/MacOS X) *if* the shiny new
	   autoconf isn't incompatible with our current autoconf stuff
	   or we can make it compatible

or

	2) put "config.sub" into CVS and check in shiny new versions of
	   both files.