Alexander K. Hansen wrote:
[]
A thread concerning this behavior has been posted at
http://lists.apple.com/archives/Xcode-users/2005/Nov/msg00267.html
Addendum: I tried this package on a box with XCode 2.1 (gcc 4.0.0)
and it built--it definitely looks to be "compiler intolerance".
This stin
Peter O'Gorman <[EMAIL PROTECTED]> said:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Daniel E. Macks wrote:
>| When the g77 package is updated next, please add:
>| InfoDocs: g77.info
>| to it so that the texinfo documentation index is updated properly.
>
> I'm not sure that there need b
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Daniel E. Macks wrote:
| When the g77 package is updated next, please add:
| InfoDocs: g77.info
| to it so that the texinfo documentation index is updated properly.
I'm not sure that there need be a new revision all that soon. My worries
about inte
When the g77 package is updated next, please add:
InfoDocs: g77.info
to it so that the texinfo documentation index is updated properly.
dan
--
Daniel Macks
[EMAIL PROTECTED]
http://www.netspace.org/~dmacks
---
This SF.Net email is sponsor
On 11/17/05, Martin Costabel <[EMAIL PROTECTED]> wrote:
> Alexander K. Hansen wrote:
> []
> > It does indeed look to be that the newer gcc version isn't tolerant of
> > these irregularities, since with XCode 2.1 the package builds.
>
> I changed the jpilot.patch file in CVS correspondingly. Does th
Alexander K. Hansen wrote:
[]
It does indeed look to be that the newer gcc version isn't tolerant of
these irregularities, since with XCode 2.1 the package builds.
I changed the jpilot.patch file in CVS correspondingly. Does this work?
--
Martin
On 11/17/05, Alexander K. Hansen <[EMAIL PROTECTED]> wrote:
> I get the following when I try to build scipy-py24 on Tiger using
> XCode 2.2 (i.e. gcc 4.0.1):
>
> building 'scipy.interpolate.dfitpack' extension
> compiling C sources
> gcc options: '-fno-strict-aliasing -Wno-long-double -no-cpp-preco
On 11/16/05, Martin Costabel <[EMAIL PROTECTED]> wrote:
> Alexander K. Hansen wrote:
> []
> > | #include
> > | int
> > | main ()
> > | {
> > |
> > | int main()
> > | {
>
> It is rather surprising that earlier gcc versions accepted such
> ridiculous code. I think this nested main() comes from a bro
I get the following when I try to build scipy-py24 on Tiger using
XCode 2.2 (i.e. gcc 4.0.1):
building 'scipy.interpolate.dfitpack' extension
compiling C sources
gcc options: '-fno-strict-aliasing -Wno-long-double -no-cpp-precomp
-mno-fused-madd -DNDEBUG -g -O3 -Wall -Wstrict-prototypes -I/sw/
inc
Jeffrey,
FYI, I have finished a revised fftw3.info script which allows
-mpi versions of fftw3 to be built as we currently do for fftw. I
will need the mpi support in fftw3 when I upgrade the gromacs-mpi
package to version 3.3 which was just released. Currently I am
stuck on some new shared lib
10 matches
Mail list logo
