Opened 11 years ago

Closed 11 years ago

Last modified 11 years ago

#42706 closed update (fixed)

fgsl: please update to 1.0.0

Reported by: Tom.Schoonjans@… Owned by: tenomoto (Takeshi Enomoto)
Priority: Normal Milestone:
Component: ports Version:
Keywords: Cc:
Port: fgsl

Description

A new version has officially been released. This one uses autotools for the build system so the portfile may need considerable modifications.

Maintainer, can you please take care of this?

Change History (3)

comment:1 Changed 11 years ago by mf2k (Frank Schima)

Cc: takeshi@… removed
Owner: changed from macports-tickets@… to takeshi@…
Version: 2.2.1

comment:2 Changed 11 years ago by tenomoto (Takeshi Enomoto)

Resolution: → fixed
Status: new → closed

Done in r117884.

comment:3 Changed 11 years ago by Tom.Schoonjans@…

Hi,

Thanks for making the update to 1.0.0.

One remark: if I run variants fgsl, I get the following output 

fgsl has the variants:
   dragonegg30: Build using the MacPorts dragonegg 3.0 compiler
     * conflicts with dragonegg31 dragonegg32 dragonegg33 dragonegg34 g95 g95 gcc44 gcc45 gcc46 gcc47 gcc48 gcc49 gfortran
   dragonegg31: Build using the MacPorts dragonegg 3.1 compiler
     * conflicts with dragonegg30 dragonegg32 dragonegg33 dragonegg34 g95 g95 gcc44 gcc45 gcc46 gcc47 gcc48 gcc49 gfortran
   dragonegg32: Build using the MacPorts dragonegg 3.2 compiler
     * conflicts with dragonegg30 dragonegg31 dragonegg33 dragonegg34 g95 g95 gcc44 gcc45 gcc46 gcc47 gcc48 gcc49 gfortran
   dragonegg33: Build using the MacPorts dragonegg 3.3 compiler
     * conflicts with dragonegg30 dragonegg31 dragonegg32 dragonegg34 g95 g95 gcc44 gcc45 gcc46 gcc47 gcc48 gcc49 gfortran
   dragonegg34: Build using the MacPorts dragonegg 3.4 compiler
     * conflicts with dragonegg30 dragonegg31 dragonegg32 dragonegg33 g95 g95 gcc44 gcc45 gcc46 gcc47 gcc48 gcc49 gfortran
   g95: Build using the Fortran compiler from g95 compiler
     * conflicts with dragonegg30 dragonegg31 dragonegg32 dragonegg33 dragonegg34 gcc44 gcc45 gcc46 gcc47 gcc48 gcc49
   gcc44: Build using the MacPorts gcc 4.4 compiler
     * conflicts with dragonegg30 dragonegg31 dragonegg32 dragonegg33 dragonegg34 g95 g95 gcc45 gcc46 gcc47 gcc48 gcc49 gfortran
   gcc45: Build using the MacPorts gcc 4.5 compiler
     * conflicts with dragonegg30 dragonegg31 dragonegg32 dragonegg33 dragonegg34 g95 g95 gcc44 gcc46 gcc47 gcc48 gcc49 gfortran
   gcc46: Build using the MacPorts gcc 4.6 compiler
     * conflicts with dragonegg30 dragonegg31 dragonegg32 dragonegg33 dragonegg34 g95 g95 gcc44 gcc45 gcc47 gcc48 gcc49 gfortran
   gcc47: Build using the MacPorts gcc 4.7 compiler
     * conflicts with dragonegg30 dragonegg31 dragonegg32 dragonegg33 dragonegg34 g95 g95 gcc44 gcc45 gcc46 gcc48 gcc49 gfortran
[+]gcc48: Build using the MacPorts gcc 4.8 compiler
     * conflicts with dragonegg30 dragonegg31 dragonegg32 dragonegg33 dragonegg34 g95 g95 gcc44 gcc45 gcc46 gcc47 gcc49 gfortran
   gcc49: Build using the MacPorts gcc 4.9 compiler
     * conflicts with dragonegg30 dragonegg31 dragonegg32 dragonegg33 dragonegg34 g95 g95 gcc44 gcc45 gcc46 gcc47 gcc48 gfortran

Any thoughts on why g95 pops up twice in each conflicts line? And why is gfortran added to the conflicts: this is no variant.

Cheers

Tom

Note: See TracTickets for help on using tickets.