discuss-gnustep
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: gcc 3.1 OK for gnustep?


From: Chris B. Vetter
Subject: Re: gcc 3.1 OK for gnustep?
Date: Mon, 30 Sep 2002 15:01:55 -0700

On Mon, 30 Sep 2002 22:46:22 +0100
Pete French <address@hidden> wrote:
> > The exception is, that with the scenario above, you will have to
> > DISable OpenSSL support in gnustep-base - otherwise Apps/Tools will
> > SIGSEGV when trying to access URLs (http and ftp). I'm not sure
> > whether this is a general problem or is due to OpenSSL being compiled
> > with gcc2.95.3...
> Interesting - I have exactly the versions you describe above, yet I am
> getting a coredump whenever I try and read a .gmodel file. It woorked
> fine until last weekend, and I am still trying to figure out what
> changed.
> Does your version load gmodels correctly and how recent is the source ?

Yes. I'm running 4.6-RELEASE (GENERIC kernel, yes, I know...) and GNUstep
is last Friday afternoon's CVS checkout (around 5pm PDT). To compile
GNUstep on my system, I basically use the 'compile-all' script with a
modification to use CC=gcc30 (3.0.4, instead of 2.95.3) and configure
gnustep-base with --disable-openssl
None of the apps I've tested b0rks, regardless of .gmodel or not,
Except for the occasional (and expected) "urgh, SIGSEGV received" from
Window Maker ;-)

> Also, can you build 'base' which debug=yes, or does it cause a gcc
> compiler error in GSXML ? I see both these symtoms on my current
> system, which is worrying as its been fine under FreeBSD until now.

Yes, I can. You might want to try --disable-openssl, as SSL is considered
part of the OS, and therefor compiled with gcc2.95.3 - or update from
ports with "make OPENSSL_OVERWRITE_BASE=YES" using your newer gcc.

-- 
Chris




reply via email to

[Prev in Thread] Current Thread [Next in Thread]