From owner-freebsd-hackers  Mon Apr 17  8:57:56 2000
Delivered-To: freebsd-hackers@freebsd.org
Received: from jestocost.cosc.morrisville.edu (jestocoast.cosc.morrisville.edu [136.204.176.67])
	by hub.freebsd.org (Postfix) with ESMTP id AF07D37B76C
	for <freebsd-hackers@FreeBSD.ORG>; Mon, 17 Apr 2000 08:57:48 -0700 (PDT)
	(envelope-from root@jestocost.cosc.morrisville.edu)
Received: (from root@localhost)
	by jestocost.cosc.morrisville.edu (8.9.3/8.9.3) id LAA06515;
	Mon, 17 Apr 2000 11:53:57 -0400 (EDT)
	(envelope-from root)
Date: Mon, 17 Apr 2000 11:53:57 -0400 (EDT)
From: Charlie Root <root@jestocost.cosc.morrisville.edu>
Message-Id: <200004171553.LAA06515@jestocost.cosc.morrisville.edu>
To: cracauer@cons.org, imp@village.org
Subject: Re: problems with "-O -pipe" in guile port
Cc: admin@csclab1.cosc.morrisville.edu, freebsd-hackers@FreeBSD.ORG
In-Reply-To: <200004171511.JAA29490@billy-club.village.org>
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

>From imp@billy-club.village.org Mon Apr 17 11:07:13 2000
>To: Martin Cracauer <cracauer@cons.org>
>Subject: Re: problems with "-O -pipe" in guile port 
>Cc: James Halstead <admin@csclab1.cosc.morrisville.edu>,
>        freebsd-hackers@FreeBSD.ORG
>In-reply-to: Your message of "Mon, 17 Apr 2000 14:24:36 +0200."
>		<20000417142436.C6672@cons.org> 
>References: <20000417142436.C6672@cons.org>  <00041017453700.36307@jestocost.cosc.morrisville.edu> 
>Date: Mon, 17 Apr 2000 09:11:52 -0600
>From: Warner Losh <imp@village.org>
>
>In message <20000417142436.C6672@cons.org> Martin Cracauer writes:
>: In <00041017453700.36307@jestocost.cosc.morrisville.edu>, James Halstead wrote: 
>: > /bin/sh ../libtool --mode=compile cc -DHAVE_CONFIG_H -I. -I. -I../libguile     -O -pipe -Wall -Wpointer-arith -Wmissing-prototypes  -c qtmds.s
>: > rm -f .libs/qtmds.lo
>: > cc -DHAVE_CONFIG_H -I. -I. -I../libguile -O -pipe -Wall -Wpointer-arith -Wmissing-prototypes -c qtmds.s  -fPIC -DPIC -o .libs/qtmds.lo
>: > 
>: > *** dies here ***
>: 
>: No error messages?
>
>If it is like the hangs that I've seen with g++, no.  There are not
>error messages.  It just hangs and eats all CPU.  I've not had a
>chance to track this down.
>
>Warner
>
I can't remember exactly but i think that the compiler was in the wait state and not taking any process time. I could be wrong. could check if sombody wants me too.

I don't know if martin knows but the workaround is to remove te -O.
If you did then ignore that last line ;)

James


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message