Summary: | Include tc-has-fortran() in toolchain-funcs.eclass | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Justin Lecher (RETIRED) <jlec> |
Component: | Current packages | Assignee: | Gentoo Toolchain Maintainers <toolchain> |
Status: | RESOLVED OBSOLETE | ||
Severity: | enhancement | ||
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | |||
Bug Blocks: | 339465, 361591, 368719 | ||
Attachments: | tc-has-fortran.check |
Description
Justin Lecher (RETIRED)
![]() Created attachment 272301 [details]
tc-has-fortran.check
tc-has-fortran.check
Any reaction here? the same issue arises for all frontends as they all can be disabled. i dont see how this is something that really needs "fixing". if you want to put pretty user friendly polish on fortran and all of its crazy eccentricities (see also Bug 348964), then perhaps it better you write a fortran eclass of some sort and stick all the crazy you want in there. i dont feel this exploding logic to try and detect user stupidness is appropriate for toolchain-funcs.eclass as it encourages adoption across the tree. Obsolete, now implemented in fortran 2 eclass |