From owner-freebsd-ports Fri Feb 11 14:23:32 2000 Delivered-To: freebsd-ports@freebsd.org Received: from mailgw1.be.to (mailgw1.be.to [210.235.212.5]) by builder.freebsd.org (Postfix) with ESMTP id 36A7D3E7C for ; Fri, 11 Feb 2000 14:23:26 -0800 (PST) Received: from mail1.be.to (point1.be.to [210.235.212.29]) by mailgw1.be.to (8.9.3+3.2W/BETO.2.1-2000020313000035) with ESMTP id HAA15207 for ; Sat, 12 Feb 2000 07:23:14 +0900 Received: from acidrain (ppp16-Mobara1.mtci.ne.jp [210.172.1.218]) by mail1.be.to (8.8.8+3.0Wbeta13/BETO.2.0-1999110714000000) with SMTP id HAA30295 for ; Sat, 12 Feb 2000 07:23:12 +0900 Received: (qmail 28965 invoked from network); 11 Feb 2000 22:22:33 -0000 Received: from localhost (HELO acidrain.localnet) (127.0.0.1) by localhost with SMTP; 11 Feb 2000 22:22:33 -0000 Date: Sat, 12 Feb 2000 07:22:31 +0900 Message-ID: <86wvobidlk.wl@dolphin.be.to> From: OKAZAKI Tetsurou To: esk@ira.uka.de Cc: freebsd-ports@FreeBSD.org Subject: Re: Old compiler problems --- how to proceed In-Reply-To: In your message of "Fri, 11 Feb 2000 21:07:53 +0100 (MET)" <14500.27019.328569.979570@i30nb2.ira.uka.de> References: <14500.27019.328569.979570@i30nb2.ira.uka.de> User-Agent: Wanderlust/2.2.17 (One Of Us) EMY/1.13.2 (Better late than never) CLIME/1.13.6 (=?ISO-2022-JP?B?GyRCQ2YlTj4xGyhC?=) APEL/10.0 Emacs/20.5 (i386--freebsd) MULE/4.0 (HANANOEN) Organization: Unknown MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Sender: owner-freebsd-ports@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In the message <14500.27019.328569.979570@i30nb2.ira.uka.de> Espen Skoglund wrote: > I just submitted an update of the XMMS port. However, some user had > problems compiling it on a i386 3.3-STABLE kernel upgraded to > 3.4-STABLE. His /usr/bin/cc was version 2.7.2.3, and if he compiled > with gcc295 everything worked fine. (The problem was that gcc just > got stuck forever trying to compile one of the files.) This is a known problem. Please see PR:gnu/8138 for details. > My question is: what is the best thing to do here? Shall I make build > dependencies on a new gcc version IF the default compiler is an old > one, or should I try to figure out why the heck the compiler hangs on > this specific file? One of workarounds is to put following conditionals: .if !defined(USE_NEWGCC) && ${OSVERSION} < 400012 CFLAGS:= ${CFLAGS:S/-pipe//g} .endif in the Makefile of that port. To fix -STABLE's /usr/bin/cc, let's apply the following patch to /usr/src/contrib/gcc/config/svr4.h and reinstall gcc. --- svr4.h~ Sat Feb 12 07:11:16 2000 +++ svr4.h Sat Feb 12 07:12:44 2000 @@ -108,7 +108,7 @@ messages. */ #undef ASM_FINAL_SPEC -#define ASM_FINAL_SPEC "%{pipe:-}" +#define ASM_FINAL_SPEC "%|" /* Under svr4, the normal location of the `ld' and `as' programs is the /usr/ccs/bin directory. */ I don't test this patch yet but it seems to work. :-) -- Tetsurou To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message