On 11/01/2008, at 10:43 PM, G.W. Haywood wrote:
> Hi there,
>
> On Fri, 11 Jan 2008 James Brown wrote:
>
>> On Intel machine, changing compiler to gcc 3.3 did not work (it does
>> on my PowerPC machine). Switched back to 4.0 and ran:
>>
>> ./configure --enable-experimental CFLAGS="-O0"
>>
>> It
Hi there,
On Fri, 11 Jan 2008 James Brown wrote:
> On Intel machine, changing compiler to gcc 3.3 did not work (it does
> on my PowerPC machine). Switched back to 4.0 and ran:
>
> ./configure --enable-experimental CFLAGS="-O0"
>
> It compiled perfectly.
>
> So thanks Frank and Trk Edwin.
FWIW I
On 19/12/2007, at 11:29 AM, fchan wrote:
> Hi,
> I just configure with CFLAGS="-O0" and did make and make install
> and it worked on my Mac running 10.4.11!
> However we in the Apple user community are at the mercy of Apple as
> to when Apple will update gcc to 4.1.1 or later. I had pre-relea
Hi,
I just configure with CFLAGS="-O0" and did make
and make install and it worked on my Mac running
10.4.11!
However we in the Apple user community are at the
mercy of Apple as to when Apple will update gcc
to 4.1.1 or later. I had pre-release version of
gcc-4.2.1 from Apple which didn't wor
On Tue, Dec 18, 2007 at 03:38:12PM +0100, Oliver Schwarz said:
> is it safe to build it with CFLAGS="-O0" and to let it run on
> production servers?
> i have to mention, that i'm no expert in using compiler options.
-O0 is safe, but as mentioned elsewhere, I'd just upgrade your compiler.
--
--
well, this is the supported ompiler from apple for this version of
the system.
now that apple ships 10.5 as the latest system version, doubts about
any fix to this issue can be raised.
they changed a lot in this area for the newer system, so prolly there
wouldn't be this problem; but i'm not
Oliver Schwarz wrote:
hey all,
just to chime in with GCC 4.0.1 compiler problems on Mac OS X 10.4.10
Server.
it breaks with the same errors mentioned:
checking for a supported version of gcc... ok (4.0.1)
checking for gcc bug PR27603... ok, bug not present
checking for gcc bug PR28045... con
hey all,
just to chime in with GCC 4.0.1 compiler problems on Mac OS X 10.4.10
Server.
it breaks with the same errors mentioned:
checking for a supported version of gcc... ok (4.0.1)
checking for gcc bug PR27603... ok, bug not present
checking for gcc bug PR28045... configure: error: your compi
Leonardo Rodrigues Magalhães wrote:
> Compiling clamav-0.92 with an old gcc (gcc 3.2 in my Fedora 4 and
> Fedora 5 machines) will make clamav behave strangely, slow ... disable
> features ... or something like that ? Is it 'very bad' to compile
> clamav-0.92 with gcc 3.2 ??
>
> Please no
Török Edwin escreveu:
> You don't need to upgrade to 4.1.2/4.2.x.
> gcc-3.4 can be nicely installed side-by-side with a 4.0.x/4.1.0 series
> gcc, all you need to do is:
>
> # apt-get install gcc-3.4
> $ export CC=gcc-3.4
> $ ./configure
>
Compiling clamav-0.92 with an old gcc (gcc 3.2 in m
Per Jessen wrote:
> All our systems are frozen - no changes until mid-Jan. clamav is one of
> very few exceptions.
>
Try:
$ CFLAGS="-O0" ./configure
If that works you can try:
$ CFLAGS="-O1" ./configure
--Edwin
___
Help us build a comprehensive Cla
Török Edwin wrote:
> You don't need to upgrade to 4.1.2/4.2.x.
> gcc-3.4 can be nicely installed side-by-side with a 4.0.x/4.1.0 series
> gcc, all you need to do is:
>
> # apt-get install gcc-3.4
> $ export CC=gcc-3.4
> $ ./configure
All our systems are frozen - no changes until mid-Jan. clamav
Please resist the urge to top-post.
On Mon, 2007-12-17 at 15:52 -0800, fchan wrote:
> Hello,
> I'm on a MacBookPro running 10.4.11 with xcode
> 2.5 and I tried your suggestion "export
> CC=gcc-3.4" and I got this error:
The advice was rather specific to Debian. And actually started by
installin
Hello,
I'm on a MacBookPro running 10.4.11 with xcode
2.5 and I tried your suggestion "export
CC=gcc-3.4" and I got this error:
checking for gcc... gcc-3.4
checking for C compiler default output file name...
configure: error: C compiler cannot create executables
See `config.log' for more detai
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Per Jessen wrote:
> I guess there was no other way than to make clamav dependent on
> gcc, but it sure is bad timing. Only a week before Christmas, most
> systems are frozen, people have already left for vacation etc.
> Updating clamav is within reaso
Per Jessen wrote:
> I guess there was no other way than to make clamav dependent on gcc, but
> it sure is bad timing.
> Only a week before Christmas, most systems are frozen, people have
> already left for vacation etc. Updating clamav is within reason for
> us, but upgrading gcc too ...
>
Y
I guess there was no other way than to make clamav dependent on gcc, but
it sure is bad timing.
Only a week before Christmas, most systems are frozen, people have
already left for vacation etc. Updating clamav is within reason for
us, but upgrading gcc too ...
Was/is there absolutely no way of
17 matches
Mail list logo
