cvs commit: ports/lang Makefile ports/lang/ifc8 Makefile distinfo pkg-descr pkg-plist ports/lang/ifc8/files assert_fail.c cxa_atexit.c cxa_finalize.c errno_location.c exclude exclude_noportdocs ld.c linux_file.c linux_stat.c mcount.S ...

Marius Strobl marius at alchemy.franken.de
Tue Jan 20 07:33:01 PST 2004


On Wed, Jan 21, 2004 at 12:05:30AM +0900, Nakata Maho wrote:
> Hi, Alex,
> 
> > It's v8 of Intels Fortran Compiler (ifc). v7 is already in the tree. He
> > follows my leading with icc, but I requested a repo copy of icc to icc7
> > whereas he just added the ifc8 port.
> yes.
> 
> > I suggest to remove the port and let cvs@ do a repo copy of ifc to ifc7.
> No. I would like to wait for several months or so, since ifc8
> is still inmature state. higaki-san reported several defects of ifc8,
> and he don't want to recommend to use as a primary fortran compiler.
> Anyway, ifc8 is not very well tested, and ifc7 is quite tested.

That's also true for ICC 8, port-wise and Intel-wise, though it would be
nice if the IFC ports would follow the scheme that the ICC ports layed out.

> so in the meantime, I don't think we need to do repo copy.

Regardless what naming scheme the IFC ports follow there should have been
a repo copy before IFC 8 was commited.

> 
> > The commit message should also have a note about using copies of large
> > parts of the icc port. I haven't looked at the files yet, but just from
> You are right. we should acknowledge your hard works. I've done
> as forced commit.
> 

Could you please also put this into the files in the FILESDIRs of the IFC
ports that have their origin in the ICC ports and if they are modified that
info, too?



More information about the cvs-all mailing list