Maneage - Tasks: task #15745, Automatically check if non-C...
You are not allowed to post comments on this tracker with your current authentication level.
task #15745: Automatically check if non-C compilers exist
Submitter: | Mohammad Akhlaghi <makhlaghi> | ||
Submitted: | Sat 08 Aug 2020 05:55:13 PM UTC | ||
Should Start On: | Fri 07 Aug 2020 11:00:00 PM UTC | Should be Finished on: | Fri 07 Aug 2020 11:00:00 PM UTC |
Category: | Software | Priority: | 5 - Normal |
Status: | Postponed | Privacy: | Public |
Percent Complete: | 0% | Assigned to: | None |
Open/Closed: | Open | Effort: | 0.00 |
No files currently attached
Depends on the following items: None found
Items that depend on this one: None found
Carbon-Copy List
There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.
No changes have been made to this item
While building GCC, we also build some other compilers besides the C compiler that we have found are necessary for some high-level software. Currently GCC also builds a C++, Fortran, Objective-C and Objective-C++.
So when Maneage doesn't build GCC itself and relies on the host's compiler, if these compilers don't exist the configuration will fail in the middle and can be very annoying (as reported in bug #58917).
But the manual solution there is really not scalable and can itself cause bugs and annoying situations (for example if a project author forgets to set 'need_gfortran'!).
So we should define a way to use the software building Makefiles to see if special compilers are necessary. This is what occurs to me right now:
For those packages that need non C/C++ compilers, we can add a special prerequisite for that compiler that is also defined during the building of GCC. In this way, with a '--dry-run' run of the 'high-level.mk', we should be able to see if certain compilers are necessary.