Hi Jeff et al:
Many thanks again for your help with this. Although this version did in fact get rid of my segmentation fault, it didn't solve my other problem, which means the other problem was not specific to compiler version, so at least I have learned something.
Given this, and what Remi Mo
Hi Jeff,
I tried your new g77 3.3.2 on 10.3 with cernlib. cernlib builds fine,
but the test fails as it was the case with 3.3(.1) (see our email
exchange from Jul 17, 2003). With the g77 3.4-20031015 it works
flawlessly.
Thanks for your effort.
Remi
On Friday, November 7, 2003, at 04:43 AM,
William and Martin: I've verified that the latest released g77 (3.3.2)
does not have the assembler bug present in 3.1,3.3.1 and Apple's
3.3-20030304. As Martin pointed out, the reason I put the 3.4 package in,
even though it is not a released version of g77, is that it was the only
version that d
William Scott wrote:
[]
Is there any way to have version 3.1 and 3.3 cohabitating in 10.3?
I don't think there is a reasonable way to have two *installed* versions
of g77 cohabitate. For two *package descriptions* cohabitating, the
right way would be to create a g77-3.1 package, i.e. instead of
I've been having a series of problems with g77-3.4 (both the binary and
what I build). Apart from the surmountable problems that this upgrade
created, I am also having problems with the compiler segmentation
faulting on compiling a program within CCP4 (fink unstable) and another
crystallograph
