On 2/2/12 12:19 AM, Mark Linimon wrote:
I'd say leave out the following stanza, and also leave out ONLY_FOR/
NOT_FOR_ARCHS:
-.if ${ARCH} == sparc64
-BROKEN= Does not compile on sparc64
-.endif
I don't have a sparc64 tb, and submitter doesn't either, and didn't test
it on sparc64.
I
On 2 Feb 2012 08:28, Michael Scheidell michael.scheid...@secnap.com
wrote:
On 2/2/12 12:19 AM, Mark Linimon wrote:
I'd say leave out the following stanza, and also leave out ONLY_FOR/
NOT_FOR_ARCHS:
-.if ${ARCH} == sparc64
-BROKEN= Does not compile on sparc64
-.endif
I don't have
On Thu, Feb 02, 2012 at 08:38:38AM +, Chris Rees wrote:
We don't build sparc packages, so no Pavmail.
Gee, I sure *thought* I was building sparc64 packages:
$ showrunning | grep sparc64
sparc64-9 20120123043600 harlow.cse.buffalo.edu math/labplot
sparc64-9 20120123043600
On 2/2/12 12:09 PM, Mark Linimon wrote:
On Thu, Feb 02, 2012 at 08:38:38AM +, Chris Rees wrote:
We don't build sparc packages, so no Pavmail.
Gee, I sure *thought* I was building sparc64 packages:
I send out mail whenever I mark things broken, but I don't necessarily
expect anyone to
On 2 Feb 2012 17:09, Mark Linimon lini...@lonesome.com wrote:
On Thu, Feb 02, 2012 at 08:38:38AM +, Chris Rees wrote:
We don't build sparc packages, so no Pavmail.
Gee, I sure *thought* I was building sparc64 packages:
$ showrunning | grep sparc64
sparc64-9 20120123043600
what is todays favorite way of doing this:
(i sent this question to submitter):
I had a question, and just for the logs:
you removed this in the Makefile, but in your fix log, you didn't
mention that you got it to compile on sparc64.
-.if ${ARCH} == sparc64
-BROKEN= Does not compile on
On Wed, Feb 01, 2012 at 11:16:38AM -0500, Michael Scheidell wrote:
The ChangeLog mentioned some sparc64 fixes, so it's worth giving it a
try again, but the port depends on boost-libs now which is marked as
broken on sparc64, so it cannot actually be tested.
So, how do you want me to handle
