The autogen-dev package installs a file /sw/include/options.h which
interferes with the building of a couple of packages that use their own
options.h during building. Several packages have noticed this and have
BuildConflicts (gcc4, g95), one (cm3-dev) has the quaint remark
This package curre
Le 9 avr. 2006 à 09:29, Martin Costabel a écrit :
The autogen-dev package installs a file /sw/include/options.h which
interferes with the building of a couple of packages that use their
own options.h during building. Several packages have noticed this
and have BuildConflicts (gcc4, g95), o
Yesterday I impulse-purchased an imac intel.
Today, in order to avoid parental responsibilities, I am trying to
get fink working.
(I accidently transfered my older /sw from my G4 laptop and a
surprising amount works, but today moved that out of the way and
started anew.)
My first proble
Hi All,
I was looking into the implications of getting the
latest pysqlite2-py sqlite interface into fink and
discovered that if I commit the driver into the tree,
it will break trac for users that already have trac
running (which is not nice). This is because sqlite2
and sqlite3 have incompatibl
William Scott wrote:
Yesterday I impulse-purchased an imac intel.
Today, in order to avoid parental responsibilities, I am trying to get
fink working.
(I accidently transfered my older /sw from my G4 laptop and a surprising
amount works, but today moved that out of the way and started anew.)
Martin Costabel wrote:
William Scott wrote:
Yesterday I impulse-purchased an imac intel.
Today, in order to avoid parental responsibilities, I am trying to
get fink working.
(I accidently transfered my older /sw from my G4 laptop and a
surprising amount works, but today moved that out of th
David Bacher wrote:
On 4/9/06, Martin Costabel <[EMAIL PROTECTED]> wrote:
Does anyone know what this package is used for and whether moving its
options.h from /sw/include/ to /sw/share/autogen/ would be noticed by
anyone at all?
As the listed maintainer, I'm happy to describe what this package
On Sun, 2006-04-09 at 12:07 -0600, Jeff Whitaker wrote:
> Bill:
>
> g95 does work on intel (gfortran doesn't). I've recently modified
> octave, fftw, and scipy-py to use g95. I'll be working on converting
> all packages to use g95.
>
The latest snapshot of gcc-4.2's gfortran should also wor
On 4/9/06, Martin Costabel <[EMAIL PROTECTED]> wrote:
> Does anyone know what this package is used for and whether moving its
> options.h from /sw/include/ to /sw/share/autogen/ would be noticed by
> anyone at all?
As the listed maintainer, I'm happy to describe what this package is
used for. It's
Thanks. But I could not figure out how to get 4.2 with subversion (I can
do it for 4.1).
For laughs, I returned to the stable release, 4.0.3, and found gfortran
4.0.3 compiles on intel. I am trying now to use it to compile ccp4. (I
got mixed results with g95, but it helped with other packa
On Apr 9, 2006, at 4:11 PM, Peter O'Gorman wrote:
On Sun, 2006-04-09 at 12:07 -0600, Jeff Whitaker wrote:
Bill:
g95 does work on intel (gfortran doesn't). I've recently modified
octave, fftw, and scipy-py to use g95. I'll be working on converting
all packages to use g95.
The latest snap
On Apr 9, 2006, at 7:11 PM, William Scott wrote:
Thanks. But I could not figure out how to get 4.2 with subversion
(I can do it for 4.1).
You don't need to use subversion, since they release weekly snapshots
of the code.
For laughs, I returned to the stable release, 4.0.3, and found
As I said in my previous message, I've been told that while prior to March 30
or so, gfortran has compiled on intel, the gfortran that was built produced
incorrect code. That is supposedly fixed in the snapshot.
FWIW, using the gnu March 10, 2006 GCC 4.0.3, gfortran seems to be
working well
13 matches
Mail list logo