Re: gcc bug? Openoffice port impossibel to compile on 4.8
-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 the traditional preprocessor.) gcc 3.3 release notes: The -traditional C compiler option has been removed. It was deprecated in 3.1 and 3.2. (Traditional preprocessing remains available.) So, I'd guess in gcc 3.x, this whole option is completely unmaintained and therefore you'd be quite on your own if you try to compile anything seriously with -traditional... :( 2.95.x is probably not going to go away for a long time. :) -BEGIN PGP SIGNATURE- Version: 6.5.8ckt iQA/AwUBPtSsxbBeowouIJajEQLSLgCaAzFTNq08M0cFkBXBHfOWMW9EVnoAoJYH Y1nnQdgORVP5+olXw+VekOYm =CJj2 -END PGP SIGNATURE- ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: gcc bug? Openoffice port impossibel to compile on 4.8
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 you tried -traditional?
DES
--
Dag-Erling Smorgrav - [EMAIL PROTECTED]
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: gcc problem/openoffice failure
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 of February), it failed (reproducably) inside Mozilla but no-one seemed interested. (The OO maintainer claimed it was a Mozilla problem but that side-stepped the fact that the OO port explicitly over-rides the "no debugging" flags in Mozilla). I know that I previously compiled OO with debugging but it seems that one of the OO or Mozilla upgrades broke it. Peter ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: gcc problem/openoffice failure
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 compile the openoffice port recently? [..] I assume you tried to compile the elephant because you weren't aware that there exist a fbsd package for it. I did the same thing until I got tired ;-) http://projects.imp.ch/openoffice/ has packages for -stable and -current. On my -stable I run openoffice-1.0.3_2. On my -current, after trying to run openoffice-1.1Beta1 and being bitten by all sort of bugs, I just installed the compat libraries for -stable and then the same openoffice-1.0.3_2 for -stable. Runs like a charm :-) marco ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
