Date:	Wed, 20 Jun 2001 20:08:27 +0300 (WET)
From:	Andris Pavenis <pavenis AT lanet DOT lv>
To:	djgpp-workers AT delorie DOT com
Subject:	Re: gcc-3.0
In-Reply-To:	<20010620184307.A8351@lauras.lt>
Message-ID:	<Pine.A41.4.05.10106201957580.105820-100000@ieva06.lanet.lv>
MIME-Version:	1.0
Reply-To:	djgpp-workers AT delorie DOT com
Errors-To:	nobody AT delorie DOT com
X-Mailing-List:	djgpp-workers AT delorie DOT com
X-Unsubscribes-To:	listserv AT delorie DOT com

On Wed, 20 Jun 2001, Laurynas Biveinis wrote:

> 
> > I also met problems building libtool-1.4 which tried to detect whether
> > -fPIC works by simply compiling source but not linking. So maybe we should
> > still reject it for DJGPP as it is not supported by binutils. I can take
> > it off of course if needed
> 
> So it seems that GCC should not reject -fPIC, at least until better
> solution is found.

No problems, I can remove it.

It would be nice if it could be tested more before next build.
Some my results:
	GRX-2.4.2 seems to work Ok when built with gcc-3.0

	Allegro works if I add option -fno-strict-aliasing and remove 
		-fomit-frame-pointer. I didn't study it much more though.

	My own C++ programs works Ok after some hacking I need
		to get them to compile (eg. adding std:: )

	libc.a built with gcc-3.0 doesn't seem to have visible problems

Some more things to test (I don't plan to do that myself):

	how it behaves on Win2K (I don't have one near me)?

	how it works without LFN support?

Andris

- Raw text -