Re: gcc problem/openoffice failure

2003-05-28 Thread Marco Molteni
Julian Elischer wrote [2003-05-27]: > > For the last month (more actually)(and after completely rebuilding my > system and all the ports on it) I have not been able to compile > the openoffice port due to gcc failures. > (I have posted the message earlier several times) > Has anyone been able to

Re: gcc problem/openoffice failure

2003-05-28 Thread Peter Jeremy
On Tue, May 27, 2003 at 04:55:47PM -0700, Julian Elischer wrote: >Has anyone been able to compile the openoffice port recently? It built successfully for me on 25th April in -STABLE. Are you using any non-default flags or options? Last time I tried to build it with debugging enabled (beginning o

Re: gcc bug? Openoffice port impossibel to compile on 4.8

2003-05-28 Thread Dag-Erling Smorgrav
Wes Peters <[EMAIL PROTECTED]> writes: > GCC 3.2 is broken by design. It insists, amongst other stupidities, on > type-checking arguments using old style declarations like: > > int foo(bar) > char *bar; > {} > > rendering most UNIX software from before 1996 uncompilable. have y

Re: gcc bug? Openoffice port impossibel to compile on 4.8

2003-05-28 Thread Dimitry Andric
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 2003-05-28 at 14:12:34 Dag-Erling Smorgrav wrote: > have you tried -traditional? gcc 3.1 release notes: The -traditional C compiler option has been deprecated and will be removed in GCC 3.3. (It remains possible to preprocess non-C code with