From: Mark Linimon [EMAIL PROTECTED]
Subject: Re: octave-forge on FreeBSD 7.0
Date: Wed, 21 Nov 2007 07:59:56 -0600
I'd rather see USE_GCC set unconditionally, so that INDEX will
be the same on 6 and 7.
Me too.
Is there any hope of the software being updated? My concern is
that once we set
IMHO, octave-forge should be merged into octave itself,
and relese version of octave and corrsponding octave-forge is old.
I think this is a temporal situation. Once octave will be updated
octave-forge will also be updated, and I believe octave-forge
will be built with gcc42.
OK, in that
On Sunday 18 November 2007, Maho NAKATA wrote:
How about doing something more simple like:
.if ${OSVERSION} = 700042
USE_GCC=3.4
.endif
which works great in my situation.
I'd rather see USE_GCC set unconditionally, so that INDEX will
be the same on 6 and 7.
Is there any hope of
On Mon, Nov 19, 2007 at 01:24:30PM +0900, Maho NAKATA wrote:
Dear portmgr@ and Stephen
Portmgr@:
Stephen Montgomery-Smith [EMAIL PROTECTED]
reported that applying following patch will unbreak
for FBSD7. Could you please approve my commit?
Index: Makefile
Dear Maho,
I noticed that you added lines like:
.if ${OSVERSION} = 700042
.if ${ARCH} == amd64 || ${ARCH} == sparc64
BROKEN= Does not compile with GCC 4.2
.endif
.endif
to the Makefile of math/octave-forge. But it also doesn't build on my
i386 FreeBSD 7.0 machine.
How about doing
=Does not compile with GCC 4.2
-.endif
+USE_GCC= 3.4
.endif
GNU_HOST= ${ARCH}-portbld-freebsd${OSREL}
cvs diff: Diffing files
From: Stephen Montgomery-Smith [EMAIL PROTECTED]
Subject: octave-forge on FreeBSD 7.0
Date: Sun, 18 Nov 2007 21:45:15 -0600
Stephen:
I noticed
