From xemacs-m  Tue Mar 18 16:00:48 1997
Received: from altair.xemacs.org (steve@xemacs.miranova.com [206.190.83.19])
	by xemacs.org (8.8.5/8.8.5) with ESMTP id QAA14921
	for <xemacs-beta@xemacs.org>; Tue, 18 Mar 1997 16:00:46 -0600 (CST)
Received: (from steve@localhost)
	by altair.xemacs.org (8.8.5/8.8.5) id OAA28799;
	Tue, 18 Mar 1997 14:12:35 -0800
Mail-Copies-To: never
To: xemacs-beta@xemacs.org
Subject: Re: [19.15-b99 on sparc-sun-solaris2.5.1] build FAILURE
References: <199703181751.JAA04973@lungo>
X-Url: http://www.miranova.com/%7Esteve/
X-Face: #!T9!#9s-3o8)*uHlX{Ug[xW7E7Wr!*L46-OxqMu\xz23v|R9q}lH?cRS{rCNe^'[`^sr5"
 f8*@r4ipO6Jl!:Ccq<xoV[Qz2u8<8-+Vwf2gzJ44lf_/y9OaQ`@#Q65{U4/TC)i2`~/M&QI$X>p:9I
 OSS'2{-)-4wBnVeg0S\O4Al@)uC[pD|+
X-Attribution: sb
From: Steven L Baur <steve@miranova.com>
In-Reply-To: Vladimir Ivanovic's message of Tue, 18 Mar 1997 09:51:35 -0800
Mime-Version: 1.0 (generated by tm-edit 7.105)
Content-Type: multipart/mixed;
 boundary="Multipart_Tue_Mar_18_14:12:25_1997-1"
Content-Transfer-Encoding: 7bit
Date: 18 Mar 1997 14:12:26 -0800
Message-ID: <m27mj497ed.fsf@altair.xemacs.org>
Lines: 48
X-Mailer: Gnus v5.4.29/XEmacs 20.1(beta9)

--Multipart_Tue_Mar_18_14:12:25_1997-1
Content-Type: text/plain; charset=US-ASCII

Vladimir Ivanovic writes:

> I cannot build with --compiler=cc --cflags="-g -fast".  (SPARCompiler
> 3.0.1 13 Jul 1994) The initial frame comes up, the modeline is drawn,
> and then nothing.  Here is what `pstack' reports: 

There are known problems with -fast on your system.


--Multipart_Tue_Mar_18_14:12:25_1997-1
Content-Type: text/plain; charset=US-ASCII

From: Martin Buchholz <mrb@eng.sun.com>
Subject: Re: message-make-message-id problems, anybody?
Date: Wed, 26 Feb 1997 17:37:57 -0800

>>>>> "Mark" == Mark Borges <mdb@cdc.noaa.gov> writes:

Mark> If this is a SUNWspro compiler (which is consistent with the -xO5
Mark> flag; sorry I missed the earlier part of the thread), then `-fast'
Mark> must be used with caution. It is a convenience switch, which turns on
Mark> other options, one of which is `-dalign'. If the other libraries
Mark> you're linking against were not compiled with this (-dalign) flag, the
Mark> results are unpredictable.

Mark> I ran into this when compiling some code that links in the Numerical
Mark> Algorithm Group (NAg) mathematical libraries. The NAg libs were
Mark> compiled with `-dalign' but the default compile flag does not include
Mark> it, and I was seeing random bus errors.

Mark> Martin?

I've never seen this, but I personally avoid -fast and -xO5.  -xO5
*did* work for me some time in the past.

...

--Multipart_Tue_Mar_18_14:12:25_1997-1
Content-Type: text/plain; charset=US-ASCII

-- 
steve@miranova.com baur
Unsolicited commercial e-mail will be billed at $250/message.

--Multipart_Tue_Mar_18_14:12:25_1997-1--

