From owner-freebsd-ports Mon Jul 15 9:58:44 2002 Delivered-To: freebsd-ports@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 87C0537B400 for ; Mon, 15 Jul 2002 09:58:41 -0700 (PDT) Received: from mallard.duc.auburn.edu (mallard2.duc.auburn.edu [131.204.2.23]) by mx1.FreeBSD.org (Postfix) with ESMTP id CB8D043E42 for ; Mon, 15 Jul 2002 09:58:40 -0700 (PDT) (envelope-from kokostm@auburn.edu) Received: from localhost (kokostm@localhost) by mallard.duc.auburn.edu (8.9.3/8.9.3) with SMTP id LAA13585 for ; Mon, 15 Jul 2002 11:58:39 -0500 (CDT) X-Authentication-Warning: mallard.duc.auburn.edu: kokostm owned process doing -bs Date: Mon, 15 Jul 2002 11:58:39 -0500 (CDT) From: Todd M Kokoszka X-Sender: kokostm@mallard To: freebsd-ports@freebsd.org Subject: problems compiling doxygen_1.2.16_1 Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII 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 Hi, I'm using FreeBSD 4.5 and gcc 3.1.0 on a i386. from the Makefile: $FreeBSD: ports/devel/doxygen/Makefile,v 1.22 2002/06/23 20:10:44 alane Exp $ c++ (gcc) takes a very long time compiling config.o and never seems to complete - the command : gmake[2]: Entering directory `/usr/ports/devel/doxygen/work/doxygen-1.2.16/src' c++ -c -O -pipe -D_THREAD_SAFE -Wall -W -I../qtools -o ../objects/config.o config.cpp By a very long time -- about 50 minutes before I stopped it. config.o was always 0 bytes. I had installed gcc-3.0.4 and it actually compiled that file in about 1 minute, but I had some compiler config problems and I ended up installing a more recent version, 3.1.0 and it doesn't work with that. It also didn't work and experienced exactly the same problem with gcc 2.95.3. Is this a problem with my configuration or a bug? Thanks, Todd To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message